WHAT THE PREVIEW STORES
Reading and filtering require no account. The preview does not save form submissions. Your browser stores a colour-theme preference and, if you use the demo shop, product IDs, sizes and quantities. No contact details or payment information are stored in the cart.
Fonts are served locally. There are no third-party advertising or analytics scripts. Hosting and network infrastructure may log technical information such as IP addresses; we do not call ordinary web use completely anonymous.
ACCOUNTS AND BOOKINGS IN LIVE MODE
Accounts use an email, password hash, private display name and age band; no full date of birth is requested. An essential, HTTP-only session cookie lasts up to seven days. Live mode stores only a hash of its session token.
Bookings store session eligibility, notice versions and status. Emergency contacts are encrypted and restricted to operational staff. Guardian consent is event-specific and does not reveal a young person’s messages, browsing or research answers.
QUESTIONS AND SAFEGUARDING
Ask RWM collects whether you are asking for yourself or as a parent/carer, the topic and explicitly attached public page, a general question, and optional age band, borough and safe reply details. Parent/carer requests also record the relationship. Safe-contact preferences and any named referral record are encrypted. A request reference and routing/follow-up state support human triage; no browsing history is attached. Information is encrypted at application level and restricted to assigned safeguarding staff. General intake retention is reviewed after 90 days; a case may need a different, documented lawful retention period.
We do not promise absolute confidentiality. Routine external referrals should be discussed with you and need appropriate informed permission; lawful safeguarding escalation may be necessary. A parent request does not grant default access to a young person’s private information. Do not send detailed allegations, offence admissions or private information about other people through a general form.
FEEDBACK AND RESEARCH
Feedback forms do not ask for direct identifiers by default. Infrastructure metadata and free text can still create identification risks. Research needs an approved purpose, protocol, consent information, age eligibility, lawful-basis assessment, withdrawal policy and retention period.
Submitted questionnaire version IDs and server timestamps support reproducibility. Raw submissions are restricted. A private withdrawal code is shown once; research teams review withdrawal requests against the disclosed study policy. No results are automatically representative or court-admissible.
YOUR RIGHTS AND CONTACT
You can review optional consents and request account deletion in your account. A deletion request is reviewed rather than automatically erasing legally retained safeguarding information. Before launch, the operator must publish its controller identity, privacy contact, lawful bases, processor agreements and rights-request procedure.
This build does not provide an active privacy mailbox. Do not send sensitive information while it is in preview. You can find UK data protection information and complaint routes at ico.org.uk.
NOTICE VERSION: 2026-10-30.v1 / DRAFT FOR PRE-LAUNCH REVIEW