Lemur Privacy Policy

Version 0.5 — 9 November 2026

This policy concerns Lemur on Android, including the Mini Zoo preview. Purchases are currently unavailable.

1. Who is responsible for the app

Publisher: Marcin Wiśniewski. Privacy contact: [email protected]. Marcin Wiśniewski is the controller of data provided to him in correspondence and when handling user requests. The postal address is in the Terms of Use.

2. What the game stores on the device

Lemur stores the chosen profile name, random local profile and game identifiers, answers, whether they were correct, response times and session dates, game history, progress, earned zoo items and sound settings. The device also retains the language setting, icon variant and the date it was changed, and the state of full-version reminders.

The data support resuming games, selecting exercises, displaying results, unlocking rewards and remembering settings. A nickname is sufficient for a profile; a surname, age, address or email is not required. Game results are not used for decisions producing legal or similarly significant effects on the user.

Profiles are not online accounts and do not have separate passwords. People using the same installation can access all profiles and results. This also applies to a teacher's device used in class.

3. Whether data reaches the publisher

The current version's code does not send profile names, answers or results to the publisher. The game has no account server, external analytics, advertising or advertising tracking tools. It does not use location, contacts, microphone or camera. It does not send automatic error reports to the publisher.

Android, the store and services configured on the device may independently process data under their own terms and the user's settings. This does not mean that the publisher receives the local game-results database.

4. Storage, backups and security

Game state is stored in the app's private storage protected by Android mechanisms. The database is not separately encrypted with a user password. Someone with access to an unlocked device may be able to read results in the game; using a screen lock is advisable.

Lemur does not operate its own cloud backup or profile synchronisation. Standard Android cloud backup for the app is disabled in this version. Device-to-device transfer may depend on the manufacturer and its tools. The publisher cannot restore lost history from its own server.

Profile data remains in the current game save until the profile is deleted or app data is cleared. History has no automatic expiry. App settings remain until changed or app data is cleared. Deletion in the interface does not guarantee specialised, irreversible overwriting of device storage.

5. How to delete data

Profile management lets you rename a profile, reset progress or delete it. Resetting keeps the profile and its name. Deleting a profile removes its history and progress from the current game save.

To remove all local profiles and settings, clear Lemur's data in Android settings or uninstall the app. Exact option names depend on the device. The publisher has no remote access to this data and cannot delete it on the user's behalf.

6. Map saved to the gallery

At the user's request, the game saves an image of the zoo map to the device gallery in Pictures/Lemur. It shows the discoveries made in the game. It is stored outside the app's private database and may be accessible to gallery apps, other authorised apps and photo-sync services chosen by the user.

Deleting a profile or uninstalling Lemur does not delete these images. Delete them separately in the gallery and, if synchronised, in the relevant service. The user decides whether to share the image further.

7. Children and school use

The game is also intended for children. It does not ask a child for contact details or require an online account. A parent, guardian or teacher should choose a profile name without unnecessary identifying information and manage access to the device. Adults sending requests should omit children's surnames and other unnecessary information.

A school or teacher using identifiable pupils' results is responsible for its own processing arrangements and obligations towards pupils. Local storage does not remove those obligations.

8. Contacting the publisher

If you write to the publisher by email or post, the publisher receives your message, attachments and contact details you provide. Email goes to [email protected]. Only the publisher has access to this inbox on Lemur's side. For postal correspondence, the postal operator processes the address data needed for delivery. Include only what is needed to resolve the issue.

The publisher uses message data to answer questions or resolve issues. The legal basis is the publisher's legitimate interest in providing support and improving the game (Article 6(1)(f) GDPR). Depending on the matter, the basis may also be performance of a contract or steps requested before a contract (point (b)), compliance with a legal obligation such as handling a complaint (point (c)), or the legitimate interest in establishing, pursuing or defending claims (point (f)).

Google Ireland Limited provides the publisher's consumer Gmail account in the European Economic Area. Google processes data in providing Gmail under its own privacy policy. Google says it may process data outside the EEA. Depending on the destination and transfer basis, it uses European Commission adequacy decisions or standard contractual clauses. Google explains details and how to obtain a copy of its clauses on its Data Transfer Frameworks page in Privacy & Terms.

The publisher keeps ordinary requests for the time needed to handle the matter and for up to 12 months after closure, so a recurring issue can be revisited. Records needed for a complaint, legal obligation or establishing, pursuing or defending claims are kept for as long as necessary for that purpose, considering applicable obligations, limitation periods and any proceedings.

Subject to the GDPR's conditions, you may request access to data supplied to the publisher, rectification, erasure, restriction and portability. You may object to processing based on legitimate interests. You may complain to the President of the Polish Personal Data Protection Office or another competent supervisory authority. Contact details are voluntary, but without them a reply may not be possible. The publisher does not subject correspondents to automated decisions producing legal effects.

9. Payments and changes

The current version does not process Google Play payments, collect card details or check a purchase account. Before purchases become available, this policy will be updated to reflect the actual transaction data flow, Google's role, any verification server and retention periods. Connecting the store may change data processing.

The date and number at the beginning identify the document version. Users should be informed of significant changes before new processing begins. Opening the privacy policy is not consent to tracking or marketing.