Version 2026-07-29
This is what Anchor holds about you, why it holds it, where it lives, and how to get it back or get rid of it. It is written to be read, not to be skimmed past.
What we hold
All of it, including the parts that are awkward to list.
Your account
Your email address, and either a password (stored only as a scrypt hash — we never hold the password itself) or a link to your Google sign-in. If you sign in with Google we ask Google for your email and nothing else.
How you like to learn
How comfortable you said you are with the technical side, whether you prefer reading, doing, watching or listening, and your language.
Your project, in your own words
Everything you told us in the interview, and every later revision of it. This is the spine of your course — it is why your lessons are about your work rather than a generic example.
The lessons written for you
Every lesson is generated for you and cached. Your project details run through the whole of it, so a lesson is personal data as much as your profile is — we treat it that way.
How you are getting on
Which sections you have worked through, and the confidence score you give yourself when you choose to. Nothing here is a grade and nothing is shown to anyone else.
What confused you
When something does not land, we record the concept and what you said about it. This is how the curriculum gets better — confusion is data about our writing, not about you.
What you built
The work you submit for feedback, every revision of it, and the feedback itself. Nothing is overwritten; each attempt is kept.
What you post to the cohort
Posts, comments and reactions, visible to everyone else in the cohort. Free text, so whatever you put there is held exactly as you wrote it. Be as careful there as you would be anywhere public.
Payment records
If you buy coaching, the record of that purchase. Not your card details — those go to the payment provider and never reach us.
Whether we may email you
One timestamp, set if you unsubscribe. Nothing else.
Your session
So you stay signed in. We store only a hash of the session token; the token itself lives in a cookie in your browser and nowhere else.
Files you attach during the interview
Not kept. A document or image you attach is passed into that one interview turn and discarded. It is never written to a database or to disk.
Why we hold it
To write your course. There is no catalogue here — every lesson is projected onto the project you described, and that only works if we hold the description. Beyond that: to run the cohort so you are not doing this alone, to prepare properly if you book a coaching session, and to see which of our own explanations keep failing so we can rewrite them.
We do not sell it, share it with advertisers, or use it to build a profile of you for anything other than teaching you.
Where it lives
In our own Postgres database, hosted in the EU. We run our own sign-in rather than handing your identity to a third party, so there is no identity provider holding your account except Google, and only if you chose Google.
The exception, stated plainly
Writing your lessons means sending your project description to an AI model, and the voice features send text to a speech service. Those calls are not currently pinned to EU-only processing — they may be handled outside the EU, including in the United States. We looked into this before accepting it, we accepted it for the alpha rather than overlooking it, and moving to EU-pinned processing is a known piece of work with a clear route. We would rather tell you than have you find out.
How long we keep it
- Your account and everything tied to it, for as long as your account exists. If you do not sign in for 24 months we delete it.
- What confused you, indefinitely — but see the next section, because we keep it after you leave.
- Purchase records for 6 years, because company accounting law requires it.
- Sessions expire on their own: 30 days signed in, 7 days otherwise.
The period for each category is written down in full in our data-retention policy, and this notice never states a period that document does not back.
What you can do about it
Take it with you
Download everything we hold about you as a single file, whenever you like. That includes the lessons written for you, which are often the part worth keeping.
Delete your account
One action, no support ticket, no waiting period. Your account, your project description, the lessons, your progress and what you built are removed.
What survives deletion, and why
Two things, and we would rather say so here than have you discover it. What confused you stays, with the link to you stripped out — those notes are how the curriculum improves for everyone who comes after, and unlinked they are no longer about you. Purchase records stay too, pseudonymised, because accounting law requires it and that requirement overrides your erasure request.
Your cohort posts also stay readable, with your name taken off them, so the conversations other people were part of do not fall apart. If a post contains something about you that you want gone, delete that post yourself before you close your account — then it goes with everything else.
Stop the emails
Every email has a one-click unsubscribe that works without signing in. You can also change it from your settings.
Export, delete and email settings all live on your settings page.
Getting in touch
Write to richard@digitalbricks.io. A person reads it. If you want your data, want it gone, or think something here is wrong, that is the address.
If you are not happy with how we have handled it, you have the right to complain to your national data-protection authority.
When this changes
If we change anything that matters — a new kind of data, a different retention period, a new service processing it — we bump the version at the top and ask you to read it again before you carry on. A changed notice nobody was shown again is not a notice anyone agreed to.