What we collect. What we never hold.

This website

Almost nothing, by default. carabase.ai sets no marketing cookies, loads no advertising trackers, and runs no client-side behavioural analytics. Netlify, which serves the site, processes ordinary request information — IP address, browser details, requested URL — to deliver and secure it, and may provide us aggregate server-side traffic statistics.

The only personal data this site collects is what you give it:

• Your email address, if you apply for the private alpha. It is stored in Loops, the email service we use to manage applications and send early-access messages. You can unsubscribe from anything we send.
• Your email address and message, if you write to hello@carabase.ai. It sits in our inbox. We read it and reply when we can.

No data is sold, rented, licensed, or traded to any third party, ever, under any circumstance.

The product

Your Carabase and its database live on your hardware. The sources you connect and the memory Carabase builds from them are stored on machines you control. Your local database is never time-limited or remotely disabled, and leaving the service never deletes local data or local features.

When you use a cloud AI

If you point your context at a cloud model, the context selected for that request is processed by the model provider you chose — that provider must see plaintext to answer, and we will not pretend otherwise. Managed inference is routed through an allowlist of endpoints that are eligible for zero-data-retention handling where providers offer it, and we do not store prompt or response bodies.

Carabase’s cloud services

During the private alpha, an optional account and connectivity layer makes your Carabase reachable from your devices, signs you in, and carries encrypted messages when your host is asleep. Its visibility is deliberately narrow:

Enforced, not aspirational. Content-free logging is tested in our release pipeline: a build fails if sentinel credentials or prompt strings reach logs, traces, or error reports. Hosted data is encrypted at rest, sensitive stores under customer-managed keys, on infrastructure where production data never flows into test environments.

Provider connections (Google, and others)

If you connect Google or another provider so Carabase can use it as a source, we request the narrowest read-only access that does that job — never permission to send, write, or anything broader than the feature needs.

What Carabase’s Google connection asks for. When you connect Google through Carabase’s own connection (the Connect Google button, which uses Carabase’s Google sign-in), Google shows you one consent screen listing these permissions, and Carabase asks for nothing else:

• Gmail, read-only (gmail.readonly) — read your messages, including their content and attachments, so they can appear in your timeline and be searched and summarised alongside everything else.
• Calendar, read-only (calendar.readonly) — read your events so they sit on the same timeline.
• Basic profile and email address (openid, email, profile) — identify which Google Account the connection belongs to, so the same account is not linked twice and a connection can never attach to the wrong account.

All of them are read-only. Carabase never asks for permission to send, modify, or delete anything in your Google Account.

Google Drive is not requested by Carabase’s Google connection. Drive can only be connected if you register your own Google OAuth client in Carabase’s advanced settings and connect with it. That connection is between your Google Account and your own client: the sign-in happens on your Mac, the tokens are held only on your Mac, your files are fetched and processed on your Mac, and Carabase’s servers take no part in it.

How the connection works. Carabase Pty Ltd operates the Google OAuth application, so our servers act as a short-lived broker for your sign-in tokens. They exchange Google’s sign-in code for a token when you connect, refresh it when your Mac asks, and revoke it when you disconnect. They handle the token in memory for the few seconds each of those steps takes, encrypt it so that only your Mac can open it, and do not keep it: no token, sign-in code or client secret is ever written to our databases, logs or error reports in a form we or anyone else could read. Your Mac stores the token in its own encrypted credential store.

Where your Google data goes. The contents of your mail and calendar are fetched directly from Google by the Carabase software on your Mac, and stored and processed on your Mac. Our servers do not receive or store them when Carabase syncs.

When a cloud model works on your Google data. If you set Carabase to use a cloud model — to answer your questions, or for the background work that summarises and indexes what it syncs — the text selected for each request, which can include text from your mail and events, is sent to that model provider so it can do the work. If you use Carabase’s managed inference, those requests pass through our gateway on the way to OpenRouter, which routes them only to zero-data-retention endpoints that do not collect data. The gateway does not store or log what you send or receive; it keeps usage quantities (model class, tokens, cost) and, for 24 hours, a one-way digest of each request so a retried request is not billed twice. With a local model, your Google data never leaves your Mac.

What our servers keep about a Google connection. A record that the connection exists: its status, the permissions granted, when it was connected, refreshed or revoked, and a keyed one-way hash of your Google Account’s identifier. Your name, email address and profile details are discarded as soon as the account has been identified. The connection record, hash included, stays after you disconnect, so a reconnection is recognised as the same account, and is deleted when you close your Carabase account.

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

• We use Google user data only to provide the features you see in Carabase: your timeline, search, and answers to what you ask.
• We transfer it only to provide those features with your consent (the model provider you chose, as described above), for security purposes, to comply with applicable law, or as part of a merger, acquisition or sale of assets after obtaining your explicit prior consent.
• No one at Carabase reads it, unless you first ask us to look at a specific item, it is necessary for security purposes such as investigating a bug or abuse, or the law requires it.
• We do not sell it, transfer it to advertising platforms, data brokers or information resellers, use it for advertising, or use it to determine credit-worthiness or for lending.

Your Google data is never used to train a model. We do not use, transfer or retain data obtained through Google Workspace APIs to develop, improve or train generalised or non-personalised AI or machine-learning models, and the model providers we route managed inference to operate under zero-data-retention terms that forbid training on your content.

You can revoke Carabase’s access to your Google Account at any time from your Google Account’s third-party access settings, independent of anything we do. Disconnecting inside Carabase stops syncing immediately, deletes the stored credential on your Mac, and asks Google to revoke it. To delete what Carabase holds, see Deleting your data.

Who we rely on

• NetlifyServes this website and receives ordinary request logs.
• LoopsStores alpha-application emails and sends our messages.
• WorkOSHandles sign-in for the cloud services. Carabase remains the authority for your account, devices, and permissions.
• Google CloudHosts the cloud services (us-central1), encrypted at rest, including the broker that handles Google sign-in tokens in memory.
• OpenRouterRoutes managed inference to model providers on our allowlist.
• Model providersProcess the context selected for a request when you choose a cloud model.

If this list changes in a way that affects your data, we will update this page and tell alpha users directly.

Your rights

If you are in the EU, UK, California, or any jurisdiction with data-protection law, you have the right to ask what we have on you, correct it, delete it, or object to how we use it. Email hello@carabase.ai and we will handle it within 30 days. There is no form. There is no ticket. Just a human reply.

Changes

If we meaningfully change this policy, we will update the date above and, where practical, notify alpha users directly. We will never shrink your rights without notice.

Contact

Carabase is operated by Carabase Pty Ltd, Australia. Questions, requests, or complaints: hello@carabase.ai.