Privacy policy
What Larova stores, and what it never sends anywhere.
The short version
The app collects nothing. Larova has no account system, no analytics, no crash reporting and no internet permission at all — not a setting you can turn off, but a permission the app does not declare, which Android enforces. Everything you write stays on the device it was written on. Nothing you put into Larova is ever sent to the developer, because there is no server to send it to.
This website is separate and is described below. It exists mainly because Google Play requires a reachable privacy policy URL. It sets no cookies, loads nothing from third-party services, and has no analytics.
Who is responsible
Nico Wiedemann, the developer of Larova, is the controller for this website under the GDPR. Contact: privacy@larova.app.
For the content you create inside the app, you are the one who decides what happens to it. The developer never receives it and cannot access it, so there is no processing to be responsible for.
The app
What Larova stores, and where
Everything you create — tiles, guides, notes, checklists, tables, contacts, photos, videos, voice recordings — is stored in the app’s private storage on the device. Photos and recordings are held as files in that private area; everything else in a local database. Other apps cannot read it, and it is deleted when Larova is uninstalled.
What Larova sends
Nothing. The app declares no internet permission, so it cannot make a network request even if a future bug tried to. There is no telemetry, no usage statistics, no crash reports, no advertising identifiers and no third-party SDKs.
Permissions the app asks for
- Microphone — only when you record a voice note, and only for as long as you are recording.
- Camera — only when you take a photo or video from within the app.
- Notifications — only if reminders are enabled.
All three are used on the device for the feature you asked for. Nothing captured through them leaves the device. Larova asks for no location permission, no contacts permission, and no storage permission — pictures and videos are chosen through the Android photo picker, which hands the app one file at a time rather than access to your gallery.
Phone calls
Larova never dials. Tapping a contact opens Android’s own phone app with the number filled in, and the person holding the phone decides whether to place the call. The app has no permission to dial on its own, and it never transmits a location.
Translation
Larova never translates anything. It has no internet connection to do it with, and no translation software inside it.
What it offers instead is a handover. On a tile there is a globe button whose menu passes the words on that tile — the title, the steps, the notes — to a translation app already installed on the phone, the same way tapping a contact passes a number to the phone app. That app does the work under its own permissions and its own privacy policy, which is worth reading if the tile holds something private. Nothing comes back into Larova, and nothing about the handover is recorded.
Phone numbers, web addresses and app names are deliberately left out of what is passed over. None of them mean anything different in another language, and a translated one pasted back would be a tile that no longer works.
If no translation app is installed, the handover is not offered. The same globe also chooses which language to read a tile in, so on a tile written in more than one language the button is still there.
A parent can also write a tile in a second language themselves, from the editor. That text is stored on the phone with the tile and travels in a backup like the rest of it. Nothing about it is sent anywhere, and Larova does not read or check what is typed in.
The activity log
Larova notes locally when a tile was opened and when a checklist item was ticked, so a parent can look back in the evening. Caregivers can add their own entries. This log never leaves the device, is kept for 30 days by default, can be shortened or cleared at any time in settings, and is a plain list of events — the app does not score, rate, interpret or draw conclusions from it.
Backup and handover files
Exporting produces a single file containing your tiles and media. You choose where it goes, through Android’s own file dialog — the device itself, a USB stick, or a cloud provider you already have installed.
If you choose a cloud destination, that provider’s own privacy policy governs what happens to the file from then on. Larova has no integration with any cloud service and no knowledge of where the file went. You can protect the file with a password, which encrypts its contents; we recommend doing so whenever the file leaves your hands. A password you lose cannot be recovered — there is no key escrow and no reset, because that would require a server.
Health information and other sensitive notes
Anything you write about a child’s health, needs or behaviour may count as a special category of personal data under Article 9 GDPR. The local-only design is the answer to that: it is not transmitted, not processed by any operator, and no data processing agreement is needed, because nobody but you and the people you hand the phone to ever sees it.
Larova is a notebook. It does not diagnose, does not calculate doses, does not interpret what you write and does not give advice. It is not a medical device and not an emergency service.
Children
Larova is set up and read by adults, even though it usually lives on a child’s device. It is not directed at children, carries no advertising, and has no social features.
Some tile types are part of a paid full version, bought once through Google Play. Google handles the payment; Larova never sees a card number, a name or an address, and nothing about the purchase is sent anywhere by the app. What it keeps on the device is the receipt Google signed, so that it can check the purchase again without asking anyone — including when the phone is offline. Tiles that arrive in a backup from somebody else keep working whether anything was bought or not.
This website
Hosting and server logs
The site is served by GitHub Pages (GitHub, Inc.). Like any web server, GitHub’s infrastructure processes technical data needed to deliver the page — including your IP address, the time of the request, the page requested and your browser’s user agent. This happens in GitHub’s systems, not ours; we have no access to those logs and cannot connect them to a person. The legal basis is our legitimate interest in serving a working website (Art. 6(1)(f) GDPR). See the GitHub Privacy Statement.
No cookies, no analytics, no third parties
This site sets no cookies and uses no analytics, tag managers, tracking pixels or embedded social media. Every asset — stylesheet, icon, image — is served from this domain. In particular no web fonts are loaded from an external service: the page uses the fonts already on your device.
Your rights
You have the right to access, rectification, erasure, restriction, data portability and objection regarding personal data we hold, and the right to complain to a supervisory authority. In practice we hold nothing about you: the app sends us nothing, and the website’s server logs sit with GitHub rather than with us. If you write to the address above, we will hold your message for as long as needed to answer it.
The Play Store
Downloading Larova from Google Play is a transaction between you and Google, governed by the Google Privacy Policy. Google may tell us aggregate, anonymised install and crash statistics through the Play Console. We do not receive personal data from Google, and Larova itself reports nothing to it.
Changes
If this policy changes, the updated version appears on this page with a new date. The app does not check for changes, and cannot, so material changes will also be noted in the release notes.