My Sweet Tales

Privacy Notice

Effective and last updated: October 27, 2026
Policy version: 2026-10-27

Leer esta política en español

Important voice and child privacy notice. My Sweet Tales is an adult-managed service for creating stories for children. Voice recordings and voice models are sensitive personal data and may be treated as biometric information under some laws. Only submit your own voice, or another person's voice when that person (or a legally authorized representative) has given informed permission. Do not submit a child's voice unless My Sweet Tales presents and you complete a verified parental-consent process for that collection.

My Sweet Tales is owned and operated by 4MINDS2TECH LLC ("4MINDS2TECH," "My Sweet Tales," "we," "our," or "us"). This Privacy Notice explains how we collect, use, disclose, retain, and protect personal information when you use the My Sweet Tales mobile application, website, and related services (collectively, the "Service"). It also describes choices and rights that may be available to you.

This Notice is part of our Terms of Service. It is not a contract that waives rights that cannot lawfully be waived. If this Notice conflicts with applicable law, applicable law controls.

Plain-language summary

1. Scope and who may use the Service

The Service is designed to be selected, configured, and managed by adults. It is not intended to allow children under 13 to create accounts or independently submit personal information. You must be at least 18 years old, or the age of legal majority where you live, to create and manage an account.

A child may listen to or read a story with an adult, but adult-facing areas—including account management, voice creation, purchases, external links, sharing, and deletion—should be used only by the adult account holder. If we learn that personal information was collected directly from a child without required authorization, we will take reasonable steps to delete it.

2. Information we collect

CategoryExamplesSource
Account and identityEmail address, display name, authentication identifiers, account status, language, and consent records.You; Google or Apple when you choose social sign-in.
Child-profile informationChild's first name or nickname, birth year or age range, language, gender if optionally provided, favorite toy, interests, and fears or topics to handle gently.The adult account holder. Please use a nickname and avoid unnecessary sensitive details.
Story and creative contentPrompts, titles, generated story text, saga relationships, covers, audio, selected language and narrator, content status, and whether a story is private or intentionally published/shared.You and our AI-assisted generation systems.
Voice DataMicrophone recordings, transcripts of required recording scripts, recording language and duration, voice name, mathematical or model-based voice representations, provider reference identifiers, and synthesized narration.You or a person you are authorized to represent; our voice-service providers.
Device and technical dataIP address, device and operating-system type, app version, device/app identifiers, push-notification token, timestamps, diagnostic logs, security events, and approximate region inferred from IP.Your device, app, servers, and service providers.
TransactionsProducts or credits purchased, price, currency, transaction identifier, payment status, and marketplace. We do not receive a complete payment-card number.Apple, Google, Stripe, or another checkout provider shown to you.
CommunicationsSupport requests, deletion or rights requests, feedback, reports, and related correspondence.You.

We do not intentionally collect precise geolocation, government identification numbers, contacts, health records, or payment-card numbers through the Service. A reference to a child's fear or preference is used only to personalize an age-appropriate story and is not intended for medical diagnosis or treatment.

3. How and why we use information

4. Legal bases for processing

Where a legal basis is required, we process information as necessary to perform our agreement with you; based on your consent for Voice Data, optional communications, device permissions, and other uses identified at collection; for our legitimate interests in providing a secure and reliable service when those interests are not overridden by your rights; and to comply with legal obligations. You may withdraw consent prospectively, but withdrawal does not make prior lawful processing unlawful and may make voice or other requested features unavailable.

5. Voice cloning, biometric notice, and authorization

5.1 What is collected and why

When you activate voice creation, we collect the recordings and related Voice Data described in Section 2 to create a reusable narration voice and synthesize stories you request. Depending on how a voice representation is created or used and the law that applies, it may be considered a voiceprint, biometric identifier, biometric information, or sensitive personal data.

5.2 Permission from the voice owner

The person whose voice is recorded must knowingly authorize the collection, creation, storage, disclosure to identified voice processors, synthesis of new narration, and retention described here. An account holder may not submit another person's voice merely because the recording is publicly available or because the person is a relative. The current in-app voice-creation flow accepts only the account holder's adult voice or another adult's voice that the account holder represents has been expressly authorized. Do not submit a minor's voice, a deceased person's voice, or the voice of a person unable to consent unless My Sweet Tales first provides a separate legally sufficient verification process for that situation. We may refuse or remove any voice when authorization is unclear.

Before accepting a new voice upload, we request an affirmative, voice-specific authorization and maintain a versioned audit record linked to that voice. The record may include the account/profile, voice identifier, selected owner category, notice version and exact notice or cryptographic digest, provider, language, method, acceptance time, and withdrawal time.

5.3 Prohibited uses

Voice Data may not be used to impersonate, deceive, defraud, harass, create endorsements, bypass authentication, create sexual or exploitative content, or violate publicity, privacy, intellectual-property, or other rights. My Sweet Tales is limited to personal storytelling; it is not an identity-authentication or general-purpose voice-cloning tool.

5.4 No sale; limited disclosure

We do not sell, lease, trade, or profit from Voice Data itself. We disclose Voice Data only to service providers needed to store recordings, create or maintain a voice reference, synthesize narration, secure the Service, comply with law, or complete a deletion request. Those providers are described in Section 7.

5.5 Retention and destruction

We retain Voice Data only while the voice remains active and needed to provide requested narration, unless a shorter period is required by law or the data must be preserved for a documented legal or security obligation. Where Illinois biometric law applies, we will permanently destroy covered biometric identifiers and information when the original purpose is satisfied or within three years after the voice owner's last interaction with My Sweet Tales, whichever occurs first. Deleting a voice initiates deletion of stored source samples and provider voice references; previously generated story audio remains only if the user chooses to retain it and applicable law permits.

6. Children's privacy and parental controls

My Sweet Tales is an adult-directed tool used by parents and other authorized adults to create content for children. We ask the adult account holder—not the child—to provide limited child-profile information. We do not knowingly permit a child under 13 to create an account, make a purchase, publish content, or submit a voice recording directly.

If a feature will collect personal information directly from a child in a situation covered by the Children's Online Privacy Protection Act (COPPA) or similar law, we will first provide the legally required notice and obtain verifiable parental consent. A general acceptance of this Privacy Notice is not treated as verified parental consent where a separate verification method is legally required. Parents or guardians may ask to review, correct, or delete a child's information and may refuse further collection by contacting us or deleting the applicable profile/account.

We do not use child-profile information for targeted advertising, build advertising profiles about children, or knowingly sell or share children's personal information for cross-context behavioral advertising.

7. When and with whom we disclose information

We disclose personal information only as described below, subject to provider configuration and the feature you use:

Recipient/categoryPurpose and data involved
code1to1Software engineering, operational support, cloud administration, security, and maintenance on behalf of 4MINDS2TECH LLC.
Amazon Web Services (AWS)Cloud hosting, object storage, queues, databases or related infrastructure, logs, and transactional email. May process account, story, audio, device, and operational information.
OpenAIAI-assisted story text and cover-image generation and safety processing. Receives the prompt and story context needed for the request, which may include child-profile details selected by the adult. Voice recordings are not intentionally sent to OpenAI for voice cloning.
Fish AudioVoice-reference creation and text-to-speech narration. May receive voice recordings or provider voice references, selected language, and story text necessary to produce audio. Under Fish Audio's standard Customer Agreement, unless an eligible Zero Data Retention configuration is enabled, Fish Audio may use customer materials as necessary to provide or improve its services and may derive aggregated data as described in that agreement. Persistent voice-reference features may require retention and may not qualify for Zero Data Retention. See Fish Audio's Customer Agreement.
Google/FirebaseGoogle sign-in when selected, app configuration, and push-notification delivery. May process authentication identifiers, device/app identifiers, and notification tokens.
AppleApple sign-in when selected, app distribution, and in-app purchases. Apple receives data under its own privacy terms.
Google PlayApp distribution and purchases on supported Android platforms. Google receives data under its own privacy terms.
StripeCheckout and payment processing where offered. We receive transaction status and identifiers, not complete card details.

Providers may change as the Service evolves. Before a materially different provider receives Voice Data or child-profile information, we will update this Notice and obtain additional permission when required. Providers process information under their applicable agreements, configurations, privacy notices, and law. My Sweet Tales seeks to minimize the information sent to each provider, but a provider's permitted use may include service improvement or aggregated data as expressly disclosed above. Do not create a voice unless the voice owner agrees to that third-party processing.

We may also disclose information: (a) when you intentionally publish or share a story; (b) to professional advisers bound by confidentiality; (c) to comply with valid legal process or protect rights and safety; or (d) as part of a merger, financing, reorganization, bankruptcy, or sale, subject to notice and applicable law. Public stories may be copied by others; do not include personal details in content you choose to publish.

8. No sale or targeted-advertising sharing

We do not sell personal information for money. We also do not share personal information for cross-context behavioral advertising or process sensitive personal information to infer characteristics about users. If these practices change, we will provide required notice and opt-out mechanisms before beginning them. We do not currently display third-party behavioral advertising in the Service.

9. Data retention

DataTypical retention rule
Account and child profilesWhile the account/profile remains active, then deleted or de-identified after a verified deletion request, subject to limited legal and security exceptions.
Stories, covers, and narrationUntil the user deletes the item or account, unless it was intentionally published and a lawful archival copy is required for moderation, disputes, or safety.
Voice DataAs stated in Section 5.5; never longer than applicable biometric-law limits.
Purchase and accounting recordsFor the period required by tax, accounting, payment-dispute, and consumer-protection law.
Security and operational logsTypically up to 24 months, or longer only when needed to investigate a documented incident or legal claim.
Consent, deletion, and rights-request recordsAs needed to demonstrate compliance, resolve disputes, and prevent unauthorized restoration of deleted data.

Deletion from active systems is followed by deletion or irreversible de-identification from provider systems as required by contract and law. Encrypted backup copies may remain until overwritten through the applicable backup cycle and are not restored for ordinary business use. We may retain the minimum information necessary to prevent fraud, enforce legal rights, comply with law, and document a completed request.

10. Security

We use administrative, technical, and physical safeguards designed for the nature of the information, including encryption in transit, access controls, restricted production access, authentication, logging, and deletion procedures. No storage or transmission method is completely secure, and we cannot guarantee absolute security. Users must protect their credentials and promptly notify us of suspected unauthorized access. We will provide legally required security-incident notices.

11. Your choices and privacy rights

Depending on where you live, you may have the right to:

Use the in-app controls where available or email contact@code1to1.com with the subject “My Sweet Tales Privacy Request.” We may verify your identity and authority before acting. An authorized agent may submit a request where permitted by law, but we may require proof of authorization and direct identity confirmation. To appeal a denied request, reply with “Privacy Appeal.” You may also complain to the privacy or data-protection authority where you live.

12. U.S. state disclosures

For residents of California and other U.S. states with comprehensive privacy laws, the categories collected, sources, purposes, recipients, and retention criteria for the preceding 12 months are described in Sections 2, 3, 7, and 9. We do not sell personal information or share it for cross-context behavioral advertising. Depending on applicable thresholds and law, residents may exercise the rights listed in Section 11.

Voice Data and child-profile information may qualify as sensitive personal information. We use them only for the disclosed Service purposes and do not use them to infer unrelated characteristics. We do not offer financial incentives in exchange for personal information.

13. EEA, United Kingdom, and Switzerland

4MINDS2TECH LLC is the controller of personal information described in this Notice. Data may be processed in the United States and other countries where our providers operate. Where required, we use an approved transfer mechanism or other legally recognized safeguard. You may have rights to access, correct, erase, restrict, port, or object to processing and to lodge a complaint with your supervisory authority. Where processing relies on consent, you may withdraw it prospectively.

14. Device permissions, cookies, and similar technology

The app requests microphone access only when needed for voice recording and notification permission when you choose notifications. You may change permissions in device settings, although a related feature may stop working. We and our providers use local storage, secure storage, tokens, logs, and similar technology for authentication, preferences, security, delivery, and performance. The Service does not respond to legacy browser “Do Not Track” signals; legally recognized opt-out preference signals will be honored where required and technically applicable.

15. AI-generated content and automated processing

My Sweet Tales uses automated systems to generate and screen creative content. These systems do not make decisions that produce legal or similarly significant effects about users. AI output may be inaccurate or unexpected; adults should review generated material before providing it to a child and should report inappropriate output. We may use automated safety tools and human review when necessary to investigate a report or protect users.

16. External services and links

App stores, identity providers, payment providers, and websites linked from the Service operate under their own privacy notices. Their independent collection is governed by those notices. This Notice covers the information My Sweet Tales receives and controls.

17. Changes to this Notice

We may update this Notice to reflect legal, technical, or business changes. We will post the new effective date and policy version. If a change materially expands how we use Voice Data, child-profile information, or other sensitive information, we will provide prominent notice and request new consent when required. Continued use alone will not be treated as consent where law requires a separate affirmative choice.

18. Contact us

Controller and Service owner: 4MINDS2TECH LLC, Lake Worth, Florida, United States
Technology and privacy contact: code1to1
Email: contact@code1to1.com
Website: mysweettales.com/4minds2tech/

For a COPPA, child-data, or voice-authorization concern, use the subject “Urgent Child/Voice Privacy Request.”