Privacy Policy
Last updated September 22, 2026
The short version
Teachers and school staff have accounts. Students do not. A student joins a class with a link and a nickname, and that nickname is essentially the whole record — no name, no email address, no date of birth, no password. We sell nothing, we run no advertising, and no analytics or ad-tech vendor sits behind us. We count page views ourselves, on our own server, without cookies and without knowing who you are.
Who we are
Dabbled for Schools is operated by Equilibrium Software Solutions LLC ("we", "us"). For anything in this policy you can reach us at john@dabbled.ai.
What we collect
Teachers, administrators and other staff
Your email address, the name you give us (both parts are optional), a hash of your password — never the password itself — whether your email has been verified, your school and your role in it, and the date your account was created. If you are the person who set up the school, your school also carries its billing balance.
Students
A nickname, an address-bar version of that nickname, the school they belong to, a token that lets their browser be recognised as the same person next time, and a recovery code so a teacher can restore that identity on a new device. That is the entire student record. We do not ask for, and have nowhere to put, a student's real name, email address, date of birth, photograph, or home address.
Rosters
A school may connect its student information system, or upload the roster it exports. Of the students on it we keep the roster's own identifier for each one and a grade — not a name. Student names in an upload are shown to the school's teachers for one day, so they can match each nickname to the roster, and are then deleted; where a connector can look names up live, they are fetched for the teacher's screen and never stored. The one durable thing a roster adds is which nickname is which roster identifier, and the school can remove it by disconnecting the roster. Parent and guardian rows in an export are ignored: we hold nothing about them. A child here is still a nickname.
Activities in use
When someone uses an activity, it reports how the play went to our own server: that it was opened, started and finished, right and wrong answers to its own questions, and any errors it hit. No IP address and no browser details go with that. To tell a return visit from a first one, and to count how many different browsers used an activity, each activity keeps one random identifier in the browser's storage for that activity alone. It is different for every activity, is never joined to an account, a nickname or a device, and goes when site data is cleared. Plays by a student on a class link are tied to the student's nickname, as described above.
What people make
The description you write of the activity you want, the answers you give to any follow-up questions, the activity that gets built, its tags and its screenshot, any lesson notes a teacher writes, and any feedback a teacher sends us. Activities a student makes are attributed to their nickname. For each activity we also keep what was sent to the AI model while building or changing it and what the model sent back, so we can see why an activity came out the way it did; it is deleted with the activity.
Billing
Payments are handled by Stripe. Card numbers never reach our servers: what we store is the customer and payment-method identifiers Stripe gives us, the amount of each payment, and a record of each activity generation and what it cost, so a school can see where its balance went.
Operational records
Ordinary server logs — requests, errors, timings. We deliberately keep personal information out of them: when the personal-information check blocks a request, for instance, the reason is shown to the person and is not written to the log.
How we use it
To run the product: authenticate you, build the activities you ask for, show your school its own work, bill for what was used, and email you when something needs your attention — chiefly the verification link when you sign up. We do not use anything from your school to advertise to you or to anyone else.
Who else sees it
- Anthropic — the activity descriptions and existing activity content are sent to Anthropic's API to build and revise activities, tag them and answer questions. Content sent through the API is not used to train models.
- Stripe — payments and stored cards.
- Our email provider — the address a verification email is sent to.
- Our hosting provider — everything, in the ordinary sense that the application runs on their machines.
- Google Fonts — the IP address of anyone loading a page, as above.
That is the complete list. We do not sell, rent, license or trade personal information, and we do not share it for anyone else's marketing.
Personal information in what people write
Before an activity request made through the guided builder reaches the model, it is screened for personal information — full names, addresses, phone numbers, anything that identifies a specific real person. If any is found, the build stops and asks for a reword rather than silently rewriting it, and the explanation shown never repeats the personal information back. The check fails closed: an unclear result blocks rather than passes.
It runs on what a student writes too. A student building their own activity from a class code is screened before anything is generated - the title they gave it as well as the request itself - and a build that does not pass is refused on the spot, with nothing stored and nothing charged.
Who can see an activity
In a school, activities are private by default. One becomes visible outside it only when someone at the school publishes it to the public library.
In an individual workspace — a tutor, a parent, a teacher on their own — it is the other way round: everything made there is published to the public library by default, which is what that free plan gives back. That includes activities made by students who join one of its classes, and the join page says so before they type anything. Any activity can be made private afterwards.
A published activity is attributed to the school or workspace, never to the teacher or student who made it. Unpublishing removes it from the library, though we cannot recall a copy someone already took.
Keeping and deleting
Activities and lesson notes can be deleted in the product at any time, and deleting means deleting. Accounts, schools and student records are kept until someone asks us to remove them — write to john@dabbled.ai and we will. Backups roll off on their own schedule, so a deleted item may persist in a backup for up to 30 days after it disappears from the product.
Children
The product is designed so that there is nothing to collect from a child. A student is never asked for a name, an email address or a birthday, and never creates an account. We rely on the school to decide which students use it and to supervise that use, and we do not knowingly collect personal information from a child. If you believe a student has typed personal information into the product, tell us and we will remove it.
Schools and education records
Where the work a student does here forms part of an education record, that record belongs to the school. We hold it on the school's behalf and act on the school's instructions, which includes deleting it when the school says so. A school administrator can see their school's activities, classes and students; a teacher sees their own classes.
Security
Passwords are stored as bcrypt hashes. Email verification links are single-use, expire, and are stored only as hashes, so the link in your inbox cannot be reconstructed from our database. Activity screenshots are served through signed, expiring links rather than public URLs. Traffic is served over HTTPS. No system is perfectly secure, and we won't pretend otherwise.
Your choices
You can see and change your own account details in the product, delete activities and notes you own, and ask us for a copy of what we hold about you or for its deletion at john@dabbled.ai. If your school holds the account, we may need to route a request through your school administrator.
Changes
If we change this policy we will update the date at the top, and we will tell schools directly about any change that materially affects student data.
Questions: john@dabbled.ai · Terms of Service