Tuloma Privacy Policy
Last updated: 18 November 2026
Effective for: the Tuloma mobile application (the "App"), published by Elma Studio AB ("Elma Studio," "we," "us," or "our").
1. Summary for Parents
We know your time is limited, so here is the short version. The full policy below explains each point in more detail.
- No accounts, ever. Tuloma does not ask your child — or you — to create an account, sign up, or log in.
- We don't collect personal information from children. No names, no emails, no photos, no birthdates, no location about your child. The only place a country appears is at the level of a whole country, never more precise: the country a feedback report you send comes from (Section 4), and the store country of a purchase in Apple's, Google's and RevenueCat's sales reports.
- Your child's progress stays on the device. Lessons completed and words learned are stored locally on the tablet or phone. We never see them, and they are never uploaded anywhere.
- No ads. No third-party trackers. No analytics SDKs watching your child. Tuloma is a closed, calm learning environment — not an advertising platform. The only usage data we receive is our own anonymous count of a handful of app events (Section 4): no SDK, no advertising identifier, no profile of your child, nothing that identifies your family.
- Purchases go through Apple or Google. Depending on your device, subscriptions are handled entirely by the Apple App Store or by Google Play, together with our subscription-management provider, RevenueCat. We never see or store your payment card details.
- The only things that ever leave your device are the technical requests needed to download lesson content, the subscription checks handled by Apple, Google, and RevenueCat, the anonymous usage counts described under Section 4, and anything you deliberately choose to send us — such as a feedback note, with the technical details the form shows you, or an invite code (see Sections 4 and 7).
- You're in control. Because we hold almost no data, there's very little for you to manage — but where anything is processed (like a transaction ID for a subscription), you have full rights to ask about it, and you can reach us any time at the contact below.
This app is designed for children roughly ages four to six. It is submitted under Apple's Kids Category and distributed on Google Play under its Families policy, both of which carry additional restrictions on data collection and advertising that we've built the app to meet from the ground up — not bolted on afterward.
2. Who We Are
Tuloma is made by Elma Studio AB (org.nr 559600-5354), a Swedish limited liability company (aktiebolag).
- Legal entity status: Elma Studio AB, org.nr 559600-5354 (registered with Bolagsverket).
- Registered address: c/o Tim Schulz, Rönngatan 6, 211 47 Malmö, Sweden
- Contact: info@elmastudio.co (our company mailbox — the single contact address for the app and for everything on tuloma.app)
For the purposes of applicable data protection law (including the EU/UK GDPR), Elma Studio AB is the data controller for any personal data described in this policy.
3. Information We Do NOT Collect
Because this point matters more than almost anything else in this document, we're stating it plainly rather than burying it in legal language.
Tuloma does not:
- create user accounts or ask your child (or you) to register or log in;
- ask for or collect your child's name, nickname, date of birth, email address, or photo;
- collect precise location data, or any location beyond a country: the country a feedback report is sent from, and the store country in purchase reports (Section 4);
- record, store, or transmit audio, video, or images from your device's microphone or camera off the device;
- use advertising identifiers (such as Apple's IDFA or Google's advertising ID) or any cross-app tracking technology;
- show any advertising, in-app or otherwise;
- run third-party analytics, attribution, marketing, or crash-reporting SDKs inside the app (the app has no Sentry, PostHog, Expo telemetry, or similar integration; the only usage counts it sends are its own anonymous events, described in Section 4); and
- maintain any account system, user profile, or any database that links activity to a person or a child. The only records on our own server are feedback reports (which carry the technical details listed in Section 4, including the anonymous ID RevenueCat gives this install, and your email address only if you add one), invite codes, and anonymous usage events that carry no device identifier, only a random ID that lasts for one app session (Section 4).
This is possible because Tuloma has no accounts and no user database. Tuloma runs only minimal server infrastructure: a content delivery network for lesson packages, and one small server of our own that receives feedback notes and invite-code requests you choose to send, and counts the anonymous usage events described in Section 4. Lesson content (illustrations, audio, and word lists) is delivered to the app as static content packages from a content delivery network, and your child's learning progress is calculated and stored only on the device itself.
4. Information Processed Automatically
Even with no accounts and no user database, a small amount of technical data is necessarily processed by the infrastructure that delivers the app and its content, and by the services that manage subscriptions. We list every category and every party here — nothing is hidden behind a generic "trusted partners" description.
| What | Who processes it | Purpose | Retention |
|---|---|---|---|
| IP address (transient, never stored by Tuloma) | Cloudflare, as our content delivery / CDN provider and as the host of Tuloma's feedback and invite server | Deliver lesson content packages (illustrations, audio, word lists) efficiently and securely; protect the feedback and invite endpoints from abuse | IP addresses are processed transiently to route and deliver content and to rate-limit abuse. Our server converts the IP address into a salted hash for abuse protection and then discards it — no IP address is ever written to storage. Tuloma does not enable, receive, or store any CDN access logs itself. Cloudflare states it retains end-user activity logs for 7 days by default. |
| Anonymous app-user ID + purchase/receipt data (no name or email attached) | RevenueCat, our subscription-management provider | Verify subscription status, manage entitlements (e.g., which lessons are unlocked), and give us totals of subscriptions and revenue, by store country, in RevenueCat's reports | Per RevenueCat's own retention policy — see their privacy policy linked in Section 7 |
| Purchase transaction data | Apple (App Store / StoreKit) or Google (Google Play Billing), depending on your device | Process the payment, manage the subscription, provide receipts and refunds | Per Apple's or Google's own privacy policy — see Section 7 |
| A rating or review, only if a grown-up chooses to leave one from the parent settings | Apple or Google, in their own rating card, under the grown-up's store account | Show it on the store listing. The app only asks the store to show its card and learns nothing about whether or how it was used | Per Apple's or Google's own policies — see Section 7 |
| The age range of the store account on the device (for example "under 13" or "18 or over"), only where Apple or Google provide one. The store may ask a grown-up first, so the app asks at a parent moment: the first setup screen or the parent settings | Read on the device from Apple (Declared Age Range) or Google (Play Age Signals) | Meet the age-signal laws that apply to apps for children, such as Brazil's Digital ECA and Texas's App Store Accountability Act. The app changes nothing based on it | Never stored and never sent anywhere: it stays in the app's memory and is gone when the app closes. The app only remembers on the device whether the grown-up shared it, declined, or was asked by Google to verify an age |
| Crash / diagnostic data | Apple and Google (built-in OS-level crash reporting only) | No third-party crash-reporting or analytics SDK (e.g. Sentry, PostHog, Expo telemetry) is integrated into the app. The only crash/diagnostic data collected is whatever Apple (App Store Connect) and Google (Play Console) gather automatically at the operating-system level as part of iOS/Android — outside the app's control and governed by Apple's/Google's own privacy policies, not Tuloma's — plus the technical details a grown-up sees and chooses to send with a feedback report (the feedback row below) | Per Apple's and Google's own retention policies — see their respective privacy policies (Section 7) |
| Content you choose to send us via the in-app feedback form: a note, optionally the word it concerns, the language pair, app and content versions, and the country your request came from, which Cloudflare works out from the request (the IP address itself is never stored). With every report the app also sends technical details, which the form tells you about and lets you see in full before you send ("Show"): the device's system version and model (such as "iPhone15,2", never the name you gave the device), whether the full version is unlocked, the anonymous ID RevenueCat gives this install, and codes for up to ten recent technical failures (such as an audio clip that didn't load), never an error message | Tuloma's own server (hosted on Cloudflare's infrastructure) | Understand and fix problems in the app and its lessons, look up a purchase you write to us about, and see which languages families ask for | Stored in Tuloma's own storage and deleted automatically 12 months after it arrives. We can delete a report sooner on request — contact us (Section 12). Tell us roughly when you sent it; the RevenueCat ID shown under "Show" also lets us find it |
| An anonymous, random install identifier + your invite-code activity (codes issued, codes claimed, free lessons earned) | Tuloma's own server (hosted on Cloudflare's infrastructure) | Run the invite programme: issue your invite code, count the families who joined with it, and unlock the corresponding free lessons | Kept while the invite programme is active; we can delete it on request — contact us (Section 12) |
| Anonymous usage events — the app opened, a step of onboarding completed, the paywall shown, a plan tapped, a lesson started or a step of it reached, a lesson's final question passed or failed, and an audio clip that failed to play (which carries the lesson number and the language pair) | Tuloma's own server (hosted on Cloudflare's infrastructure) | Understand how the app is actually used — where families stop during setup, how many reach the paywall, and where a lesson gets stuck — so we can fix what is broken and improve what is not | Stored as one record per event per app session, and deleted automatically after about three months. Each record holds the event (for a lesson or a failed clip, also the lesson and language pair), the app version and platform, the time, and a random ID created when the app launches. That ID is never written to the device, is new every time the app starts, and is not linked to your purchases, your invite code, or anything else, so it cannot tell us who you are or connect one session to the next; it exists only so we count sessions rather than taps. An event carrying anything else is stripped before it is stored, and no IP address is ever stored (Section 3). |
| An email address | Tuloma's own server (hosted on Cloudflare's infrastructure) | Only if you volunteer it in the feedback form: to answer your note, or, on the "request a language" screen, to reach you if you offer to help build that language. It is optional, stored with that one report, and used for nothing else | Deleted automatically 90 days after we have dealt with your report, and in any case with the report after 12 months; sooner if you ask us to delete it (Section 12) |
Why we are allowed to process it (legal bases). Delivering lesson content and managing your subscription is processing necessary to perform our contract with you (GDPR Art. 6(1)(b)). Protecting the service from abuse — the rate limiter hashes an address rather than storing it — and counting the anonymous usage events above rest on our legitimate interests (Art. 6(1)(f)) in keeping the app working and making it better; those counts never identify a person and are never used for advertising or profiling. Where you deliberately send us something — a feedback note, an invite code, an email address you volunteer — we rely on your consent, and you can withdraw it at any time by asking us to delete it (Section 12).
None of the identifiers above are used to build a profile of your child, to target advertising, or to contact your child. They exist solely to make the app function, to run the invite programme, and to let Apple, Google, and RevenueCat process a subscription your family has chosen to buy.
5. Children's Privacy (COPPA / GDPR Article 8 / UK Children's Code)
Tuloma is designed for children roughly ages four to six and is submitted under Apple's Kids Category, which requires strict limits on data collection, no third-party advertising or analytics, and a "parental gate" in front of anything an adult should approve.
We built Tuloma's architecture — no accounts, no user database, on-device progress storage — specifically so that, in practice, we collect no personal information from children at all. This is our primary strategy for meeting the substance of the world's major children's privacy frameworks, including:
- the U.S. Children's Online Privacy Protection Act (COPPA), enforced by the FTC;
- the EU General Data Protection Regulation, Article 8 ("GDPR-K"), which governs children's data across the EU/EEA; and
- the UK GDPR and the ICO's Children's Code (Age Appropriate Design Code).
We are not claiming certification under any of these frameworks — this policy describes, honestly, what the app does and does not do, and we design toward the substance of each framework's requirements rather than treating any of them as a checkbox.
What this means concretely:
- Where a technical identifier (like the anonymous ID RevenueCat uses to track a subscription) is processed, it is used solely to support the internal operation of the app — verifying entitlement to paid content, and looking up a purchase when a parent sends us a feedback report — never to build a profile of your child, never for behavioral advertising, and never to re-identify or contact your child.
- Parental gate: any action that leaves the app's protected learning environment — starting a purchase, restoring a purchase, sending a feedback report or invite code, asking the store for its rating card, or opening an external link such as this privacy policy from within the app — sits behind a simple adult-level task (for example, a math question or a press-and-hold action) designed to be difficult for a young child to complete accidentally.
- No behavioral profiling, no marketing to children. Nothing in the app is designed to encourage a child to buy anything, share information, or leave the app.
- Inadvertent collection: if you believe we have somehow collected personal information from your child in a way inconsistent with this policy, please contact us immediately at the address in Section 12 so we can investigate and delete it as quickly as possible.
- Verifiable parental consent: because we do not collect personal information from children and rely only on data processing necessary to deliver the app and manage a subscription the parent purchases, we do not currently operate a verifiable-parental-consent flow. If that changes — for example, if we ever introduce a feature that does collect personal information from a child — we will update this policy and put the appropriate consent mechanism in place first.
6. Purchases & Subscriptions
Tuloma offers a limited free tier (currently three lessons — which can grow to more through our invite programme, see Section 7) plus paid subscription plans (currently 59 SEK/month or 449 SEK/year in Sweden; in other countries the store sets the price in the local currency — the store always shows you the exact price and currency before you confirm a purchase).
All purchases are handled exclusively through:
- Apple (the App Store and StoreKit) on iPhones and iPads, or Google (Google Play Billing) on Android devices — whichever store you downloaded the App from acts as the merchant of record for every transaction; and
- RevenueCat, a subscription-management service we use to verify entitlements and manage the subscription lifecycle across devices.
We — Tuloma — never see, receive, or store your payment card or bank details. RevenueCat receives an anonymous app-generated identifier along with purchase and receipt data; RevenueCat never receives your name, email, or any other information that identifies you or your child. That identifier also travels with a feedback report you send us (Section 4), so that we can look up your purchase if you write to us about it.
For purchase-related terms (billing, renewal, cancellation, and refunds), the terms and refund process of the store you purchased from apply — on Apple devices, see reportaproblem.apple.com; on Android devices, use your Google Play order history (play.google.com). Subscriptions renew automatically unless cancelled in advance through your device's store account settings (Settings → your name → Subscriptions on iOS; Play Store → Payments & subscriptions on Android).
- Apple's Privacy Policy: https://www.apple.com/legal/privacy/
- Google's Privacy Policy: https://policies.google.com/privacy
- RevenueCat's Privacy Policy: https://www.revenuecat.com/privacy/
7. Third Parties We Use
We keep this list short and exhaustive on purpose. Tuloma does not use advertising networks, marketing pixels, or general-purpose analytics SDKs; the only usage data that exists is our own anonymous event counts (Section 4). The only parties involved in running the app are:
| Party | Role | Data involved |
|---|---|---|
| Cloudflare (R2 / CDN) | Delivers lesson content (illustrations, audio, word lists) to the app | Transient IP address at time of content request |
| Tuloma's own server (hosted on Cloudflare's infrastructure) | Receives feedback reports and invite-code requests you choose to send, counts the anonymous usage events, and runs the invite programme | Only what you deliberately send it (including the technical details the feedback form shows you), plus the anonymous event counts and invite activity described in Section 4; no IP address is stored |
| Apple (App Store, StoreKit) | Processes payments; distributes the app; shows its own rating card when a grown-up asks for it | Purchase/transaction data; device and account data per Apple's own policies |
| Google (Google Play Billing) | Processes payments on Android; distributes the app on Android; shows its own rating card when a grown-up asks for it | Purchase/transaction data; device and account data per Google's own policies |
| RevenueCat | Manages subscription status and entitlements | Anonymous app-user ID; purchase/receipt data |
| Apple / Google (OS-level only) | Automatic, built-in crash/diagnostic reporting at the operating-system level | No third-party crash or analytics SDK is used; whatever Apple/Google collect natively is governed by their own privacy policies, not a Tuloma integration |
We do not sell personal information. We do not share information with data brokers or advertisers. We only disclose information to the parties above (to operate the app), or if required to comply with a legal obligation, protect our rights, or in connection with a merger, acquisition, or sale of assets — in which case this policy would continue to apply to any transferred information.
8. Data Storage & International Transfers
Tuloma is built to serve families outside mainland China (Apple's Chinese App Store filing requirements and our content-delivery infrastructure are not currently compatible with mainland China; Hong Kong, Taiwan, and Singapore are supported).
Because there is no user database, there is very little data to "store" in the traditional sense:
- Your child's learning progress lives only on their device and is never transmitted to us. So do three small settings the app keeps for the rating invitation — when the app was first opened, when the invitation was last shown, and whether it was tapped — so that it waits a few days and doesn't keep coming back.
- The anonymous usage events (Section 4) are stored in Cloudflare's analytics storage attached to our own server and deleted automatically after about three months. Each record carries only the session-only random ID described there; nothing in them ties a session to a person, a device, or a family.
- Lesson content is delivered from Cloudflare's global network, which may serve requests from data centers outside your own country. Cloudflare processes the minimal request data (like IP address) needed to deliver that content.
- Subscription data processed by RevenueCat, Apple, and Google may be processed in the United States and other countries where those companies operate, under the safeguards those companies maintain for international transfers (including the EU-U.S. Data Privacy Framework and/or Standard Contractual Clauses, as applicable). See their respective privacy policies (Section 6) for details.
9. Your Rights
Because Tuloma holds almost no personal data, most privacy requests are already satisfied simply by deleting the app from your device — at which point any locally stored progress is removed along with it.
Where any personal data is processed as described above (Sections 4, 6, and 7), and depending on where you live, you may have rights including the right to:
- ask what information is being processed and why;
- ask us to correct inaccurate information;
- ask us to delete information;
- object to or restrict certain processing;
- receive a copy of your information in a portable format; and
- withdraw consent, where processing is based on consent (for example the optional email address you may volunteer on the "request a language" screen, or any other note you deliberately send us — withdrawing it means we delete what you sent).
To exercise any of these rights, contact us at info@elmastudio.co (see Section 2). We will respond as promptly as we reasonably can and in any case within the timeframe required by applicable law.
If you are located in the EU/EEA and believe we have not addressed your concern adequately, you have the right to lodge a complaint with your local data protection authority, or with Sweden's supervisory authority (IMY):
Integritetsskyddsmyndigheten (IMY)
Complaints about how we handle your personal data can be submitted to IMY, the Swedish supervisory authority for data protection, via https://www.imy.se/privatperson/utfora-arenden/lamna-ett-klagomal/ (in Swedish; IMY also provides general guidance in English at https://www.imy.se).
If you are located in the United States and have concerns related to children's privacy specifically, you may also contact the U.S. Federal Trade Commission (FTC) at https://www.ftc.gov.
If you are located in the United Kingdom, you may contact the Information Commissioner's Office (ICO) at https://ico.org.uk.
10. Data Security
We take reasonable technical and organizational measures to protect the limited data described in this policy, including:
- encrypting data in transit (HTTPS/TLS) between the app and our content delivery and subscription infrastructure;
- relying on Apple's, Google's and RevenueCat's own security standards for payment and subscription data, rather than handling payment details ourselves; and
- minimizing what we collect in the first place, so there is simply less to protect.
No method of transmission or storage is 100% secure, and we cannot guarantee absolute security. If we become aware of a data security incident affecting personal information we process, we will take appropriate steps consistent with applicable law, including notifying affected users and/or authorities where required.
11. Changes to This Policy
We may update this policy from time to time — for example, as the app adds features, or as laws change. If we make material changes (particularly any change that would mean collecting more information from children than described here), we will update the "Last updated" date at the top of this page, and where appropriate, provide notice within the app before the change takes effect. We encourage you to review this policy periodically.
12. Contact Us
If you have questions, concerns, or requests relating to this policy or to privacy in the app generally, please contact us at:
Elma Studio AB
Email: info@elmastudio.co
Address: c/o Tim Schulz, Rönngatan 6, 211 47 Malmö, Sweden
Company registration number (org.nr): 559600-5354
This policy is intended to be read alongside Tuloma's Terms & Conditions. It applies to the Tuloma mobile application only. The tuloma.app website has its own Privacy Policy and Terms of Use.
