0Free tier
Readable content Coggy receives when you use Coggy Free.
Privacy Promise
You should know exactly what Coggy can and cannot see.
Private by default. Cloud by choice. I want the trade-offs to be obvious: what stays on your Mac, what gets encrypted, what cloud AI can briefly read, and what happens if you lose your recovery code.
Best default: Coggy Free sends us nothing. It runs on your Mac with on-device AI. You do not need an account, and Coggy cloud is not involved.
One deliberate exception: when you press Publish in Share, Coggy puts that one page, and nothing else, on the web at a link you can delete anytime.
EncryptedAt rest
With Coggy Pro, we store encrypted data, salts, wrapped keys, and billing counts. We cannot read the content at rest.
In memoryCloud AI
When you use cloud AI, your query and chosen context are briefly readable while the request is processed.
GoneIf lost
Lose both passphrase and recovery code, and there is no support reset. The data is unrecoverable.
Quick scan
What leaves your Mac?
The bars are just a visual guide. The labels below are the real promise.
Coggy Free
NothingNo readable content goes to Coggy. On-device AI only. No account required.
Encrypted Cloud Storage
Encrypted onlyOnly encrypted data and account details leave your Mac. Your readable content does not.
Cloud AI Request
Temporary processingIf you choose cloud AI, your query and context are briefly readable while we process the request.
Cloud AI request
What happens during a cloud AI request
Cloud AI is useful, but it has a real privacy cost. This is where that cost happens.
You choose what to send
Your Mac sends only the query and context you selected over TLS.
Plaintext in memory
Your query is readable in memory, for the duration of your request, while we call the model.
Provider cache
The model provider may cache the prompt for about five minutes under no-training terms.
Not saved as content
We keep usage counts and costs for billing. We do not keep the readable prompt or response as billing data.
Stored data ledger
Coggy Pro: zero-knowledge by architecture
When you create a Pro account, your Mac derives keys from your passphrase with Argon2id. The passphrase never leaves your machine.
Ciphertext
Your data is encrypted with XChaCha20-Poly1305. Only your devices can derive the keys.
Random salt
A public ingredient for key derivation. It does nothing without your passphrase.
Authentication derivative
A way to verify you know your passphrase without sending the passphrase to us.
Wrapped master keys
Your master key, locked under keys from your passphrase and recovery code. We can store it because we cannot open it.
Usage counts
Counts and costs for billing, never the content of what you asked or received.
The recovery rule
The real trade-off
Here is the catch: if you forget your passphrase and lose your 12-word recovery code, your encrypted data is gone. Not "call support" gone. Mathematically gone.
We cannot reset what we never had. That is the cost of privacy that does not depend on us.
Billing, precisely
Stripe handles cards. We store your email for login and usage counts for billing, not your prompts or responses.
Boring cryptography on purpose
The cryptography is intentionally boring: Argon2id, HKDF-SHA256, XChaCha20-Poly1305, Ed25519, and BIP-39 recovery codes. Standard pieces, no clever shortcuts.