Construct3D Privacy Policy

1. What data Construct3D processes

Construct3D processes device and interaction data needed to provide the mixed-reality experience. This may include headset position and orientation, controller or stylus input, and optional hand-tracking input.

Construct3D also uses Meta platform services to verify that the current user is entitled to use the application.

If you choose to save a construction, Construct3D stores the saved construction locally on your device so that you can load it again later.

For collaborative features, Construct3D may process platform and session data needed to identify participants, invite users, join shared sessions, and keep multiple users in the same mixed-reality workspace. This may include Meta user identifiers, Oculus or Meta usernames, joinable-status information, deep-link or destination information, lobby or match session identifiers, and shared scene state such as object ownership, point updates, controller or stylus poses, and other geometry actions needed to synchronize a session.

If voice chat is enabled, Construct3D may request microphone access and process live microphone audio for in-session voice communication between participants.

Construct3D does not create a developer-managed user account system for end users and does not store user-created constructions on a developer-operated cloud service.

Construct3D does not request camera permissions for raw camera-image capture. Mixed-reality passthrough is presented through system capabilities provided by the headset platform.

2. How Construct3D uses this data

• To operate the geometry application, including construction, selection, manipulation, and visualization of geometric objects.
• To support optional hand-tracking interaction when available and enabled.
• To verify app entitlement through Meta platform services.
• To identify participants in collaborative sessions, show who is present, and associate created geometry with the user who created it.
• To support invitations, deep links, joinable sessions, and destination-based session routing through Meta platform features.
• To synchronize shared geometry and interaction state between participants in a live collaborative session.
• To enable optional in-app voice communication between session participants.
• To save and reload constructions locally on the device when the user explicitly uses the save/load features.

3. Service providers and sharing

We do not sell personal data.

We do not upload user-created constructions or geometry work to developer-operated external servers for general cloud storage.

Some platform-related information may be processed by Meta as part of app distribution, entitlement verification, store delivery, invitations, deep-link routing, presence, and platform operation, subject to Meta's own terms and privacy policies.

For remote collaboration features, session and identity data may also be processed by third-party service providers that operate networking or voice infrastructure for Construct3D, such as Epic Online Services, subject to their own terms and privacy policies.

Shared session state is sent to the other participants in a collaboration session so that they can see the same geometry, tools, and interactions in the same workspace.

4. Storage and retention

Saved constructions are stored locally on your device until you delete them, clear the app's local storage, or uninstall the app.

Construct3D is not designed to record, archive, or transcribe in-app voice chat.

We do not maintain developer-controlled cloud copies of saved constructions or developer-managed online user profiles for end users of Construct3D.

If third-party networking or voice providers are used for collaborative sessions, they may temporarily process session-related data needed to deliver those services under their own retention and operational policies.

5. Requesting data deletion

All users may request deletion of any developer-controlled data collected from or about them by contacting: hannes.kaufmann@tuwien.ac.at.

Because Construct3D does not maintain developer-controlled cloud accounts or remote storage for user-created constructions, deleting the app or clearing the app's local storage removes locally stored constructions from your device.

If collaborative features are used, requests concerning Meta platform data or Epic Online Services account or service data may also need to be made through those providers, depending on which system controls the data.

If you contact us to request deletion, we will delete any developer-controlled data we have about you, or confirm that we do not maintain such data.

6. Contact

Hannes Kaufmann
Email: hannes.kaufmann@tuwien.ac.at
Project page: https://www.ims.tuwien.ac.at/projects/construct3d