LEGAL · VERSION 1.2 · 26 OCTOBER 2026
Privacy Policy
In short: we collect as little as we can and never sell it. Your cockpit's data is stored in the EU, in its own database. Stripe handles cards, and GitHub handles sign-in. There are no tracking cookies and no ads. You can download your data from your cockpit, or delete your account yourself at dovre.dev/account, or write to hello@dovre.dev.
This policy covers Dovre Cloud (dovre.dev and the cockpits under it). Dovre you run on your own machine or your own Cloudflare account sends us nothing.
1. Who is responsible
ANDREAS BERG DOTDEV (organisation number 937 794 355), a Norwegian sole proprietorship, is the controller for the personal data described here. Questions go to hello@dovre.dev.
2. What we process
- Your account. Your email address, your GitHub user id and login, and when you signed up.
- GitHub access. When you connect the Dovre GitHub App, we keep its access and refresh tokens, encrypted, along with the users and orgs you installed it on. The tokens let your cockpit read from GitHub and, once you confirm, write as you. You can revoke them on GitHub at any time.
- Your cockpit. Its address (yourname.dovre.dev), its members and their roles, and pending invites, which hold a GitHub username for up to 7 days.
- Billing. Your Stripe customer id and your plan's status, period, seats and trial dates. Stripe keeps your card, billing address and VAT ID. We never see your card number.
- Sign-in. Sessions, and short-lived sign-in codes and hand-offs. These are stored as hashes or random ids, never as passwords. Dovre has no passwords.
- Technical data. When you sign in, your IP address goes to Cloudflare Turnstile to stop bots, and into a counter that limits sign-in attempts. That counter is removed within 15 minutes. Cloudflare's request logs, which can include an IP address, are kept for a few days so we can fix errors.
3. Why, and on what basis
- To run the service you signed up for: sign-in, your cockpit, GitHub access, team members. Basis: contract (GDPR Art. 6(1)(b)).
- Billing and bookkeeping. Basis: contract, plus our legal duty under the Norwegian Bookkeeping Act (Art. 6(1)(c)).
- Security and preventing abuse (Turnstile, attempt limits, error logs). Basis: legitimate interest in keeping the service and its users safe (Art. 6(1)(f)).
- Emails about your account and plan, such as sign-in codes, trial and payment notices, limit warnings and changes to these policies. We don't send newsletters or marketing. Basis: contract.
4. Your cockpit's contents
Your cockpit stores what it fetches for you: pull requests, issues, checks and deploys from GitHub and the other apps you connect. It also stores your notes, a log of the actions you took (with the email address of the person who took them), and, if you use them, Bino's conversations and what the bridge reports from your own machines (agent session titles, prompts, summaries and costs). Some of this names other people, such as the authors of pull requests.
You decide what your cockpit connects to, so for this data you (or your team's owner) are the controller, and we process it on your behalf and only to run your cockpit. We don't read it, other than when you ask us to help or to keep the service safe. If you need a data processing agreement, write to hello@dovre.dev.
If you add a model provider's API key for Bino, your messages to Bino go from your cockpit straight to that provider (Anthropic, OpenAI or Google), under your own agreement with the provider. They don't pass through any other service of ours. The key is kept as an encrypted secret on your cockpit, and we never show it again.
5. Who we share it with
We use these processors, and no one else gets your data. We never sell it.
- Cloudflare. Hosting, the databases, sign-in emails, Turnstile and request logs.
- Stripe. Payments, invoices, tax and the billing portal.
- GitHub. Sign-in, and the GitHub App your cockpit acts through.
We may disclose data when the law requires it, for example to the tax authorities.
6. Where it is
Our account database, each cockpit's database and the exports we make for you are created in Cloudflare's EU jurisdiction, so they're stored in the EU. Cloudflare, Stripe and GitHub are US companies and may process some data, such as requests passing through Cloudflare's network, outside the EEA. Where they do, it's covered by the EU–US Data Privacy Framework or the EU's standard contractual clauses.
7. How long we keep it
| Data | Kept |
|---|---|
| Account and GitHub tokens | Until you delete your account, which you can do yourself at dovre.dev/account. That cancels your plan and deletes your cockpits right away. Tokens are dropped as soon as you revoke them on GitHub. |
| Sign-in session | 30 days, or until you sign out |
| Sign-in codes and hand-offs | 10 minutes at most, deleted once used |
| Sign-in attempt counter (IP) | 15 minutes |
| Team invites | 7 days, or until used or withdrawn |
| Your cockpit's data | While your plan runs. After the plan ends there are 30 days read-only, then we email you a link to an export and delete the cockpit 7 days later. |
| Exports you download from your cockpit | 7 days |
| The export we email when a plan ends | 14 days, so it stays available for 7 days after the cockpit is deleted |
| Backups | Deleted data is gone from our database backups within 30 days |
| Record of a deletion | Kept so we can show it was done. It holds an internal ID, what was deleted, why and when, and no name or email. |
| Invoices and payment records | As long as Norwegian bookkeeping law requires (five years) |
| Request logs | A few days (Cloudflare's standard retention) |
9. Your rights
You can ask for access to the personal data we hold about you, or a copy of it, and ask us to correct it, delete it, restrict how we use it, or move it elsewhere. You can also object to processing based on legitimate interest. You can download your cockpit's data from its Plan and team page, and delete your account yourself at dovre.dev/account. For anything else, write to hello@dovre.dev and we'll answer within 30 days. If you think we've got it wrong, you can complain to the Norwegian Data Protection Authority (Datatilsynet) or to the authority where you live.
10. Changes
If we make a change that matters to you, we'll email you before it takes effect. The version and date at the top of this page show which text applies.