Provide the service
We use account and story-related information to let users sign in with email or Sign in with Apple, create story drafts, generate storybooks, open finished stories, and return to previously created content.
Detailed Privacy Policy
Privacy Policy for StoryWithMe
This Privacy Policy explains what information StoryWithMe collects, how we use it, how we store it, and what choices users have.
Overview
What this policy covers
StoryWithMe is an AI storybook creator intended to help parents and families create and read personalized illustrated stories together. This policy applies to StoryWithMe, this support website, and related support communications.
StoryWithMe is designed for parent-managed and family-managed storytelling. We expect a parent, guardian, or another responsible adult to create and manage the account and decide what information is entered into StoryWithMe.
Collected Data
Information we collect
We keep collection to the minimum needed to provide StoryWithMe. We do not collect biometric identifiers for child identification.
| Data category | Examples | How collected | Main use |
|---|---|---|---|
| Account information | Email address, display name, login method, session token, Apple user identifier when Sign in with Apple is used | Entered by the user during sign in or account setup, or received from Apple when the user chooses Sign in with Apple | Authentication, account continuity, and support |
| Profile information | User avatar, profile completion state | Added or updated inside StoryWithMe | Display profile information and personalize the account |
| Family and role data | Character names or nicknames, age or age range if provided, hobbies, companion descriptions, role traits, story preferences | Entered by the user when creating story characters | Generate consistent personalized stories and role-based story content |
| Uploaded photos or images | Photos uploaded for Family, Friends, Toys, or companion-style characters | Uploaded by the user when they choose to add a photo-based character | Create an illustrated character reference and generate personalized storybook illustrations |
| Story creation inputs | Story prompt, selected art style, page count, selected characters | Entered by the user when starting a story draft | Generate the requested storybook |
| Generated content | Story text, story pages, story cover, generated illustrations | Created by the service after a generation request | Let the user read, revisit, and manage finished stories |
| Voice recordings and voice profiles | Microphone recording, voice profile name, voice sample URL, provider voice identifier, consent confirmation, and voice profile status | Recorded or uploaded only when the user chooses to create a custom voice profile | Create and manage optional custom read-aloud voices for private family story narration |
| Read-aloud audio data | Selected voice, story page text sent for narration, generated audio file, audio URL, page timing or word timing data, audio generation status | Created when the user requests read-aloud audio for a story page | Play narrated story pages, cache generated audio, and keep reading progress aligned with the page text |
| Purchase and entitlement information | App Store product identifier, transaction identifier, original transaction identifier, purchase or restore status, subscription status, current period dates, coin balance, coin ledger entries, and limited App Store verification data | Received from Apple StoreKit, Apple App Store Server APIs, and StoryWithMe purchase confirmation flows | Deliver subscriptions, one-time coin packs, feature entitlements, purchase restore, refunds or dispute support, and fraud prevention |
| Device and diagnostics information | App version, language, platform, basic usage events, advertising or device identifiers where allowed, and limited diagnostics from service providers | Collected during use of StoryWithMe | Maintain app reliability, troubleshoot issues, understand feature health, measure advertising performance, and improve the service |
| Support communications | Email content sent to support@storywithme.love | Provided by the user when contacting support | Customer support, troubleshooting, privacy requests, and submission communication |
How We Use Data
Why StoryWithMe uses personal and story-related information
Personalize story generation
Character names or nicknames, descriptions, hobbies, age or age range if provided, role descriptions, style choices, uploaded images if provided, and story prompts are used to create more relevant, more consistent, and more personalized storybook results.
Maintain safety and quality
User text, uploaded images, generated story text, and generated illustrations may be checked through moderation, validation, or safety flows to reduce unsafe, inappropriate, or unusable content and to support product integrity. Voice recordings and generated audio may also be processed to create, validate, and deliver read-aloud features.
Provide purchases and entitlements
Purchase and entitlement information is used to verify App Store purchases, activate subscriptions, add coins, prevent duplicate grants, restore eligible purchases, and help with billing or purchase-related support.
Respond to support requests
We use information users provide in support messages to answer questions, investigate problems, and respond to privacy-related requests.
Measure advertising performance
With user permission where required by platform rules, StoryWithMe may use Meta/Facebook App Events to understand whether StoryWithMe ads lead to app installs, app activity, or purchases, and to improve StoryWithMe advertising campaigns.
Voice and Audio
How optional voice cloning and read-aloud audio work
StoryWithMe offers read-aloud story features. Custom voice profiles are optional and should only be created by an adult who has the right and permission to use the recorded voice.
Microphone permission
StoryWithMe asks for microphone access only when a user chooses to record a voice sample. Users can decline microphone access, use default narrator voices, and manage microphone permission in iOS Settings.
Voice sample consent
A custom voice profile requires consent before it is saved. The person recording should be the speaker or should have clear permission from the speaker. Voice cloning must not be used to imitate someone without authorization.
Voice processing providers
Voice samples, selected voice profile details, and story text may be processed by trusted text-to-speech or voice service providers to create provider voice identifiers and generated narration audio. These providers may process the data only as needed to provide the requested feature.
Generated narration
Generated read-aloud audio and timing data may be cached so the same story page can play without regenerating audio each time. Users can delete stories or voice profiles inside StoryWithMe.
Purchases
Subscriptions, coin packs, and App Store processing
StoryWithMe uses Apple In-App Purchase for subscriptions and one-time coin packs. Apple processes payment information; we do not receive full credit card or bank account numbers.
Apple payment processing
Purchases are completed through the App Store. Apple may provide transaction identifiers, product identifiers, subscription status, renewal status, and related verification data so StoryWithMe can deliver purchased features.
Subscriptions
StoryWithMe may store subscription plan, status, current period, renewal or restore information, and entitlement history so the app can provide the correct access while the subscription is active.
Coins
Coin balances and coin ledger entries are stored to apply one-time purchases, monthly subscription grants, and feature charges such as additional story creation or optional custom voice recording.
Restore and support
Purchase records may be used to restore eligible purchases, avoid duplicate grants, investigate failed purchases, support refunds or disputes, and prevent fraud or abuse.
Analytics and Ads
Meta/Facebook App Events and tracking permission
StoryWithMe uses product analytics to improve the app. We may also use Meta/Facebook App Events to measure and improve advertising for StoryWithMe on Meta platforms.
Tracking permission on iOS
On iOS, StoryWithMe asks for App Tracking Transparency permission before enabling Meta advertiser tracking or advertiser identifier collection. Users can allow or deny this permission and can change it later in iOS Settings.
Advertising measurement
If permission is granted, Meta/Facebook App Events may receive device identifiers, product interaction events, and limited purchase-related events to measure ad performance and improve StoryWithMe ad campaigns.
Content excluded from ads tracking
StoryWithMe does not send uploaded photos, voice recordings, story prompts, story text, generated story content, child descriptions, or support message content to Meta for advertising tracking.
Internal analytics
StoryWithMe may separately collect app usage events for internal analytics, reliability, and product improvement. These internal analytics are designed to avoid sending passwords, emails, prompts, photos, voice recordings, and story text as event properties.
Data Protection
How data is protected and shared
StoryWithMe does not sell personal information. StoryWithMe may use Meta/Facebook App Events for advertising measurement and campaign improvement only as described in this Privacy Policy and subject to platform permission requirements.
Trusted service providers
We may use trusted service providers to operate StoryWithMe, including hosting, authentication, storage, moderation, AI generation, text-to-speech, voice processing, Apple purchase validation, analytics, crash diagnostics, and support. These providers process information only as needed to provide, secure, improve, or support StoryWithMe.
Feature-based processing
Depending on the feature used, character descriptions, story prompts, uploaded images, voice samples, story text for narration, generated audio, purchase verification data, and generated content may be processed by service providers to generate, moderate, store, verify, or deliver storybook content.
Provider protections
We require service providers to protect user information and to use it only for the purposes described in this Privacy Policy or otherwise disclosed to users.
Limited advertising partners
We do not provide uploaded photos, voice recordings, story prompts, generated stories, or child-related story details to ad networks or data brokers. Advertising measurement data may be shared with Meta/Facebook App Events only for StoryWithMe ad measurement and campaign improvement, and only where permitted.
Security and encrypted transport
StoryWithMe applies security controls to protect data in transit and at rest, including encrypted transport channels and controlled storage access.
Children's Privacy
How StoryWithMe approaches child-related information
StoryWithMe is designed for parent-managed and family-managed storytelling. We expect a parent, guardian, or another responsible adult to create and manage the account and decide what information is entered into StoryWithMe.
For the “Your Child” character type, StoryWithMe does not allow users to upload real-person photos. Child-like story characters are created from text descriptions only.
For Family, Friends, Toys, and companion-style characters, users may optionally upload a photo if they have permission to use it.
We recommend using nicknames or story names instead of full real names when creating characters.
StoryWithMe does not collect or build biometric identifiers from children, including facial-recognition templates or facial feature vectors for child identification.
StoryWithMe does not knowingly send child-related information, child descriptions, uploaded photos, voice recordings, story prompts, or generated story content to Meta/Facebook App Events for advertising tracking.
Retention and Deletion
How long data may be kept
This section explains how long StoryWithMe may keep account information, role information, uploaded content, generated stories, and support records.
StoryWithMe keeps account records, role information, story drafts, uploaded content, voice profiles, generated narration audio, purchase entitlements, coin records, and generated story content while the account remains active so users can access and manage their stories and purchases.
Users can delete characters, stories, uploaded photos, custom voice profiles, and their account from inside StoryWithMe.
When a user deletes a character, story, uploaded photo, custom voice profile, or account, StoryWithMe removes the related active records from the service. Some backup copies may remain for a limited period for security, recovery, or legal reasons before being deleted or overwritten.
Purchase and entitlement records may be retained for as long as reasonably necessary to provide active subscriptions, restore purchases, prevent duplicate grants, support refunds or disputes, satisfy accounting obligations, and comply with App Store or legal requirements.
Support emails and related troubleshooting records may be kept for as long as reasonably necessary to respond, maintain support quality, and document support-related communications.
Some information may be retained where reasonably necessary for security, fraud prevention, legal compliance, billing, dispute handling, or backup and recovery.
User Choices
Access, correction, withdrawal, and privacy requests
Access and updates
Users can update certain profile details and manage story-related content inside StoryWithMe.
Delete story content
Users can delete generated stories, characters, uploaded photos, and custom voice profiles from inside StoryWithMe.
Voice choices
Users can use default narrator voices instead of creating a custom voice profile. Users can also manage microphone permission in iOS Settings and delete custom voice profiles in StoryWithMe.
Subscription choices
Users can manage or cancel Apple subscriptions in their Apple Account subscription settings. StoryWithMe provides purchase restore support for eligible App Store purchases.
Delete account
Users can initiate account deletion from the StoryWithMe profile settings. For help related to that process, users can email support@storywithme.love.
Optional information
If a user does not want to provide optional profile, character, photo, voice, or story details, they may avoid entering that information. Some personalization, read-aloud, or custom voice features may be reduced because StoryWithMe depends on those details to generate personalized storybooks and narration.
Support and privacy contact
Users may contact support@storywithme.love to ask privacy-related questions, request support, or follow up about account-related actions.
Security and Policy Updates
Operational notes
Reasonable security measures
We seek to use reasonable technical and organizational measures to protect account and story-related information. No internet or storage system can be guaranteed to be perfectly secure.
Policy updates
We may update this policy as StoryWithMe or legal requirements change. Updated versions will be posted on this website with a revised effective date.
Contact
Privacy and support contact
For privacy-related questions, account follow-up, or support requests, please contact the StoryWithMe team.
Email support@storywithme.love
Operator: AILIFE TECHNOLOGY PTE. LTD.