Data handling and security
Last updated 19 November 2026
What you enter
In the Studio you can enter:
- An industry, report type, report name and audience
- Your BI tool and the names of your data sources
- Column names, table names or a CREATE TABLE script
- KPI names, targets and RAG thresholds
- Free-text notes about what the report should do
- Meeting notes, transcripts or emails, if you choose Start from your notes (see below)
We do not ask for, and you should not enter, data rows, customer records or personal information. To sign in we also need your email address.
Where it goes
When you click Generate design pack, what you entered is sent from your browser to our server on Vercel, and from there to Anthropic's Claude API (model: Claude Opus 5.5) to write the blueprint. If Anthropic's safety systems decline a request, it may be retried automatically on another Claude model. The AI Design Studio sends the generated blueprint to the same API to draw page mockups.
Anthropic does not use inputs or outputs from its commercial API to train its models by default. Anthropic keeps API inputs and outputs for a limited period for safety and abuse monitoring and then deletes them. See Anthropic's Privacy Center for current details.
Meeting notes and transcripts
With Start from your notes you can paste notes or upload a .txt, .md, .docx, .pdf, .vtt or .srt file, and Blueprint BI pulls a brief out of them for you to check.
- Remove personal details first. Names and roles aren't needed, only what people asked for. Before anything is sent, your browser checks the text for email addresses, UK phone numbers and postcodes and offers to replace them with [email], [phone] and [postcode]. The check can't find names, so please remove those yourself.
- Files. Text, Markdown and transcript files are read in your browser. Word and PDF files are sent to our server, turned into text in memory and discarded straight away: the file itself is never saved and never sent to the AI.
- Where the text goes. The text of your notes is sent to Anthropic's Claude API (model: Claude Haiku 5.5) once, to be read into a brief. Anthropic's retention policy, described above, applies.
- What we keep. We don't store your notes or the uploaded file anywhere: not in our database and not in our logs. Only the brief you review and generate from is saved, as the inputs of that design pack. The short quotes shown next to each field stay in your browser and aren't saved.
- Counts, not content. We record how the feature is used (for example how many KPIs and gaps were found) as numbers in our own database. No text from your notes is recorded, and no third-party analytics are involved.
What we store
Our database is hosted by Supabase in London (AWS eu-west-2). We store:
- Your account: your email address, your plan and when you joined. We use your email to send sign-in links, which are delivered by our email provider, Resend. There are no passwords.
- Your blueprints: the inputs you entered and the blueprint Claude generated (each version, if you edit and regenerate), your KPI icon choices, any review links with their comments, answers and approvals, and any AI Design Studio page mockups, so you can reopen them without paying for them again.
- A usage log: for each AI request, the time, stage, model, number of tokens, cost and duration, plus a one-way hash of your IP address used only to stop abuse. The log does not contain what you typed.
- Feature usage counts: for Start from your notes, numbers such as how many KPIs, gaps and questions were found and whether a design pack was generated, linked to your account. Never any text.
- Server logs: our hosting provider, Vercel, records standard request logs (such as IP address, time and page requested) and error messages for a short period.
We keep your account and blueprints until you delete them. Usage log entries are kept after an account is deleted, but no longer linked to you, so we can track overall costs.
Blueprint BI uses only the cookies needed to keep you signed in. It does not use third-party analytics or advertising trackers.
Review links
On Pro you can share a design pack with your client for review. Here is how review links work and what they store.
- Who can see it. Anyone who has the link can read the design pack, so share it only with the people reviewing it. Each link is a long random address that can't be guessed, and review pages are kept out of search engines.
- Revoking and expiry. You can revoke a link at any time in the pack's Review tab; it stops working straight away. You can also set links to expire after 7, 30 or 90 days.
- What we store about reviewers. Reviewers don't need an account. When they comment, answer an open question or approve, we store the name and email address they enter, what they wrote, which version they approved and when, and a one-way hash of their IP address used only to limit abuse. The pack's owner sees all of this; other reviewers see names but not email addresses.
- Client name and logo. If you add them when sharing, they are stored with the link and shown on the review page and the PDF.
- Emails. We email you when a reviewer comments, answers or approves (you can turn this off), and email reviewers who took part when you share a new version. These emails contain names, the pack title and a link, never what anyone wrote. Every reviewer email has a link to stop further emails about that pack. Emails are sent by our email provider, Resend.
- How long. Review data is kept with the design pack and deleted when you delete the pack or your account. Revoking a link stops access but keeps the comments and approvals already given, so you have a record of the sign-off.
How to delete your data
- Delete a design pack with the bin icon next to it in the Studio sidebar. All its versions, mockups, review links, comments and approvals are deleted with it.
- Delete your whole account with Delete my account at the bottom of the Studio sidebar. This permanently removes your email, plan, blueprints and mockups straight away.
- Or email milestone@milestonebi.com and we will do it for you.
Security
- All traffic is encrypted with HTTPS.
- The Claude API key and database secret key are held only on the server and are never sent to your browser.
- Database row level security means each signed-in user can read only their own records.
- Plans, usage limits and rate limits are enforced on the server.
- AI Design Studio mockups are shown in a sandboxed frame that cannot run scripts.
Questions
Email milestone@milestonebi.com. See also our privacy policy and terms.