What data Vox Ordo processes, why, where it lives, who our subprocessors are, how we secure it, and how long we keep it. This is Part B of the Terms of Service & Privacy Policy Agreement.
Vox Ordo is local-first by design. Your dictation and screen-context (Lumen) data lives on your own disk, not our servers. Disk access and computer control are off by default, and server-side features only ever run on data you explicitly connect.
What we collect, why, and where it lives.
| Data | Why & where it lives |
|---|---|
| Your code (the Mirror) | A server-side working copy of repositories you connect, so Aria can work while your laptop is closed. Ingest is read-only and non-destructive — your local files are never modified by ingest, secrets and large/binary dirs are excluded, and changes sync back only with your approval, with backups, never deleting your files. |
| Calls & transcripts | Calls with Aria are recorded; we store the audio, transcript, and summary. You consent to recording when you use the voice line. Spoken security codes/PINs are automatically scrubbed and never stored. |
| Memory & context | Per-account memory and context summaries to make Aria useful across sessions. Web chat-turn storage is opt-in. |
| Screen & dictation context (Lumen) | Stored locally on your own device (sovereign, local-first). Not sent to our servers unless you explicitly connect it to your runner. |
| Disk access (if enabled) | On a call you may grant Aria read-only access to listed folders — gated by your TOTP code, restricted to an allow-list, secrets redacted, and every access logged. |
| Computer control (if enabled) | Aria can view your screen and control your cursor/keyboard only after a one-time OS permission and a per-call PIN; it turns off automatically when the call ends. |
| Automated communications | With your configuration, Aria may draft and (when you approve) send email or messages on your behalf. |
| Account & billing data | Email, plan, usage ledgers, and payment records. Card data is held by Stripe, not us. |
We share data with the following providers to deliver the Service:
| Subprocessor | Purpose |
|---|---|
| Anthropic | LLM / model inference |
| ElevenLabs | Voice & call recording |
| Twilio | Telephony / SMS |
| Stripe | Payments (holds card data) |
| Resend | Email delivery |
| Hosting provider | Server infrastructure |
A current list is maintained on request; business customers may request a DPA.
If you choose to connect your Google account, Vox Ordo requests the following scopes and uses them only as described:
gmail.readonly — your agent lists and reads messages in your Gmail, at your request, to answer you and to maintain your own day context.
gmail.send — your agent sends email from your address only when you tell it to.
calendar — your agent lists your events and creates events you ask for.
Vox Ordo's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used only to provide the features above to you; it is never sold, never used for advertising, never used to train models, and never read by humans except with your explicit permission for support, for security investigation, or where the law requires. You can disconnect Google at any time from your workspace settings or at myaccount.google.com/permissions; on disconnect we delete stored Google tokens, and cached Google data is removed within 30 days in line with our retention policy.
We protect your data with:
Changed 2026-06-27: an earlier version of this policy said we did not encrypt data at rest. That is no longer true — customer data, call recordings and backups are held on an encrypted volume. We would rather show you the change than quietly revise it.
Default retention is 30 days. You choose your own retention window; there is a hard maximum of 6 months — we don't hold your data longer than that.
When data reaches the end of your retention window it is archived — soft-deleted and recoverable, never hard-deleted — and we give notice before any wipe.
You may export your data (/account/export) or request deletion at any time. We honor deletion requests within 30 days, subject to legal and billing retention obligations. We aim to align with GDPR/CCPA.
— retention reflects the policy Ian locked 2026-07-05 (default 30 · manual 7/30/90/180 · hard max 6 months · archive-not-delete) and supersedes the older clickwrap language ("24-month call retention / 30-day post-cancel"). Confirm this is the policy that binds users at launch.
You may export your data, request deletion, change your retention window, or ask for our current subprocessor list at any time. Business customers may request a DPA. Contact us at privacy@voxordo.io.
This Privacy Policy is Part B of the single Vox Ordo Agreement; see the full Terms of Service & Privacy Policy for the Terms of Service (Part A) and Acceptable Use Policy (Part C).
Vox Ordo by InSync Tech uses SMS to reply to conversations you start with your assistant, to deliver account and onboarding notifications, and to send summaries or reminders you request. When you opt in to text messaging we collect your mobile phone number, your opt-in consent record (date, time, and method of consent), and the content of the messages you exchange with the Service.
No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. All the categories of information described in this Privacy Policy exclude text messaging originator opt-in data and consent; this information will not be shared with, or sold to, any third parties for any purpose. Message content and phone numbers are shared only with our SMS delivery subprocessor (Twilio) as necessary to deliver the messages you asked for.
You can opt out of text messages at any time by replying STOP to any message. After you opt out you will receive one final confirmation message and nothing further. Reply HELP for assistance, or contact us at support@voxordo.io. Message and data rates may apply; message frequency varies based on your use of the Service.