Skip to content
BeMe
Home How It Works Pricing About FAQ
Parent Login Get Started
Home How It Works Pricing About FAQ Parent Login Get Started
Parent Consent & Data Protection

You stay in control of your child’s digital protection.

Before BeMe begins protecting a child’s digital environment, we first verify the adult providing consent. This page explains what you agree to, what information may be used, what BeMe avoids collecting, and how you can change your decision later.

Last updated: 27 July 2026 Consent can be reviewed or withdrawn
Consent before protection

BeMe does not begin child-related processing until the parent journey is completed.

  • The adult confirms lawful parental or guardian authority
  • The adult accepts the relevant legal documents
  • Phone and identity verification are completed
  • A verifiable consent record is created

Verified adult

BeMe confirms that consent comes from an adult claiming lawful authority over the child.

Specific permission

Consent covers defined safety, account, verification and security purposes—not unrestricted use.

Recorded clearly

A consent reference connects the parent’s declarations, verification steps and accepted legal versions.

Withdrawable

A verified parent may request withdrawal of consent and discontinuation of child-related processing.

On this page
1. Why verification comes first 2. The consent journey 3. Who may provide consent 4. What you are consenting to 5. Device permissions 6. The consent record 7. What BeMe may store 8. What BeMe does not intend to do 9. How child data is protected 10. AI safety analysis 11. Human access 12. Service providers and disclosure 13. Retention and deletion 14. Parent rights and controls 15. Withdrawing consent 16. Explaining BeMe to your child 17. Security safeguards 18. Changes requiring fresh consent 19. Questions and contact
Starting onboarding?

The interactive consent and verification journey is separate from this reference page.

Begin Parent Consent
In plain English

BeMe asks an adult to verify first because a child cannot independently authorise the processing required for the service. Consent is tied to a clear purpose, recorded for accountability and capable of being withdrawn.

01

Why parent verification comes first

BeMe is designed for child-safety use. Providing that protection may require the processing of information associated with a child’s device, communications environment, safety alerts and parent account.

Because this information can be sensitive, BeMe does not rely on a simple unchecked statement that someone is a parent. The onboarding process is designed to obtain an affirmative declaration, verify the adult’s contact details and identity, and create a record showing what was accepted.

A checkbox alone is not the complete consent evidence.

The checkbox records the parent’s decision. The wider consent record connects that decision with verification results, timestamps and the legal text accepted.

02

The consent journey

The parent journey is designed as a sequence of clear, intentional steps:

01

Review. The adult reads the consent explanation and linked legal documents.

02

Declare. The adult confirms age, authority and understanding through affirmative actions.

03

Verify contact. The registered phone number is confirmed through OTP or an equivalent method.

04

Verify identity. The adult completes the supported identity-verification journey.

05

Create evidence. BeMe generates a unique consent reference and records the result.

06

Continue. Child onboarding and device configuration can begin after successful completion.

A failed, abandoned or incomplete verification journey does not authorise BeMe to begin the protected child-data processing that depends on verified consent.

03

Who may provide consent

The consenting person must be at least 18 years old, legally competent and the child’s biological parent, lawful guardian, or another person possessing valid legal authority to make the relevant decision.

A minor cannot independently create a verified parent account, consent on behalf of an adult, or bypass the verification process. A person without lawful authority must not configure BeMe on a child’s device.

Authority must be genuine and current

If guardianship, custody or decision-making authority changes, the parent account information and permissions should be updated promptly.

04

What you are consenting to

By completing the parent-consent journey, you authorise BeMe to perform the processing reasonably required for the selected service. Depending on the final product configuration, this may include:

Parent account operation

Creating and securing the verified parent profile, dashboard and contact channels.

Identity and authority checks

Confirming the adult’s phone number, identity and consent completion status.

Child onboarding

Linking an authorised child profile, device and supported safety configuration.

Safety analysis

Identifying patterns that may indicate grooming, bullying, sextortion or other supported risks.

Parent alerts

Providing risk classifications, contextual summaries and safety notifications.

Service security

Preventing misuse, protecting accounts, investigating incidents and maintaining audit records.

Consent is not permission for BeMe to use child information for any unrelated purpose. Processing remains subject to the Privacy Policy, Child Safety Policy and applicable law.

05

Device permissions remain visible and controllable

Certain BeMe features may require device or operating-system permissions. These may vary according to the device, supported application and feature being configured.

The parent should review each permission before enabling it. Permissions may ordinarily be changed or revoked through the relevant device or application settings, although revocation may reduce or disable the associated protection.

Granting one permission does not automatically authorise unrelated permissions. BeMe should request access in a manner connected to the feature for which that access is needed.

06

The BeMe consent record

When the journey is completed successfully, BeMe may create a Consent Record that connects the adult’s declarations and verification results to a unique reference.

One consent reference. One connected evidence trail.

The same consent reference may connect consent acceptance, OTP verification, identity verification, the parent account, later child onboarding, permissions and any subsequent withdrawal or update.

The record may include:

  • A unique Consent ID or UUID
  • The server-generated date and time of consent
  • The version of each accepted legal document
  • A cryptographic hash or equivalent integrity reference for the accepted document
  • The state of each required checkbox or affirmative action
  • OTP verification status and timestamp
  • Identity-verification status and timestamp
  • Relevant technical session information, such as IP address and user agent
  • Later consent changes, withdrawal requests or re-verification events
07

What BeMe may store

The exact information stored depends on the final technical architecture, provider integration, enabled features and applicable legal obligations. Categories may include:

Parent information

Name, contact details, account identifiers and verification status.

Consent evidence

Consent reference, timestamps, declarations, accepted versions and audit events.

Child profile information

Limited details required to connect the authorised child profile and device.

Device information

Device identifiers, operating-system details, permissions and configuration status.

Safety information

Risk events, classifications, alert metadata and limited context needed for the parent.

Security records

Login events, access logs, suspected misuse, incident records and support activity.

The Privacy Policy should be treated as the detailed source for final data categories, purposes, retention and service-provider disclosures.

08

What BeMe does not intend to do

BeMe’s child-safety purpose does not require unrestricted commercial use of a child’s information. BeMe does not intend to:

01

Sell children’s personal data to data brokers or advertisers.

02

Create cross-service behavioural advertising profiles of children.

03

Use private child communications for unrelated marketing.

04

Allow routine employee reading of private conversations.

05

Require passwords, banking information or unnecessary identity documents by email.

06

Use BeMe as a covert surveillance tool for adults, partners or employees.

09

How child information is protected

BeMe aims to apply privacy-by-design and data-minimisation principles to child-related processing. This means collecting or retaining only what is reasonably required for the stated safety, security and compliance purposes.

Access should be limited according to role and need. Sensitive information should not be exposed broadly within the organisation, and service providers should receive only the information needed to perform their contracted function.

Where the product architecture supports on-device processing, certain analysis may occur locally rather than requiring complete message content to be transferred to BeMe systems. The final technical behaviour must be reflected accurately in the Privacy Policy.

10

Consent to AI-assisted safety analysis

BeMe may use automated and AI-assisted systems to identify linguistic, behavioural or contextual patterns associated with supported online-safety risks.

These systems may make mistakes. They can misread sarcasm, slang, cultural references, relationship context or message history. They can also miss harmful conduct that occurs on unsupported platforms or is disguised through images, code words or disappearing content.

AI identifies signals. Parents make decisions.

An alert is not proof of abuse, guilt or criminal conduct. Parents should assess context and seek qualified assistance where the concern is serious.

11

Human access is not the default

BeMe is intended to rely primarily on automated processing rather than routine manual reading of a child’s private communications by employees.

Limited human access may occur only where technically available, legally permitted and reasonably necessary for an authorised support request, security investigation, abuse prevention, legal compliance or another documented operational need.

Such access should be restricted to authorised personnel, subject to confidentiality and limited to the minimum information reasonably required.

12

Service providers and permitted disclosures

BeMe may use carefully selected service providers for functions such as identity verification, OTP delivery, cloud hosting, security, payment processing, communications and technical support.

Service providers should be contractually restricted to using personal information for the agreed service and should apply appropriate confidentiality and security measures.

Information may also be disclosed where required by applicable law, valid legal process, a competent regulator or another lawful authority, or where reasonably necessary to protect a child or another person from serious harm.

13

Retention and deletion

Personal information should not be retained indefinitely merely because it was collected. Retention depends on the type of information, service need, account status, legal obligations, security requirements and dispute or audit needs.

Final periods to be confirmed

[INSERT THE APPROVED RETENTION PERIODS FOR ACTIVE ACCOUNT DATA, CHILD-SAFETY RECORDS, CONSENT EVIDENCE, VERIFICATION RESULTS, SUPPORT RECORDS AND DELETED ACCOUNTS.]

When information is no longer required, BeMe should delete, anonymise or securely isolate it in accordance with the approved retention schedule and technical capabilities.

Some records—particularly consent evidence, transaction records, fraud-prevention logs or legal notices—may need to be retained after account closure where legally required or reasonably necessary to establish compliance.

14

Your rights and controls as a verified parent

Subject to applicable law, verification and permitted exceptions, a parent may request:

  • Access to information about the parent account and linked child profile
  • Correction of inaccurate or incomplete parent or child information
  • Review of consent status and accepted document versions
  • Withdrawal of consent for child-related processing
  • Deletion or closure of the account and linked child profile
  • Information about relevant service providers or processing purposes
  • Review of a grievance or unresolved privacy concern

BeMe may need to verify the requester before fulfilling a sensitive request. A request may be limited where disclosure would adversely affect another person, reveal protected security information, conflict with law or prevent retention of a record BeMe is required to preserve.

15

What happens when consent is withdrawn

A verified parent may withdraw consent through the available account controls or by submitting a verified request to BeMe.

After valid withdrawal, BeMe should stop future child-related processing that depends on that consent. This may disable monitoring, alerts, device connections and other protection features linked to the child profile.

Withdrawal affects future processing

It does not automatically make earlier lawful processing invalid, erase records that must be retained by law, cancel an unpaid financial obligation, or prevent BeMe from preserving limited evidence required for security or legal compliance.

BeMe may request re-verification before processing a withdrawal to prevent an unauthorised person from disabling a child’s protections or deleting sensitive records.

16

Explaining BeMe to your child

Where safe and age-appropriate, parents are encouraged to explain why BeMe is being used, what types of online risks it is designed to identify, what alerts may be shared with the parent and how the child can raise a concern.

Using child-safety technology openly can support trust and reduce the risk that protection is experienced as punishment or secret surveillance.

Parents should avoid shaming, threatening or automatically punishing a child based solely on an alert. A child may be the victim of manipulation, grooming, coercion or abuse and should be approached calmly and protectively.

17

Security safeguards

BeMe aims to use technical and organisational safeguards appropriate to the nature of the information and the risks involved.

Encryption

Protecting information in transit and, where appropriate, at rest.

Access controls

Restricting administrative and operational access according to role and need.

Audit trails

Recording important consent, account, security and administrative events.

Least privilege

Limiting personnel and provider access to the minimum required function.

Account protection

Using verification, secure sessions and other controls to reduce unauthorised access.

Incident response

Investigating, containing and responding to suspected security or privacy incidents.

No service can guarantee absolute security. Parents should use a strong password, secure their phone and email account, protect OTPs and promptly report suspected compromise.

18

Changes that may require fresh consent

BeMe may update features and legal documents over time. A minor wording or formatting change may not require the parent to repeat the full journey.

However, BeMe may seek fresh consent where a material change affects:

  • The categories of child information processed
  • The purpose of child-related processing
  • The permissions required from the child’s device
  • The nature of AI-assisted analysis or parent alerts
  • The parties receiving sensitive child information
  • The legal basis or parent declarations relied upon

Fresh consent may be linked to the existing parent account and consent history so that the evidence trail remains clear.

19

Questions, requests and grievances

For questions about parent verification, consent status, account data, withdrawal, correction, deletion or privacy, contact BeMe using the details below.

Legal entity [INSERT REGISTERED LEGAL ENTITY NAME]
Privacy/support email [INSERT PRIVACY OR SUPPORT EMAIL]
Grievance Officer [INSERT NAME OR DESIGNATION]
Grievance email [INSERT GRIEVANCE OFFICER EMAIL]
Registered or business address [INSERT COMPLETE REGISTERED/BUSINESS ADDRESS]
Protect your verification details

Never send your password, OTP, banking information or an unnecessary government identity document by ordinary email. BeMe may ask you to use a secure verification channel instead.

Consent is a continuing relationship—not a one-time checkbox

This page should be reviewed against BeMe’s final identity provider, technical architecture, retention schedule and legal advice before commercial launch.

Ready to continue?

Begin the verified parent-consent journey.

Review the agreement, confirm your authority and proceed securely to identity verification.

Begin Parent Consent
BeMe

AI-powered child-safety technology designed to help parents recognise serious online risks while keeping consent, privacy and responsible data practices at the centre.

Verified Parent Consent Privacy by Design

Product

How It Works Get Started Features Pricing FAQs

Company

Our Team About BeMe Contact Support

Legal

Privacy Policy Terms of Use Child Safety Policy Consent & Data Protection Cookie Policy
Need help?

Let’s make digital safety easier to understand.

Questions about consent, supported devices or how BeMe works? Reach out to the team.

Contact BeMe
Built around responsible protection
Verified Parent Consent Privacy by Design Responsible AI Data Protection Principles

© 2026 BeMe Labs. All rights reserved.

BeMe is an awareness and alerting platform. It does not replace parents, emergency services, law enforcement or professional support.