Privacy Policy
Last updated: 7 October 2026
The short version. Lolo Cards has no sign-up and no server of its own. We never ask for your name, email address, or phone number, and we cannot tell who you are. The voice answers you record stay on your iPhone. They are never uploaded, never transcribed, and we never receive a copy.
What does leave the phone, from version 1.1 on: the purchase status that Apple and RevenueCat need to unlock the app, and usage statistics sent to Google Analytics for Firebase - when the app was installed and opened, which screens were shown, whether a trial or subscription started, and an approximate country. We use them to see whether the app works for people and whether our ads on Google and Apple are worth paying for. None of it is tied to your name, none of it includes your recordings or what you said, and the app never shows the App Tracking Transparency prompt because it does not track you across other companies' apps and websites. Section 7 lists every company and exactly what it receives.
1. Who we are
Lolo Cards is an iOS app published under the trading name WHITE APPS.
For anything related to this policy or to your data, write to support@white-apps.online. The person who wrote the app answers that address.
2. The app has no account and no server
There is nothing to sign up for. The app does not create a profile, does not ask for an email, and has no way to log you in. Everything it knows - which cards you have seen, what you marked as a favourite, your progress, and your recordings - lives in the app's own storage on your iPhone.
We do not run a server for Lolo Cards. There is no database of users, no cloud sync, and no back end of ours that your phone talks to. The card bank ships inside the app, and the smart session is assembled on the device.
The Home Screen widget (version 1.1 and later) shows a question of the day from that same card bank. To keep it in step with the app, Lolo Cards saves the next few days' questions to a small storage area on your iPhone that only the app and its widget can read. The widget makes no network connection and sends nothing anywhere. Deleting the app removes that data along with everything else.
3. Your voice answers
This is the part of the app that handles something genuinely personal, so it gets a section of its own.
Where they are
When you tap the microphone on a question card, the app records audio and saves it as an ordinary sound file inside its own container on your iPhone, named after the card it answers. That file is the only copy that exists.
The app deliberately does not switch on iOS file sharing, so that folder does not show up in the Files app and no other app can read it. The recordings are reachable from inside Lolo Cards, and from nowhere else on the phone.
Who can reach them
Only you, on that phone. The recording is not uploaded anywhere. It is not sent to us, to a transcription service, to a speech-recognition model, or to any other company. The app performs no transcription at all - it never turns your voice into text, because it has no reason to. We have never received a recording, we have nowhere to put one, and we could not listen to one if we wanted to.
iCloud backup
If iCloud Backup is switched on for your iPhone, the app's files - including your recordings - are part of that backup, the same as the rest of your phone. That is Apple's backup, held under your Apple ID, not our server; we have no access to it. It exists so that your answers survive a lost or replaced phone.
If you would rather they were not backed up, switch off Include recordings in backup in the app's Settings. It applies to the recordings you have already made as well as to new ones. You can also manage backups for each app in iOS Settings → your name → iCloud.
Deleting them
- One answer - tap the microphone on a card that already has a recording, and the app offers to record a new one over it. The old file is replaced at the moment the new recording finishes, and not before: that way a recording that goes wrong never leaves you with nothing. Recording over an answer is currently the only way to remove a single one.
- All of them - delete the app from your iPhone. The recordings go with it, permanently. There is no copy on our side to restore, and no copy anywhere else - unless you took one yourself by exporting it, or unless it is inside an iCloud backup you made.
Exporting - the one way out, and you start it
In My answers you can export a single recording or all of them at once. Export hands the file to the standard iOS share sheet, and you choose what happens next: save it to Files, send it in Messages or Mail, AirDrop it, put it wherever you like.
The question travels with the recording, so the file still makes sense a year later. A
single export is a copy of the sound file named after the question, with the question text
alongside it. Exporting everything produces a zip of those files plus a plain
Answers.txt listing, for each one, the question, the category and deck it came
from, the date you recorded it, how long it is, and the file name. Nothing else
goes into an export - no identifiers, no progress, no favourites, and nothing
about your device.
We are not part of that. The share sheet belongs to iOS, not to us. We receive no file, no copy, and no notification that an export happened. Once you send a recording to another app, service, or person, it is in their hands and their privacy policy applies - we have no control over it and no way to take it back.
4. The microphone
The app asks for microphone access for exactly one purpose: to record the voice answer you chose to record. It records only while you are recording, and it does not listen at any other time.
Before iOS shows its own permission dialog, the app explains in its own words what the microphone is for. Nothing is requested until you tap through that explanation - the system prompt can only be answered once, and asking for a permission before saying why is a bad way to treat someone.
If you refuse the permission, or turn it off later in iOS Settings → Lolo Cards, everything else in the app keeps working - all 4,700 cards, the smart session, favourites and progress. You simply cannot record an answer until you allow it.
5. Sharing a question
The share button on a card opens the same iOS share sheet and passes it the text of the question. Nothing else goes with it, and we do not see where you sent it or whether you sent it at all.
6. Photos and other things we do not touch
The app never asks for access to your photo library, your camera, your contacts, your calendar, your location, or your health data, and it cannot read any of them. In the "Show me" mini-game a card may ask you to show something from your own phone - you open your gallery yourself, and the app neither sees nor receives whatever you show.
7. Who receives what
This is every company that receives anything from the app, what it receives, and why. Some rows apply only to one version of the app; you can see yours in iOS Settings → General → iPhone Storage → Lolo Cards.
| Who | What they receive | Why |
|---|---|---|
| Apple (App Store, StoreKit) |
Your Apple ID, your payment method, your billing country, and the purchase itself. Apple tells the app only whether a purchase is currently valid and when it renews. | Apple sells and charges for everything bought inside an iOS app. There is no other way to pay. |
| RevenueCat (version 1.1 and later) |
A random identifier its SDK creates for this installation, your purchase and subscription status as Apple reports it, technical facts about the device (model, iOS version, app version, language, store country), which purchase screen was shown and whether it was closed or a purchase started. If you installed the app from an ad in the App Store, it also receives the attribution token described in the Apple Ads row below, and the random Firebase identifier described in the Google row. | RevenueCat checks your subscription, draws the purchase screen, and lets us change prices and layout without shipping a new version. |
| Google (Google Analytics for Firebase, version 1.1 and later) |
A random identifier created for this installation (the app instance ID), the identifier for vendor (IDFV, the same for all our apps on this iPhone), if you installed after tapping an ad in the App Store, the attribution data Apple provides for that ad, when the app was first opened, sessions and how long they lasted, which screens were shown, purchases and trials (product, price, currency), device model, iOS version, app version, language, and an approximate location (country and region) derived from a masked network address. Not your name, your Apple ID, your recordings, the questions you open or anything you say. | To count installs and see how the app is used, and to measure whether our own Google ads lead to installs and subscriptions. Google may compare these events on your device with its own ad data to report conversions to us in aggregate ("on-device conversion measurement"); the raw data stays on the device. |
| Apple Ads (via RevenueCat, version 1.1 and later) |
If you installed the app after tapping an ad in the App Store, Apple's AdServices framework gives the app a one-time token. RevenueCat exchanges it with Apple for the campaign, ad group and keyword that led to the install. Apple does not include who you are. | To know which of our App Store ads bring people who actually keep the app. |
| Superwall (version 1.0 only) |
A random identifier its SDK creates for this installation, technical facts about the device (model, iOS version, app version, language, and an approximate country derived from the network address), which paywall was shown, what you tapped on it, and whether a purchase or trial started. | In version 1.0 Superwall drew the purchase screen. Version 1.1 no longer contains it. |
| Google (Google Fonts, version 1.0 only) |
Your device's network address, and the technical description that travels with any web request - device type, operating system, browser engine - at the moment the purchase screen is drawn. Nothing about you, your answers, or what you do in the app. | The version 1.0 purchase screen is a web layout whose typeface is delivered from Google's font servers. |
| We do | Nothing that identifies you. We see aggregate reports from Apple, RevenueCat and Google - how many people installed, opened the app, saw a purchase screen, started a trial or subscribed, and from which ad campaign - and Apple's payout figures. | To know whether the app makes enough to keep existing, and where to spend on ads. |
We never see your card number, your name, your email address, or your billing address. Apple does not give them to us, and we do not ask.
None of these companies receives your recordings, the text of the cards you open, your favourites, or anything you type or say. Their own policies: Apple, RevenueCat, Google (and how Google uses data from apps that use its services), Superwall.
8. What the app does not have
Written as a list because the absences are the point:
- No tracking. The app never shows the App Tracking Transparency prompt, so the Advertising Identifier (IDFA) is not available to it or to any SDK inside it. Nothing about you is combined with data from other companies' apps or websites to target ads at you, sold, or shared with data brokers - including as those terms are defined by the California Consumer Privacy Act.
- No ads inside the app. No ad networks showing ads, no sponsored cards. We advertise the app elsewhere, and section 7 describes how we measure those ads.
- No analytics on what you say or answer. Usage statistics record that a screen was shown, not which question was on it, and never anything you recorded.
- No crash reporter of ours. If you have chosen to share analytics and crash reports with Apple in iOS settings, that is a collection by Apple under Apple's policy, not by us.
- No account, no login, no cloud sync.
- No chat, no comments, no uploads, no way to publish anything. Nothing you do inside Lolo Cards is visible to another person, and there is no user-to-user content of any kind.
9. Legal basis and where the data goes (EU and UK)
- Performance of a contract. Checking whether your purchase is valid and showing the purchase screen. Without it the app cannot know what to unlock.
- Legitimate interests. Counting installs, sessions and purchases, and measuring which of our ads work, so we can tell whether the app can keep existing and where to spend. We use the least identifying data that answers those questions: random installation identifiers, no profile, nothing tied to you as a person, and no Advertising Identifier.
Apple, RevenueCat, Google and Superwall all run on infrastructure that includes servers in the United States. Where data is transferred out of the European Economic Area or the United Kingdom, those transfers rely on the standard contractual clauses adopted by the European Commission and used by those providers.
10. Children
Lolo Cards is rated 13+. It is not directed at young children, and we do not knowingly collect personal data from anyone of any age - the app has no account, and the anonymous statistics in section 7 identify an installation, not a person.
If you are a parent and want the app's recordings gone from a child's phone, deleting the app removes them entirely.
11. Your rights
If you are in the EU, the UK, or California, the law gives you the right to access a copy of your personal data, correct it, delete it, restrict or object to its processing, receive it in a portable form, and complain to your local data protection authority. We do not discriminate against anyone for exercising these rights.
The honest version of this section. We hold no personal data about you ourselves. RevenueCat and Google hold records keyed only by random identifiers created for your installation, and nothing connects those identifiers to your name - so we cannot find "your" record if you write to us. What works instead: deleting the app removes your recordings and resets the installation identifiers, so a new install starts as a stranger. For anything Apple, RevenueCat or Google holds, their policies and their own request processes apply, and all are linked above. If you still want to write to us, please do - support@white-apps.online.
12. Security
Your recordings sit in the app's own storage on your iPhone, protected by iOS file protection and by your device passcode. They are not transmitted, so there is no connection to intercept and no server of ours to breach. The practical exposure is the phone itself: anyone who can unlock your iPhone can open the app and play your answers. If that matters to you, a passcode and Face ID are the protection - the app does not add a lock of its own.
13. Changes to this policy
If we change how the app handles data, we will update this page and change the date at the top. A change of substance - anything that would send data somewhere it does not go today - would be described here before it ships, and noted in the app's release notes.
14. Contact
Questions, requests, or complaints: support@white-apps.online. We answer within a few business days.