Privacy
How StoryCue actually handles data today — not a template, not legal boilerplate, just what the product in front of you really does.
This page hasn't been reviewed by a solicitor yet, and it describes the product as it exists right now, not any future version. If you spot anything that needs tightening, or you're a school asking a question this page doesn't answer, tell us: jack@snapshotschools.co.uk.
The short version
StoryCue runs entirely in your browser. There is no account, no login, and no server StoryCue controls that stores anything about your child. Every story you build exists only on the device you built it on, for as long as you keep it there.
What StoryCue collects, and where it goes
Name, pronouns, companion, sensitivities, reading level
Typed into the creator to personalise a story. Used live, in your browser, to build the text on screen. Never sent anywhere — there's no server request that carries this data at all.
A story you write yourself ("write your own story")
Saved to your browser's local storage only, under a key named storycue_custom_stories. Not uploaded, not synced, not visible to anyone else — including us. Clearing your browser's site data deletes it permanently; there's no backup copy anywhere.
A photo you choose to add to a step
Kept in this browser tab only, while it's open, so the photo can follow the story into read mode and the PDF. Never uploaded to a server, never used for anything else. Closing the tab removes it — photos aren't saved with a story, so they need adding again next time.
Everything else (the dictionary of built-in stories)
The only thing your browser fetches from StoryCue's server is the static dictionary itself — pre-written, reviewed story text with no information about you or your child in it.
What StoryCue doesn't do
- No accounts, no login, no email collected.
- No analytics or tracking scripts of any kind run on this site today.
- Nothing about your child is sent to a third-party AI provider — the dictionary stories are pre-written and reviewed, not generated from what you type.
- Nothing is sold, shared, or used for advertising. There's nothing to sell — StoryCue doesn't have a copy of your data to begin with.
- No cookies are set beyond what's strictly needed to run the page.
Children's data
A child doesn't create an account or type their own information into StoryCue — a parent, carer, or member of school staff does, on their behalf, and it stays on that person's own device. There's no profiling, no behavioural advertising, and no data StoryCue holds centrally to protect in the first place.
If you're a school
There is currently no school account, shared caseload storage, or Data Processing Agreement — that's a planned future feature, not something you can switch on today. Right now, using StoryCue in a school works exactly the same way as a parent using it at home: everything stays local to the device it's used on, with no central record for the school to govern. If your own data protection process needs more than this page before staff use it, that's the right instinct — ask the contact below before relying on it for pupil work.
Questions or concerns
Contact: jack@snapshotschools.co.uk. We'll fix this page the moment something here turns out to be wrong or out of date.