Privacy Policy
Last updated 31 October 2026
This policy explains what Burhan, operated by Mustafa Alfar, stores about you and the people in your workspace, why, and for how long. It is written to be read, not skimmed; if anything is unclear, write to hello@useburhan.com.
1. Account data
- What: your name, email address, password (hashed by our sign-in provider; we never see it), workspace name, and who invited whom.
- Why: to sign you in, run your workspace and contact you about the service or your bill.
- How long: until you delete your account. Billing records are kept as long as tax law requires.
2. What you upload and configure
- Documents (specs, stories, PDFs): stored as extracted text so Burhan can read them and draft journeys. Kept until you remove the document or delete the project.
- Journeys and their edit history (who changed what, when).
- Environments: the URLs you ask us to test.
- Test accounts: the username and password of each test account. Passwords are encrypted at rest with a key held only on our servers, are never shown back in the app, and are typed into the application under test only by the runner, never shown to the AI. Deleted when you delete the account, project or workspace.
- Your Anthropic API key, if you add one: encrypted at rest the same way, shown only by its last four characters, used only to make AI calls for your workspace, removable at any time.
3. What a run records
When Burhan walks a journey it keeps evidence so a person can check the result:
- a screenshot at the end of each step and a video of the whole run;
- the application's API calls during the run (URL, status, timing, and response bodies, with fields that look like tokens, passwords or keys replaced by “[hidden]” before storage);
- the page outline the AI saw, the AI's notes, console errors, and timing and cost.
This evidence can include whatever your application shows to the test account, such as test customers' names. Use test data in test environments. Evidence is kept with the run until the run, journey, project or workspace is deleted. Videos and screenshots are stored in a private bucket and served only through short-lived signed links to members of your workspace.
4. AI processing
To draft journeys and judge results, we send relevant parts of your documents, journeys and the page the runner sees to Anthropic's API. Anthropic processes it under its API terms and, by its stated policy at the time of writing, does not train models on API inputs and outputs. If you use your own Anthropic key, those calls happen under your own agreement with Anthropic. We log each call's purpose, model, token counts and cost, but not its content.
How Burhan improves. Burhan learns from how it is used: when journeys are edited or removed, when a red result is marked “not a bug”, and when runs get stuck. From these it writes short lessons that improve how it drafts and runs tests. A lesson used for every customer is written in general terms and never contains your names, links, emails, documents, screenshots or data. A lesson about your app is used only for your project. Our team reviews every lesson before it is used. We do not use your content to train AI models.
5. Payments
Payments are handled by Stripe. We never see or store your card number; we keep Stripe's customer and subscription identifiers, your plan, and invoice records.
6. Who else processes your data
| Provider | Purpose | Region |
|---|---|---|
| Supabase | Database, file storage (videos, screenshots) and sign-in | EU / US (per project settings) |
| Vercel | Hosting the web app | Global edge, US origin |
| Railway | Running the test browser (runner worker) | US |
| Anthropic | AI that reads documents, drafts journeys and judges results | US |
| Stripe | Payments and invoices | US / EU |
| Sentry | Error reports from the app, to fix bugs (no IP, cookies, emails or names sent) | EU (Frankfurt) |
| PostHog | Product analytics and session replays, with your consent (no names sent) | EU (Frankfurt) |
| Meta Platforms | Measuring our Facebook and Instagram ads, only after "Accept all" (hashed account id, no name) | EU / US |
| Measuring our LinkedIn ads, only after "Accept all" | EU / US |
We do not sell your data. We share it only with these providers, to run the service and, if you choose "Accept all", to measure our own ads, or when the law requires. We never use what is inside your workspace (documents, journeys, runs, evidence) for advertising.
7. Cookies
We use the cookies needed to keep you signed in and to remember your workspace and language. With your consent, we also use PostHog analytics cookies to see how Burhan is used: which pages are visited, which steps people complete, fail or leave (for example: a setup step, saving a journey, choosing a plan), and session replays with every form field masked. Events carry your account id, workspace id and email address, never your name or anything you type. With the same consent, Google Analytics counts visits and where they come from: it receives page views and the referring site only, with IP addresses anonymised, and never loads before you accept. Until you choose, and if you decline, we count the visit without cookies: the page and your country (read from the request, then the IP address is dropped), nothing stored on your device that follows you. Separately, we note which ad or website brought you here (the campaign names in the link and the referring site, no personal data) in our own cookie, and keep it on your account when you sign up, so we know which ads work.
Only if you choose "Accept all", the Meta pixel and the LinkedIn Insight Tag also load, so Meta and LinkedIn can tell us which of our ads led to visits and sign-ups and show our ads to people like those who visited. They set their own advertising cookies. When you sign up after "Accept all", our server tells Meta that a sign-up happened, with your account id in hashed form, your browser's IP address and user agent, and Meta's own cookie ids; never your name or anything you type in Burhan. "Analytics only" and "Reject" keep all of this off. One exception, so we know which ad works: if you arrived by clicking one of our Meta ads and then sign up, our server tells Meta that this ad click led to a sign-up, sending only the click id Meta put in the ad link, your browser's user agent and your account id in hashed form; no IP address, no cookies, no email, nothing you type in Burhan. To change your answer, clear this site's data in your browser and choose again. We never sell data.
Inside the dashboard, once you are signed in, we record how you use it (session replays with every form field masked, plus the steps above) to see where Burhan is confusing and fix it, This uses PostHog's analytics cookies while you are in the dashboard, even if you did not accept them on the website. You can turn these cookies and the recording off any time in Your account → Privacy. On the public website, visitors in the EU, the EEA, the UK and Switzerland are only recorded if they accept cookies. Everywhere else, the website uses these analytics cookies and session replays (form fields masked) from the first page, and a notice says so with an Opt out button; opting out stops it on that browser. Advertising tags (Meta, LinkedIn) still load only after "Accept all".
8. Where data is stored
Your data is stored by the providers above in the regions listed. If you need your data kept in a specific region, tell us before you start; we will say whether we can do it.
9. Your rights
- Access and export: everything in your workspace is visible in the app; ask us for an export and we will provide one.
- Correction: edit your profile, documents and journeys in the app.
- Deletion: deleting a project removes its documents, journeys, runs and evidence; deleting your account removes your personal data. Backups are overwritten within 30 days.
- Complaint: if you are in the EU/EEA or UK you can complain to your data protection authority; we would rather you wrote to us first.
10. Security
Encrypted transport everywhere, credentials and keys encrypted at rest, access limited to members of your workspace, private storage with signed links, and secrets redacted from recorded API responses. If we learn of a breach affecting your data we will tell the workspace owner without undue delay.
11. Children
Burhan is for businesses and is not directed at children under 16.
12. Changes
We will email the workspace owner about material changes to this policy before they take effect.
Contact
Mustafa Alfar · hello@useburhan.com