How to communicate age assurance to end users
.png)
Age assurance is rolling out across more consumer platforms, and teams responsible for user growth metrics are wondering the same thing: will a new age check hurt conversion or make the product harder to use? For users, a request for a selfie, government-issued ID, or other age signal can feel disruptive, especially during onboarding or when trying to access a particular feature.
Persona has helped some of the world’s largest platforms roll out age assurance to millions of users. We’ve seen firsthand that successful rollouts depend on more than just picking which age assurance methods to offer. How you introduce the change, prepare users, and communicate what will happen can make the difference between frustration and trust.
This guide groups those insights into six critical tips to help product, compliance, and trust and safety teams communicate age assurance clearly and reduce negative feedback from their communities.
For this guide, we consulted with Vys, a trusted advisor to leading platforms and age assurance providers on child safety. You’ll see us reference their Socializing the Launch guidance to showcase an additional perspective to what we’ve learned.
1. Communicate consistently to build trust
Most users will learn about a new age-assurance policy from an email, product prompt, help article, privacy notice, and/or support reply. If those sources contradict each other, the reasoning for an age check can look untrustworthy, which may lower conversion rates.
Before you sit down to draft your age assurance policy notices, establish the precise answers your teams should reuse. They should cover:
Who is affected, including regions, age thresholds, account states, features, and experiences
When the age check appears in the user journey
Which methods are available to each relevant user group or region
What each method processes, who processes it, and what the platform receives
How retention, deletion, and redaction rules work
What success, inconclusive, technical, review, and age-restricted results mean, including retries, alternate methods, support, and appeals
Assign a clear owner to each fact. For example, trust and safety should own policy intent and outcomes; product should own placement in the journey; privacy and legal should approve data-use and retention claims; support should use the same approved answers.
Example: Social media. If live streaming is limited to adults, document the trigger, methods by region and/or market, access changes by outcome, and the help or appeal route. Every source should match those facts.
2. Inform users well before the first age check
An age check screen should not be the first time a user encounters notice about a new age assurance policy. Instead, your platform should inform affected users about what’s changing well before they run into an age check while onboarding, signing in, or accessing a feature.
Tailor the notice to affected users in specific regions or feature cohorts, or to users with a relevant account status. This approach helps ensure that your notice is relevant to the right users compared with a generalized, global announcement. Relevant communication channels that you may want to target, in order, include:
Help center and privacy pages
In-app communications and/or emails that you use to send advance notices
In-app communications that preview the change in product as the launch approaches
Be sure to localize the message and include parent or guardian communications where the rollout calls for them. Organizing a pilot or staged rollout can help you surface user questions and adjust your solution before the broader launch. For example, if you find during the pilot that many users cannot use a certain method or keep asking for another option, change the method mix or consider adding more explanations.
Example: Voice chat. Notify affected players before the age gate is implemented: “Starting [date], players who use voice chat may need to confirm they meet the age requirement. See available methods, how information is handled, and where to get help.”
3. Increase trust with transparency
Before the user opens a camera, presents an ID, or moves on to another method, explain why the check is there. Walk through what the user will provide, how the information will be used, and where to get help or choose another method.
Below, we include key best practices for explaining these rollouts.
Explain why your platform is conducting age assurance
The purpose of age assurance is to understand whether a user is eligible to access a service, feature, or good, based on their age. That’s different from understanding their identity, which requires a deeper understanding of their personal data.
Before you begin an age check, help your users understand what you’re doing with their data, why, and when you’ll delete it. By clear that you’ll only retain the age outcome (e.g., “over 18”) and will redact any personal information presented.
Present the available age assurance methods in plain language
Whenever possible, give your user options for age assurance, whether that’s a selfie age estimation, government-issued ID, localized digital identity, or another supported method. Be transparent if some methods are available only in certain markets or for certain types of users.
For each method, explain the information needed, what the platform receives, common reasons it may not work, and the alternative if one exists. Method availability and disclosure requirements can vary by market and should be confirmed with compliance, privacy, and legal before launch.
Be transparent about how their data is secured and processed
A message stating “Your data is secure” doesn’t actually explain what happens to a selfie or ID. Before they submit anything, share what data is used for an age assurance decision. Make the link to the full privacy notice easy to find. Your notice should detail:
What the method collects and why
Who processes the information and what the platform receives
How long data is retained and when it’s deleted or redacted
Whether the information is used for any other purpose
Help users understand what happens next
If a verification fails, don’t just share a generic “verification failed” message. Help your users understand the difference between an inconclusive result from a technical error or an age-restricted result. Then, share the next step on the same screen, like retry, use another method, or appeal.
If appeals are available, provide a link to the challenge process right on the result screen. And, make sure that your help center and support guidance have clear explanations for how the process will work.
Example: AI chatbot companies. If an 18+ conversational mode is gated, explain that the check enables access based on age. Present the available methods for age assurance and share, what happens if the result is inconclusive. Don’t imply that the service establishes the user’s real-world identity unless it actually does.
4. Prepare support before launch
Your support team should be ready to handle the cases that your main age assurance flow missed or can’t account for. Give your support agents approved answers and escalation routes well before deploying your age assurance solution.
Support guidance should cover:
Questions about data use and integrity of checks (e.g., is this phishing?)
Users who can’t use an available method
Repeated inconclusive or inaccurate results
Appeals and age-policy disputes
Camera, document, connectivity, and account problems
Make sure your support team understands what they may and may not collect during troubleshooting and where to submit sensitive evidence. Agents should not ask users to send IDs, selfies, or other personal information through email or other unapproved channels. Any personal data should be securely handled and deleted, and users should receive immediate confirmation after deletion.
Example: Online marketplace. If an age check prevents a seller from sending a message or a restricted good, the seller may contact support for more information. Provide your support team with approved explanations, a troubleshooting path, and an escalation or appeal route.
5. Provide information across your product and support centers
Before rolling out a new age assurance policy, provide clear notice across your product, including in-app messaging, help center articles, privacy notices, and support materials. Your users should know what to expect and where to find more information.
| What users may ask | Where to answer it |
|---|---|
| Why am I being asked? | Provide advance notice with in-product prompts. Use the help center to share full background and details. |
| What will I need to share? | Tell users what the check involves before they begin. Explain other available options in the help center and cover how their information is used in the privacy notice. |
| Who handles my information, and how long is it kept? | Highlight the facts users are most likely to care about during the check. Link to the privacy notice for full details about who handles the information, how long it is kept, and when it is deleted. |
| What happens if the check doesn’t work? | Tell users what to do next on the result screen. Use the help center and support to explain retries, other ways to complete the check, and troubleshooting. |
| What if the result is wrong? | Link directly to the review or appeal process from the result screen, when one is available. Explain the process in the help center as well. |
Before launch, complete the age assurance process as if you were a user, from the first notice through the final result. Test both a successful check and common problems to make sure users can understand what’s happening and easily find help or next steps.
Example: Social media. If users need to confirm their age before using direct messages, explain why when the check appears and tell them what to expect. Link to more information about verification options and privacy, and make it easy to get help if something goes wrong or the result is incorrect.
6. Help users navigate the process with clear, consistent messaging
The process can feel disruptive, and unclear explanations can make the experience even more frustrating. Let users know what to expect, explain why the check is required and how their information will be handled, and make other verification options and support easy to find.
Track age-related regulatory updates with Persona Atlas
To help compliance, product, and trust and safety teams keep up with evolving age assurance regulations, we offer Atlas, the first collaborative database tracking developments worldwide. Atlas is updated regularly with the latest age assurance regulations. Use the visual explorer or integrate with a publicly available API to help inform your decision across jurisdictions.
Learn more about Vys
Vys is a youth safety product advisory firm that supports enterprises in gaming, social media, marketplaces, and more industries, with their product and policy roadmaps for under-18 audiences.. Vys embeds with product, trust and safety, and policy teams to identify youth safety risks, co-design product and policy solutions, and implement safeguards that meet both regulatory demands and user expectations. From age assurance and trust models to safety-by-design frameworks and AI risk assessments, Vys turns complex youth safety challenges into scalable strategies that help platforms mature responsibly without sacrificing innovation.
The information provided is not intended to constitute legal advice; all information provided is for general informational purposes only and may not constitute the most up-to-date information. Any links to other third-party websites are only for the convenience of the reader.