Ingenium — last updated 11 July 2026
Ingenium is a brain-training and speed-reading app made up of short exercise games across several categories, plus a reading-speed test. This policy explains what information the app handles, where it is stored, and the limited cases in which anything leaves your device.
Ingenium is local-first: there are no accounts, no login, and no backend that stores your data. Your training progress, session history, and settings live only on your device and are not associated with any account. This policy covers the Ingenium mobile app as distributed on the Apple App Store and Google Play. It does not cover third-party services you may reach through the app (Wikipedia, Google), which have their own privacy policies (see Section 9).
Ingenium is provided by Bohdan Varchenko (the "developer", "we", "us"), an individual developer, who is the data controller for the limited processing described in this policy.
All of the following is stored only on your device, is not sent to us or to any server, and is not linked to any account or identifier. It is held in a local SQLite database file (named ingenium.sqlite, created by the app in its private documents area) and in the operating system's standard app-settings storage (SharedPreferences on Android / user defaults on iOS).
Exercise and progress data (local SQLite database):
Settings and preferences (local app-settings storage):
None of this is transmitted off the device by the app.
A note on data persistence: your locally stored progress and settings are preserved across app updates — an update migrates the local database as needed, so your exercise history and preferences carry forward. Your data is removed only when you uninstall the app or reset it yourself.
The app does not collect, request, or store any of the following:
No advertising SDKs are used and the app does not track you across other apps or websites, so Apple's App Tracking Transparency prompt is not shown. The app does use Google's Firebase Analytics for pseudonymous, opt-in usage measurement (off by default — see Section 7); that is product analytics only, builds no profile of you, and collects no advertising identifier.
The app connects to the internet in a small number of clearly defined cases. Below is each one, honestly described. The app does not send your progress, session history, or settings in any of these requests.
a) Reading content — Wikipedia (Wikimedia Foundation). To provide texts for the reading exercises, the app makes one-way GET requests to the public Wikipedia API to download article text. It sends only the standard request information any web request includes — your device's IP address, a fixed app identifier in the request ("Ingenium/1.0 (reading exercise)"), and the title and language edition of the article it is fetching. It does not send your name, progress, or an account identifier (there is no account). Be aware that, as with any web request, the article you request and your IP address are visible to Wikimedia.
You can also tap the attribution links shown on a Wikipedia-sourced exercise; these open the Wikipedia article page and the Creative Commons license page (creativecommons.org) in your device's external web browser. Once a page opens in your browser, that browser (and the site you open) handles the request, including your IP address and any browser cookies.
b) Display fonts — bundled, not downloaded. The app's display fonts are packaged inside the app itself, so no fonts are downloaded at runtime and no font requests are made to Google or any other server.
c) Crash reports — Firebase Crashlytics (Google) — opt-in only. Described in detail in Section 7. This is off by default and only sends data after you explicitly opt in. The app initializes Firebase so this feature can exist, but sends no data to Firebase unless and until you opt in. No diagnostic or analytics information is sent to Google unless you enable the corresponding privacy option (crash reporting or analytics).
d) Usage analytics — Firebase Analytics (Google) — opt-in only. Described in detail in Section 7. This is off by default and only sends data after you explicitly opt in. When enabled, it sends pseudonymous product-usage events — which exercises and screens you use, your daily-training and reading-speed-test completions, the daily-training skills you prioritize, favorites you toggle, the app settings you change, and the steps of the subscription flow, as counts, levels and durations — never your scores or results, the texts you read, or any personal data, and with no advertising identifier and no ad personalization.
e) Feature suggestions — Cloud Firestore (Firebase, Google). If you open Suggest a feature (in Settings) and tap send, the app writes your idea to our Cloud Firestore database. What is sent: the idea text you wrote, any optional title, category and importance you selected, an optional email only if you chose to provide one, and your app version, platform (iOS/Android) and interface language. It does not include your name, an account identifier (there is no account), your training progress, or your session history. Nothing is sent unless you deliberately tap send, and these writes are gated by Firebase App Check (Play Integrity on Android, App Attest on iOS) to block automated spam. Submitted ideas are stored in our Firebase project, are readable only by the developer, and are used solely to guide future development. Please avoid including personal information you would not want us to see.
Aside from the cases above, the app has no other servers it talks to. It uses no push-notification server (see Section 8).
Crash reporting is off by default and strictly opt-in. Nothing is sent until you explicitly turn it on. On first run the app asks once whether you want to help by sending crash reports, and you can change your decision at any time in Settings → Privacy.
When — and only when — crash reporting is enabled, a crash or fatal error sends the following to Google (Firebase Crashlytics):
Crash reports do not include your name, email, an account identifier set by us, your training progress, session history, or the texts you read. Because the crash-reporting library attaches the installation identifier above, we describe these reports as containing no personal data or account identifier from the app, rather than as fully anonymous.
Turning it off: if you disable crash reporting, collection stops and any reports captured but not yet sent are deleted from your device.
Crash data sent to Google is processed by Google under Google/Firebase's own privacy terms (see Section 9).
Usage analytics is also off by default and strictly opt-in, controlled by the same first-run choice and its own Settings → Privacy toggle. When — and only when — you enable it, the app sends pseudonymous product-usage events to Google (Firebase Analytics): which exercises you start and finish, your daily-training and reading-speed-test completions, the skills you prioritize for daily training, which screens and statistics you open, favorites you toggle, the app settings you change (such as theme, language, and the privacy toggles), and the steps of the subscription flow — as counts, difficulty levels and durations, never free text and never your scores or results.
Firebase Analytics also attaches the standard data its SDK collects: an app-instance identifier (a pseudonymous id generated by the library, not linked to any account), the app version, the device model and OS version, a coarse region derived from your IP address at collection time (the IP address itself is not retained by us), and your content language (the interface/content language you chose — a setting, not personal). Ad personalization is disabled, and no advertising identifier (IDFA/AAID) and no vendor/Android identifier is collected — this is product analytics only, never advertising or cross-app tracking.
Analytics events do not include your name, email, an account identifier set by us, your training progress, session history, or the texts you read. Turning it off: disable analytics in Settings → Privacy and collection stops; the app also resets the analytics state, dropping the app-instance identifier and any locally cached events.
POST_NOTIFICATIONS). Used only for local reminders you set up for training and reading. These reminders are generated entirely on your device — there is no push server, no Firebase Cloud Messaging, and no APNs token. Your reminder times, days, and text never leave your device. Notifications are opt-in; you can grant or revoke this permission from the Notifications screen or your system settings, and reminders can be turned off at any time.RECEIVE_BOOT_COMPLETED). Used only to re-schedule your existing local reminders after you reboot the device or update the app, so they are not lost.The app does not request location, camera, microphone, or contacts permissions, and does not use exact-alarm scheduling on Android.
The only third parties that may receive any data, and only in the limited ways described above, are:
We do not sell or share your personal information with any third party for advertising or any other purpose.
Some reading passages come from Wikipedia and are used under the Creative Commons Attribution-ShareAlike 4.0 (CC BY-SA 4.0) license, with attribution to the article and its authors. Each Wikipedia-sourced exercise shows a link to the source article and to the license text.
Because your data lives only on your device, you control its lifetime:
We do not retain any copy of your data, because we never receive it. Crash reports and pseudonymous analytics you choose to send are retained by Google/Firebase under Google's retention terms.
We support the rights available under the EU/UK GDPR (including access, rectification, erasure, restriction, portability, and objection) and the California CCPA/CPRA (including the rights to know, delete, and opt out, and the right not to be discriminated against for exercising them).
Because Ingenium stores your data only on your device and holds none of it on our servers, you exercise most of these rights directly and immediately: your data is already in your possession, you can view it in the app, and you can erase it by uninstalling. We do not sell or share your personal information as those terms are defined under the CCPA/CPRA.
For any question about this policy or your rights, contact us at bohdan.varchenko.dev@gmail.com.
Legal bases (GDPR). For the limited processing that occurs: fetching reading content from Wikipedia relies on our legitimate interest in delivering core app functionality, because it is necessary to provide the reading exercises you request; crash reporting and usage analytics both rely on your consent (which you may withdraw at any time).
Ingenium is not directed to children under 13 (or under 16 where a higher age applies), and we do not knowingly collect personal information from children. The app has no accounts and does not collect information that directly identifies you, as described above. If you believe a child has provided personal information in a way that concerns you, contact us at bohdan.varchenko.dev@gmail.com.
Ingenium stores your data on your own device, in your own location. Data leaves your device only for the limited flows in Section 6. Any opt-in crash reports and analytics data are handled by Google and may be processed on servers in the United States or other countries; Wikipedia content requests are handled by the Wikimedia Foundation, which may likewise process them outside your country. These transfers are governed by the respective providers' privacy policies (Section 9).
We may update this policy as the app evolves. When we make a material change, we will update the "Last updated" date above and publish the new version at the policy's canonical URL: https://ingenium-brain-training.web.app/. Significant changes may also be noted in the app or its store listing. The updated policy becomes effective when it is published at the URL above.