Effective date:
Story for Kids is a personalized story application published by CuteGhost. This policy explains its child profiles, AI generation, story storage and sharing, subscriptions, customer support, and privacy controls. It applies specifically to Story for Kids, not to every other CuteGhost application.
For privacy questions and parental requests, contact support@cuteghost.com.
Profiles and choices: A parent can enter a child's name or nickname, age range, gender, interests, and picture, and choose story settings such as companion, theme, goal, mood, ending, and narrator. Profiles and preferences are stored locally. When a story is requested, the relevant profile details and choices are also sent to our backend and stored with the story request. Please avoid entering surnames, addresses, school details, or other unnecessary identifying information in names or descriptions.
Pictures and descriptions: If a parent chooses AI picture generation, the selected photograph or written description is sent for processing. The original selected photograph is used in the generation request and is not saved as an original photograph in our Firebase database or Storage by the current app. The resulting generated pictures, their descriptions, and job records may be stored. This does not mean an external AI provider has no retention; its processing is addressed below.
Stories and generated content: We store story requests, concepts, selected concepts, generated text, pictures, synthetic narration, and generation status and evaluation records. Downloads and exported files can also be stored on your device. The app does not require recordings of a child's voice to create narration.
Account and usage identifiers: Firebase Authentication creates an account identifier without requiring an email address or password. We use it to associate requests and stored content with the account. Generation requests also send this account identifier to our third-party AI service as a session identifier.
To enforce generation allowances across account deletion and reinstalling, we verify Apple's signed app transaction and a device-verification value. We derive a hashed quota identifier from the verified app transaction, application, and environment. We retain this pseudonymous identifier, generation counts, and usage-period dates. It is not anonymous merely because it is hashed. Our quota-verification code does not save the raw signed Apple transaction or device-verification UUID in the quota ledger or its logs.
Purchases: Apple processes App Store payments. RevenueCat processes purchase and subscription information and account identifiers so the app can determine subscription access. We do not receive your full payment-card details.
Support and operations: If a parent contacts us in the app, our separate support service receives the message, the account identifier, app version, and operating-system version, and stores the conversation and replies. Our infrastructure and service providers also process request and security metadata needed to run their services. Backend operational logs can include account and job identifiers, timestamps, model names, statuses, and errors.
We use information to create personalized stories and pictures, provide synthetic narration, store and download content, support parent controls, deliver requested sharing, handle support, determine subscription access, enforce generation allowances, and protect and operate the service.
Story for Kids does not display third-party advertisements, use AdMob, or send behavioral event analytics through Firebase Analytics in this release. We do not sell personal information. Necessary operational diagnostics are different from advertising or behavioral analytics.
AI generation uses third-party AI services, including large language models and services that generate pictures and synthetic narration. These services may route requests to other model-hosting providers. Depending on the requested feature, the request may contain the child's name, age range, gender, interests, story choices, written descriptions, generated content, and reference pictures. A selected original child photograph is sent for picture generation only when the parent chooses that feature. Subsequent story requests may use the generated avatar as a reference picture.
Our AI service providers receive the content needed to perform the requested generation and an account-based session identifier. Depending on the feature, this can include the profile details, descriptions, pictures, and generated content described above.
Google Firebase provides authentication, App Check, cloud functions, database, and content storage. Apple provides App Store purchases and signed app-transaction information. RevenueCat provides subscription access management. Our support service operates separately on Google Cloud.
These providers process information to deliver the requested features and operate their services. Third-party AI providers may retain requests, reference pictures, generated outputs, and related technical information under their own terms, privacy policies, and service settings. Data-handling practices, retention periods, and permitted uses vary by provider; we do not promise that AI processing has zero retention or that provider-held data is deleted immediately after generation.
Do not assume that withdrawing permission in the app deletes information already processed by a provider. Contact us with questions or deletion requests concerning previously transferred information.
Profile setup and parent controls are accessed through parent mode. Child mode applies the permissions selected for the active child. Parents can control browsing of the public story shelf, starting new stories, and the story choices available to a child.
Opening an unfamiliar shared-story link in child mode requires the parental gate before its preview is fetched or displayed. Downloading an incoming shared story requires parent mode. Stories already installed on the device remain readable.
Before starting story creation or AI picture generation without existing permission, the app presents an AI permission notice. Declining does not send that generation request. Permission is stored on this device and covers subsequent story and picture generation on this device.
A parent can withdraw AI access in parent Settings. Future generation asks for permission again. Existing downloaded stories remain readable, and requests already accepted by our backend may finish. Withdrawal does not by itself delete existing profiles, content, or support records.
Camera and photo permissions can also be managed in iOS Settings. The app's parental gate and local permission setting are access controls; they are not, by themselves, proof that legally verifiable parental consent has been obtained.
Stories are not added to a public community feed automatically. A parent can enable a story-sharing link or export and share a file. Anyone with a valid link and access to the app may obtain the shared story's title, text, pictures, and narration. Those outputs can contain the child's name or resemblance. We do not include the full private profile record in the shared-story response.
Disabling a link prevents new shared-story lookups through the app. Previously issued media URLs or copies already obtained by another person may remain usable. Account deletion removes our stored story files and active sharing records. We cannot remotely erase someone else's downloaded or exported copy.
The ready-made public story shelf is separate from these personal sharing links. Disabling browsing of that shelf does not automatically delete previously installed content or revoke personal links enabled by a parent.
Locally saved profiles and downloads remain on your device until removed through available app controls, account deletion, or removal of app data. Removing only a local story download does not delete its backend record. Removing only a child profile locally does not erase the profile details already contained in earlier story requests.
Delete Account in parent Settings deletes the Firebase authentication account, account-associated story and custom-picture records, stored user media, and active sharing records in our story backend. After our server acknowledges the deletion request, the app signs out and attempts to remove its locally saved profiles and account content. Online cleanup continues in the background; the local completion message does not confirm that online cleanup has finished. The current local cleanup does not explicitly clear Firestore's persistent offline cache, and exported copies may remain outside the app's managed storage. Minimal pseudonymous quota records remain separately to enforce allowances and prevent repeated account deletion from resetting generation limits. These quota records do not contain child names, photographs, or story text.
The separate support service is not automatically erased by the current in-app account deletion operation. Contact support@cuteghost.com to request review or deletion of support information. Purchase records held by Apple and service-provider records are subject to their applicable obligations and retention arrangements.
Parents may contact support@cuteghost.com to request access to, correction of, or deletion of their child's information, or to object to further use. We may need to verify the requester's authority before disclosing or deleting information. Please do not send additional child photographs or unnecessary identifying details just to make a privacy request.
Deleting your account does not cancel an Apple subscription. Manage or cancel subscriptions through your Apple account's subscription settings.
We use authenticated services and access controls to help protect stored information. No service can guarantee absolute security. Our infrastructure and providers may process information outside your country. Processing locations depend on where our service providers operate, and privacy laws may differ from those in your country.
We will update this policy when our practices change and show the revised effective date. Where applicable law requires additional notice or renewed parental consent, simply continuing to use the app is not a substitute.
Privacy questions and parental requests: support@cuteghost.com.
The following general policy applies to CuteGhost applications other than Story for Kids, unless an application has its own specific policy. It does not describe Story for Kids. For Story for Kids, including its profiles, AI processing, subscriptions, support, and deletion, use the dedicated policy above.
This general policy applies to CuteGhost applications other than Story for Kids unless we provide an application-specific policy. The dedicated Story for Kids policy above applies to Story for Kids and takes precedence over this general policy for that application.
A) Analytics and app usage data
We use Firebase Analytics to understand how users interact with the Apps. This may collect information such as:
We do not use Firebase Analytics to collect your name, personal contacts, or private content.
B) Crash and diagnostics data
We collect crash and diagnostics information to identify and fix bugs and improve stability. This may include:
C) Advertising data (AdMob)
Some Apps display ads using Google AdMob. Ad providers may automatically collect information such as:
AdMob and other ad partners may use this data to measure ad performance and, where allowed, provide personalized ads.
D) Permissions you choose to grant (Camera/Photos/etc.)
Some features may request device permissions such as Camera or Photos. When you use these features:
We do not intentionally store your photos/videos on our servers. However, if a feature relies on a third-party service (for example, for ad measurement or analytics around that feature), limited data may be transmitted to that provider as described in this policy.
Important: Permission prompts and in-app explanations describe why the permission is needed. You can deny permissions and still use other parts of the Apps.
We use collected information to:
We may share information in these situations:
A) With service providers (third parties)
We use third-party services to operate and improve the Apps, such as:
These providers may process data according to their own privacy policies and terms. We only use reputable providers and configure them to the extent available to limit data collection to what is necessary.
B) Legal and safety reasons
We may disclose information if required to comply with law, enforce our terms, or protect the rights and safety of users and others.
C) Business changes
If we are involved in a merger, acquisition, or sale of assets, information may be transferred as part of that transaction.
A) App permissions
You can manage permissions (Camera, Photos, etc.) in your device settings at any time.
B) Analytics
Depending on your device and platform options, you may be able to limit some analytics collection through system privacy settings.
C) Advertising / tracking (iOS)
If an App uses tracking for ads, iOS may show an App Tracking Transparency prompt. You can allow or deny tracking. You can also manage this later in iOS settings.
D) Personalized ads
Where available, you may be able to limit personalized ads through device settings and Google ad settings.
We retain analytics and crash/diagnostic data only as long as needed for:
Retention periods can also depend on the default retention settings of Firebase/AdMob and the controls they provide.
We take reasonable measures to protect information from unauthorized access, alteration, or destruction. However, no method of transmission or storage is 100% secure.
Our Apps may be used by children (for example, math learning apps). We do not knowingly collect personal information directly from children. If you believe a child provided personal information to us, contact us and we will take appropriate steps to delete it where applicable.
Note: Apps that show ads may still involve third-party ad/analytics collection as described above. We encourage parents/guardians to supervise children’s app use and review device privacy settings.
Your information may be processed in countries other than where you live, depending on where service providers (such as Google) operate their systems.
We may update this Privacy Policy from time to time. When we make changes, we will update this page with the revised policy. Continued use of the Apps after changes means you accept the updated policy.
If you have questions about this Privacy Policy or privacy practices, contact: support@cuteghost.com