Omniscio — Privacy Policy

DRAFT v2 — pending attorney review. Rewritten to (a) reflect the owner's launch decisions (Omniscio rebrand; US-only launch; voice off by default; team features kept) and (b) correct every accuracy problem the code-grounded red-team found — telemetry is described honestly as always on (no opt-out), all real subprocessors are named, the cost/usage-upload claim is fixed, and the sensitive personal-development data the app stores locally — and, for AI-coaching and journal reflection, sends to Anthropic on your own API key — is now disclosed (§2, §5, §8). Not final legal advice. Re-verify technical specifics against the shipped build at go-live. Bracketed [PLACEHOLDER] items need an owner/attorney decision.

Effective date: [OWNER: publication date — set at launch] Last updated: 2026-08-04

Editorial note — this draft supersedes the earlier one. This is the authoritative, current privacy-policy draft for the launched product (Omniscio LLC). It supersedes the earlier audit-era draft docs/PRIVACY_POLICY.draft.md, which still uses the pre-rebrand "Agent Mission Control" branding and an operator-BYOK controller framing and is retained only as a historical PII/data-flow inventory — do not treat it as the current policy. (The companion docs/DPIA.draft.md already cross-references this policy's §6.)

1. Overview

Omniscio (the "App") is a desktop application published by Omniscio LLC ("the Company," "we," "us"), a North Carolina limited liability company. Omniscio helps you run and manage AI coding agents on your own computer. (Omniscio was previously named "Agent Mission Control.")

Omniscio is local-first by design. Most of your data — your projects, agent sessions, the full text of your conversations, local cost tracking, settings, and any API keys you provide — is stored on your own device and is not uploaded to us. A limited, purpose-specific set of data is handled in the cloud to run accounts, billing, support, opt-in-or-default diagnostics, and the optional team features. This policy explains both.

Where you are. The Services are currently offered only in the United States. This policy is written for US users; if we expand to other regions we will provide region-specific terms.

2. Data stored locally on your device

Stored in a local database (mission-control.db, in your OS application-data folder) and an encrypted local config file, and not sent to the Company except as described in Sections 4–6:

• Sessions and conversations — your agent sessions and full message history (prompts, agent responses, system messages, attachments).
• Projects — names and local folder paths.
• Costs and usage (local) — per-session AI cost/token estimates and a local cost log (see Section 6 for what leaves the device).
• Automations, schedules, saved prompts.
• Channels/integrations you connect (e.g., SMS, Slack, Telegram, RSS, webhooks, email) — their message history and config.
• Notes/knowledge, settings, and credentials (Section 3).
• Personal-development data (only if you use those features) — the optional AI-coaching, journal/reflection, and self-assessment ("Life Inventory") features store the notes, ratings, and generated insight/profile text you create. This can include psychological, emotional, and health-adjacent information about you, and is kept locally on your device. The AI-coaching and journal-reflection features additionally send the relevant text to Anthropic to generate insights — on your own Anthropic API key (the same key your coding agent uses; if you have no API key set, those AI features don't run). Life Inventory is computed on your device with no AI call. (See Sections 5 and 8.)
• Local logs — diagnostic logs for troubleshooting; not sent to us unless diagnostics are on (Section 6) or you send a report.

You can delete local data in the App and remove the App's data folder.

3. Credentials and API keys (verified)

• API keys and OAuth tokens you provide are stored locally and encrypted at rest using your OS secure storage (Windows DPAPI / macOS Keychain / Linux libsecret), with an encryption marker on the stored value.
• They are decrypted only in the App's main process to make the requests you direct; they are stripped before reaching the App's interface layer and are not uploaded to the Company's servers.
• BYOK keys are used solely to authenticate the requests you initiate to that provider, and (when you ask the App to validate a key) are sent directly to that provider, never to a Company server.

4. Data we handle in the cloud

When you use features that need our backend (Google Firebase / Google Cloud), we process a limited set of data:

• Account and identity — user ID, email, plan/tier, and (for team features) organization and role.
• Billing and AI-credit metering — a billing/credit record (balance and holds), an append-only usage/metering ledger of AI requests routed through our gateway, a hashed key identifying your gateway access, and a Stripe customer identifier. Card/payment details are handled by Stripe, not stored by us.
• Identified usage and spend aggregates — for signed-in users, we upload daily aggregates of AI spend and usage (e.g., daily spend in USD, sessions started, active minutes, top features), keyed to your account. These are identified, not anonymous. (This corrects any impression that nothing derived from your local cost data leaves the device — the raw local cost log stays local, but these daily aggregates are uploaded.)
• Support and feedback — if you contact support or submit a bug report/feedback, we receive the content plus limited diagnostics; a single bug report may be copied to several processors listed in Section 5.
• Team/collaboration features (enabled by you) — Team Chat messages, reactions, and shared-artifact ("Shares") content and comments are stored in the cloud for real-time collaboration. Note: a shared artifact's visibility can be private, unlisted (accessible to anyone with the link), or public, and comment threads may be readable by other signed-in users of the Service. Choose visibility accordingly.
• Inbound email and support storage — if you use agent-email or support chat, inbound email bodies and support/helpdesk conversations are stored server-side (see retention in Section 9).

We do not upload your local session history or project code as part of normal operation.

Where your data is processed (data residency). The cloud data described above is processed and stored in the United States. Our backend — Google Firebase / Firestore / Cloud Storage / Cloud Functions — runs in a US region (us-central1, Iowa), and crash/error reports go to Sentry's US region. Mobile push notifications are delivered through Google Firebase Cloud Messaging (FCM), a global Google service, so notification content (such as a session name or message subject) transfers to Google's infrastructure. The Services are offered only in the US (Section 1); we do not currently operate EU/UK regions or rely on Standard Contractual Clauses (SCCs) for cross-border transfers. If you access the App from outside the US, you understand your data is transferred to and processed in the US.

[FOR COUNSEL — cross-border transfer (Schrems II): the current posture relies on US-only distribution rather than a transfer mechanism. If distribution is ever extended to EU/UK data subjects, establish a lawful transfer mechanism (SCCs / UK IDTA / an adequacy decision) or pin an in-region deployment before doing so. See DPIA risk R5.]

Cookies (functional only). If you use the optional web-access feature (pairing a phone or browser to the App over your local network), the App's local server sets a single strictly-necessary functional cookie — amc_web_token (HttpOnly, SameSite=Lax) — so your paired browser stays signed in across page loads. Its value is your session access token, not a tracking, analytics, advertising, or cross-site identifier, so it is exempt from cookie-consent requirements as a strictly-necessary cookie (it is set as soon as you sign in to that feature, before any banner). We set no advertising or third-party tracking cookies.

5. Third parties and subprocessors

We use the following. Core services run the Services; optional ones receive data only if you enable the relevant feature.

Core subprocessors

Optional / secondary (only when you enable them)

• AI sign-in / OAuth provider — authenticates your Claude/Anthropic account.

• Other AI providers you configure (e.g., OpenAI/Codex, Google Gemini, DeepSeek, Moonshot/Kimi, Zhipu/GLM, MiniMax, xAI, OpenRouter, and other coding-agent engines you select) — receive your prompts/context when you use them, on your own API key, under their terms.

• Channel integrations you connect — receive data only for the integrations you enable, each a direct connection to your own account. These include Pushbullet (SMS gateway — receives SMS/MMS content and synced contact info), messaging platforms (Slack, Telegram), and meeting, content & automation tools (Granola, Fathom, Canva, Zapier), plus the email/calendar accounts you link.

• Board / project-management integrations you connect (e.g., Trello, Jira, Notion, Linear, ClickUp, Airtable, Asana) — when you sync a board, member names/emails and card content are exchanged with that service on your own account/key, under their terms.

• Bank sync (the Coffer feature, via a SimpleFIN bridge) — if you connect a bank, a credentialed request plus your bank account balances and transaction history are exchanged with the SimpleFIN bridge you configure (self-hosted or a third-party-hosted bridge), on your own bridge subscription under its terms.

• Contact/company enrichment (only when a contact or company card is enriched) — an email address is sent to Gravatar to resolve a profile image, and a company domain to Clearbit to fetch a logo.

• SMS GIF search (Klipy) — if you insert a GIF in the SMS composer, your typed GIF search terms are sent to Klipy; it uses a Company-held default key unless you set your own.

• Web-access and data tools (Firecrawl, Apify, X/Twitter) — when you use a built-in web-scraping, data-extraction, or read-only tweet/user-search feature, the URLs, queries, or page content you request are routed through our gateway on Company-held keys.

• Bundled AI providers (OpenAI, Google Gemini, Perplexity) — an off-by-default "bundled API keys" feature lets your agent call these providers through our gateway on Company-held keys. OpenAI is available today; Gemini and Perplexity are pre-integrated but not yet active, and will be moved to the Core list before that path is enabled.

• Team-chat voice/video calls (LiveKit) — an in-development feature not yet reachable in shipped builds; when it ships, realtime call audio/video will route through LiveKit Cloud on a Company-minted access token, and LiveKit will be added to the Core list before that path is enabled.

• Screen capture & "Snip to Text" — if you use the on-demand snip/OCR feature, the screen region you capture is sent as an image to Anthropic (Claude Vision, for text extraction) and, for an AI-generated snip title, to OpenRouter — only when you explicitly trigger it. An image cannot be automatically redacted, so anything visible in the region you capture (including other people's data) is sent as-is; avoid capturing sensitive on-screen content.

• Meeting transcription — if you turn on meeting transcription, audio of the meeting — which can include other participants — is streamed to a speech-to-text provider (e.g., Deepgram) on your own provider key to produce a transcript (in shipped builds; otherwise the feature stays notes-only), and attendee names may be stored in your local notes. You are responsible for any notice or consent your jurisdiction requires from other participants on the call.

• Voice features (off by default) — if you turn on voice, speech-to-text streams your microphone audio to the provider you select (Deepgram, ElevenLabs, or Groq) on your own key; text-to-speech sends the response text to Fish Audio by default through a Company-funded relay (Fish Audio is a Company subprocessor for this path), or to xAI Grok / ElevenLabs / Speechify / Pika on your own key.

Voice is OFF by default. Speech-to-text and text-to-speech are turned off out of the box; unless you turn them on in Settings, no microphone audio or voice data leaves your device. If you enable voice, audio and voice data are sent to the providers listed above — which can be sensitive personal information (see Section 8).

[OWNER/ATTORNEY — keep this list authoritative.] The complete factual inventory of every external destination that user or contact data can reach (each with its data category and code call-site) is maintained internally in docs/SUBPROCESSORS.md, which holds the authoritative current count. Keep this §5 reconciled with that inventory and with the customer-facing Subprocessors page, and update all three before adding any new processor. Destinations reached only on your own key/account (the "Optional / secondary" items above) are your direct providers under their own terms; the Core table lists those the Company operates under its own accounts.

6. Diagnostics and product telemetry (always on)

Omniscio collects diagnostic and product-usage data to keep the App reliable. This collection is always on — there is no setting that turns it off. The disclosure here is how we keep it honest, not a promise you can disable it. The one related control is "Auto-Email Crash Reports," which gates only whether a crash report is additionally emailed to us; it does not stop crash capture (Sentry) or usage telemetry.

When it starts. This diagnostic collection begins when the App first launches — before, and independent of, any sign-in or Terms-acceptance step. Some fleet-health signals (for example, an install/first-run event, aggregate error/crash reports, and the diagnostic digests) can be sent before you sign in or accept these terms. Because the collection is mandatory, not consent-based, accepting the Terms and this Policy is how you are informed of it — it is not an on/off choice.

• What we collect: app version, operating system/platform, OS version, CPU architecture and core count, a coarse total-memory figure (rounded to whole gigabytes, never an exact size), feature-usage counts, crash/error reports, and the identified daily spend/usage aggregates described in Section 4. This also includes two typed-text streams — the text you type into Settings search and the questions you ask the in-app help / Ask-Omniscio assistant. Both are scrubbed of credentials and file paths and keyed only to a random install identifier (never your name, account, or a session). The Settings-search term is reduced to a short scrubbed snippet. The full text of your Ask-Omniscio help question is collected (scrubbed of credentials and file paths, bounded to about 2,000 characters), so we can understand and fix the problems people are actually having — a help question can therefore include personal details you type into it, so treat it like a support message.
• Reduction and encryption: reports are automatically processed to reduce personal identifiers — we attempt to remove usernames, file paths, and message content, and error messages are truncated. This reduction is best-effort, not a guarantee that every identifier is removed (identifiers embedded in free-text error strings may remain). Our fleet-diagnostic payloads (sent to our diagnostics endpoint) are encrypted on your device before they leave it. Our crash-report and weekly-digest emails are sent over TLS (encrypted in transit) but their bodies are not additionally encrypted; in those emails the subject line carries only a shortened, hashed hostname token, while the full device hostname remains in the email body (so reports from different machines can be told apart).
• What we don't do: we do not read your code or the content of your agent conversations for telemetry, and we do not sell this data.

[FOR COUNSEL — lawful-basis review: always-on collection with no opt-out (usage telemetry + crash capture), including the typed Settings-search and help-question text, needs a lawful-basis review for each target jurisdiction, or a restriction of distribution scope. See DPIA risk R6.]

7. How we use data

To provide, operate, and secure the Services; authenticate you; process payments and operate the AI-credit allowance; prevent abuse/fraud of credits; provide support; diagnose and improve reliability and features; and comply with legal obligations. We do not sell personal information and do not use your prompts, code, or conversations to train the Company's own models.

8. Your California privacy rights (CCPA/CPRA)

California residents have rights to know, access, correct, and delete personal information, and to data portability, subject to exceptions. We do not sell or share your personal information (including "sharing" for cross-context behavioral advertising as defined by the CPRA).

Categories of personal information (Notice at Collection):

[FOR COUNSEL — financial-data category vs. coffer (F117 / RT-F040): the Payment/financial row above is scoped to payment-card details handled by Stripe and asserts nothing financial is "stored by us." The coffer feature (currently in-development / default-hidden, gated behind cofferEnabled / AMC_SHOW_COFFER=1) stores STRUCTURED local financial data on the user's own device — bank balances, a transaction ledger, payee names, and SimpleFIN provider account ids — a distinct, more-sensitive category than payment-card-via-Stripe. Before coffer ships enabled, broaden this category description (or add a row) to disclose the local-finance data, and add the corresponding entry to the SUBPROCESSORS list / PII inventory. Nuance for counsel: coffer data is local-first and the operator may be its own controller — a policy-copy judgment, not asserted here.]**

• Sensitive personal information: we collect voice/biometric data only if you turn on voice features (off by default). If you do, you have the CPRA right to limit the use of sensitive personal information — exercise it by turning voice off in Settings (which stops any further voice data) or by emailing legal@omniscio.com. We use voice data solely to provide the voice features you enabled — never to infer characteristics about you, and never sold or shared.
• Personal-development features (AI-coaching, journal, Life Inventory): if you use these optional features, they can hold psychological, emotional, and health-adjacent information you record about yourself. This data is stored locally on your device. The AI-coaching and journal-reflection features additionally send the relevant text to Anthropic on your own Anthropic API key to generate insights (if you have no API key set, those AI features don't run); Life Inventory is computed on your device with no AI call. You can delete this data in each feature's own screen; note that the App's "erase all local data" function does not remove these personal-development stores, and the AI-coaching and Life-Inventory features also write files under your ~/Claude folder (separate from the App's data folder) — remove those directly if you want them gone. Because these features use your own API key, the Company does not receive this data, and we do not use it to train the Company's own models (Anthropic processes it under your own Anthropic account's terms). You have the CPRA right to limit its use — turn the feature off, delete the data, or email legal@omniscio.com. [FOR COUNSEL — confirm the sensitive-PI treatment / right-to-limit and the consent basis; these local stores are retained until you delete them (the synthesized coaching profile, journal entries, and Life-Inventory results are not auto-expired) and are EXCLUDED from the App's unified erase-all — PII_INVENTORY F119 / F125 / F131; DELETION_PROPAGATION_MAP.]
• Screen captures and meeting audio: the optional Snip-to-Text and meeting-transcription features can capture sensitive on-screen content or the voices of other people on a call. They run only when you enable or trigger them, and captured images are sent to an AI provider unredacted (an image cannot be scrubbed). [FOR COUNSEL — the multi-party-consent basis for meeting-audio capture, and the un-redactable image egress for screen captures (SUBPROCESSORS.md rows 1/2/11; PII_INVENTORY meeting-consent notes) — confirm the disclosure and any two-party-consent-state posture.]
• How to exercise your rights: email legal@omniscio.com. We will verify your request against your account information and respond within 45 days (extendable once by 45 days if reasonably necessary, with notice). We will not discriminate against you for exercising these rights.

(Other US state privacy laws may apply as we grow; we will honor applicable rights.)

9. Data retention

[ATTORNEY — confirm these periods are defensible; reconcile the 24-month aggregate limit and the others with the actual TTLs configured in the build.]

10. Security

We use technical and organizational safeguards: encryption of credentials at rest on your device (OS secure storage), encryption in transit (HTTPS/TLS), encryption of diagnostic payloads before egress, and access controls on our backend. No system is perfectly secure.

At-rest posture for your local data. Your local database (mission-control.db) and any saved user attachments are not application-encrypted by default; they rely on your operating system's full-disk encryption (e.g., BitLocker / FileVault / LUKS) as the compensating control, together with OS file-system permissions. An optional database-encryption feature can be enabled for defense-in-depth. (Credentials and API keys are separately encrypted at rest as described above.)

Breach notification. If a breach affects your personal information, we will notify you and the appropriate authorities without undue delay and within any timeframe required by applicable law. We maintain an internal incident-response process (detect → contain → assess scope → notify affected users and regulators as required → remediate → document). (We deliberately do not commit to a single fixed number of days here, because US state breach-notification deadlines vary; "as required by law" covers the strictest applicable one.)

11. Data-processing addendum (business/team customers)

If you use Omniscio on behalf of an organization and we process personal data on your behalf through the team features, a data-processing addendum (DPA) governs that processing and lists our subprocessors. A DPA is available on request for business/organization customers — contact us at the address in Section 13. We are putting data-processing agreements in place with the subprocessors listed in Section 5: agreements are in effect with our core platform processors (Google Cloud / Firebase, Sentry, and Resend), and we are securing or confirming them for the remaining subprocessors. We maintain an internal data-processing register that records the current DPA status for each subprocessor, and we publish the current list on our Subprocessors page.

[FOR COUNSEL — subprocessor DPA coverage: this statement was corrected to match the internal DPA register (07-dpa-register.md), which currently records DPAs in effect for Google Cloud/Firebase, Sentry, and Resend; a gap for AgentMail; pending verification for Cloudflare and ErrPort; and deferred/reconcile status for Stripe and the helper-AI gateway vendors. Close the outstanding gaps (or narrow the §5 list) before publication so §11 and the register stay consistent.**]

12. Children's privacy

The Services are not directed to children under 18, and we do not knowingly collect their data.

[FOR COUNSEL — incidental third-party minors (RT-F039): the clause above addresses the operator (the account holder). But the product's primary PII subject matter is inbound THIRD-PARTY contact data — the people who SMS, email, Slack, or Telegram the operator — and any of those senders could be a minor, with their message content + identity stored and potentially sent to LLM / voice vendors. The app has no age signal and no minor-detection on inbound sender PII. This is likely a defensible starting position (US-only distribution + not-directed posture), but it is a counsel judgment: note the incidental-third-party-minor exposure for review, parallel to the incidental special-category-data position taken elsewhere in the DPIA / draft policy.]**

13. Contact

Privacy questions or requests: legal@omniscio.com, Omniscio LLC, 5301 Terminal St, Charlotte, NC 28208.

14. Changes

We may update this policy; material changes are indicated by the "Last updated" date and, where appropriate, additional notice. Continued use after changes take effect is acceptance.

DRAFT v2 — pending attorney review. Not final legal advice. Technical details reflect the codebase as read during drafting and must be re-verified at go-live.