Privacy Policy

This policy covers two separate things, and we’ve tried to keep them separate throughout:

1. This website (aios.graphenlabs.com) — where you learn about AIOS, create an account, purchase a license, and manage billing.
2. The AIOS desktop application — the software that runs on your own computer.

These are different systems with different data footprints. The Site necessarily collects account and billing information to function. The desktop app, by design, does not. See “The AIOS desktop app: what never leaves your machine” below for the full explanation of the second point.

Account information. When you create an account, authentication is handled by Clerk, our identity provider. Clerk collects and stores your email address and any authentication credentials you use to sign in (password, magic link, or OAuth provider identity, depending on how you choose to sign in). We receive your email address and a Clerk-issued user ID from this process so we can associate a license with your account.

Payment information. Billing is handled by Dodo Payments, who acts as the merchant of record for all AIOS purchases. When you purchase a license, Dodo Payments collects and processes your payment details (card number, billing address, and related transaction data) directly. Graphenlabs does not receive, store, or have access to your full payment card details — we receive confirmation that a payment succeeded, a transaction reference, and the billing metadata needed to issue and manage your license (such as plan tier and billing cycle).

License metadata. To issue and manage your license, we store a small, deliberately minimal record tied to your account: license tier (Free, Individual, or Enterprise), seat count (for Enterprise), the email address associated with the license, license status (active, expired, deactivated), and issuance/expiry timestamps. This metadata is what allows the desktop app to verify your entitlement offline — see the license system description below.

Server logs and technical data. Like most web applications, our hosting and infrastructure providers generate standard server logs when you access the Site — IP address, browser/user-agent string, requested URL, timestamp, and response status. These logs exist for operational purposes (debugging, abuse prevention, uptime monitoring) and are not used to build advertising profiles or sold to anyone.

Support communications. If you contact us for support, we retain the content of that communication (and the email address it came from) for as long as needed to resolve the issue and for a reasonable period afterward for context if you follow up.

What we do not collect on this Site. We do not run third-party analytics trackers, advertising pixels, or behavioral-profiling scripts. We do not sell personal information. We do not collect the contents of your AIOS desktop corpus — your chats, documents, research, or repositories never reach this website or our servers, because they never leave your machine (see below).

We process the information above for the following purposes, each tied to a specific need:

• To provide the service — authenticating you, associating a license with your account, and letting the desktop app verify that license.
• To process billing — enabling Dodo Payments to charge you for a purchased plan and to handle renewals, refunds, or disputes.
• To provide support — responding to questions or issues you raise with us.
• To maintain and secure the Site — server logs help us debug outages, detect abuse, and keep the account system reliable.
• To communicate necessary account or billing notices — for example, a payment failure or license expiry.

We do not use your account or payment data for advertising, and we do not build behavioral profiles from Site usage.

We rely on a small number of named third-party services to run the Site and account system. We do not hand your data to data brokers or ad networks, and we’ve limited this list to the processors actually required to authenticate you, bill you, and host the Site:

• Clerk (authentication) — processes your email address and sign-in credentials to authenticate your account. Clerk’s own privacy policy governs how it handles this data: see Clerk’s Privacy Policy on their website.
• Dodo Payments (billing, merchant of record) — processes your payment details and handles the transaction as merchant of record for your purchase. Dodo’s own privacy policy governs how it handles payment data: see Dodo Payments’ Privacy Policy on their website.
• Hosting/infrastructure providers — generate the standard server logs described above as a function of serving the Site.

We do not control these providers’ own data practices beyond the data we send them, and we encourage you to review their respective privacy policies if you want the full picture of how each handles data on their end.

We retain account and license metadata for as long as your account is active, plus a reasonable period afterward to handle billing disputes, license reactivation, or legal obligations (typically no more than a few years past account closure, unless a longer period is legally required). Server logs are retained on a rolling basis for operational purposes and are not kept indefinitely. Clerk and Dodo Payments retain the data they process according to their own retention policies, which are described in their respective privacy policies linked above — we don’t dictate their retention windows, but we also don’t ask them to retain data longer than needed to serve their function for us.

You can request to access, export, or delete the account and license data we hold about you by contacting us at the address below. Because the data footprint here is intentionally small — an email address, a license tier, and billing status, not a behavioral profile — most requests are straightforward to fulfill quickly. Note that:

• Deleting your account will deactivate any associated license (the desktop app will fall back to Free tier per its normal grace-period handling — see the license system note below).
• We can delete or export the account and license metadata we control directly. Data held by Clerk (your authentication record) or Dodo Payments (your payment history) may also be subject to their own data-subject request processes, since they are independent processors of that data; we’re happy to help you route a request to them if needed.
• Some minimal billing records may need to be retained even after a deletion request, where we’re legally required to keep transaction records (e.g., for tax or accounting purposes).

If you’re a resident of a jurisdiction with a statutory right of access, correction, deletion, or portability (such as the EU/UK under GDPR or certain U.S. states), those rights apply here and we’ll honor requests consistent with applicable law.

The Site uses the session cookies Clerk sets to keep you signed in — these are functional, not tracking, cookies; they exist so you don’t have to re-authenticate on every page load. We do not add any analytics, advertising, or cross-site tracking cookies of our own. If that ever changes, we’ll update this section and our footer claim accordingly before it does, not after.

The Site and AIOS are not directed at children under 13, and we do not knowingly collect personal information from anyone under 13. If you believe a child has provided us with personal information, contact us at the address below and we will take steps to delete it.

Graphenlabs and the third-party processors we use (Clerk, Dodo Payments, our hosting providers) may process and store data in countries other than your own, including the United States. Where required by applicable law, we and our processors rely on appropriate safeguards (such as standard contractual clauses or equivalent mechanisms) to govern these transfers. By using the Site, you understand that your information may be transferred to and processed in a country with different data protection laws than your home jurisdiction.

We may update this policy as the Site, the account system, or applicable law changes. If we make a material change, we’ll update the “Last updated” date above and, where the change is significant, provide more prominent notice (such as a banner on the Site or an email to account holders). Continued use of the Site after a change takes effect constitutes acceptance of the revised policy.

Everything above describes this website. The desktop application is a different system with a different privacy story, and it’s worth stating plainly rather than leaving it implied.

AIOS is a local-first desktop application. Its database (SQLite), its vector store (ChromaDB), and its stored credentials (your operating system’s own keychain) all live on your computer, not on ours. Your chats, your ingested documents, your research corpus, your repositories, and everything else you build inside AIOS stays on your machine by default. We do not have a server that receives, stores, or has visibility into any of it. Specifically:

• Per-launch local authentication. Each time you launch AIOS, the app generates a fresh random token that gates its own local API — this token never leaves your machine and exists purely to stop a stray webpage or process from talking to your local AIOS backend without your knowledge.
• OS keychain for secrets. If you connect a cloud model provider (optional — see below) or configure any API key, that key is stored in your operating system’s own credential store (via keyring), not in a plaintext database and not on our servers.
• Offline license verification. Your AIOS license is a cryptographically signed token that the desktop app verifies against a public key baked into the application itself. Verifying your license does not require contacting Graphenlabs’ servers — AIOS can check what you’re entitled to without phoning home.
• Nothing sent unless you explicitly enable it. AIOS does not transmit your data anywhere by default. If you choose to connect a cloud model provider (bring-your-own-key), enable live web search, or use another feature that explicitly reaches an external service, only the specific request you make goes out to that specific provider — governed by that provider’s own terms, not ours — and only because you turned it on. The local corpus underneath it stays local regardless.

The only data flow between the desktop app and Graphenlabs is the offline license check described above, and even that is designed to work without a network round-trip in the common case. We built it this way deliberately: the thesis behind AIOS is that you shouldn’t have to trust a server you don’t own with your research, your documents, or your code, and that starts with not asking for that trust in the first place.

Questions about this policy, or requests relating to your account or license data, can be sent to privacy@graphenlabs.com. For questions specifically about how Clerk or Dodo Payments handle data they process on our behalf, their own privacy policies (linked above) are the authoritative source, though we’re glad to help you find the right channel if you’re not sure where a request belongs.