Legal

Privacy Policy

Effective date: April 29, 2026

This Privacy Policy explains how Tales collects, uses, stores, and shares information when you use the Tales website, iPhone app, and related backend services. Tales is operated by Available Pretext Lda.

Tales is built for parents and guardians creating personalized bedtime stories for children. Some features run locally on your device, while other features use cloud services to authenticate accounts, validate purchases, and generate story content.

1. Information We Collect

Account and sign-in information

When you sign in, we receive account-related information from the sign-in provider you choose, currently Apple or Google. Depending on the provider and what is made available, this may include a provider account identifier, email address, email verification status, and provider name. We also create internal account, session, and device records such as a backend user ID, refresh-token records, device ID, session timestamps, user agent, and IP address.

Subscription and billing information

If you purchase or restore a subscription or other in-app purchase, we process subscription tier, product ID, transaction ID, original transaction ID, purchase or expiry timing, receipt-validation metadata, and limited fraud-prevention and entitlement records. Purchases are billed by Apple, not by the Tales website.

Story and personalization information

To create personalized stories, Tales may store or process information you enter in the app, such as child names and ages, companion or character names, character types, preferences, story themes, values, selected language, illustration style, story prompts, generated story text, generated page images, and related task status records.

If you upload participant photos, those images may be processed to prepare story generation inputs and visual references. Uploaded character and participant images are treated as app content, not as identity-verification documents.

Device, sync, and local storage information

Tales stores data on your device using local app storage, the device keychain, and optional Apple iCloud technologies. Depending on the features you use, this can include locally saved stories, story pages, characters, children, user profile data, auth tokens, cached app configuration, onboarding flags, and CloudKit-synced records stored in your private iCloud database.

Operational and security information

We may collect technical and operational data needed to run and protect the service, such as request metadata, error logs, authentication events, usage counters, generation-task records, admin audit logs, and security or abuse prevention signals.

Website information

The public Tales website is a static marketing site. The current contact form validates input locally in your browser only and, in its current implementation, does not send or store your message with us. If you visit the website, your browser may still make routine requests to infrastructure or asset providers needed to load the site, such as hosting, fonts, or image resources.

2. How We Use Information

We use information described above to:

• create, maintain, secure, and delete user accounts;
• authenticate users and manage sessions across devices;
• provide local and cloud-based story creation features;
• process participant images and generate stories and illustrations;
• sync app content through iCloud and CloudKit when enabled;
• validate subscriptions, restore purchases, and manage entitlements;
• prevent fraud, abuse, and unauthorized access;
• debug, monitor, and improve service reliability and performance;
• comply with legal obligations and enforce our terms.

3. Local Processing and Cloud Processing

Some Tales features can run locally on compatible Apple devices using Apple system frameworks for text and image generation. When you use those local-generation paths, the story-generation request may remain on device instead of being sent to Tales cloud generation services.

Other features use the Tales backend, including account authentication, subscription validation, upload handling, resumable generation tasks, and cloud story generation. When those features are used, relevant input data is sent to our backend and, where needed, to service providers supporting that workflow.

4. How We Share Information

We may share or disclose information in the following circumstances:

• with Apple and Google for sign-in, App Store billing, iCloud, and CloudKit functionality;
• with AI and media-processing providers used by the service, including OpenAI and Fal.ai, when needed to generate or transform cloud-based story content;
• with hosting, infrastructure, storage, logging, and security providers acting on our behalf;
• if required by law, legal process, or to protect rights, safety, and the integrity of the service;
• in connection with a merger, acquisition, restructuring, financing, or sale of assets, subject to applicable confidentiality and legal protections.

We do not state in this policy that we sell personal information for money. If our practices materially change, we will update this policy.

5. Retention

We retain different categories of information for different periods depending on how the service works:

• account, session, subscription, security, and compliance records may be retained while your account is active and for a reasonable period afterward when needed for fraud prevention, accounting, dispute handling, or legal compliance;
• uploaded participant images on the backend are designed to be short-lived and are typically cleaned up after roughly 15 minutes;
• backend-generated story records and related hosted media are designed to be temporary and are typically retained for about 15 to 30 minutes on the backend, depending on the current retention configuration;
• resumable generation-task metadata is designed to be retained for a limited period, currently about 24 hours;
• local device storage and CloudKit private-database records remain until you delete them, remove the app, disable sync, or delete your account.

6. Your Choices and Controls

• You can review and update many profile, child, character, story, and subscription settings directly in the app.
• You can sign out of the current device or all devices from the app settings.
• You can delete saved content inside the app.
• You can initiate account deletion in the app settings. Based on the current app flow, this is intended to delete the backend account immediately, remove app-owned CloudKit records, clear local app data, and return the app to a signed-out state.
• App Store subscriptions are managed separately through Apple and are not canceled automatically when you delete your Tales account.

7. Children's Privacy

Tales is intended to be used by parents or guardians, not by children acting on their own to create an account or purchase services. If you provide a child's name, age, photo, or other child-related content, you represent that you are authorized to do so and that the information is being provided for a family storytelling purpose.

We expect adults to supervise use of the service and to manage child-related content and account settings, including deletion requests.

8. International Processing

Depending on the providers and infrastructure used, information may be processed in countries other than your own. Where required, we rely on contractual, technical, and organizational measures designed to protect personal information.

9. Changes to This Policy

We may update this Privacy Policy from time to time to reflect changes to the app, backend services, legal obligations, or operational practices. When we do, we will update the effective date above.

10. Contact

If you have questions about this Privacy Policy or wish to make a privacy-related request, contact Available Pretext Lda through the support contact details published for Tales in the app or on the official Tales website.