Legal

Children's Safety & Age Assurance Policy

Operated by Belaffee Pty Ltd (ABN 18 698 604 214), trading as RevvMeet  ·  Last updated: 17 June 2026

Operated by: Belaffee Pty Ltd (ACN 698 604 214 / ABN 18 698 604 214), trading as "REVVMEET" ("we", "us", "our")

01Purpose and commitment

REVVMEET is a community for car enthusiasts. Parts of the Platform involve user-generated content, live streaming, real-time interaction, and paid features. We are committed to protecting minors and to meeting our legal obligations regarding the age of our users across every market in which the Platform is available.

This policy sets out:

• the minimum age to use REVVMEET;
• how we assure user age ("age assurance");
• how we handle the personal information of younger users;
• how we detect, prevent, respond to, and report child sexual exploitation and abuse (CSEA) and grooming; and
• the roles, records, and review cycle that make the above auditable.

02Minimum age

The minimum age to hold a REVVMEET account is 16. Where local law sets a higher minimum age for a service of this kind, the higher age applies.

03Age assurance — how we verify age

Self-declaration alone is not where we intend to stop. This section separates what is in place today from what is being added, so the difference is visible rather than implied.

At sign-up (account creation):

1. Declared date of birth (not just "are you over 16?" — a full DOB, entered once, not editable by the user without review).
2. Age-assurance provider — chosen, not yet live. Yoti is our selected provider, using facial age estimation as the primary method and ID or document verification where estimation is inconclusive or a user is near the threshold. It is not yet integrated. Until it is, a declared date of birth is the only age signal we hold, and we would rather say that here than imply a stronger check than we perform.

Ongoing / reactive:

• Behavioural and reported signals. If a user's behaviour, content, or a report suggests they are under 16, we suspend the account pending re-assurance and require a successful age check to continue.
• Appeals. A user who believes an age decision is wrong may appeal via safety@revvmeet.com; we re-assess promptly and keep a record.
• No circumvention. Attempts to falsify age are a Terms of Service breach and result in removal.

Privacy-by-design constraints on age assurance (these are obligations, not options):

• Collect the minimum data needed for the check.
• Do not retain biometric inputs (e.g. selfie images) beyond the moment of estimation unless strictly necessary and separately consented; retain only the result (pass/fail/estimated band) and an audit log.
• Use vetted processors under a DPA; document the cross-border transfer if the provider is offshore.
• Never use age-assurance data for advertising, profiling, or any secondary purpose.
• Run a Privacy Impact Assessment / DPIA on the age-assurance flow before launch (eSafety expressly recommends this).

04Handling younger users and accidental under-age sign-ups

• If we learn an account holder is under 16 (AU) or under the applicable local minimum, we restrict then remove the account and delete associated personal information within 30 days (proposed — confirm before launch), except where retention is legally required.
• We provide clear, plain-language notice explaining why access was restricted and how to appeal or recover data.
• We maintain a record of each such action (date, signal, decision, outcome) as evidence of reasonable steps.

05Child sexual exploitation and abuse (CSEA) — zero tolerance

REVVMEET prohibits, and acts decisively against, any content or conduct that sexualises, exploits, endangers, or grooms a minor.

Prevention and detection:

• Image and video uploads are scanned via automated moderation ([AWS Rekognition for images; Google Video Moderation for video]) before public availability; media defaults to pending and only approved content is shown publicly.
• Live streaming (Go Live, Battles) is the highest-risk surface because it cannot be pre-moderated. See the Live Streaming & Creator Terms and the Moderation-Ops Runbook for real-time controls (kill-switch, in-stream reporting, proactive sampling, banned-term detection).
• [CONSIDER] integrating known-CSAM hash-matching (e.g. via a service such as Thorn Safer, or PhotoDNA where available) so known illegal material is blocked at upload.

Response and reporting:

• Suspected CSEA content is immediately removed/quarantined, the account is suspended, and evidence is preserved (do not delete; preserve per legal-hold).
• We report suspected CSEA to the appropriate authorities, which may include:
• the eSafety Commissioner (Australia);
• the Australian Centre to Counter Child Exploitation (ACCCE) / AFP; and
• NCMEC (US National Center for Missing & Exploited Children) CyberTipline where there is a US nexus or where required by a processor's terms.

No private-channel risk to minors: because the platform is 16+, but as a safeguard, we design against features that enable an adult to isolate, privately contact, or build secrecy with a younger or vulnerable user.

06Roles, records, and review

To evidence "reasonable steps", we maintain:

• Verification methodology + rationale (this document plus the technical configuration).
• Verification attempt logs (method used, outcome, timestamp).
• Dispute/appeal cases and outcomes.
• PIA/DPIA for the age-assurance and moderation flows.
• Staff training records and moderation audit results.

Accountable owner: Annol Kimurgor, Director, Belaffee Pty Ltd. Review cycle: at least every 6 months and after any material change to features (e.g. launching live streaming) or to applicable law.

07Contact

• Child-safety / urgent: safety@revvmeet.com
• Privacy: privacy@revvmeet.com
• eSafety Commissioner (AU): esafety.gov.au

Document control: drafted 17 June 2026. Pending: (i) lawyer review; (ii) selection + integration of age-assurance provider; (iii) DPIA completion; (iv) reporting-pathway confirmation.