Privacy
Last updated 1 November 2026.
Dabster is a log for home learning, on the website and the phone app. This notice says what we store so the app can work for a household, why, and how to reach us.
Who we are
Dabster Ltd runs Dabster and is the controller of the personal data described here. Email contact@dabster.app.
What we store
- Account email and display name. Your password is stored hashed by the sign-in service. We cannot read it.
- Household name, timezone, and any transcript contact details you type.
- Children's names, an optional date of birth, and optional photos. An adult adds these. Children do not have their own logins.
- Learning records you enter: activities, journals, books, plans, subjects, reports, and files you upload.
- Email addresses of people you invite.
- Support messages, and an optional reply email.
- An email you leave on the coming-soon form, so we can tell you when families can join. That email is not an account.
- Cookieless page views and referrers on the public pages. Signed-in pages are not included.
Notes are free text. You may record health or special educational needs details there. We only use them to show them back to your household.
The phone app uses the camera only when you scan a book barcode or take a photo to upload. It keeps your sign-in in the phone's secure storage.
Why, and on what basis
- To run the household workspace you asked for. Basis: our contract with you.
- To keep the service secure, fix crashes, and answer support. Basis: our legitimate interest in a safe, working service.
- To see which public pages are visited. Basis: our legitimate interest in improving the site.
- To tell you when families can join, if you left an email. Basis: your consent. You can withdraw it at any time by emailing us.
We need an email and a password to create an account. Without them we cannot provide the service. We do not make automated decisions about you.
Children
An adult account holder enters a child's record. Dabster is not directed at children. We do not advertise to them. We do not sell their records, and we do not share them for ads or research. A parent can use the rights below on a child's behalf.
Who else sees data
- Other adults in your household. Members can see the household's records, including the children's.
- Supabase, in London: the database, sign-in, and private files.
- Vercel: hosting, plus cookieless analytics on the public pages.
- Resend: invitation, password, support, and interest-list email.
- Sentry, in the EU: a crash stack and a short reference. No session replay.
- Proton: email sent to contact@dabster.app.
- Google Books and Open Library. A book lookup sends only the ISBN, from our server. Book covers load straight from them, so they see your device's IP address when a cover is on screen.
Outside the UK
Vercel, Resend, and Google are in the United States. Sentry is in the EU and Proton is in Switzerland, which the UK treats as adequate. Transfers to the United States rely on the UK–US data bridge or the UK's international data transfer addendum.
How long
We keep the household's records while the account exists. An admin can download a copy from Settings. The household owner can delete the workspace in Settings. That removes the household's records, uploaded files, and that owner's login. Other members have to be removed first. A member who is not the owner can ask the owner to remove them, or email us to delete their login. If deletion from Settings is not possible, email contact@dabster.app and we will delete within one month. Copies we keep for backup are deleted on the same cycle. An email on the coming-soon list stays until we open signup or you ask us to delete it.
Your rights
You can ask for a copy of your data, a correction, deletion, or a portable copy. You can ask us to restrict use, and you can object to uses based on our legitimate interests. Where we rely on consent, you can withdraw it. Email contact@dabster.app. We reply within one month. You can also complain to the Information Commissioner's Office at ico.org.uk.
Cookies
Sign-in uses cookies the app needs to keep you logged in. Public analytics do not use cookies. There is no advertising cookie.