Privacy policy
In short. Learnwall has no accounts and no ads. Your goals, flashcard progress and the list of apps you block stay on your phone.
What leaves the phone: the topic you type and the pack settings with your phone’s region setting, reports of faulty flashcards, purchase status, and anonymous crash reports and usage statistics, which you can switch off in the App’s settings.
On the getlearnwall.com website, visit statistics (Microsoft Clarity) run only with your consent, and so does ad measurement (Google); before you choose, Google Analytics receives at most one cookieless ping. Details in section 14.
1. Who we are
We are Smart Apps Factory (“we”, “us”), the maker of the Learnwall app (the “App”) and the getlearnwall.com website. The full details of the data controller are in section 15.
For personal data: privacy-smartappsfactory@gmail.com. Anything else: smartappsfactorydevs@gmail.com. The rules for using the App are in the terms of use.
2. Data that stays on your device
The following is stored only in the App’s private storage on your phone. We cannot see it.
- your answers from setup: how much you scroll, your goal and its date,
- your flashcard packs, which cards you have learned and when each one is due for review,
- daily statistics and your streak,
- the list of apps you chose to block and until when each one is unlocked,
- your settings and the badges you earned.
To show the lock screen, the App checks which app is currently open. It uses Android’s usage access for this. The check happens on the device, only against your own list of blocked apps. We do not build or send a history of the apps you use.
The App is excluded from Android cloud backup. Uninstalling the App or clearing its data removes everything listed above.
3. Data sent to our servers
3.1 Pack topic and settings
When you create a pack, the App sends the topic you typed, the level, the scope, the flashcard language, the App language and the region set on your phone (for example “PL”, never your location). We use them to:
- search for sources in Wikipedia and Wikidata and, if there is not enough text, through Google Search,
- generate and verify flashcards with Google’s Gemini models,
- count how often a topic is chosen per language and region, so we can suggest popular topics to others. A topic is suggested only after we have reviewed it and enough different people have chosen it. Next to the count we keep only a one-way code of your anonymous identifier, to tell people apart.
Finished packs are stored and reused for anyone who asks for the same topic and settings. A pack is not linked to you. When you ask for more cards on a topic, the new cards join the shared pack for everyone. Because the topic becomes part of a shared pack, please do not type personal information into the topic field.
3.2 Reports of faulty flashcards
When you report a flashcard, the App sends the pack ID, the card ID and your anonymous identifier, so the card can be re-checked and replaced.
3.3 Anonymous technical identifier
When the App starts, it receives a random identifier from Google Firebase. It lets the App connect to our servers securely and lets us apply a fair daily limit on new packs. It is also used to check purchases (section 5). With it our servers keep only the counters of the daily limits and whether the free first pack has been used. It is not an account. It is not linked to your name, email address or phone number.
3.4 App integrity check
Requests to our servers carry a proof from Firebase App Check and Google Play Integrity that they come from a genuine copy of the App. This protects the service from abuse.
4. Diagnostics and usage statistics
- Crash reports (Firebase Crashlytics): device model, Android version, App version and the technical trace of the error. We do not add your topics or answers to crash reports.
- Usage statistics (Google Analytics for Firebase): events such as screens opened, setup steps completed and unlocks, tied to a random app-instance identifier and to the anonymous identifier from section 3.3 (we attach the same identifier to crash reports, to match them with problems reported by testers). In the European Economic Area, the UK and Switzerland we collect them only with your consent. Collection of the advertising ID is switched off and the data is not used for advertising.
- Install source (Google Play Install Referrer): once, on first launch, the App reads from Google Play where the install came from: the campaign and page of our website whose link you tapped (for example a blog post), or “organic” if there was none. It contains no personal data. It is sent as a usage statistic, so only under the same conditions as the item above, and it waits on the device until they are met.
- Consent message (Google User Messaging Platform): on first launch the App asks Google whether consent is needed in your country and, if so, shows the message. Google receives your IP address and basic technical device data for this. Your choice is stored on the device in the standard IAB TCF format.
- Remote configuration (Firebase Remote Config): the App downloads its settings from our servers, which also lets us compare versions of the purchase screen.
You can switch off crash reports and usage statistics at any time in the App: Settings → Usage statistics and crash reports. You can change or withdraw consent to statistics there too: Settings → Manage consent for statistics. The choice applies at once and stays after a restart.
5. Purchases
Subscriptions and one-time purchases are handled by Google Play. We use RevenueCat to check whether your purchase is active.
- RevenueCat and we receive the product, the purchase status and dates (including when a free trial starts and ends), a purchase token, your country and currency.
- Your customer identifier at RevenueCat is your anonymous identifier from section 3.3. This lets our servers confirm on their own that a purchase is active.
- RevenueCat also receives your IP address and basic technical device data, such as the Android and App version and the language.
- When you restore a purchase after reinstalling, RevenueCat moves it to the new anonymous identifier.
We never receive your card number or other payment details.
6. Permissions the App asks for
| Permission | Why |
|---|---|
| Usage access | To notice that you opened an app you chose to block. Processed on the device only. |
| Display over other apps | To show the flashcard screen instead of the blocked app. |
| Foreground service | To keep the lock working while the App is in the background. |
| Notifications | To show that the lock is active. |
| Run at startup | To turn the lock back on after the phone restarts. |
| Internet | To build packs, check purchases and send diagnostics. |
7. What we do not collect
- your name, email address or phone number,
- location, contacts, photos, camera or microphone,
- the list of apps installed on your phone or a history of how you use them,
- the advertising ID.
The App shows no ads. We do not sell your data.
8. Legal bases
- Performance of a contract (Art. 6(1)(b) GDPR): building packs, the lock itself, purchases.
- Consent (Art. 6(1)(a) GDPR, and for cookies the ePrivacy rules): usage statistics in the App, and Microsoft Clarity with its statistics cookies, Google Analytics cookies and Google advertising cookies (ad measurement and remarketing in Google Ads) on the website. You can withdraw consent at any time without affecting earlier processing.
- Legitimate interest (Art. 6(1)(f) GDPR): security and abuse prevention, crash diagnostics, and checking whether the consent message has to be shown.
9. Who processes the data
| Provider | What for |
|---|---|
| Google (Firebase, Gemini, Google Play) | Servers, pack generation, integrity checks, crash reports, usage statistics, consent message, configuration, payments |
| RevenueCat | Checking the status of purchases |
| Microsoft (Clarity) | Visit statistics of the getlearnwall.com website, only with consent |
| Google (Google Analytics 4) | Visit statistics of the getlearnwall.com website: before consent at most one cookieless ping, cookies only after consent |
| Google (Google Ads) | Ad measurement and remarketing for the getlearnwall.com website, only with consent to “Marketing” |
| Wikimedia (Wikipedia, Wikidata) | Source texts and the vocabulary of language packs; receives search queries built from the topic, sent from our servers |
These providers may process data outside the European Economic Area, including in the United States, under the safeguards required by the GDPR, such as standard contractual clauses.
10. How long we keep data
- Data on your device: until you uninstall the App or clear its data.
- Shared packs: for as long as the service runs. They contain no information about you.
- Crash reports: up to 90 days.
- Usage statistics: up to 14 months.
- Microsoft Clarity: session recordings up to 30 days, aggregated site statistics up to 13 months.
- Purchase records: for as long as tax and accounting law requires.
11. Your rights
Under the GDPR you can ask for access to your data, its correction, deletion or restriction, object to processing, and ask for a copy in a portable form. You can also lodge a complaint with your data protection authority; in Poland this is the President of the Personal Data Protection Office (UODO).
Because we hold no account and no contact details for you, most of your data can be removed by clearing the App’s data or uninstalling it. For anything else, write to privacy-smartappsfactory@gmail.com.
12. Age
The App is intended for people aged 16 and over. We do not knowingly collect data from children.
13. Changes
If this policy changes, we will publish the new version on this page and update the date at the top.
14. The getlearnwall.com website
- Server: the site is served by Google Firebase Hosting. For every visit the server records technical request data, including the IP address and browser type, for security and to run the site (legitimate interest).
- Your cookie choice is stored in your browser (localStorage, keys
stcm.consent.*). This is essential, so we do not ask on every visit. - Campaign of your visit: if the address you opened carries campaign parameters (for example
utm_source), the site keeps them in your browser (localStorage, keylw.attrib) for up to 30 days, together with the page you came from. When you tap a Google Play link they are added to it, so that Google Play can tell the App which page the install came from. Nothing is sent to us by this, and it contains no personal data. You can delete it in your browser settings. - Microsoft Clarity starts only after you allow “Analytics”. It records how you use the site: clicks, scrolling, mouse movement and session recordings, plus device data and an approximate location derived from the IP address. Text typed into fields is masked. Clarity sets the cookies
_clck(up to a year),_clsk(one day) andCLID(up to a year), and Microsoft may also useMUID. The data is processed by Microsoft Corporation, including in the United States (EU-U.S. Data Privacy Framework). More: Microsoft privacy statement. - Google Analytics 4 loads with the page in Consent Mode v2. Until you choose, every consent signal is set to denied and the page view is not sent: if you leave without choosing, Google receives one cookieless ping (page address, browser and device data, approximate location from the IP address) and sets no cookies. After you choose, the page view is sent with your choice. “Analytics” allows the signal
analytics_storageand the analytics cookies (_ga,_ga_*). The data is processed by Google, including in the United States. More: Google privacy policy. - Changing your choice: “Cookie settings” in the site footer or the icon in the bottom-left corner. After you withdraw consent, Clarity stops collecting data, the cookies of the withdrawn category (Clarity,
_ga,_gcl_au) are deleted, and Google Analytics and Google Ads receive the denied signals again. - Marketing (Google Ads) is optional. If you allow “Marketing”, the consent signals
ad_storage,ad_user_dataandad_personalizationare set to granted. Google may then set the cookie_gcl_au(up to 90 days) and use it to measure the results of our ads (for example that a visit ended with a tap on the Google Play link) and to build audiences of visitors for remarketing. The data is processed by Google LLC and Google Ireland Limited, including in the United States. More: Google advertising partner policies and My Ad Center. Without this consent all three signals stay denied and these cookies are not set.
15. Data controller
The data controller is ASSERT SOLUTIONS IT PIOTR DOBRZYŃSKI, ul. Ludwika Waryńskiego 2b-11, 26-610 Radom, Poland, trading as Smart Apps Factory.