How we handle the voice — and your organisation’s data.
We designed My Voice First to collect the child’s voice, not to build a database of it. Here’s what that means in plain English.
1. How children’s activity answers are processed
Children’s activity answers are processed entirely in the browser on the device being used. The completed Young Person’s Voice PDF is generated on that same device and saved there — it is not generated on or stored on our servers.
When a child chooses to “send” their voice, we send only a short notification email to the chosen staff member. The email does not contain the child’s answers and no document is attached. The completed PDF remains on the device for staff to collect.
2. What My Voice First does and doesn’t store
We do not store children’s answers. They exist only during the active session on the device and are destroyed once the document has been created and the notification sent. We never hold a historical record of a child’s voice.
We do store organisation data needed to run your subscription: your home or organisation name, staff names, staff email addresses and roles, and account information for the person managing the subscription. We also record anonymous engagement counts (how often an activity was opened or completed) that are never linked to an individual child and never contain a child’s words.
3. How organisation and staff accounts are protected
Each home’s account is kept separate from every other home. Individual staff authentication, administrator-controlled access and database-level isolation mean one home cannot see another home’s data.
4. Authentication and access
Staff sign in with their own credentials. Access to features is controlled by the home’s administrator, so each staff member only reaches what they need. The person managing the account controls who is invited and what they can do.
5. Data separation
Every home’s organisation data lives behind its own access boundary. Professional Feedback requests are tied to the requesting home, and completed feedback is sent directly to that home — not shared across accounts.
6. Encryption
Data in transit is protected using encryption. Organisation data is stored on our platform’s secure infrastructure with appropriate access controls.
7. Payment processing
Payments are handled by Stripe. We do not see or store your full card details. Stripe processes your card and subscription information securely.
8. Data retention
We keep organisation data for as long as your subscription is active, and for a short period afterwards to handle closure, accounting and legal obligations. Because we do not store children’s answers, there is no children’s data to delete on closure — completed documents remain your responsibility. Full details are in our Data Retention & Deletion explanation.
9. Subprocessors
We use approved subprocessors — for example our payment provider (Stripe) and our hosting and email providers — under written contracts with equivalent data-protection obligations. A current list is in our Subprocessor information.
10. Safeguarding
My Voice First is a communication aid, not a monitored safeguarding-reporting or emergency service. Children always have a clear route to share a worry, but staff must follow their own safeguarding procedures. Because we do not retain children’s answers, a disclosure that is started but not completed and sent is not kept — staff should remain vigilant through their normal practice. See our Safeguarding Statement for more.
