Privacy notice
For wellbeingengine.io and the developer sandbox for the Intelligent Wellbeing Engine (IWE). Last updated 25 September 2026.
Who is responsible for your data
wellbeingengine.io is operated by All Toogether Ltd, a company registered in England and Wales (company number 14775309), whose registered office is Jactin House, 24 Hood Street, Manchester, United Kingdom, M4 6WX.
All Toogether Ltd is the data controller for personal data processed through this site. We are registered with the Information Commissioner's Office under registration number ZB544902.
What we collect, and why
There are two quite different things going on, and it matters which is which.
1. When you request sandbox keys
Calling POST /sandbox/signups, or using the button in our docs, stores:
| What | Why | Basis |
|---|---|---|
| The email address you supply | To identify your sandbox client and contact you about the key | Legitimate interests - providing the sandbox you asked for |
| A hashed version of your IP address | Rate limiting and abuse prevention. We store an HMAC, never the address itself, and cannot recover it | Legitimate interests - keeping a free public service usable |
| Your browser user-agent and referring link | To understand which channels and AI assistants send developers to us | Legitimate interests |
2. Inside the sandbox itself
Nothing about you, and nothing about anybody else. The sandbox runs against a synthetic workforce we generated - invented people, invented answers. Sandbox keys are deliberately not granted permission to create respondents, so no real person can be enrolled through them, and the engine has no free-text field to put personal data into.
If you later run the IWE on your own people, that is a separate deployment under a separate agreement, and your organisation is the controller for it.
How long we keep it
Sandbox keys expire 30 days after issue. A scheduled job then deletes the client record, and your email address is deleted with it. This is enforced by the database rather than by anyone remembering to do it.
Who we share it with
We do not sell or share your details. They sit with our infrastructure providers:
- Database hosting: a managed PostgreSQL service, with data stored in London (UK)
- Application hosting: the cloud platform that runs this website and its API
Your rights
You can ask for a copy of what we hold, ask us to correct or delete it, or object to our processing. Deletion is usually immediate - there is very little to remove, and it would have gone within 30 days anyway.
If you are not happy with how we have handled something, you can complain to the Information Commissioner's Office at ico.org.uk.
What is counted when you read a page
Each page load and each page exit is counted, with the page address, the page you came from if your browser passes it on, and your browser and device type. Both addresses are cut short at any "?" or "#", so nothing added to the end of a link is kept. The counting service also receives the few technical details it needs to accept a count: which version of its script sent it, when, and a one-off number for the event. That is all. The counting mode we use does not derive a country from your connection.
Your IP address is used for one purpose at the moment it arrives: together with your browser type, the site name and a secret value that changes every day, it is turned into a hash, and then discarded. The hash cannot be turned back into your address. Because the secret changes daily, the same visitor produces a different hash tomorrow, so visits cannot be linked across days and no profile of any person is ever built. Within one day, repeated views from the same address and browser count as one visitor; that is the whole extent of it. Nothing is placed on your device to recognise you when you return.
The counting is done by PostHog, a service we use as a processor, on servers in the European Union. PostHog acts only on our instructions and may not use the data for its own purposes.
Why we count, and on what basis
We count so that we know which pages are read and whether the site is working. Our lawful basis is legitimate interests. We judged that interest against the effect on you: no cookies, no identifier that persists beyond a day, no marketing use, no sharing. We concluded the effect is minimal. You may object at any time by writing to the address below; because nothing identifies you, we cannot single out your visits, but we will consider the objection and answer it.
The analytics project has a twelve-month retention setting, but automatic deletion under that setting is not currently enforced.
Cookies and local storage
This site does not use cookies. Nothing is stored on or read from your device to count visits, so the rules on cookies and similar technologies do not require your consent, and the site shows no banner. We do not track visitors across sites, and we do not share data with advertising networks.
The interactive demo stores a single access key in your browser's local storage. This is strictly necessary for the demo to function, is first-party only, is never transmitted to third parties, and is not used for tracking or profiling. If the key arrives as part of a link, it is moved into that storage and removed from the page address before anything else on the page runs, so it is never part of what is counted. You can clear it at any time through your browser settings.
Contacting us
For data deletion requests, abuse reports, or questions about sandbox access, email hello@wellbeingengine.io.
We aim to respond to data protection requests within one month, as required by the UK GDPR.
Changes
If we change this notice we will update the date at the top.