Child safety,
treated as product
architecture.
The safest version of a children’s product is often the one that removes the risky layer entirely. Dreamtime Stories keeps the surface intentionally narrow: no behavioral advertising, no social mechanics, and adult-facing account controls.
Last updated: June 2026
No ads and no behavioral advertising
We do not run display ads, rewarded ads, or behavioral advertising in Dreamtime Stories. We do not use child activity to build advertising profiles.
No chat, no public profiles, no user-generated content
Dreamtime Stories does not expose open chat, friend systems, public posting, or community feeds. That removes an entire class of stranger-contact and moderation risk.
Sensitive actions stay in adult-facing flows
Purchases, account deletion, privacy requests, and other account-level actions are handled through parent-managed or adult-facing surfaces rather than child-directed flows.
Limited first-party analytics only
Where product analytics are enabled, they are collected in our own backend for internal operations and product improvement. We do not send these events to third-party analytics or ad-tech platforms.
We avoid child-input surfaces that do not need to exist
We do not ask children to submit names, email addresses, photos, or free-form text in the normal product experience. The product is intentionally narrower for that reason.
Data in transit is encrypted
Traffic between the app, website, and backend is protected with TLS. Account credentials are stored using standard password hashing rather than reversible storage.
We remove avoidable risk before adding controls
We prefer to remove high-risk mechanics instead of layering warnings on top of them later. That is why Dreamtime Stories avoids ads, social posting, and unnecessary data collection in the first place.
For more detail on analytics, retention, and deletion, see the privacy policy and the account deletion page.