Privacy Policy
App: Recursa (ch.animenkor.recursa)
Last updated: 7 October 2026
Contact: recursa@animenkor.ch
This policy describes what Recursa does with your data. It is written to be specific rather than broad: where the app collects something, it says what and why, and where it does not, it says so.
Summary
Recursa is a reminders app. It works entirely offline, and an account is optional. Without an account, nothing you enter leaves your phone unless you send us feedback.
If you create an account, your reminders sync to a server so they survive a reinstall and can be shared with a household. That is the only reason data is transmitted.
There is no advertising, no analytics and no tracking of any kind in this app. Nothing about your usage is measured or sold. Crash reports are off unless you turn them on.
Using Recursa without an account
If you never sign in, all of your data stays in a database on your device: reminders, notes, categories, completion history, streaks, achievements and settings. None of it is transmitted anywhere, and we have no way to see it. The one exception is feedback, and only when you send it (see Feedback).
You can use the app this way indefinitely. Reminders, repeats and notifications all work offline.
What is collected when you create an account
Account information
- Email address — used to identify your account, sign you in, and send password resets or sign-in links.
- Password — stored only as a salted hash by our authentication provider. It is never stored in readable form and is never visible to us.
- Username and display name (both optional) — only if you choose to set them, for use in the social features described below.
Your reminder content
Once signed in, the following synchronises to the server:
- Reminder titles and notes
- Categories you create, and their names and colours
- Repeat schedules, due dates and the time zone a reminder was created in
- Completion history: when something was marked done, skipped or snoozed, how late it was, and which member of a household did it
- Streak counts and unlocked achievements
- Household (“space”) names and their member lists
This exists so your reminders survive losing your phone, and so a shared household list shows the same thing to everyone in it.
Notification token
If notifications are enabled, Google Firebase Cloud Messaging issues a token identifying your app installation, and we store it so the server can send you a notification. It is tied to your account, is not readable by other users, is deleted when you sign out, and cannot identify you personally on its own.
What stays on your device even with an account
Some data is deliberately never uploaded:
- Your app settings — theme, notification digest time, time zone
- The calculated schedule of individual upcoming notifications
- Your biometric unlock preference
Biometric unlock
If you enable biometric unlock, your fingerprint or face is never collected, transmitted or seen by the app. Recursa asks the operating system to confirm it is you, and receives only a yes or no. The biometric data itself never leaves the secure hardware on your phone, which is outside the app’s reach by design.
What is stored on the device, protected by that biometric check, is a session token that lets you sign in again without retyping your password.
Crash reports
Crash reports are off unless you turn them on in Settings → Diagnostics → Send crash reports, with or without an account. You can turn them off again at any time there.
While they are on, a crash sends Google Firebase Crashlytics a report so the bug can be found and fixed. A report contains what went wrong in the app’s code, the app version, your phone’s model and Android version, the time, and a random identifier for this installation. It does not contain your reminders, notes, lists or account details, and it is not linked to your account.
Crashes from before you turned reports on are deleted rather than sent. Google keeps crash reports for 90 days.
Feedback
Settings → Send feedback sends us a message from inside the app, with or without an account. Nothing is sent until you press Send, and what is sent is what the form shows:
- The category, subject and message you write
- An email address for our reply, only if you give one. If you are signed in, your account email is filled in for you, and you can remove it.
- Unless you untick them: the app version, your phone’s model and Android version, whether you are signed in, and how many changes are waiting to sync
Nothing from your reminders, lists or account is attached. The message passes through our server to our own mailbox, where it is kept like any other email sent to us. To stop abuse, the server counts how many messages were sent in the last hour, per account (or all together without one), and deletes each count after that hour.
What other people can see
Friends
If you add friends, they can see: your username, your display name, your level, your total XP and your best streak. That is the entire list.
Friends cannot see your reminders, your notes, your categories or your completion history. This is enforced by the database itself, not just by the app.
Your email address is never shown to other users, including friends. Searching for a user by username returns only their username and display name.
Households (shared spaces)
Members of a household you join can see everything in that household: reminder titles, notes, categories, and the completion history including who completed what and when. This is the purpose of a shared household, and it applies only to reminders inside it — your personal reminders are never visible to anyone.
When you complete a household chore, other members receive a notification naming you and the chore.
Invitations
If you invite someone by email, that email address is stored so the invitation can be matched when they join, and it is visible to other members of that household. If you would rather not share an address, use an invite link instead.
Who processes your data
- Supabase — hosts the database and handles accounts and authentication. Their servers also log request metadata such as IP addresses, as any web service does.
- Google Firebase Cloud Messaging — delivers push notifications. For household reminders, a notification’s text can include a reminder title, so that text passes through Google’s servers in transit.
- Google Firebase Crashlytics — receives crash reports, only if you turn them on in the app (see Crash reports).
- Metanet — our email provider, which sends account confirmation, sign-in and password-reset messages and household invitations, and delivers feedback you send to our mailbox.
Data is transmitted over encrypted connections (HTTPS/TLS) and stored on servers in the European Union.
What we do not do
- No advertising, and no ad identifiers are read
- No analytics or usage measurement
- No crash reports unless you turn them on, and no performance reporting
- No location collection. Your time zone is stored so a reminder set for 9am stays at 9am; that is not your location.
- No contacts, camera, photo or microphone access
- No selling or sharing of data with third parties for their own purposes
- No profiling and no automated decision-making
Deleting your data
Deleting individual items. You can delete reminders, categories or a whole household at any time in the app. Deleted items are retained server-side as markers so that the deletion propagates to your other devices rather than reappearing.
Deleting your account. In the app, go to Settings → Delete account. This is immediate and cannot be undone. It removes your account, reminders, notes, categories, completion history, streaks, achievements, friendships and notification tokens.
You can also email recursa@animenkor.ch from the address registered to the account, and we will delete it within 30 days.
Two limitations worth stating plainly: reminders you created inside a shared household remain visible to that household, because they belong to the shared list rather than to you alone; and completion records in a shared household are kept but no longer linked to you.
Signing out does not delete anything. It ends the session on that device and keeps your local reminders.
Your rights
If you are in the EU, Switzerland, the UK or a comparable jurisdiction, you can request access to your data, correction of it, deletion of it, or a copy of it in portable form, and you can object to processing. Write to recursa@animenkor.ch and we will respond within 30 days.
Children
Recursa is not directed at children under 13 and we do not knowingly collect data from them.
Security
Connections use TLS. Passwords are salted and hashed. Access to your data is enforced at the database level by row-level security policies, so a bug in the app cannot expose another user’s reminders. Session tokens stored for biometric unlock are held in the operating system’s hardware-backed keystore.
No system is perfectly secure, and we do not claim otherwise.
Changes
If this policy changes materially, the date at the top will change and the new version will be published here. Continuing to use the app after a change means accepting the updated policy.
Contact
Responsible party: Robin Engweiler, Switzerland.