⚠️ Draft for review — not legal advice.
This is a working draft. It must be reviewed and approved by a qualified data-protection / education-law professional and the responsible Data Protection Officer before it is published or relied upon. Placeholders in [square brackets] need real values.
Sub-processors
Last updated: Draft — not yet published
The third parties Storyjar relies on to run the service, what they do, and where data is held. We keep this list short by design.
Each sub-processor below operates under a data-processing agreement. We give schools prior notice before adding or changing a sub-processor.
| Sub-processor | Purpose | Personal data | Location |
|---|---|---|---|
| Railway | Application hosting, database and file storage | All service data (children's moments, staff/parent accounts) | [UK/EU region — required] |
| GitHub | Source-code hosting (no personal/customer data) | None (code only) | — |
Requirement: every sub-processor that handles personal data must store and process it in the UK/EU. The hosting region must be set to a UK/EU location before any real child data is stored. [Action: confirm and pin the Railway region to UK/EU; keep this table in step with reality.]
What we deliberately do not use
No analytics providers, no advertising networks, no social-media pixels, no behavioural-profiling services. Children are never tracked or profiled.