Omniscio

Omniscio — Privacy Policy

Effective date: 2026-08-20 Last updated: 2026-11-16


Key terms at a glance

Plain-English summary — not a substitute for the full Privacy Policy. This box is a quick, friendly overview of the points people ask about most. It is not legal language and does not replace the numbered sections below, which are the Policy that actually applies. If anything here seems to differ from those sections, the full sections control.


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 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, except an own DeepSeek or DeepInfra key you save for cloud sessions, which is also kept encrypted on our server while it is saved and withdrawn when you remove it (see §3). A limited, purpose-specific set of data is handled in the cloud to run accounts, billing, support, always-on diagnostics, the optional team features, and the optional (end-to-end encrypted) Cross-Device Sync. 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), a local config file (the credentials and connected-account identities in it are encrypted; the rest of the file is not), and data files in that folder, and not sent to the Company except as described in Sections 4–6:

Some operational data also lives outside that folder. If you use the App's built-in developer tooling (the dev pipeline / cloud test offload — see §4), it writes to a folder called .amc in your user home directory: branch names, run history, job ledgers, and the App's local access token. That folder is not inside the application-data folder, so removing one does not remove the other.

To delete your local data: delete it in the App, remove the App's data folder, and remove the .amc folder in your home directory if it exists. If you moved the screen recorder's folder to another location, or exported recordings to another folder, delete those copies there too — removing the App's data folder does not reach them. If a session ran in an isolated working copy, the App kept a full copy of that project in a working-folders folder — beside the project, or in the folder you chose for it — with its own dependencies; remove those folders too, because removing the App's data folder does not reach them. One record inside that folder outlives an in-App deletion or "erase all local data": the cost/spend ledger for money already spent, which is kept as a billing record until the data folder itself is removed (Section 9).

3. Credentials and API keys (verified)

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:

We do not upload your local session history or project code as part of using the App — unless you turn on Cross-Device Sync, which uploads an end-to-end encrypted copy as described above. Separately, the built-in AI helpers listed in Section 5 — such as the daily digest, Tasks if you turn it on, and Omni in Mission Control, which reads board items, comments, documents, sheets and answers people submit on a form — send the parts of a session they work on to an AI provider, and for Omni that includes other people's names and comments, sometimes through our gateway.

One exception, and it is not part of the App you install. The Company's own repository ships a developer tool ("cloud test offload") that our engineers can run to execute a build or test suite on Company machines instead of their own. When a developer explicitly turns it on, it uploads a bundle of the code in their working folder — including files they have not committed — plus the name and email recorded on each commit, to a Company-owned Google Cloud Storage bucket in the United States, where Company-owned worker machines unpack and run it. Bundles are deleted on a 7-day schedule and run logs on a 14-day one.

A second exception, of the same kind, is the master sync. The same source repository ships a contributor tool ("master sync") that reconciles a developer's checkout with the team's shared branch. It is off by default and, like cloud test offload, runs only from a source checkout — never from an installation you download. When it cannot settle a conflict on its own it spawns paid coding-agent sessions — a coordinator and workers — that read, edit and commit the conflicting files in the contributor's checkout. By default those sessions run on the contributor's own default coding engine; the tool's own settings (masterSyncProvider and the two model settings beside it) move the whole sync to another engine, and a provider set there that the spawn refuses falls back to that default engine. The conflict payload goes to whichever engine the sync runs on — if that is DeepSeek, our gateway sends each request to DeepSeek itself first, which is China-hosted, and fails over to DeepInfra in the United States. The request is metered on a Company-held gateway key when a contributor's developer model subsidy is enrolled, and otherwise on the contributor's own key for that engine.

This is called out here for completeness and honesty, not because it affects you: both tools live only in the Company's source repository and are not included in the application you download and install, so no customer installation can reach either. The people whose code and identity they handle are the Company's own contributors, working on the Company's own code. (The rest of the DeepSeek footprint — the Company-key lanes, and the coding engines a customer chooses for themselves — is in Section 5. The built-in helper features never use DeepSeek.)

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 the United States on Google Cloud: Firestore and file storage are in us-east1 (South Carolina), and processing (Cloud Functions) and backups are in us-central1 (Iowa), with some backup storage in a US multi-region. Crash/error reports go to Sentry's US region. Shared video recordings are the one exception: when a Share carries a video (a screen recording, a capture project, or a feedback video), the mp4 is stored in Cloudflare R2 (the same provider already used for the agent-email relay — see Section 5), in Cloudflare R2's Eastern North America (ENAM) region. That region is Cloudflare's placement for the bucket rather than a contractual commitment, so we do not promise that a shared recording is stored in the United States. Mobile push notifications are delivered through Google Firebase Cloud Messaging (FCM), a global Google service, and, on Apple devices, Apple's push service, so notification content transfers to that provider's infrastructure. Content-free notifications are on by default, so a phone notification carries only a generic title and a reference to the item. If you turn them off, a paired phone's notifications can carry an SMS sender's name and phone number, a preview of the SMS text, and an email subject. If you access the App from outside the US, you understand your data is transferred to and processed in the US. Cloud test offload (the first of the two developer tools described in Section 4) is US-only too: its storage bucket and worker machines run in us-central1 (Iowa), so a contributor's code snapshot and the name/email recorded on their commits are processed in the United States. Master sync (the second) follows the engine it runs on: on a non-US engine such as DeepSeek a conflict payload can leave the United States, as Section 4 describes. Some AI and voice vendors are also outside the US, as the next paragraph explains.

Some AI vendors are outside the US. Being offered only in the US bounds where our customers are; it does not bound where a vendor is. A small number of the helper-AI and voice vendors in Section 5 process content outside the United States on Company-held keys — most notably CrofAI (China; a retired coding lane, existing sessions only), DeepSeek (China), Zhipu/GLM and Moonshot/Kimi / MiniMax (China), Fish Audio (China-founded; the default read-aloud relay), the Alibaba-operated model upstream some OpenRouter requests are served by, and SiliconFlow (China), one of the hosts OpenRouter can pick for the Gemma 4 model when you choose it for Instant Fix. The published Subprocessors page lists each one under "Where processing happens" with what it receives and when. None of them receives Google user data through the DeepSeek lane: that lane is switched off whenever a Google account is connected (see §15). We do not currently operate EU/UK regions or rely on Standard Contractual Clauses (SCCs) for those transfers.

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 two strictly-necessary functional cookies. omniscio_web_token (HttpOnly, SameSite=Lax) keeps your paired browser signed in across page loads — its value is your session access token. omniscio_device_id (HttpOnly, SameSite=Lax, Max-Age of 400 days) is a persistent, server-assigned random device identifier: the App mints one for a browser that has not paired before, so it can tell your paired devices apart, show you which ones are paired, and let you sign an individual device out. Neither cookie is a tracking, analytics, advertising, or cross-site identifier, so both are exempt from cookie-consent requirements as strictly-necessary cookies (each is set as soon as you sign in to that feature, before any banner), and both are first-party — shared with no third party. Clearing omniscio_device_id through your browser's settings simply makes that browser look like a new device the next time you pair it. The App sets no advertising or third-party tracking cookies. Our public websites (omniscio.com and docs.omniscio.com) separately use Google Analytics to understand site traffic (and, when we advertise, the Meta and Google Ads conversion tags described in Section 4), loaded behind a consent banner — including these legal pages, whichever of our two sites you open them on. The consent gate itself loads on every page of both sites that carries analytics (the help library, the /welcome page and the account-email link page carry neither), but the Google Analytics script is fetched only once your choice permits analytics — so a visitor who has not accepted downloads no analytics script at all, and Google Analytics receives your IP address, user-agent and the page URL only from that point. No visitor is opted in by default: in every time zone, Google Consent Mode holds analytics and advertising storage denied until you accept, and no analytics or advertising cookie is set until you accept. See our Cookie Notice for details and opt-out options.

Website A/B tests (first-party). When we test two versions of a page on omniscio.com, you see one version for your browser session. Until you press Accept on the cookie banner, that is all: the version is kept in your browser's session storage (cleared when you close the tab), no identifier is created, and nothing about the test is sent to us. If you press Accept on the banner that names it, your browser's local storage then keeps which version you were shown (omniscio-exp) and a random anonymous visitor ID (amc-anon-id), so you see the same version each visit; our own server records, without cookies or any third party, that this anonymous ID saw that version and, if you click a download link, which version your browser was in (the download click does not carry the ID). If you then sign in to the App with Google or GitHub, the sign-in tab opens omniscio.com/welcome, which links the version you saw to your new account once, so we can tell which version led to sign-ups; that link is made only if you pressed Accept. We never collect your name or email through the website for this. You can withdraw at any time - press Decline on the omniscio.com banner, use the "Do Not Sell or Share" link, or turn on Global Privacy Control - and the visitor ID, the stored version and the first-view marker are deleted from your browser immediately, nothing further is recorded, and the opt-in has to be given again to resume; records we already hold can no longer be linked to your browser; the same happens if you change your choice in another tab. Your answer covers both sites — it is remembered in a cookie scoped to omniscio.com as well as in this browser's local storage — while the A/B version and ID stay in this browser on omniscio.com. A choice made on an earlier banner that did not mention the visitor ID does not count as consent to it; if you accepted analytics on that banner, the banner asks you once more about the visitor ID only, and your analytics choice is not changed by your answer. Anonymous first-view records are deleted after about 400 days.

5. Third parties and subprocessors

We use the following. Core services run the Services; optional and secondary ones receive data only when you use the feature they serve, except the few whose entry says they run by default.

Core subprocessors

Provider Purpose Data involved
Anthropic (Claude) Default AI provider powering agent sessions, and the fallback route for the screen recorder's automatic summaries. If you set up an AI bot that answers in a Team Chat channel, the messages it answers also become that session's prompt — including other members' messages. The optional personal-development features (AI-coaching, journal reflection) also call Anthropic to generate insights — normally on your own Anthropic API key (the same key the agent uses), though a key already stored in the App, including a Company-held key on a plan that includes AI credits, can fund those calls instead. Mission Control's What Next also asks Anthropic for Claude through our gateway, on your own Anthropic key or on a Company-held one — its answer, the lookups behind it, and its deeper look, which uses a more capable Claude model. Your prompts, code, file contents, conversation context, and attachments — sent when you run an agent (directly or via our gateway) — plus, for the personal-development features, the coaching/journal text those insight calls process (on your own key, or on a stored / Company-held key when one funds the call). What Next sends the question, the board context, and the matching snippets from each source that person has connected and allowed — email, calendar, Team Chat, board items, GitHub, Jira, Linear, Asana, ClickUp, Notion, OneDrive, Dropbox, plugins, Vault notes, Google Docs and meetings. For a Team Chat AI bot, the triggering message, the surrounding channel messages and the attachment file names are sent; member display names are replaced with pseudonyms and guest messages are excluded, but the message text itself and the file names are not removed.
Google — Firebase / Google Cloud Authentication, database (Firestore), cloud functions, hosting, our AI gateway (Cloud Run), secret storage — and, on the Gemini engine, the live speech-to-text for dictation — and bot protection (reCAPTCHA, through Firebase App Check) on the public pages of the Forms plugin Account/identity, billing/metering, aggregates, support, diagnostics, and team data described above. For dictation, the live microphone audio of what you dictate (see the FlowVoice row). On a public form, the visitor's IP address and browser signals.
Stripe, Inc. Payment processing and US sales-tax calculation Payment method and billing details (held by Stripe); the Company receives a customer identifier and subscription status.
Sentry Application crash/error reporting Crash/error reports with scrubbed messages (see Section 6).
Resend Transactional email delivery (bug reports, digests, notifications) and product activation / marketing email (the onboarding drip) The email content the App sends (e.g., your bug report and diagnostics); for activation/marketing messages, your email address and the message content.
SMTP2GO Transactional email sent by our self-hosted backend apps — account invitations and password resets The recipient's email address, the message subject and body, and any attachment. That recipient can be an invitee you invited, who is not a user of the Services at all.
Twilio SendGrid Transactional email for the Calendar Scheduler booking feature — booking confirmations, approval requests, reminders, and cancellation / reschedule notices The invitee's email address, their name, and the booking details carried in the message, including anything they typed into the notes or the host's own questions.
Cloudflare Agent-email relay (inbound/outbound) and its outbound send leg; transactional notices (account security and sign-in location, account deletion, tier changes, invitations) sent through Cloudflare's Email Sending API; storage of shared video recordings in Cloudflare R2; and bot protection (Turnstile) on public forms Email routed through the agent-email feature (sender, recipient, subject, body and attachments); the recipient and content of the account notices above; the mp4 of every video Share — screen content plus microphone and system audio, and, when the camera overlay is used, the webcam video of you and anyone in frame composited into that same mp4 (held in Cloudflare R2's Eastern North America (ENAM) region — a placement Cloudflare applies to the bucket, not a residency guarantee); and, on a public form, your IP address and browser signals.
OpenRouter, Moonshot/Kimi, Zhipu/GLM, MiniMax, Meta (Muse), Qwen (via our AI gateway, on Company-held keys; OpenAI models are reached through OpenRouter) Cost-efficient "helper" AI models for built-in features — inbound agent-email pre-screening/classification (OpenRouter, on google/gemini-2.5-flash-lite), session-title generation, session summaries and daily digests, screen-recording summaries and chapters, Plain Speak rewrites, contact-name inference, Team Chat AI (a channel summary built from up to that channel's newest 100 messages, and @mc answers from the boards a channel's members share — both carrying other channel members' message text), Supermail AI email filtering + "Catch me up" thread summaries, and Inbox Pilot (which reads the recent turns of an agent session to decide whether it needs your attention, and — when you have it drafting replies — writes the suggested reply), Omni and Mission Control AI helpers (form-answer triage, document and spreadsheet reading, item progress checks, advice, break-downs, board reports and the advisor quick question, which send board item names and columns including people columns, comments, teammates' names, document and spreadsheet text, and form answers from people who may not use Omniscio), and Tasks AI planning — ranking what to do right now, the daily check-in and its chat, Plan my day, the Break it down interview, the arrange pass, Plan chat, the session-end learnings distill, and the session-end catch scan (watching finished sessions for follow-up tasks) The prompt/message content those helper features process, routed through our gateway on Company-held keys. (OpenRouter is the helper provider; the OpenAI models it uses are served through it.) The built-in helper features never use DeepSeek, on any key, including a DeepSeek key of your own. Tasks AI planning asks for the OpenRouter helper lane but is not guaranteed to reach it: the App's key order decides which key pays and which vendor receives the request — an AI key you have saved, then Omniscio credits, then the Company allowance this row describes. It sends your task text, task-list context, About You planning profile, Tasks memory/learnings, check-in and Plan chat messages, and — from the session-end catch scan — up to about the last 12,000 characters of the session it reads (your turns and the assistant's). Plan my day also carries your day's calendar: meeting start and end times, plus event titles when Show meeting names in AI planning is on. This includes the daily digest, which is on by default and carries the first message of every session it summarises — except AI-coaching and journal sessions, which it leaves out. Team Chat channel AI is not guaranteed to reach this lane either — it follows the same key order, and it sends the channel transcript it summarises (up to that channel's newest 100 messages, each author labelled Participant N with email addresses, phone numbers and links removed) and, for an @mc answer, the asking member's question plus the shared board context. Zhipu/GLM runs on a Company z.ai key, and Moonshot/Kimi, MiniMax, Meta (Muse) and Qwen run through the pooled Company OpenRouter key, so those coding lanes are NOT limited to your own key — the "other AI providers you configure" bullet below describes the separate BYOK case. For screen-recording summaries, it receives the finished recording's transcript (up to about 12,000 characters, with timestamps), which can include the voices of other people on a recorded call transcribed by our speech providers.
DeepSeek (via our AI gateway, on Company-held keys) Ask Omniscio help questions for people who have no AI account of their own connected, the starter agents offered during onboarding, and coding sessions you run on Omniscio credits — only while no Google account is connected. Connecting Google switches this lane off, and those features move to another provider. What you type to those agents and the work they do on your computer. Never Google user data.
DeepSeek and DeepInfra (upstreams serving our DeepSeek lane) The "DeepSeek" models above are served first-party by DeepSeek on a Company-held key, and DeepSeek is China-hosted — so a request on that lane leaves the United States. If one of them errors, our gateway automatically retries the same request against DeepInfra, also on a Company-held key and hosted in the United States. DeepSeek V4 Pro has no failover and stays on DeepSeek. Ask Omniscio's last fallback reaches a DeepSeek model through OpenRouter instead, under the same no-Google-account condition. The same prompt/message content the DeepSeek lane processes.
CrofAI (retired coding lane) CrofAI ran as a Pro coding lane on a Company-held key, receiving the whole session — every prompt, every file the agent read, and every tool result. It was retired on 2026-09-21; its endpoint no longer serves requests and no new session can select it, but it stays listed because existing CrofAI sessions and their recorded spend still resolve through it. CrofAI is China-hosted, so while such a session runs, that content is sent there. The whole coding session's prompts, files and tool results, for a session that already uses the lane.
FlowVoice (dictation — Omniscio cloud speech by default, or Google Gemini, Omniscio hosted, or Fluid Speech Mini on your own computer) OS-wide voice dictation (speech-to-text) into any app — on by default, and engaged only while you hold its shortcut — and the screen recorder's automatic captions, which are on by default and are transcribed through Omniscio cloud speech whenever that is the engine (the default), and otherwise on your own computer. Dictation uses the engine you choose in Settings. Omniscio cloud speech (the default) sends your audio through our own cloud to our speech-to-text provider, currently Soniox; if Soniox refuses the stream or fails before any words are transcribed, our cloud continues that dictation on our first backup provider, Inworld, then on Meta Muse Voice Transcribe if that one refuses too, and, only where it is configured, on Deepgram after that. Gemini transcribes in Google's cloud. Omniscio hosted (paid plans) sends it to our own server, which streams it to our speech-to-text provider for that engine, Deepgram. Fluid Speech Mini transcribes on your own computer, so the audio never leaves it. On Omniscio cloud speech and Omniscio hosted, an optional AI tidy-up (on by default, switchable in Settings) removes filler words and stray repeated words before the text is typed: it never rewords what you said, and when it is slow or unsure your words are typed exactly as spoken. Live microphone audio of whatever you dictate, plus your dictation language (for example "en"). For screen-recorder captions, it receives the recording's audio — your microphone plus, by default, your computer's system audio, which on a recorded call or meeting includes other participants' voices. With Omniscio cloud speech, it goes from your device to our own cloud service, which streams it to Soniox — or, when Soniox refuses the stream or fails before any words are transcribed, to Inworld, then to Meta Muse Voice Transcribe if Inworld refuses too (and, only where it is configured, to Deepgram after that) so the dictation is not lost — and returns the transcript to you (the provider can change, and our Subprocessors page lists the current one). With Gemini, that audio goes from your device to Google's live speech-to-text API — on your own Google key, or, if you have none, through our relay on a Company-held key. With Omniscio hosted, it goes to our own server together with a coarse foreground app name (for example "Chrome"), and our server streams the audio to Deepgram and returns the transcript. With the AI tidy-up on (Omniscio cloud speech and Omniscio hosted only), the text of each dictation — never the audio — goes through our AI gateway to OpenRouter, which runs it on Cerebras with data collection refused; only the tidied text comes back. With Fluid Speech Mini, nothing leaves your computer. The window title is deliberately not sent on any engine: a title can carry a document or person name, an email subject, or a URL, so it is captured locally for your own dictation history only and stays on your device.
Supermail backend Company self-hosted backend (US) for the Supermail mail client and its server-side contact enrichment — engaged only when you use Supermail. Connecting a mailbox copies that mailbox onto this backend so the app can search, thread and summarize it. Your connected mailbox, mirrored server-side — senders and recipients including cc and bcc, subjects, full message bodies and attachments, sent mail, drafts and labels, plus the mailbox's stored connection credentials (encrypted) — together with the contact-enrichment lookups performed on the Company backend. Retention is in §9.
TypeSafe (via our AI gateway, on Company-held keys) The primary lane for the "Jev" decision feature — a typed question-and-answer call with a confidence score rather than generated prose. It runs on its own when the features that use it are working (for example the email safety screen and the spam check on texts); an OpenRouter route on the same gateway is the backup when TypeSafe is unavailable The situation text and the questions submitted to a decision call, which can include message and email text.
Omniscio backend apps (Company self-hosted) Our own backend services for support chat (the helpdesk), the plugin marketplace, Mission Control project boards (including the Monday.com and Trello board connections that run through them), importing boards from tools you connect, and the relay that carries some Shares — each engaged when you use that feature The support conversations, board items, members' names and email addresses, imported board data, marketplace requests and relayed Share content those features handle.
unpkg.com Serves the React runtime into a viewer's browser for a Share whose document runs code — automatically, whenever such a Share is opened The viewer's IP address and browser user-agent; no user content.
Hugging Face Download of the on-device model files (embedding, captioning and on-device speech) the App runs on your machine Your IP address and browser user-agent; no user content — only the model file is fetched.
GitHub (ffmpeg download) The App ships no ffmpeg. The first time a recording needs transcoding and none is present, the App fetches one automatically, with no prompt: first through your package manager (winget Gyan.FFmpeg on Windows, Homebrew on macOS), then, if that fails, a pinned, checksum-verified build from github.com Your IP address and request metadata (to GitHub, and to the package sources behind winget and Homebrew); no recording or other user content.
jsDelivr Serves files the Video Editing Suite plugin downloads to run on your computer — a Google Fonts typeface you pick, and the GPU runtime its on-device background removal needs — fetched only when the plugin needs one Your IP address and browser user-agent; no user content.
ffmpeg build server (ffmpeg.martin-riedl.de) The Video Editing Suite plugin fetches a pinned ffmpeg static build from this server on macOS and Linux the first time it needs one and none is installed Your IP address and request metadata; no recording or other user content.
Agent Client Protocol registry (cdn.agentclientprotocol.com) Download of the public list of coding agents you can add, when you open that list or add an agent (kept for a day) Your IP address and request metadata; no user content.
LiveKit (real-time call media) — not yet active In development; not enabled in the current build, so no data reaches LiveKit today. When Team Chat voice/video calls ship, LiveKit will act as the real-time audio/video relay (SFU), engaged only when you start or join a call, with the Company minting a scoped access token on its own LiveKit account (Company-operated, lane-2). LiveKit will be added to the Subprocessors list before that path is ever enabled. Once enabled: live audio and video of the call participants (including other members on the call) plus call room/token metadata.

Optional / secondary services

Most of these receive data only when you turn on or use the feature they serve; the few that run by default say so in their entry. Our Subprocessors page is the complete, current list.

In-app voice is OFF by default — FlowVoice dictation and recording captions are ON. The in-app speech-to-text and text-to-speech features are turned off out of the box. FlowVoice dictation ships on: it captures nothing until you hold its shortcut, and while you hold it your microphone audio goes to the FlowVoice providers in the table above; turn FlowVoice off in Voice settings to stop it. The screen recorder's captions also ship on, so with the default Omniscio cloud speech engine a recording's microphone and system audio goes to the providers listed above automatically, and once a one-time notice has been shown its transcript goes to OpenRouter for a summary (see Screen recorder captions and summaries). If you enable in-app voice, its audio and voice data are sent to the providers listed above. Dictation audio, in-app voice data and recording audio can all be sensitive personal information (see Section 8).

Other sites and services. The App, our websites, our emails, and content you view through the Services may contain links to third-party websites, tools, or services we do not operate. This Policy does not apply to those third parties, and we are not responsible for their content, practices, or privacy policies. Review the privacy policy of any third-party site or service before you provide it your information.

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, with exactly one exception: plugin feature counts, which have their own switch (see below). The disclosure here is how we keep it honest, not a promise you can disable it. Three settings control only the emails, never the collection: "Auto-Email Crash Reports" (Settings → Diagnostics → Health) controls the detailed crash email and the crash record sent with our usage telemetry — turning it off leaves crash capture by Sentry and every other telemetry leg running; "Email diagnostics to the team" (Settings → Diagnostics) silences the weekly usage digest and the crash email; and "Email crash reports" silences the crash email while keeping the weekly digest.

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.

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.

De-identified and aggregated data. Where we use aggregated or de-identified information, we maintain and use it only in de-identified form and do not attempt to re-identify it, except as permitted by law to test that the de-identification is effective. This paragraph does not describe the identified usage and spend aggregates covered in Section 4: those are uploaded keyed to your account and are personal information, not de-identified data, and they are handled as described in Sections 4, 6 and 9.

Disclosures for legal reasons and business transfers. We may disclose personal information when we reasonably believe it is necessary to: (a) comply with applicable law, regulation, legal process, or an enforceable governmental request; (b) enforce our terms and policies; (c) detect, prevent, or address fraud, security, or technical issues; or (d) protect the rights, property, or safety of the Company, our users, or the public as required or permitted by law. If the Company is involved in a merger, acquisition, financing, reorganization, bankruptcy, or sale of all or part of its assets, personal information may be transferred as part of that transaction; we will require the recipient to honor this Policy or will notify you of any material change to how your information is handled.

8. Your US state privacy rights

Depending on your state of residence, you may have privacy rights under a comprehensive state privacy law — including California (CCPA/CPRA), Virginia (VCDPA), Colorado (CPA), Connecticut (CTDPA), Utah (UCPA), and Texas (TDPSA), and other states as their laws take effect. Subject to the exceptions in each law, these rights generally include the right to know and access the personal information we hold about you, to correct it, to delete it, to obtain a portable copy, and to opt out of targeted advertising, the "sale" of personal information, or certain profiling. We do not sell your personal information for money. However, our public websites use Google Analytics with advertising features ("Google signals"), which discloses online identifiers to Google for cross-context behavioral advertising and is therefore treated as a "share" (and, in some states, a "sale") under the CPRA and similar laws. You can opt out at any time using the "Do Not Sell or Share My Personal Information" link in our website footer, by turning on Global Privacy Control (which we honor), or via the controls in our Cookie Notice. No other category of personal information is sold or shared, and none of the data inside the App is shared for advertising.

The California-specific disclosures below (the Notice at Collection and the sensitive-personal-information right to limit) are provided for California residents; the mechanics for exercising your rights, honoring opt-out preference signals, and appeals apply to residents of every state whose law provides them.

Sources of personal information. We collect the categories below from: you (what you type, upload, or connect); your use of the Services (automatically — feature usage, diagnostics, and device and network information); service providers acting on our behalf (for example, our payment processor); and third parties you connect or who contact you through an integration you enable (for example, the senders of messages you receive in a connected channel).

Categories of personal information (Notice at Collection):

Category What we collect Purpose Disclosed to service providers? Sold or shared?
Identifiers account ID, email, display name, profile photo (a link from your sign-in provider, or the image file itself if you upload one), IP address, device/install ID account, login, security, support Yes Yes — website visitors only (IP address, Google Analytics / Meta browser ids and page activity on our public websites; see below)
Commercial information plan/tier, billing and purchase records billing, subscription Yes (Stripe) No
Internet/network activity feature usage, diagnostics, crash reports reliability, product improvement Yes (e.g., Sentry) Yes — website visitors only (IP address, Google Analytics / Meta browser ids and page activity on our public websites; see below)
Geolocation (coarse) country and region inferred from your IP address on every sign-in, plus a coarse browser/OS device label. Kept as a per-account current-location record (countries seen and up to 10 device labels) and a sign-in location history that stores a per-account salted hash of the IP, not the address itself — see §4 and §9. sign-in security (new-location and new-device notices) and an audit trail of where the account has been used; sales tax and availability Yes — the region used for sales tax goes to Stripe Tax; the sign-in location history is not disclosed to a service provider No
Payment/financial payment-card details (handled by Stripe; not stored by us). Plus, if you use the Coffer personal-finance feature: structured financial data stored in your local encrypted database — bank balances, credit limits, a dated transaction ledger, and payee names (a SimpleFIN bank sync you connect is user-direct). payment; personal budgeting Card details: Stripe. Coffer data: local to your device; SimpleFIN sync user-direct No
Sensitive personal information FlowVoice dictation is on by default and captures audio only while you hold its shortcut; in-app voice and text-to-speech are used only if you enable them: microphone audio / voice recordings sent to your chosen speech provider, and response text sent to the text-to-speech provider. Also, by default, the screen recorder's captions send each recording's audio — your microphone and, by default, your computer's system audio, which on a recorded call includes other participants' voices — to those cloud speech providers. A recording made with the camera overlay also contains webcam video of you and anyone in frame; that video is not sent to a speech provider, and it leaves your device only if you share the recording or upload it to a service you connected. No SSN; your credentials stay on your device. Provide default-on FlowVoice dictation when you hold its shortcut, the voice features you turn on, and the default-on recording captions Yes — to the voice provider you select (and Fish Audio or Soniox, which read aloud through Company-funded relays), and, for recording captions, to the cloud speech providers named in §5 No
Sensitive personal information (personal-development features) If you use the optional AI-coaching, journal/reflection, or self-assessment ("Life Inventory") features: psychological, emotional, and health-adjacent notes, ratings, and generated profile/insight text you create. Stored locally on your device. AI-coaching and journal reflection also send the relevant text to Anthropic to generate insights — usually on your own API key, but a key you have already saved in the App, or a Company-held key on a plan that includes AI credits, can fund those calls instead; Life Inventory is computed locally with no AI call. The daily digest (on by default) leaves AI-coaching and journal sessions out. With Cross-Device Sync on (off by default), the AI-coaching and Life Inventory records are also uploaded, end-to-end encrypted (§4); journal entries are not. Provide the personal-development features you use Anthropic (your own, a stored, or a Company-held key) for coaching/journal insight generation No

Sharing for cross-context behavioral advertising. The online identifiers collected by our public websites (such as your IP address and a Google Analytics identifier) are shared with Google for cross-context behavioral advertising through Google Analytics' advertising features, and — when we run ads on those platforms — with Meta and Google Ads to measure which ads led to a download, signup or purchase (the Meta Pixel, the Google Ads conversion tag and our server-side reports to Meta described in Section 4). These are the only "sharing" we do. No visitor is opted in to this sharing by default: it starts only after you press Accept, in every time zone. You can opt out (see the "Do Not Sell or Share My Personal Information" link and Global Privacy Control described below, and our Cookie Notice). No other category in the table above is sold or shared, and nothing inside the App is shared for advertising.

Right to opt out of "sharing"; Do Not Sell or Share My Personal Information. Because our public websites use Google Analytics advertising features and Meta / Google Ads conversion measurement (a "share" for cross-context behavioral advertising, as described at the top of this Section), you have the right to opt out. To do so, use the "Do Not Sell or Share My Personal Information" link in our website footer, turn on Global Privacy Control, or use the controls in our Cookie Notice. We do not sell your personal information for money.

Opt-out preference signals (Global Privacy Control). Some browsers and extensions can send an opt-out preference signal such as Global Privacy Control (GPC). We honor GPC as a valid request to opt out of the sharing described above — when we detect a GPC signal on our website, we disable the Google Analytics advertising features, load no Meta or Google Ads tag, store no ad click id, and send no report to Meta for that browser.

"Do Not Track." Some browsers offer a "Do Not Track" (DNT) setting. There is no common industry standard for responding to DNT signals, so we do not currently respond to DNT signals; we honor Global Privacy Control instead (above). The App itself sets no advertising or cross-site tracking cookies (see Section 4); the advertising technologies on our websites are described in our Cookie Notice.

California "Shine the Light." California Civil Code § 1798.83 lets California residents request information about personal information disclosed to third parties for those third parties' own direct-marketing use. We do not disclose personal information to third parties for their own direct marketing, so there is nothing to report; you may still contact legal@omniscio.com with questions.

Nevada. Nevada law lets residents submit a request not to sell certain covered information. We do not sell such information, but you may direct a verified request to legal@omniscio.com.

Texas. We do not sell sensitive or biometric personal data for monetary consideration, and Texas residents may exercise the access, correction, deletion, portability, opt-out, and appeal rights described in this Section.

9. Data retention

Data Retention
Local data (sessions, messages, keys) On your device until you delete it. Removing the App does not delete it by default — on Windows the uninstaller asks and defaults to keeping it; on macOS, dragging the App to the Trash leaves the data folder. Remove the data folder (and any session working-copy folders) yourself to erase it (see §2).
Personal-development data (AI-coaching profile/insights, journal entries, Life-Inventory results) On your device until you delete it in the feature or run "erase all local data" — not automatically expired (see §8)
Account and billing records Life of your account, then up to 7 years (tax/accounting/legal)
Sign-in location history (country/region, new-country flag, salted IP hash) About 90 days, then deleted automatically. The account's current-location record is kept while the account exists and deleted with it. Opt out at any time (§8)
Cloud backup to Omniscio (encrypted on your device) Until you replace it with a newer backup or delete it; deleting removes every stored version
Cross-Device Sync locker (end-to-end encrypted) While your sync locker exists — sync keeps the latest version of each synced record (deletions included) and periodically compacts and garbage-collects older segments; deleting your account deletes the whole locker
Raw diagnostic events we receive in our fleet store About 180 days
Installation-level fleet rollups (per-install daily spend/usage, keyed to the random install identifier rather than your account) About 1 year for the per-install daily digests; the install record itself about 180 days after the install last reports; the raw events behind them are deleted at 180 days
Identified usage/spend aggregates About 180 days, keyed to your account
On-device diagnostic logs Rotated on disk — the 18 most recent log files: about a week of history on a busy machine, longer when the App writes less, and nothing older than 30 days
Support / helpdesk conversations About 12 months
Inbound agent-email content About 90 days
Scheduled agent-email messages Until sent — the message body and subject are deleted at send, and the row with its recipient addresses about 5 days later. A message that is never sent is deleted about 33 days after its scheduled time. A send that keeps failing is set aside with its identifiers (no content) for about 90 days
Supermail's server-side copy of a connected mailbox (messages, bodies, threads, labels, attachments) While the mailbox is connected to Supermail. Disconnecting a mailbox in Supermail deletes that mailbox's copy — its messages, threads, labels and attachments, and the contact details no other mailbox still uses. Supermail cannot disconnect your only remaining mailbox, and it has no in-app way to delete your Supermail account: to delete the account and everything stored for it, email legal@omniscio.com
Team Chat message history No automatic deletion today — nothing deletes a Team Chat message by age, on any plan. A message stays until you or a channel admin deletes it, or until your account is deleted. Plan-based retention limits may be introduced when paid plans launch; if we do that, we will update this policy before any limit takes effect
Team Chat audit events (workspace settings changes, retention-policy changes and other admin actions recorded in the audit log) About 730 days, then deleted automatically
Microsoft Teams history imported into Team Chat Only messages from the last 365 days are imported; once imported they follow the Team Chat message-history retention above
Search index About 13 months
Shared artifacts ("Shares") and their comments Until you delete the Share — or, if you gave it an expiry date, until that date passes: from then on its link answers "expired" and no longer opens, its stored page, image and file objects are removed by our cleanup (about 15 minutes, while the App is running), and a video's files are deleted by a server sweep that runs every 6 hours, so within about 7 hours. A Share with no expiry date is kept until you delete it; we do not remove Shares by age. A Share opened with Anyone with the link may have been indexed or cached by search engines, and we cannot delete those copies
A shared recording's watch analytics (one row per play session: session id, first and last time, furthest point reached, seconds watched, duration, country, salted IP and browser user-agent hashes) About 180 days, then deleted automatically. A viewer's Do Not Track or Global Privacy Control signal stops the watch session being stored
A view-capped Share's counted-viewer row (salted hash of the viewer's network address and the time it was counted) About 180 days
Share commenter sign-in record (Google email, display name and photo, created when someone signs in to comment) No fixed period — held until the commenter asks us to delete it (email legal@omniscio.com). It is not linked to an Omniscio account unless the same email address already has one
Download-click attribution records (campaign tags, referrer, the first page of our websites you visited, the one-time download code, a salted truncated IP hash, and — only with advertising consent — the ad click ids, Meta browser ids, browser id, user-agent and page URL) About 180 days. The channel and first page we linked to your account at sign-up stay on your account until you delete it. Withdrawing advertising consent removes the advertising fields at once
Local cost/spend ledger (session id, account id, provider, amount, timestamps — no message content) Kept by design after you delete a session or run "erase all local data", because it is the billing record for spend already incurred. It is removed with the App's data folder (§2)
Repository bundles and run logs from the internal developer offload (§4) 7 days (bundles) / 14 days (run logs), by automatic schedule

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, Resend, and Cloudflare), 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.

12. Children's privacy

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

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.

15. Google user data

This section explains how Omniscio handles data it receives from Google when you choose Connect Google in the App. It applies in addition to the rest of this policy.

What we access, and why. Omniscio uses Google data only to provide features you can see and use in the App:

Where it's stored. Google data is processed on your own computer. Any local copies, such as a copy of your mailbox for fast search, stay on your device, and contacts are held in memory only. Your Google access token is stored on your device, encrypted with your operating system's secure storage, and is never sent to Omniscio's servers. The one exception is the Calendar Scheduler plugin: when you connect Google Calendar to it, a Google refresh token is sent to and stored on the Calendar Scheduler server, encrypted, so it can check when you are free and add booked meetings to your calendar while your computer is off; it only asks Google for your name, email address, free/busy times and the events on calendars you own, and choosing Disconnect revokes that access at Google and deletes the token. If you turn on cloud backup or cross-device sync, that data is end-to-end encrypted on your device before it is uploaded, so Omniscio cannot read it.

When it leaves your computer.

Google user data is never sent to DeepSeek. While a Google account is connected, Omniscio does not run anything on DeepSeek on your computer: agent sessions cannot start or continue on a DeepSeek model (on any key or provider), and Ask Omniscio and the onboarding starter agents use a different provider. The built-in AI helpers never use DeepSeek at all. To use DeepSeek again you must first disconnect Google, which deletes the local Google data listed under "Your controls" below.

We do not sell Google user data, use it for advertising, or use it to decide creditworthiness. We do not use Google user data to develop, improve, or train generalized AI or machine-learning models. Omniscio staff do not read your Google data unless you ask us to (for example, in a support request), it is needed for security (such as investigating abuse), or the law requires it.

Your controls. You can disconnect Google at any time in Omniscio's Settings. Disconnecting revokes Omniscio's access at Google and deletes the local copy of your mailbox, your Google Meet list, the email samples Omniscio saved from Gmail, and the people and profile details it built from your email. Past daily digests, writing-style guides you created, and agent sessions you ran on your email — including bug reports that arrived by email — stay until you delete them. You can also remove Omniscio's access at myaccount.google.com/connections.

Limited Use. Omniscio's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.