Privacy policy

Last updated 12 October 2026. Questions: hello@burgr.ai

Burgr tells your software which AI model to call for each request. This page says what we handle to do that, why, and for how long. The short version: your AI provider keys never reach us, your prompts are analysed but not stored, and we keep routing metadata, not text.

What we keep

• Your account: your email address and name from the sign-in provider you used (Google, Microsoft or GitHub), which provider it was, and your organization's name, members and plan. We do not store passwords: there are none.
• API keys: only a fingerprint of each Burgr API key and its first few characters, so we can recognise it. The full key is shown to you once and cannot be recovered.
• A record of each routing call: the time, which model and provider we recommended, the difficulty tier and use case we judged, the estimated cost, and whether governance checks flagged anything (the names of the checks, not the text). No prompt text, messages or tool contents are stored. A repeated task is recognised by a one-way fingerprint of its system prompt, so the prompt itself is not kept.
• Answer-quality reports, if you turn them on: only flags such as the finish reason, whether a check passed, and token probabilities. Never the answer text.
• Your settings: your stack, pinned tasks, governance preferences and saved criteria.
• Payments: if you subscribe, you enter your card on the secure pages of our payment processor, Stripe. Card numbers go to Stripe and never reach Burgr. We keep a Stripe customer ID, the subscription ID, the plan, the billing interval, the status and the period dates.

How long

Routing records and quality reports are kept for 13 months and then deleted automatically. Your account, settings and billing record are kept until you delete your account. Stripe keeps its own records as required by law.

What we do not have

We never receive your OpenAI, Anthropic, Google or other provider keys. Burgr answers "which model?" and your software then calls the model itself, with your key. The model's answer never passes through Burgr. The optional project scanner runs on your own computer and sends only model names, never your code.

Who processes the text of a request

• When your software asks Burgr to route a request, the text you send for analysis is read by Burgr's own request analyzer, which runs on a private service. It is used to judge difficulty, use case and the governance checks, and it is not stored.
• If that service is unavailable, a backup analysis service run by a cloud provider on our behalf may read the same text for that one decision. While the backup is in use, the text goes to that provider, which does not promise zero retention. If neither is available, Burgr falls back to simple rules that read only the shape of the request.
• If you send a request without an account (the demo on our website), the same applies, and no text is stored.

Where it runs, and who helps us run it

Burgr is hosted on Microsoft Azure in Canada. Account and routing records are kept in a PostgreSQL database there. Our domain's DNS is on Cloudflare (traffic is not routed through Cloudflare). Payments are processed by Stripe. You sign in through Google, Microsoft or GitHub, which tell us your name and verified email and nothing else. Our pages load fonts from Google Fonts, so your browser contacts Google when a page opens.

We work out a visitor's country from their IP address on our own server, only to show prices in Canadian or US dollars. The address is not stored and not sent anywhere. IP addresses are also held in memory for a minute at a time to limit abuse, and are not written to our database.

Cookies and local storage

We set one cookie, a sign-in session cookie, which is needed to keep you signed in. We do not use advertising or tracking cookies. Your browser's local storage remembers your display choices, such as light or dark mode and your currency.

Google user data

If you sign in with Google, we receive your email address, name and Google account ID to create and recognise your account. We use them for nothing else. We do not sell them, share them with anyone for advertising, or use them for anything unrelated to running your Burgr account. Burgr's use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements.

Your choices

You can delete keys, settings and pins in the console, and turn off answer-quality reports and governance checks at any time. To delete your account and everything linked to it, write to hello@burgr.ai. We do not sell data.

Security

Connections use HTTPS. API keys and sessions are stored only as one-way hashes. Each organization can see only its own data. No system is perfectly secure, so please tell us at hello@burgr.ai if you see a problem.