ORBITRA / DATA USE
Understand where your data goes.
Website visits, booking a meeting, and connecting a customer environment are different data journeys.
The website experience.
The guided demo runs illustrative scenarios in your browser. It does not request customer credentials or connect to identity systems. Restarting or refreshing the demo resets its conversation.
Optional Google Analytics loads only if you accept it, and you can change that choice at any time. The privacy policy lists what it records. No visitor-identification scripts are used.
Booking a conversation.
Booking buttons open Calendly in a new tab. Information you provide there is handled through Calendly and Orbitra’s meeting workflow. Booking a conversation does not authorize access to your organization’s systems.
Do not include passwords, API keys, access tokens, or sensitive customer records in scheduling notes.
Customer-platform data.
Identity information, response records, integration messages, and support material are separate from marketing-site data. Their processing depends on the agreed deployment and the services involved.
The website is hosted on Google infrastructure with application servers in Canada. That does not change where customer-platform data is processed; your deployment and agreement set that out.
Confirm the details for your environment.
- Which information each connection can read or change.
- Where primary records and shared services process that information.
- Which providers receive it and for what purpose.
- Retention, deletion, backup handling, and access controls.
- How your agreement governs customer data and support.
We confirm these details for your deployment in the service documentation and your agreement.