What Coggy collects, and why.

Coggy, Inc. is a Delaware corporation and the controller of the data described here.

Post: 350 E 400 S, STE 54472, Salt Lake City, UT 84111, United States. Email: help@coggy.ai. The postal address is a mail suite that is checked rarely, so email is the route that reaches us.

This page covers coggy.ai — the waitlist, the account you can sign into at coggy.ai/account, and the ordinary logs that come with running a website — and the Coggy apps for Mac, iPhone, and Apple Watch, including the cloud features you choose and paid subscriptions.

The Privacy Promise is the product document about your content: it goes further into what stays on your devices and what an optional cloud step can read. Coggy is in private alpha, and this page changes as the product does.

When you join the waitlist we collect your email address, which page you signed up from, and the campaign labels carried by the link you arrived on, if any. We use them to email you about launch and about alpha invitations, and for nothing else.

Resend, our email provider, stores the list and sends the mail on our behalf. Every email carries an unsubscribe link, and unsubscribing stops the mail.

Once an address has unsubscribed, submitting the form again changes nothing: nobody can put you back on the list against your wishes, and you cannot re-subscribe yourself by accident. To re-join, email help@coggy.ai. Unsubscribing keeps your address on the list marked as unsubscribed, which is what makes it stay unsubscribed. Ask us to delete it and we delete it.

An account holds your email address, a random salt, an authentication derivative of your password, and usage counts for your plan's limits. Your password and your encryption keys are derived on your device and never sent to us, which is why we cannot read the content you store.

Changing your passphrase takes your recovery code, and a credential step-up is good for ten minutes. We keep the account while you have one. Ask us to delete it and we delete it.

Coggy's default is that your content stays on your device. Content leaves it when you choose a step that sends it, and each of those steps names what it is about to send before it goes.

• Cloud transcription sends the audio you are transcribing: that audio goes to our account service and to OpenAI, which transcribes it.
• Cloud AI sends your question and the memory context you picked for it to a third-party model provider — Anthropic for Claude, OpenAI for Codex — and it is readable to that provider while the request runs.
• Publishing a page sends the page you publish to our publish service.

Agreeing to a policy is not the same as choosing a cloud step, and it does not stand in for one.

Coggy's memory service runs on your own Mac, on the loopback interface, for the one person signed in to that Mac. It is not part of the iPhone app. It holds the most personal material in the product, so its rules are here in full.

Before launch, and as a condition of launch: the memory service requires a local secret and checks the host on every request, so nothing else on your machine or network can read or change your memory; Claude Code conversations are ingested only from projects you opt in, one project at a time; speech that did not wake Coggy is not kept; where a source records consent and consent was declined, the content is rejected as it is written rather than filtered as it is read; deleting a memory item stays inside your vault; and a model key you store is never handed back out.

Those are the rules of the locked-down build, which is being prepared now. They are not yet true of a build running on a Mac today, and this page will drop the qualification only once that build ships.

We do not use identifiable content of yours to train or fine-tune models, and nobody at Coggy reads your content to improve the product. We count things — how often a feature runs, how often it fails — as aggregate, de-identified statistics.

The site runs no analytics and no advertising trackers, loads no third-party fonts, and sets no cookies on the public pages. We do not sell your data, and we do not share it with anyone for their own purposes.

Billing is not open yet. When it opens, Stripe runs checkout and the billing portal on the web and Mac, and Apple runs in-app purchases on iPhone. Card numbers go to Stripe or to Apple and never to Coggy, and the account page can send you to Stripe's billing portal and nowhere else.

Vercel hosts coggy.ai and records ordinary request logs, including IP addresses, which we use to keep the site running and to look into abuse. The password-gated preview site sets one cookie so testers do not retype the password; it carries no personal data.

We keep personal data only while it is doing the job it was collected for, and then we delete it. Where a fixed period genuinely applies, this page will name it rather than leave you guessing.

You can end your account at any time, and it takes effect immediately. To have your data deleted, email help@coggy.ai. After a 30-day grace period the account and its data are deleted on our retention schedule, and if a deletion fails, that same address is the one that gets it fixed.

We will not claim more than that. Asking for deletion is not the same as deletion having finished everywhere, and some copies are out of our reach: files you exported or shared, copies held by someone you sent them to, and records a provider or the law requires us to keep.

You can ask to see what we hold, to correct it, to receive a copy, or to have it deleted, and you can withdraw consent or unsubscribe at any time.

In the UK and EU you also have the rights to restriction, portability, and objection under the GDPR, and you can complain to your supervisory authority. Where the GDPR applies, our legal basis for account data and for cloud transcription is performing our contract with you. Email help@coggy.ai and we will act on it. There is no charge and no form to fill in.

Coggy is not for anyone under 13, or under the higher minimum age your country sets.

Coggy is a United States company, and the providers named above process data in the United States.

The date at the top of this page is the date of its last change. If a change affects what we collect or who processes it, we will say so here before it takes effect.