Privacy policy

Darce runs on your computer. This page explains exactly what leaves it, where it goes, and what we keep.

Updated October 9, 2026

Darce (the CLI at npm darce-cli, the API at api.darce.dev and this website) is operated by Amer Sarhan. Questions about this policy: privacy@darce.dev.

The short version

  • Your code and prompts go to the model provider you pick, through our API. We don't store them.
  • We keep your email, your plan, and counts of requests, tokens and their cost, so we can run your account and bill you.
  • The CLI sends no telemetry. Undo snapshots, sessions and the brain view stay on your computer.
  • You can delete your account and its usage history at any time from the dashboard.

What the CLI sends, and to whom

To answer a request, Darce sends your message, the parts of files it reads, and the output of commands it runs to api.darce.dev. Our API passes them to OpenRouter, which routes them to the provider of the model you chose (for example Anthropic, OpenAI, Google, Alibaba or DeepSeek). Those companies process the content under their own policies. Before anything is sent, Darce removes secrets it recognises from command output and withholds secret environment variables from the commands it runs.

Some features send a little more, only when you use them:

  • Command check. Before running a script with an innocent name, Darce may send the command and the script's source to a small classifier model (TypeSafe) to check whether it reaches outside your machine.
  • Voice (/voice on). A short summary of what Darce is doing goes to a model that writes one sentence, and that sentence goes to ElevenLabs to be spoken.
  • Images. Your image prompt goes to the image model you use, through OpenRouter.

Our API reads the content only to forward it. It doesn't log or store the text of your prompts, files or answers.

What we store

  • Account: email address, a hashed password (bcrypt), your API key, your plan, and when you signed up.
  • Usage: for each request, the model, the number of tokens, its cost and the time. No content.
  • Payments: handled by Stripe. We store your Stripe customer and subscription IDs, never card details.
  • Email: sent through Resend. Account emails (confirming your address, password resets, plan changes, a note when your allowance runs out) always arrive. For your first two weeks you also get a few short tips and a note from Amer, plus release emails later; every one has an unsubscribe link. We keep a log of which emails were sent and whether you confirmed your address.
  • Trial keys: "Try it now" creates an anonymous trial account with the same usage data and no email.

What stays on your computer

Your API key (in ~/.darcerc, readable only by you), session history, saved memory and logs (in ~/.darce), undo snapshots (private git refs in your repository) and the /brain view (served on 127.0.0.1 only). We can't see any of it.

This website

The site uses Google Analytics to count visits and see which pages are useful, which sets cookies. It's hosted on Vercel, which keeps standard request logs. The dashboard stores your API key in your browser's local storage so you stay signed in.

How long we keep it

Account and usage data are kept while your account exists. When you delete your account (Dashboard → Settings), your account, API key and usage history are deleted. Payment records Stripe must keep for tax and accounting stay with Stripe.

Your choices

You can see your usage in the dashboard, change your password, cancel your plan and delete your account there. For anything else, including a copy of your data, email privacy@darce.dev.

Children

Darce is not meant for anyone under 16.

Changes

If this policy changes in a way that matters, we'll say so in the changelog and update the date above.