Privacy Policy

Codeep is built to keep your code, your prompts, and your API keys yours. This page is the plain-English version of what that means in practice — what we store, where it lives, who can see it, and what we don't do.

Who this applies to

This policy covers everyone using the Codeep ecosystem: the CLI (npm package codeep), the macOS app, the iOS app, the VS Code extension, and the codeep.dev dashboard. Wherever the rules differ by client, we call it out below.

Your API keys

Codeep talks to LLM providers (Anthropic, OpenAI, Google, Z.AI, DeepSeek, MiniMax, Ollama) using API keys you provide. Where those keys live depends on the client:

• CLI: a config file at ~/.codeep/config.json, readable only by you (filesystem permissions).
• macOS / iOS: the system Keychain, with iCloud Keychain sync turned on so the same key reaches your other Apple devices. Codeep never sees the plaintext once stored — we read it back through the OS, which controls access.
• codeep.dev (optional):if you choose to mirror keys across clients via the dashboard, the ciphertext sits in our database, encrypted at rest. The decryption key is derived from your account and never leaves the server boundary; humans on our side can't read your stored keys.

What you can do

You can delete a key from any client at any time. Deleting from one client doesn't auto-delete from others — that's deliberate, so a typo on one device doesn't wipe your setup elsewhere. To purge everywhere, sign in to codeep.dev and clear from there; the next pull on each client removes the local copy.

Your conversations

Chat history (your prompts, assistant replies, tool calls) lives on the device that produced it. The CLI writes to ~/.codeep/sessions/; the Mac and iOS apps write to ~/Library/Application Support/Codeep/conversations.jsonand the equivalent iOS sandbox.

If you sign in to codeep.dev: we replicate your sessions to our database so they reappear on your other clients (your Mac, your iPhone, the dashboard). The replicated copy contains the same messages you saw locally — including tool inputs and outputs.

If you don't sign in:conversations stay on the device. We don't see them, can't retrieve them, and have no way to back them up if you lose the device.

Project memory

When you open a project (folder) in the CLI, the Mac app, or the VS Code extension, Codeep creates a .codeep/directory inside that folder with a manifest and any per-project notes you write. This stays in your project — it's not synced to our server unless you explicitly enable project sync from codeep.dev.

Account info

You sign in to codeep.dev with GitHub OAuth. We store:

• Your GitHub username and numeric user ID (so we can map sessions to you).
• Your email address (for service notifications — we don't market to it).
• A sync token (a long random string we issue at sign-in; it goes in the device Keychain).

We don't request scopes beyond read:user and user:email. We can't see your repos or any private GitHub data through this sign-in.

When you talk to an LLM

The agent sends your messages directly from your device to the LLM provider you chose (Anthropic, OpenAI, etc.). Those messages do not pass through our servers. Provider-side, each company has its own data policy — most retain prompts for short periods for abuse monitoring; some let you opt out via their dashboards.

If you use the codeep.dev session sync, the messages get a secondtrip — to our database, for cross-device replay. That copy is encrypted in transit (HTTPS) and at rest in the database. It's readable by you when you sign in from another client, and (in principle) by our infrastructure team when debugging an outage. We don't share it with anyone else.

Local network access (iOS)

The iOS app supports pointing at an Ollama daemon on a Mac on the same network (e.g. http://your-mac.local:11434/v1). When you set that URL in Settings, iOS may prompt you for “Local Network” access — that's the system permission required to send a packet to your LAN; we don't scan the network or discover devices.

What we don't do

• No analytics SDKs.No Mixpanel, no Amplitude, no Segment, no Firebase Analytics, no Google Analytics. The apps don't phone home with usage telemetry.
• No ad networks. No tracking pixels, no ad SDKs.
• No third-party crash reporters by default. Crashes go to Apple via TestFlight / standard Apple tooling and to codeep.dev's server logs for the dashboard side — no Sentry, Bugsnag, etc., unless we add one with a separate release-notes mention.
• No tracking of your code. The CLI and apps read your files locally to answer your prompts; the contents never leave the device except as input to the LLM provider you chose, or — if you opted in — as part of a session synced to codeep.dev.
• No data sale.We don't sell any of the above to anyone.

Your rights

• Export everything. From the dashboard you can pull every session as JSON. Mac and iOS additionally let you export individual conversations as Markdown.
• Delete your account. Sign in to codeep.dev → Account → Delete. This permanently removes your sessions, stored keys, and account record from our database, usually within 24 hours. Local copies on your devices stay where they are until you delete the apps.
• Use the apps without an account. Sign-in is optional. The CLI and the native apps work fully offline-of-our-server; you only need it for cross-device sync.

Children's privacy

Codeep isn't designed for users under 13 and we don't knowingly collect data from anyone in that age range. If we learn we have, we'll delete it.

Changes to this policy

When we change anything material, the “Last updated” date at the top changes, and we'll surface the change in the in-app release notes. We won't add new categories of data collection without notice.

Contact

Questions, data requests, account deletion outside the dashboard: [email protected]. The source code for the apps is public — read it for yourself at github.com/VladoIvankovic.