Terms of use and privacy notice
Version November 2026
The service
Try for Tomorrow is an online tool, provided by Rethink Food, that Foundations use to deliver a six-session programme to young people. It has three parts:
- Facilitator portal: a Foundation's facilitators set up cohorts and groups, run each session and record the group's surveys.
- Pledge screen: during a session, each young person picks a pledge (or writes their own idea) on the facilitator's device.
- Admin console: Rethink Food staff manage Foundations and accounts, see programme reports, and look after the data.
A public counter shows the programme-wide pledge total only, with no individual data.
Who can use it
Only invited adults can sign in; young people never have accounts.
| Role | Who | Can |
|---|---|---|
| Facilitator | Adults delivering the programme for one Foundation | Run sessions for their own Foundation only; keep its class lists; see its pledges and surveys. |
| Admin | Rethink Food staff | Manage Foundations, accounts and session content; see programme reports by pupil code; moderate own ideas; carry out erasure and retention clean-up. Admins cannot see young people's names. |
| Manager | Rethink Food staff and programme partners | See the same reports as admins, read-only. Managers cannot change anything or see young people's names. |
- Accounts are created by Rethink Food. You're emailed a link to set your own password (at least 10 characters); nobody else ever knows it.
- Sign in with your own account and don't share it.
- A sign-in ends when the browser closes, and after 4 hours with no activity (never while a session's pledges are open).
- Rethink Food can switch an account off at any time; it stops working straight away.
Your responsibilities as a facilitator
Your Foundation remains responsible for the young people in its care. By using the tool you agree to:
- Enter each young person as first name and surname initial only (for example "Ava B."), and nothing else about them.
- Have the consent your Foundation needs before young people take part, and record in the survey only how many have evaluation consent. Where that consent is recorded is your Foundation's responsibility.
- Remind young people, when they write their own idea, not to include anyone's name or contact details.
- Use a device and browser you control where you can, sign out at the end, and not leave a signed-in screen unattended.
- Remove a young person from the class list when they leave, and pass on any request to delete a young person's data to Rethink Food.
What data the tool holds
A young person's name is held in one place only, their Foundation's class list. Everything else about them uses a random code (for example p_5af02beb), so reports never show who pledged what.
| Data | What it contains | Who can see it |
|---|---|---|
| Class list | Each young person's first name and surname initial, their group and code | That Foundation's facilitators only. Rethink Food staff cannot read it. |
| Copy on your device | The same class list, kept in the browser while you're signed in | You; cleared when no one is signed in on the device |
| Pledges | Code, session, chosen pledge, the young person's own idea if written (up to 200 characters), status, date | The Foundation's facilitators; Rethink Food staff (by code only) |
| Session records | Which session was run with which group, when, pledge counts, whether the physical task was done | The Foundation's facilitators; Rethink Food staff |
| Group surveys | Show-of-hands counts for the whole group, the number with evaluation consent, the facilitator's name, Foundation and (if given) school or organisation | The Foundation's facilitators; Rethink Food staff |
| Your account | Your name, work email, role, Foundation, and the school or organisation you gave | You; Rethink Food staff |
| Requests you send | Changes you ask for (name, Foundation, email, account deletion) | You send them; Rethink Food staff deal with them |
| Programme counts | Totals of sessions and pledges, with no individual data | Anyone (public counter) |
| Audit log and problem reports | What admins changed; error messages from the tool, with codes and emails masked | Rethink Food staff |
Free-text own ideas may, despite the reminder, contain personal details. Rethink Food can reject an idea so it is no longer counted, and erase it with the young person's other data.
How long data is kept
Young people's data is kept for 2 years from their cohort's last activity: its last session, survey or class-list change.
- After 2 years Rethink Food clears the cohort: its names, pledges (including own ideas) and codes are deleted for good. Every clear is recorded.
- The programme's counts and the group survey counts are kept after that, because they contain no individual data.
- A young person removed from a class list loses their name from the tool straight away; their pledges stay, under the code only, until the cohort is cleared or an erasure is requested.
- Adult accounts are kept while the person works on the programme, and deleted when they leave it or ask for it to be deleted.
- Backups follow the same 2-year rule.
Your rights and erasure
A request to see, correct or delete a young person's data goes to their Foundation, which passes it to Rethink Food. The facilitator gives Rethink Food the young person's code (cohort page, "Show IDs"); Rethink Food never needs their name. Every pledge they made is then deleted, with their code and name, and the deletion is recorded.
For your own account: you can see and update it on Your account (your name in the portal's top bar), ask for your name, Foundation or email to be changed, and ask for your account to be deleted. You can also contact Rethink Food directly.
Security
Access is enforced by the database itself, not just by the screens, so a facilitator can only ever reach their own Foundation's data.
- Separation: names are readable only by the Foundation's own facilitators; every other record refuses any field that could hold a name.
- Sign-in: personal accounts, passwords of at least 10 characters set by the person, sign-out when the browser closes or after 4 hours idle, and class lists cleared from the device when no one is signed in.
- Connections: the site is served only over encrypted connections (HTTPS), only works from its own address, checks that requests come from the real site, and blocks scripts from anywhere else.
- Accountability: admin changes are written to an audit log that cannot be edited or deleted.
Who processes the data
The tool runs on Google's Firebase, and its database is stored in Google's London region.
| Processor | Used for | Data it handles |
|---|---|---|
| Google Firebase (database, sign-in, hosting) | Storing the data, signing in and serving the site | Everything listed above |
| Google reCAPTCHA | Checking that requests come from the real site | Technical signals from the browser |
| Google Fonts | The site's typefaces | Visitors' IP addresses |
| YouTube / Vimeo | Session films, only when a facilitator presses Play | Viewing data, under their privacy-friendly embed settings |
No data is sold or used for advertising, and nothing is shared beyond these processors without the Foundation's agreement.
Use, availability and contact
- Use: the tool is for delivering and evaluating the Try for Tomorrow programme only. Don't enter information beyond what it asks for, try to reach another Foundation's data, or share sign-ins. Rethink Food may switch off an account that breaks these terms.
- Availability: the tool is provided as it is, without a guaranteed service level. It may occasionally be unavailable; pledges already saved are not lost.
- Changes: Rethink Food may update the tool and these terms, and will tell you of material changes before they apply.
- Contact: questions, problems and data requests go to Rethink Food at info@rethinkfood.co.uk.