Legal · Privacy
Privacy Policy
The short version sits at the top — what Corivo reads from your screen, where it lives on your computer, and how to keep specific apps off-limits. The desktop source is public for inspection, and the full legal text follows below.
Last updated: May 20, 2026
The plain-English version.
Four claims, no marketing language. Tap any card to jump to the detailed legal text further down.
- 01Jump to details
No screenshots, ever.
Corivo reads screen content as structured text through your operating system's accessibility APIs — macOS Accessibility on Mac, UI Automation on Windows — never as pixels or images. There are no screenshots being stored, anywhere.
- 02Jump to details
Lives in a local database.
That structured text sits in a SQLite database on your computer. It doesn't stream to our servers. No cloud sync of what you read, write, or remember.
- 03Jump to details
You decide what's off-limits.
Exclude any app from being captured — banking, messaging, password managers, anything you want kept dark. Once excluded, that app is invisible to Corivo.
- 04Jump to details
Desktop source is public.
The Corivo desktop app is on GitHub under Apache-2.0.
This Privacy Policy describes how Corivo (“we”, “us”, or “our”) collects, uses, and shares information when you visit corivo.ai(the “Site”) or use the Corivo desktop application for Mac or Windows (the “Service”). We split the policy into two parts — what happens on the website, and what happens inside the app — because the data flows are different. By using our Site or Service, you agree to the practices described in this policy.
1. When you visit corivo.ai (the Site)
When you visit the Site, we automatically collect certain information about your device, including information about your web browser, IP address, time zone, and some of the cookies that are installed on your device. We also collect information about which pages you view, what referred you to the Site, and how you interact with it. We refer to this automatically-collected information as “Device Information.”
We collect Device Information using:
- Cookies — data files placed on your device that often include an anonymous unique identifier. For more information about cookies, and how to disable them, visit allaboutcookies.org.
- Log files — record actions on the Site, including IP address, browser type, ISP, referring/exit pages, and timestamps.
- Analytics tags — small scripts (e.g., Google Tag Manager, Microsoft Clarity) used to understand aggregate site usage so we can improve the experience.
When you sign up for the waitlist or contact us, we collect your name, email address, and any other information you choose to provide (“Contact Information”). We use Contact Information only to respond to you and to send the product updates you opted in to.
2. Screen context and on-device capture
The Corivo app reads what's on your screen through your operating system's accessibility APIs — macOS Accessibility on Mac, UI Automation on Windows. Those APIs expose screen content as structured text— the document title and headings, the message you're reading, the ticket fields, the calendar event. They do not expose raw pixels.
As a result, Corivo does not take screenshots, capture image data, or record your screen. There are no image files generated, stored on disk, or transmitted anywhere. If something on your screen can't be expressed as text through accessibility (e.g., a video frame, a chart drawn on a canvas), Corivo does not see it.
Reading the accessibility tree requires you to grant Corivo accessibility permission in your operating system's settings — System Settings › Privacy & Security on Mac, Settings › Privacy on Windows. You can revoke that permission at any time, after which Corivo will stop capturing screen context.
The Corivo desktop app is open source under Apache-2.0 at Principle-Labs/corivo-desktop. You can inspect how the app reads structured screen context and applies local privacy controls in the public repository.
3. Where your data is stored
Structured text captured from your screen, along with any notes, embeddings, and memory entries Corivo derives from it, are written to a local SQLite databaseon your Mac (under your user's Application Support directory). This database does not sync to our servers, to iCloud, or to any other cloud provider.
We do not maintain a copy of your screen context or memory database on our infrastructure. If you delete your local database, that data is gone — there is no server-side copy to recover from. (We recommend you treat the database the same way you treat the rest of your local data: include it in Time Machine or your usual backup workflow if you want a recovery path.)
Aggregate, non-content telemetry (e.g., crash reports, the fact that an action was performed) may be sent to us to improve the Service. This telemetry does not contain the content of your screen context or memory entries.
4. Open source desktop app
Corivo's desktop app source is public under Apache-2.0. Open source is not a substitute for a privacy policy, but it gives users and security-minded teams a concrete way to inspect the local capture, local storage, and exclusion paths described here.
The public repository is https://github.com/Principle-Labs/corivo-desktop.
5. App-level exclusions
You can mark specific applications as excluded inside Corivo's settings. Once an app is excluded:
- Corivo will not read its accessibility tree while it is focused or frontmost.
- No new structured text from that app enters your local database.
- Any past entries derived from that app can be purged from the local database from the same settings panel.
We recommend excluding banking apps, password managers, private messaging clients, and any other app where the content should remain dark to Corivo. Exclusions take effect immediately and persist across app restarts.
6. When data leaves your Mac
Corivo delivers value by handing the right context to an AI model when you ask it to do something. That step does involve sending context to a model provider(the LLM API you have configured). We're being explicit about this because it's the most common source of confusion about an on-device app.
Context only leaves your Mac when you initiate an action that requires a model call — for example, asking Corivo to draft a reply, summarize a thread, or run an agent task. It is sent to the model provider you have configured. Corivo does not proxy or store those requests on our infrastructure by default.
Please treat the context Corivo sends to your model provider the same way you treat any other request you make to that provider directly — the provider's terms, retention, and security practices apply to that data once it leaves your computer.
7. Connected tools (integrations)
When you connect a tool such as Linear, Notion, Gmail, Slack, GitHub, Google Docs, Sentry, Google Calendar, Mem, or Intercom, Corivo stores the OAuth or API access token for that tool locally so it can fetch data on your behalf.
Data fetched from connected tools is treated the same as on-screen context: it is held in the local SQLite database and, when a model call is involved, follows the same flow described in Section 5. You can disconnect any tool at any time inside Corivo's settings, which revokes the local token and stops further reads from that tool.
8. How we use Personal Information
We use the information we collect to:
- Provide and improve the Site and the Service;
- Send waitlist confirmations, product updates, and support responses — only if you opted in;
- Screen for fraud or security incidents;
- Analyze aggregate, non-content usage to improve features;
- Comply with applicable legal obligations and enforce our terms.
You can opt out of marketing emails at any time using the unsubscribe link in any message we send.
9. Sharing your information
We share information with third parties only to operate the Service, as described in this policy, or where required by law. We do not sell your information.
- Service providers — companies that provide services on our behalf (e.g., email delivery, analytics, cloud infrastructure for the website). These parties are bound by contractual obligations to keep your information confidential.
- Model providers — the LLM API you have configured, as described in Section 5.
- Law enforcement or regulators — when required by applicable law, subpoena, or legal process.
- Business transfers — in connection with a merger, acquisition, or sale of all or a portion of our assets.
Your screen context, your local memory database, and the content of your connected tools are never sold, shared with third parties for advertising, or used to build advertising profiles.
10. Data retention
We retain Site analytics data and Contact Information for as long as necessary to provide the Service and fulfill the purposes outlined in this policy, unless a longer retention period is required by law.
Your screen context and local memory database live on your Mac and are retained for as long as you keep them — deleting them is something you do locally, on your machine. We do not hold a server-side copy that needs to be retained or deleted separately.
If you wish to delete your Contact Information from our systems, please contact us at [email protected].
11. Do Not Track
We do not alter our Site's data collection or use practices when we see a Do Not Track signal from your browser.
12. Your rights
Depending on your location, you may have rights regarding your Personal Information, including the right to access, correct, or delete the data we hold about you, or to object to or restrict certain processing. To exercise any of these rights, please contact us at [email protected].
Note that screen context and memory data already live on your Mac — you can access and delete those directly from Corivo's settings without going through us.
13. Security
We implement industry-standard technical and organizational measures to protect Personal Information we hold against unauthorized access, alteration, disclosure, or destruction. However, no method of transmission over the Internet or electronic storage is 100% secure, and we cannot guarantee absolute security.
For data living on your computer, the security boundary is your operating system user account. On Mac, we recommend enabling FileVault and staying on a current macOS version. On Windows, enable BitLocker (where available) and stay on a current Windows version.
14. Changes to this policy
We may update this Privacy Policy from time to time to reflect, for example, changes to our practices or for other operational, legal, or regulatory reasons. The updated version will be indicated by a revised “Last updated” date at the top of this page. We encourage you to review this Privacy Policy periodically.
15. Contact us
For more information about our privacy practices, if you have questions, or if you would like to make a complaint, please contact us by email at [email protected].