Parent Age Verification Statement
Last updated: 17 November 2026
Draft — pending legal review. This version has not yet been signed off by a solicitor.
The whole of the adult check, in one document: the single question it answers, the document and liveness capture our partner asks for, the fact that no image, document number or date of birth is ever stored on TeenViews, how long Didit holds any copy, the named staff who can reach a verification record under contract and why, what a failed check means and how to ask for a person to review it, why it is entirely separate from a teenager's 13 to 17 check, what we will never do with an image, and how the statement is reviewed. Retention periods and access requests are cross-referenced to the Parent Privacy Notice.
In short
Everything about the 18+ check in one place: why it exists, what our verification partner asks for, what we keep (the outcome, never your documents), who may look and what they promised, what a failure means, and why it is separate from a teenager's own check.
1. Why the check exists
The parent portal lets an adult see a small summary of a teenager's activity and, for a 13 to 15 year old, set a few limits. That is only safe if the person on the other side really is an adult, so we check before any link can be made. It is not a background check, a credit check, or a judgement about you as a parent. It answers one question: are you 18 or over.
Access to the Parent Portal confers visibility of limited categories of data relating to a child and, for a linked child aged 13 to 15, the ability to configure participation limits. The platform therefore requires verification that the account holder is an adult before any ParentLink may be established. The check determines a single fact, whether the account holder has attained the age of 18, and constitutes neither a background check nor an assessment of parental suitability.
2. How it works
You open the check from your account page. Our verification partner, Didit, asks for a photo of an identity document (a passport, driving licence or similar) and a short selfie video or photo so it can confirm the document belongs to a living person in front of the camera. You can stop at any point. Nothing is created if you do not finish.
The check is performed by the platform's identity verification processor. The account holder is asked to capture an identity document and a liveness capture of their face. The processor compares the document, the face and the estimated or documented age, and returns a decision to the platform. The account holder may abandon the process at any point, in which case no verification outcome is recorded and no ParentLink may be established.
3. What happens to your documents
None of it is stored on TeenViews UK. Your document photograph and your selfie go straight from your browser to Didit, and we never receive them: not into our database, not into our file storage, not into a backup, not into an email. Didit may keep them for up to 30 days, on servers in Europe, so the check can be reviewed or repeated if something goes wrong. After 30 days they are deleted. Section 8 covers Didit's own policies. What comes back to us is small: the outcome, the date, the method used, a check reference, and a one-line reason if it failed. Never the images, never the document number, never your date of birth. That record is described in section 8 of the Parent Privacy Notice. A small number of named staff can reach the images at Didit. Section 7 sets out who they are, why, and what they promised.
No document image or liveness capture is stored on any platform system: captures are transmitted directly from the account holder's browser to the identity verification processor, Didit, and are not written to any platform data store, file store, backup or correspondence. The processor retains them for a maximum of 30 days within the European Economic Area for audit, dispute resolution and technical review, deleting them at expiry. The platform receives and retains only the verification outcome, the date, the method, a processor reference and any failure reason, as described in section 8 of the Parent Privacy Notice. Processor-side access by named personnel is governed by section 7.
4. If it fails
A check can fail because the document could not be read, because the face did not match, or because the age came back under 18. A failed check does not close your account or stop you using the portal pages. It does mean a link cannot be created yet, and you can try again. If a check repeatedly fails and you believe that is wrong, contact us and a person will look at it. You can also ask for a person to review any decision the check makes about you, at no cost, and we will reply with a decision and a reason.
A check may fail where the document cannot be validated, where the face does not match the document, or where the verified or estimated age is below 18. Failure does not result in suspension of the Parent Account and does not prevent access to informational pages of the Parent Portal; it prevents establishment of a ParentLink. The account holder may re-attempt, and may at any time request human intervention in, and contest, an automated decision, expressing their point of view and receiving a response with reasons, in accordance with Articles 22(3) and 13(2)(f) UK GDPR. Where repeated failures occur and the account holder contests the outcome, the matter shall be reviewed by a member of platform staff.
5. Why the teenager's own check is separate
Teenagers are checked against the 13 to 17 age range when they sign up. That is a different question from yours, answered by a different process, and a pass on one does not affect the other. Your check says nothing about a teenager, and theirs says nothing about you. Neither result is ever shown alongside the other.
Verification of a user aged 13 to 17 establishes eligibility within a statutory age band and is performed separately from adult verification. The two processes are independent: an outcome in one has no evidential or procedural effect on the other, and neither is disclosed alongside the other.
6. How long we keep the result
The result we hold, meaning the outcome, the date, the method and any reason, is kept while your account exists and deleted with it. The images are not ours to delete: Didit holds any copy for up to 30 days and then removes it. If you ask for your data while a copy still exists, we can retrieve it for you; if the 30 days have passed, it no longer exists, and we will tell you so in writing rather than leave you wondering. You can ask what we hold, or ask for your account and its check record to be deleted, at any time. Section 9 of the Parent Privacy Notice explains how to ask, and section 6 of that notice lists our retention periods.
The verification outcome, date, method, reference and any failure reason are retained for the life of the Parent Account and deleted upon deletion of the account. Document images, biometric captures, document numbers and dates of birth are not retained by the platform at any point; the processor retains any copy for a maximum of 30 days and deletes it thereafter. Where an access request is made within that period the platform will retrieve a copy, and where the period has expired it will confirm the position in writing. Access requests and retention periods are governed by sections 9 and 6 of the Parent Privacy Notice respectively.
7. Who can look, and what they promised
A small number of named TeenViews staff can reach the images at Didit. They are authorised individually and can only open a record for a defined reason. Who: only staff whose role requires it, authorised individually by the Safeguarding Lead or an Admin. Never the wider team, never an operator, never an organisation. Why: chiefly so we can answer a right of access request. If you ask us for everything we hold about your check, that includes being able to retrieve the image while it still exists. The other permitted reasons are investigating a disputed or failed check, meeting a legal or safeguarding obligation, and answering a regulator. What they are bound to: every one of them is contractually bound to our strict privacy standards. They must not share the image with anyone, copy or screenshot it, save it to a personal device or send it by email, use it for any other purpose, or describe it to anyone who is not authorised. Breaking that duty is a disciplinary matter and a breach of contract. Every opening of a verification record is logged, with who opened it, when, and which record. Staff cannot edit or delete that log.
A restricted group of named platform personnel holds processor-side access to verification records, including document images and liveness captures. Access is granted individually by the Safeguarding Lead or an Admin role holder, reviewed periodically, and revoked on change of role or departure. Permitted purposes are the fulfilment of an Article 15 UK GDPR access request; investigation of a disputed, failed or suspected fraudulent check; compliance with a legal obligation, safeguarding referral or request of a competent authority; and response to a regulator. Personnel are bound by written confidentiality and data protection obligations prohibiting disclosure to any third party, copying, retention on personal devices or in personal correspondence, use beyond the authorised purpose, and description to any unauthorised person; breach constitutes a disciplinary offence and, where applicable, breach of contract. Each access is recorded in an append-only audit log identifying the person, the date and time, and the record accessed; personnel cannot amend or delete entries.
8. Didit's own policies
Didit is a separate company, and it has its own privacy policy and its own terms of service. Those documents cover the parts of the check that Didit performs, and they are published by Didit and available from Didit. Where their notice and ours differ about Didit's own processing, theirs describes their side and ours describes ours. Where they differ about what TeenViews does with the result, this statement and the Parent Privacy Notice are the ones that apply to us. Our contract limits Didit to verifying age, holding the images no longer than 30 days, and deleting them. It must not use them for anything else, sell them, or pass them on without our written instruction.
The verification processor publishes and maintains its own privacy notice and terms of service, which govern its processing and are available from the processor. Those documents prevail as a description of the processor's processing; the Parent Privacy Notice and this statement prevail as a description of the platform's processing. The Article 28 agreement restricts the processor to age assurance, imposes the 30-day retention limit and requires deletion thereafter, prohibits sale, secondary exploitation and disclosure save on documented instruction or as required by law, and is supported by a transfer risk assessment.
9. Security during the check
The capture happens in your browser and is sent straight to Didit over an encrypted connection. It does not pass through our servers on the way, which is why we can say we never hold it. Liveness detection exists to stop someone else's photograph being used in your place, which protects the portal from being opened by a person who is not an adult. If a check is interrupted, nothing is created.
Captures are transmitted from the account holder's browser to the processor over an encrypted channel and do not traverse platform infrastructure. Liveness detection is applied to prevent presentation of a third party's image and to preserve the integrity of adult verification. An interrupted check results in no stored outcome.
10. What we will never do with your images
We will not use them to train a model. We will not use them for advertising or profiling. We will not show them to another parent, an organisation or any other user. We will not ask you for a second copy of your document for our own records, because we do not want one. We will not keep them past Didit's 30 days, because we do not have them to keep.
Identity images and captures are not used for model training, advertising, profiling or marketing, are not disclosed to organisations or other users, and are not retained beyond the processor's 30-day period. The platform does not request or hold duplicate copies of identity documents for its own records. Section 5 of the Parent Privacy Notice sets out the full list of recipients of parent data.
11. Review, changes and contact
This statement is reviewed at least once a year, and sooner if the way the check works changes or the law changes. The version you accepted is recorded against your account. If it changes in a way that affects you, we tell you by email before the change takes effect, and you can close your account if you do not accept it. Questions about the check go to our data protection contact through the Parent Hub; section 12 of the Parent Privacy Notice sets out how complaints work and how to reach the Information Commissioner's Office.
This statement is reviewed at least annually, and additionally upon any material change to the verification process or applicable law. The version accepted by an account holder is recorded server-side. Amendments materially affecting the account holder are notified by email in advance of the effective date, and an account holder who does not accept an amendment may close the Parent Account before it takes effect. Queries are directed to the platform's data protection contact; complaints are governed by section 12 of the Parent Privacy Notice.
Legal & policy queries: legal@teenviews.org.uk
Safeguarding concerns: safeguarding@teenviews.org.uk
This policy aligns with our Privacy Policy, Safeguarding Policy, Community Guidelines, and Terms of Service.
