Skip to content

Collect less, expose less, and keep a record of every high-risk access.

Privacy Center explains how data is used in product language; formal legal policies and regional terms are provided separately in Legal Center.

Identity, Safety Event, growth content, and payment data are not piled into one big table.

Identity

Family / Child / Consent

Safety

Events / Handover / Evidence

Content

Artifacts / Portfolio

Billing

Entitlement / Payment

A binding relationship does not mean access to all data.

Institutions can only read the fields required for the current service by default; Partner uses a scoped token.

  • Family: full calendar & alerts
  • Institution: assigned children only
  • Partner: scoped token

High-risk operations must leave a record of who did what, and when.

  1. Access record: who viewed what, whenAudited
  2. Change record: high-risk actions only
  3. Export / deletion request history

A unified product does not mean children's sensitive data is centralized across borders by default.

01

Japan data plane

02

China data plane

Children's work is not public content by default.

Works entered into Grow are governed separately from the platform's own content; they must not be used for marketing by default.

Need to access, export, or delete data?

Specific rights and processing timelines follow the formal policy of your region.

  • Access request
  • Export
  • Delete / correct