Privacy policy

The short version

Dreambly World keeps normal play and progress on the device. Cloud personalization remains off until Dreambly enables it for the closed beta, and even then it works only inside PIN-protected Parental settings after a parent or legal guardian reads our notice and enters a beta access code. Only then may the parent send a one-word name the parent gives a story character, optional pronunciation help, character choice, and the story text needed to create private narration and matching captions. Only the parent or legal guardian operates personalization; children do not enter names and only read or listen to a finished edition. Dreambly does not collect a parent email for this feature. The voice provider may keep the request text and generated audio in Dreambly’s account history; see “Personalized editions” below. The beta has no child accounts, ads, real-money purchases, third-party analytics, behavioral tracking, or public sharing.

Information kept on your device

The app stores only the information needed to make the experience work on the device, including:

• explorer names or nicknames, story casting choices, progress, unlocked activities, and app preferences;
• download and offline-cache status for story, art, audio, and app files; and
• technical status used to show whether offline content is ready.

Except when a parent starts the custom narration process described below, this information stays in the browser or app storage on the device. Local information can be removed by clearing the site's or app's storage. In a Trusted Web Activity, uninstalling the app may not clear the browser origin’s storage; Parental settings includes the explicit deletion control for personalized data. Explorer profile names are never sent and are never used for personalization.

Network activity

The iPhone and iPad app packages its interface, stories, illustrations, narration, captions, and games inside the installed app. The web edition downloads those same files from the Dreambly World site so they can be available offline. When closed-beta personalization is enabled, the web or Android edition downloads requested custom narration and matching captions from Dreambly’s narration service, which runs on our infrastructure provider. That provider processes beta access records, rendering requests, and private generated files on Dreambly’s behalf. The running experience does not use third-party analytics, advertising, or behavioral tracking.

Parental access code

The local four-digit PIN is an adult gate for Parental settings; it does not by itself unlock cloud narration. Parental settings lock again as soon as the adult returns to the stories, and always within 15 minutes, so creating or editing an edition asks for the PIN each time. During the closed beta, cloud narration also requires a beta access code that Dreambly gives directly to a participating parent. Before a code is accepted, Parental settings shows our notice describing what is sent, where it goes, how long it is kept, and how to remove it. The parent confirms that they are the parent or legal guardian and enters the code; no name is sent at that step.

The access code is not an account. Dreambly does not collect the parent’s email, name, or any other contact detail to issue or redeem it. Entering a code creates a beta access token on this device. Dreambly’s service stores only a keyed hash of the code, a hash of the token, the notice version the parent saw, the issue and expiry times, and a count of the test editions used. Each code can be activated on a limited number of devices, includes a small number of test editions at no charge, and cannot be bought. Access expires after 90 days and must be entered again sooner if the notice, provider, data, or purpose materially changes. Choosing Remove personalization & delete revokes the token on the server, deletes linked hosted jobs, and removes personalized data from the device.

Personalized editions and purchases

The web playtest may show a clearly labeled, no-charge preview of the parent purchase and personalization flow. It does not process a payment. A future store release may offer a one-time personalized edition purchase behind the parental gate. Apple or Google would process that transaction and payment details; Dreambly World would use only the resulting entitlement status to unlock the feature.

With an active beta access token, choosing Hear in story voice or Create edition sends, for each of up to two characters the parent casts in a supported story, a one-word name the parent gives a story character, optional pronunciation help, the selected character, the story-pronoun choice for that character in this edition (keep the original, she/her, he/him, or they/them), the story identifier, and only the narration text needed for that request through our infrastructure provider to our voice-generation provider. A name preview sends only that one character’s name and pronunciation help with the story and character choice. Story pronouns describe how a character is referred to in the edition and are not a request for a child’s gender; Dreambly does not ask for age, gender, birthday, or a photo. The beta access token, profile identifier, and network address are not sent to the voice-generation provider, and nothing in the request identifies your family. The voice is chosen by Dreambly for that story. The voice-generation provider may keep the request text and generated audio in Dreambly’s account history and is not obliged to delete it; because nothing in that history identifies a family, Dreambly cannot remove one family’s entries from it. Dreambly does not permit advertising, profiling, public posting, or sale of this information. Before enabling personalization, Dreambly turns off model training for its voice-generation account through the provider’s data-use setting and keeps dated evidence of that setting; the in-app notice carries the no-training statement only while that opt-out is in force and evidenced. This feature remains disabled unless these safeguards and the provider terms Dreambly has accepted are in place.

Generated audio, captions, and the edition manifest are stored privately under a random identifier while the edition is being prepared and are accessible only with the beta access token. After every file is downloaded and verified, the app requests immediate deletion of the hosted copy. Interrupted or abandoned jobs and hosted files are automatically removed within 24 hours. The verified device copy remains available offline until the parent removes personalization, uses the original-story option, or clears local storage. A keyed HMAC of the requesting network address and request times is retained for no more than 24 hours to enforce abuse and cost limits; request bodies and names are excluded from application logs and caches.

Children and families

Dreambly World is designed for children to use with their families. Custom narration is offered only inside PIN-protected Parental settings with a beta access code. The parent or legal guardian, not the child, chooses the story character, enters a one-word name the parent gives a story character and optional pronunciation help, previews the name, and creates, edits, or removes the edition. Children only read or listen to the finished edition; the child experience has no name entry, generation, purchase, chat, or microphone feature. Personalization is optional: children can read every original story without a parent providing a name for cloud narration. A parent may review the categories of information associated with their beta access, stop future collection, remove personalization, and request deletion from Parental settings or by contacting Dreambly. Removal immediately blocks new generation and removes local personalized narration, captions, cached previews, and choices; hosted jobs linked to that access token are also deleted.

Service providers and security

Dreambly uses an infrastructure provider for private app infrastructure and generated-file storage and a voice-generation provider for the parent-requested voice rendering. No email provider is involved in this feature. The names of these providers are available on request through support@dreamblyme.com. These providers may process only the limited information needed to perform their contracted service. Dreambly requires restricted use, security, and deletion terms before enabling closed-beta personalization and discloses the provider’s retention above. Beta access tokens are high-entropy, stored only as hashes on the server, scoped to personalization routes, and revoked on removal. Personalized network responses are marked private and not cacheable by shared caches.

Contact

Dreambly World is operated by Dreambly Me, LLC, 5900 Balcones Drive STE 100, Austin, TX 78731, United States. Questions, parent-access requests, removal requests, and deletion requests can be sent to support@dreamblyme.com, made by phone at (512) 650-8563, or mailed to the address above. If you choose to email, the information in your message is handled by your email provider and received only so the request can be answered and documented.

Policy updates

If the app's data practices change, this page will be updated before the changed practices are released. The effective date above shows when this policy was last revised.