Digital Bricks Training

Your data

Version 2026-09-08

This is what Digital Bricks Training 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 name, your email address, and — if you use it — a link to your Google sign-in. There is no password: signing in means asking us for a link, and we email you one that works once and lasts about fifteen minutes. We hold a one-way hash of each of those links until it expires, never the link itself. If you sign in with Google we ask Google for your email and nothing else. Your name is only ever shown to someone else if you are coaching them: it signs the notes and sessions your learners read, so they know who wrote them. Your email address is never shown to them.

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.

What a coach told us about you, if one invited you

If a coach or trainer signed you up rather than you finding us yourself, they described you and your work to us before you had an account — what you are trying to build, what you already know, and which ideas they think you need first. We keep that, and the programme they put together from it. If they emailed you the invitation from here rather than sending it themselves, we also keep the address they sent it to and when it went. You can read every word of it in your export, it is yours to change once you are signed in, and deleting your account deletes it.

The lessons written for you

Most lessons are 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. If a coach or trainer is working with you, they can also rewrite one of your lessons themselves — the words, the blocks, all of it. It stays yours alone: rewriting your copy changes nothing for anybody else. When they have, the lesson says so at the top and names them, because a lesson your coach wrote for you is a better lesson and you should know which is which. From that point the engine leaves that one alone rather than rewriting it as your project moves on. Every version we have ever held for you is in the file you can download, along with who last changed it and when.

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. Who can see it is the next section.

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. If a coach is working with you, they can read it — see the next section.

What your coach writes about you

If a coach or trainer is working with you, they can set up a programme for you: what to call it, the day it starts, and the day the two of you agreed it would end. You see all three on your course page, and they are in the file you can download along with who set it up and when. The agreed end is what the pace line on your page measures against; it is a date you agreed, not a deadline anything enforces, and a programme carries on exactly as before once it has gone by — your coach decides when a programme is finished, not the calendar. When it is finished they can file it away, which takes it off the list of what you are working on now and changes nothing else: the whole of it — the lessons, the meetings, the work you sent in, the notes — stays where it is, and you can still read all of it whenever you want, exactly as they can. You can be on more than one at a time, and coming back later for something new gives you a second one rather than changing the first. They can also write notes about how you are getting on, and record the sessions you have together — when you meet, for how long, and what happened. A session can be with you alone or with a group you are part of, and they can attach a short list of things to look at before it. Most of what they write is written for you: those notes appear on your course page and in the file you can download, exactly as your coach wrote them, signed with their name, and each one says who it was written for. Some of it is not. A coach can also keep a note for their own use while they are working out how to help you — thinking out loud about what might be getting in your way, the kind of thing they would say to a colleague rather than to you. Those notes are not on your course page and they are not in the file you can download. We are telling you the category exists because you should know it does, not because there is anything hidden about you being decided in it: your coach chooses that for each note, one note at a time, and sharing is what happens unless they say otherwise. Whether you had a session, when, for how long and what was agreed is always yours to read — a meeting is never hidden, only a coach’s own working note about one can be. The prep list is the same list your coach is looking at — it can name a lesson or a piece of work they have already set you, it is a suggestion of what to do next, never a deadline, and nothing on it marks you as behind. They can also set out what you are working towards — the things you have agreed you will produce — in their own words. Those appear on your course page as your objectives, and in the file you can download, along with who set them and when. They can also say which parts of your programme an objective needs, which shapes what gets planned for you. When you send work in, we record which objective it was answering, so you and your coach can find it later — and when nothing obvious fits, we record nothing rather than guess. Nothing anywhere records an objective as finished or unfinished: there is no tally and no pass mark on any of it, and nothing is ever marked complete on your behalf. Your coach can say where they think you are on the things the two of you agreed to work on — that is the next section, and it is always against a target you agreed together, never a mark on a piece of work. When a coach retires an objective, it stops being counted but your own answers under it stay exactly where they were. When you delete your account, your objectives — including the retired ones — go with it, as do your own notes and your one-to-one sessions; a group session is a record of a meeting other people were also at, so that row stays and no longer mentions you. That is true of every note your coach wrote about you, the ones kept for their own use included: they are still about you, so they go when you go.

Your reviews, and what you are working towards

If a coach or trainer is working with you, a programme comes with four reviews built in: one at the start, one around halfway, one at the close, and one a few weeks afterwards to see what actually changed in your work. Your coach can also record a check-in at any date they like, as many as are useful — those sit alongside the four and replace none of them, so a check-in never means one of the four has been dropped. All of them are on your course page, with their dates, whether or not anyone has written them up yet — an unwritten review is your coach's to do, never something you are late for, and nothing anywhere is locked or held back because one is outstanding. The two of you can also agree a short list of things you are working on — three or four, in their words and yours — and for each one a number out of ten you have agreed you are heading for. Your coach then says where they would put you on each, out of that agreed number, when you meet and at each review. You see all of it: the things you agreed, the number you are heading for, and every score they have given, on your own page and in the file you can download. Two things about those numbers are worth saying plainly. A number is never recorded on its own — your coach cannot save one without writing down what they mean by it, and that write-up is written for you to read. And it is only ever measured against the target the two of you agreed: it is not a mark on a piece of work, it is not compared with anybody else, nobody is ranked, and nothing you can or cannot do depends on it. It is a human being saying what they think, out loud, so you can both see whether it is going where you wanted. A coach can also keep their own working note on a review, the way they can on anything else, and you do not see those — but the numbers and the dates are never in that half. When you delete your account, your reviews, the things you agreed and every score go with it.

Work your coach sets you

A coach or trainer can set you a piece of work with a date on it — a title, a brief in their own words, what they will look at it against, and how to send it back. You see all of it, exactly as they wrote it, and so does anyone else it was set for if it was set for a group. What you send in is kept, every revision of it, and nothing is overwritten. A date that has gone past changes nothing: it stays on your page with its date shown, nothing locks, nothing is marked late and nothing anywhere records a piece of work as missed or failed. If the person coaching you asks the assistant to look at what you sent, you get the same named-criteria feedback the rest of the product gives — never a mark and never a number. When you delete your account, the work your coach set you alone goes with it, and so does everything you sent in against any of it; a brief set for a whole group stays, because it was never only about you.

What you and your coach say to each other

You can send a question to the coach working with you, and they can answer. We hold what each of you wrote, when, and which thing on your programme it was about — a lesson, a meeting, a review, something your coach asked you for, or something you sent in — when you started it from one. Both sides are held exactly as you each typed them. We also hold whether the other person has opened a message yet, so you can tell whether a question has been seen; neither of you is shown the moment the other read anything. When you send a question, we email your coach to tell them, and that email contains what you wrote, so your words go through the company that sends our email and into your coach's mailbox. If nobody is set as your coach, it goes to the people who run this. It works the same way in the other direction: when your coach answers, we email you to say so, and that email carries their newest message and a link that opens the step it was about. Only that one message goes — never the rest of the conversation, which stays here. If you have asked us not to email you we don't send it, and their answer is waiting for you the next time you open the product. Nothing you write here is sent to a model, and nothing here is used to write your lessons — a question you addressed to a person goes to that person. When you delete your account the whole conversation goes, their side of it as well as yours.

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.

What computer you build on

If you run the setup check, we keep what it found: your operating system, your shell, whether Node, Git or Docker are installed, and the folder name you gave for your project. We keep the answers, not the text you pasted in — that goes to the AI model that reads it and is then discarded, because a terminal paste is the single most likely place for a password or a key to turn up.

The starter documents we write for you

When you move your project onto your own computer, we write you a set of starter documents — a project-memory file for your coding agent, a PROJECT.md describing what you are building, and a first task document — based on your project description. We keep every version we generated, so you can always see what we told you.

What your coding agent tells us

If you connect your coding agent, it can send us a short report at the end of a working session: what you set out to do, what changed, what runs, what is stuck, and what you said you did not understand. It is TEXT ONLY — never your files, never your code, and never a screenshot. If it looked at your screen it sends a written description of what it saw, not the picture. We use it to answer your questions with some idea of what you have actually been doing, and the 'what you did not understand' part goes into the same pile as everything else that confused you, so we can rewrite the explanations that keep failing. You can cut it off at any time by revoking the key on your settings page, and nothing you have already done is affected. Nothing in these reports is graded, scored, or used to unlock anything.

The key your coding agent uses

The name you gave the machine, when you created the key, and when it was last used. We store only a one-way hash of the key itself — you are shown it once and we cannot look it up again.

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. It stops the email we would choose to send you. It does not stop a sign-in link, because that is the only way into your account and taking it away would lock you out of it — so if you ask for a link, you get one, whatever this timestamp says.

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 to an interview answer is passed into that one turn and discarded — it is never written to a database or to storage. This is different from files you upload to a lesson or to a piece of work, which are described just below and which we do keep.

Files you upload and we keep

You can attach a file to an answer or to a piece of work you submit — a document, a PDF, an image, a recording, a spreadsheet, a zip, whatever you have. We keep the file itself, its name, its size and its type, when you uploaded it, and which answer or piece of work it belongs to. It is stored in Europe, and it is only ever served back through this site to someone signed in — never from a public address. You and your coach can open it; other learners cannot. Three things we would rather you heard from us than found out. We accept any kind of file, and we do NOT scan uploaded files for viruses or malware — so a file you upload is a file we have not checked. A file you upload is only ever DOWNLOADED, never opened inside a page here: nothing you or anyone else uploads can run code on this site. And uploaded files are NOT included in our backups, so if one were ever lost you would need to upload it again. Deleting your account deletes the files themselves, not just the record of them.

Who can see it

Most of this is between you and the software that writes your lessons. There are three exceptions, and they are worth knowing before you write anything down.

You

All of it. Your settings page hands you the whole lot as one file whenever you ask, including the parts you have forgotten you wrote.

Your cohort

What you post to the feed, and nothing else. Your project description, your progress, what confused you and what you submit for feedback are never posted there by us. Sharing one piece of work with the cohort is a separate choice you make one piece at a time, and the feedback you were given on it is never shared along with it.

Your coach, if you have one

If a coach or trainer is working with you, they can see your project description, how far along your path you are, the confidence you gave yourself after each lesson — which now appears on a chart on your own page too, beside what your coach thinks, where before it was collected and shown to nobody — what confused you, and what you sent in for feedback together with the feedback you got back. They can also write notes about you and record your sessions. Almost all of that you read too: everything they write for you is on your own course page, in their words, and each note says who it was written for. The one exception, and we would rather you heard it here than worked it out: a coach can keep a note for their own use while they are working out how to help you, and you do not see those. They are not a file of judgements about you. There is no ranking: you are never compared with anybody else, anywhere in this product, because we do not produce that and would not know how. Nothing is graded by a machine either — no software here puts a number on anything you make. What your coach can do is say where they would put you, out of ten, on the handful of things the two of you agreed you are working on, against the target you agreed for each — and they cannot record one of those without writing down what they mean by it, which you read. What they are is a coach thinking on paper. Everything else — what they can see about you, what they set you, when you met — you can see too. They can also rewrite one of your lessons for you, which changes your copy and nobody else’s and is named on the lesson when they have. They can also set you work with a date on it and read what you send back, and the two of you can write to each other directly — anything you send them, they can read, which is the point of sending it. If nobody is coaching you, nobody is looking.

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.

Videos your coach chooses

A lesson can carry a video that already lives on YouTube, Vimeo or Loom. When that block is on the page, your browser fetches the video from them directly, so those companies see your IP address and that you opened that video — the same as if you had clicked through to their site. We pick the privacy-respecting version of each player where one exists, so nothing is set up to follow you around, and we never let a lesson embed anything from anywhere else. Nothing about what you watch comes back to us.

How long we keep it

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 we choose to send you has a one-click unsubscribe that works without signing in, and you can change it from your settings. Two messages are not like that and we would rather say so: a sign-in link, which you have just asked for and which is the only way into your account; and the one-off invitation a trainer may have emailed you before you had an account, which had no account to unsubscribe and no list behind it.

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.