Skip to content
Masalize

Privacy Policy

Last updated: [EFFECTIVE DATE]

Draft

This text is under legal review and will be updated before launch. Highlighted parts are placeholders or details that are still being confirmed.

DRAFT — not to be published without legal review. Bracketed fields are placeholders. Sentences marked "[TO VERIFY: …]" must not be published until the app's or the provider's actual behaviour is confirmed. The Turkish version (gizlilik-politikasi-tr.md) is the reference text; this is its English counterpart.

Last updated: [EFFECTIVE DATE]

This policy explains what information is processed when you use the Masalize mobile app, why, who it is shared with, where and for how long it is kept, and how you can exercise your rights.

1. Who we are

Masalize is provided by Ramazan Savaş, trading as RS Medya, a sole proprietorship in Türkiye ("Masalize", "we"). Address: Maltepe Mah. Yılanlı Ayazma Sok. No:13/1A Kapı No:1, 34000 Zeytinburnu, İstanbul, Türkiye · Email: [email protected] (until this address is active: [email protected])

The controller of your personal data is Ramazan Savaş (RS Medya), as a natural person. [TO VERIFY: whether an EU representative under GDPR Art. 27 and a UK representative will be appointed.]

2. Who the app is for

Masalize is designed for parents and legal guardians. An adult opens the account, enters the child's details, makes purchases and manages settings. Children may watch or listen to the resulting stories and cartoons together with their parents, but we do not ask children for information and the app is not intended for children to create accounts, make purchases or change settings on their own. Purchases, settings and content creation sit behind a parental gate. [TO VERIFY: which screens the parental gate covers.]

When you enter information about your child, you confirm that you do so as the child's parent or legal guardian and on the child's behalf.

3. Account and sign-in

You do not need to give us your name, email address or phone number to use Masalize. When you first open the app, an anonymous account identified by a random ID is created for you. The session that unlocks this account is kept in your device's secure storage (Keychain on iOS, [TO VERIFY: Block Store / app storage] on Android), so your account can come back if you delete and reinstall the app. [TO VERIFY: if iCloud Keychain sync is enabled, add that the session will sync to your other devices signed in to the same Apple Account.]

If you wish, you can link your account to an email address. It is used only to send you sign-in codes and to restore your account on another device — not for marketing. [TO VERIFY: whether email linking remains after the move to cloud backup.]

3a. Where your content lives

  • On your phone: Generated stories and cartoons (audio and video files) are downloaded to your phone and stored there encrypted. They can be opened only inside the Masalize app; the app does not offer saving to the photo gallery or sharing.
  • In your own cloud account (backup): So that your content can come back if you lose or replace your phone, it is backed up in an app-specific area of your own cloud account:
    • on iOS, Masalize's private database in your iCloud account (Apple CloudKit private database);
    • on Android, Masalize's hidden app folder in your Google Drive (not visible in your Drive file list). This requires signing in with your Google account and granting Masalize access only to its own app folder ("appdata"); Masalize cannot see your other Drive files. This backup is hosted by Apple or Google and is subject to that cloud service's terms. Backed-up content is encrypted with an app-specific key; we cannot read the backup, and it is not stored on our servers. It uses your cloud storage quota. [TO VERIFY: (1) where the encryption key is kept and whether the backup can be opened if it is lost; (2) what the app receives from Google at sign-in (name, email, account ID) and whether any of it is sent to our servers; (3) whether backup is optional or on by default.]
  • On our servers: The server copy of audio and video files exists only for delivery. It is deleted 7 days after your phone has downloaded and backed it up, and in any case within 30 days. Metadata such as the title, the "Why?" question and short answer, conversation questions, the daily task and a small cover image stays on our servers while your account exists, so we can show your library.

4. What we process and why

InformationExamplesWhy
Account IDRandom user ID, account creation timeTo recognise your account and show you your content
Email (optional)The address you link for backupSign-in codes, account recovery
Child profileChild's first name or nickname, age range (0–2, 3–4, 5–6, 7–8), form of address (girl / boy / prefer not to say), interests, chosen character, content languageTo create personalised stories and cartoons
Family preferencesFaith framework ("None · General values" or Islam), music preference, app languageTo tailor content to the framework and language you choose and to show suitable ready-made content
Creation requestsType, topic, "What should they learn?" goal, text you write in your own words, tone, length, names of side characters (e.g. sibling, grandparent, pet), "Why?" questionTo create what you ask for and to check that free text is suitable for children
Generated contentAudio and video files (on our servers only for delivery, see section 3a); title and story metadata, "Let's talk" questions, daily task, small cover imageTo deliver it and show your library
Task check-insTasks you mark as done and the dateTo show task progress
Child photo (optional, beta)A single photo you pickOnly to create a cartoon character that looks like your child (see section 6)
SubscriptionPlan, start and renewal dates, store transaction IDTo recognise your plan and remove ads
Push tokenToken for sending notifications, platformTo tell you that content is ready (only if you allow notifications)
Free-story device recordOn iOS, a per-device flag in Apple DeviceCheck; on Android, an irreversible hash of the app-specific device ID and a Google Play Integrity verdictTo give the ad-rewarded free story only once per device and to prevent abuse (see section 8)
Technical recordsJob status, error codes, cost counters, IP address and timestamps seen by our serversTo run the service, fix errors, keep it secure and prevent abuse (e.g. rate limits)

What we don't do:

  • We do not sell your information.
  • We do not use your or your child's information for ad targeting or profiling, and we do not share it with ad companies.
  • We do not use third-party analytics or behavioural tracking tools in the app. [TO VERIFY: update if an analytics or crash-reporting SDK is added to the release build.]
  • We do not access the microphone or camera. Your photo library is accessed only when you pick a photo, and only for that photo.
  • We do not collect location.

A request about free-text fields: please do not write your child's surname, address, school, health information or other sensitive details in the free-text fields (topic, learning goal, "Why?" question, side character names). These texts are sent to our AI provider to write the story.

5. Faith preference

The faith framework is optional; the default is "None · General values". If you choose a faith, it is used only to prepare content within that framework and to show suitable ready-made content. Because information about religion or belief is treated as special-category (sensitive) data in many laws, we process this preference only with your explicit consent, and you can switch back to "None" in settings at any time.

6. Child photo and photo-based character

This feature is optional, in beta, and offered in [TO VERIFY: which plan]. No photo is processed unless you use it.

  • Before uploading, you separately confirm that you are the child's parent or guardian and consent to the photo being processed for this purpose.
  • The photo goes to a private area on our servers that the app can upload to but cannot read back.
  • The photo is used only to create a cartoon character resembling your child and that character's poses. During this step the photo is sent to our image-generation provider. [TO VERIFY: which providers receive the photo — fal.ai and, if used for visual checks, Anthropic — and their retention.]
  • The photo is deleted from our servers as soon as the job starts (whether it succeeds or fails). Photos not attached to a job are deleted automatically within 30 minutes.
  • We do not extract face recognition data, face templates or other biometric identifiers from the photo, and we do not use it for identification. [TO VERIFY: confirm with the generation pipeline.]
  • The resulting cartoon character images and poses (not the photo itself) are kept in your account so the same character can be reused. They are deleted when you delete the character or use "Delete my data". [TO VERIFY: "Delete my data" does not yet remove the pose archive; must be fixed before the feature is enabled.]

7. AI-generated content

Personalised stories, cartoons, covers and conversation questions are generated automatically by AI; they are not written or drawn by a person. The part of your input needed to create the content (e.g. the child's name, age range, interest, goal, side character names) is sent to these providers:

  • Story writing and suitability checks: Anthropic (Claude models)
  • Narration: ElevenLabs (the narrated text may include the child's name)
  • Scene, pose and cover images: fal.ai (image descriptions; the photo for a photo-based character)

We work with these providers under service terms that limit their processing to providing the service on our behalf. [TO VERIFY: that each provider does not train models on API data, their retention periods; sign and file current DPAs.] We do not use your information to train AI models.

Every item passes an automated suitability check before delivery, but automated checks are not perfect. See the Terms of Use, "AI-generated content".

8. Advertising

The free version shows ads; paid plans have no ads.

  • Our ad provider is Google AdMob. Ads appear as a small banner in a separate area on the home screen, library and player, a short interstitial before ready-made content, and an optional rewarded ad for the free trial story. No ads appear on the creation screens, the parental gate or the plans screen.
  • Every ad request is tagged to Google as child-directed and as under the age of consent, requests non-personalised ads only, and limits ad content to the most suitable rating (G).
  • The app does not ask for tracking permission (App Tracking Transparency); we do not collect the advertising ID or use it for targeting.
  • To serve ads, Google's ad software receives certain technical information from your device (e.g. IP address, device model, OS, app information, ad interactions). For child-directed requests Google uses it for limited purposes under its own policies (serving and measuring ads, preventing fraud). [TO VERIFY: add Google's current links.]
  • When you earn the free story through a rewarded ad, Google tells us the ad was watched using your account ID and a single-use ticket number; the story credit is granted only after this server-side confirmation.
  • The free story is given once per device. On iOS a per-device flag is stored in Apple's DeviceCheck service (Apple does not give us an identifier for your device); on Android the app-specific device ID is turned into an irreversible hash with a secret server key, and Google Play Integrity verifies the device is genuine. This record is not linked to your account, is not combined with other information and is not removed by "Delete my data"; its only purpose is to stop the free credit being granted again on the same device.

9. Payments

Subscriptions are bought through the Apple App Store or Google Play. Your payment details are handled by the store; we never see them. Our subscription infrastructure provider RevenueCat links the purchase information from the store (product, transaction ID, dates, renewal status, country/currency) to your account ID.

10. Notifications

If you allow notifications, we notify you when content is ready or a creation fails. Your device's push token is kept on our servers, and notifications are delivered via Expo's push service and Apple (APNs) / Google (Firebase Cloud Messaging). [TO VERIFY: whether notification text includes the child's name.] You can turn notifications off in your device settings at any time.

11. Who we share information with

We share information only with the service providers that help us run the service, and only as much as needed:

ProviderPurposeLocation
SupabaseDatabase, accounts, file storage, server functionsEuropean Union (Ireland). [TO VERIFY: support/maintenance access from the US]
Google Cloud (Cloud Run)Content generation servers and system logsEuropean Union (Netherlands)
AnthropicStory writing, free-text suitability checks, visual quality checksUnited States
ElevenLabsNarration[TO VERIFY: US / EU data residency]
fal.aiImage generation (scenes, poses, covers; photo-based character)United States [TO VERIFY]
Google (AdMob)Ads in the free versionUnited States and Google's global infrastructure
Apple (DeviceCheck), Google (Play Integrity)Once-per-device free storyUnited States and provider's global infrastructure
RevenueCatSubscription validation and managementUnited States
Expo, Apple, GoogleNotification deliveryUnited States
[EMAIL PROVIDER]Sign-in code emails for account linking[TO VERIFY]

Apple (iCloud) and Google (Google Drive), which hold your content backup, are not in this table: the backup is in your own cloud account, governed by your agreement with Apple or Google, and encrypted so that we cannot read it.

Beyond this, we may disclose information only where required by law (e.g. a lawful request by authorities), to protect our rights, or in a merger or transfer of the business, provided the protections in this policy continue to apply.

12. International transfers

Our main database and generation servers are in the European Union. Some providers listed above (in particular AI, advertising, subscription and notification providers) process data in the United States or other countries. We make these transfers with the safeguards required by applicable law (for example, the European Commission's Standard Contractual Clauses or adequacy decisions, and for users in Türkiye the standard contracts published by the Turkish Personal Data Protection Authority). [TO VERIFY: the transfer mechanism for each provider.]

13. How long we keep information

InformationRetention
Audio and video files on our servers7 days after your phone has downloaded and backed them up; in any case deleted within 30 days
Encrypted content on your phoneUntil you delete the app or the item (on your device)
Cloud backup (iCloud / Google Drive)Until you delete it (in your own cloud account; see section 14)
Account, child profiles, preferences, content metadata (title, questions, task, small cover), task check-insWhile your account exists; deleted immediately with "Delete my data". [TO VERIFY: set an inactivity period for anonymous accounts, e.g. 24 months]
A single item or child profileUntil you delete it (deleting a profile deletes that child's content)
Child photoDeleted as soon as the job starts; if not attached to a job, within 30 minutes
Technical records of failed or flawed generations (input, story text, check reports, small output copy)Up to 14 days for troubleshooting, then deleted automatically; "Delete my data" deletes them immediately
Server system logs (no child names or story text)30 days
Subscription recordsUntil the account is deleted; records subject to legal retention duties for the period the law requires [TO VERIFY]
Free-story device recordIndefinitely (not linked to an account)
Backups[TO VERIFY: Supabase backup retention]; deleted data leaves backups at the end of that period

14. Deleting your data

In the app, go to Parent → Privacy & data → Delete my data to permanently delete your account and all child profiles, generated content, jobs, credits, subscription records, push tokens, all your files on our servers and related technical records. This cannot be undone.

  • Encrypted content on your phone is removed when you delete the app. Your cloud backup is in your own account [TO VERIFY: whether "Delete my data" also deletes the backup]; you can delete it yourself: on iOS, Settings → [your name] → iCloud → Manage Storage → Masalize; on Android, Google Drive → Settings → Manage apps → Masalize → Delete hidden app data.
  • Deleting your data does not cancel your store subscription. Cancel it separately in App Store or Google Play settings.
  • The free-story device record is not deleted (section 8).
  • If you cannot use the app, email [email protected]. Web deletion request page (required by Google Play): https://masalize.com/hesap-silme.

You can also delete a single item or a single child profile in the app.

15. Security

Information is encrypted in transit. Each family can access only its own records, enforced on the server. Files are kept in private storage on our servers, delivered through short-lived (6-hour) signed links and deleted after delivery; on your phone and in your cloud backup they are stored encrypted. The app cannot read back the photo upload area. Access keys exist only on our servers. No system is completely risk-free; if a breach occurs we will make the notifications required by law.

16. Your rights

Depending on where you live, you may have the right to access, correct, delete, restrict or object to processing of your data, to data portability, and to withdraw consent at any time. Users in the EEA and the UK may also complain to their local data protection authority.

Additional information by region: EEA and UK in section 16a, United States in sections 16b–16c, other countries in section 16d.

Send requests to [email protected] or in writing to Maltepe Mah. Yılanlı Ayazma Sok. No:13/1A Kapı No:1, 34000 Zeytinburnu, İstanbul, Türkiye. Because accounts are anonymous, we may ask you to include the Account code shown in the app so we can find your account. [TO VERIFY: the app should show a copyable account code.] We reply within 30 days at the latest.

16a. Users in the European Economic Area and the United Kingdom

Legal bases (GDPR / UK GDPR Art. 6 and 9):

ProcessingLegal basis
Account, child profile, creation requests, generated content, delivery, backup, notifications, subscriptionPerformance of our contract with you (Art. 6(1)(b))
Automated suitability checks, security, abuse and fraud prevention, troubleshooting records, once-per-device free storyOur legitimate interests in keeping children safe and the service secure (Art. 6(1)(f))
Faith preference (special-category data)Your explicit consent (Art. 9(2)(a))
Child photo for a photo-based characterYour consent as parent (Art. 6(1)(a))
Ads in the free version (AdMob, non-personalised, child-directed)[TO VERIFY: legitimate interests or consent; ePrivacy / PECR rules on device access may require consent for ad SDKs — lawyer]
Records we must keep by lawLegal obligation (Art. 6(1)(c))

Children. The app is used by parents, who act for their child. We do not rely on a child's own consent (Art. 8). In line with the UK Children's Code and the GDPR's focus on the best interests of the child, we keep privacy-protective settings by default: no profiling, no personalised ads, no location, no sharing of content with other users, and the photo feature is off unless you choose it.

Automated decisions. Free text is checked automatically for suitability and may be rejected; this has no legal or similarly significant effect on you. You can contact us if you think a request was wrongly rejected.

Transfers outside the EEA/UK are made under the European Commission's Standard Contractual Clauses (and the UK Addendum / IDTA), or to US providers certified under the EU-US Data Privacy Framework and its UK extension. [TO VERIFY: per provider.]

Your rights: access, rectification, erasure, restriction, objection (including to processing based on legitimate interests), data portability, and withdrawal of consent at any time without affecting earlier processing. You can complain to the data protection authority where you live or work — in the UK, the Information Commissioner's Office (ico.org.uk).

Representatives. EU representative (Art. 27 GDPR): [TO VERIFY: name and address]. UK representative (Art. 27 UK GDPR): [TO VERIFY: name and address].

16b. United States — notice to parents (COPPA)

This section is our direct notice to parents under the Children's Online Privacy Protection Act (COPPA).

  • Operator: Ramazan Savaş (RS Medya), Maltepe Mah. Yılanlı Ayazma Sok. No:13/1A Kapı No:1, 34000 Zeytinburnu, İstanbul, Türkiye · [email protected].
  • What we collect and how. Masalize is designed so that the parent, not the child, enters information. You may give us your child's first name or nickname, age range, form of address, interests, learning goals, free text you write, names of side characters, an optional faith preference and, only with your separate consent, a photo of your child. We do not ask children to enter information and do not enable children to make their information publicly available.
  • Information collected automatically. When content plays in the free version, Google's ad SDK collects persistent identifiers and technical information to serve contextual, non-personalised ads, cap how often an ad is shown and prevent fraud. These identifiers are used only to support the internal operations of the app; ad requests are tagged as child-directed so that Google does not use them for behavioural advertising or profiling. Our servers also use an account ID and, on Android, a hashed device ID for security and to give the free story once per device.
  • How we use it. Only to create and deliver your personalised content, keep the service secure and provide support. We do not use children's information for targeted advertising and do not sell it.
  • Disclosure. We disclose information only to service providers that help us run the app (listed in section 11), under contracts limiting their use to providing the service. We do not disclose children's information to third parties for their own purposes.
  • Consent. By creating a child profile you, as the parent, provide consent for the processing described here. For the photo-based character we obtain your separate consent before the photo is uploaded. [TO VERIFY: COPPA requires verifiable parental consent using an FTC-recognised method (for example, a payment transaction with notice, or a knowledge-based or ID check). A tick box alone is not enough. Options: (a) offer child-profile and photo features in the US only after a verified method such as an in-app subscription purchase with notice; (b) rely on a method approved by counsel. Lawyer decision before US launch.]
  • Retention. We keep children's information only as long as needed (see section 13) under a written data retention policy; server copies of media are deleted within 30 days, troubleshooting records within 14 days, and inactive accounts after [TO VERIFY: 24 months].
  • Your rights as a parent. You can review the information we hold about your child, ask us to delete it, and refuse further collection or use at any time — in the app (Parent → Privacy & data) or by emailing [email protected]. If you refuse, features that need that information will no longer be available.
  • Security. We maintain a written information security program (see section 15). [TO VERIFY: write and keep the program document.]

16c. United States — state privacy laws

  • We do not sell or share personal information (including for cross-context behavioural advertising) and we do not use children's information for targeted advertising or profiling. Ads in the free version are contextual and non-personalised.
  • Residents of states with consumer privacy laws (for example California, Connecticut, Colorado, Virginia) can ask us to access, correct or delete their information as described in section 16, whether or not those laws apply to a business of our size. We will not discriminate against you for exercising these rights.
  • App store age signals. Where a state law requires it (for example Texas, Utah, Louisiana, Alabama, and California from 1 January 2027), we use the age range and parental-consent status that the App Store or Google Play provides only to apply age-appropriate settings and to comply with the law, and we do not keep it longer than needed. [TO VERIFY: implementation of Apple's Declared Age Range API and Google Play's age signals.]

16d. Other countries

  • Brazil (LGPD and Law 15.211/2025 "ECA Digital"): we process children's data only in the child's best interest and with the specific consent of a parent; we do not profile children for advertising. [TO VERIFY: age assurance, guardian-linked accounts and a legal representative in Brazil are required before release there.]
  • Canada (PIPEDA; Quebec Law 25): a parent gives consent for children under 13 (under 14 in Quebec). You may complain to the Office of the Privacy Commissioner of Canada or, in Quebec, the Commission d'accès à l'information.
  • Australia (Privacy Act 1988): you may complain to the Office of the Australian Information Commissioner. We will update this policy when the Children's Online Privacy Code takes effect.
  • Elsewhere: we apply the protections in this policy to all users. If your local law gives you additional rights, contact [email protected].

17. Changes

We may update this policy as the app or the law changes. We will announce material changes in the app and ask for your consent again where required. The current version is always at https://masalize.com/privacy.

18. Contact

Ramazan Savaş (RS Medya) · Maltepe Mah. Yılanlı Ayazma Sok. No:13/1A Kapı No:1, 34000 Zeytinburnu, İstanbul, Türkiye · [email protected]