Privacy policy
Last updated: 15 November 2026
This is a translation. The English version is the authoritative one.
Recourse is a personal safety app: when you trigger it, it records video, sound and location and sends them, encrypted, to people you trust. It is built so that we cannot see your recordings or know who your witnesses are. This policy explains exactly what reaches our servers.
Who is responsible
Recourse is run by Aleksei Finik, who is the data controller. For any question about your data, write to [email protected]
What we cannot see
Video, sound and location are encrypted on your phone with keys that never reach our servers; only the witnesses you chose can open them. Your list of witnesses is kept only on the phones. Alarms are sealed envelopes in a common feed that every phone downloads, so we cannot tell whom an alarm is for. Witnesses reach us through a relay that hides their network address. SMS alerts are sent by your phone directly through your mobile carrier, and the phone numbers stay on your phone.
What we store
- Account: your email address, and either a password hash or your Google account identifier if you sign in with Google.
- Phone registration: a random device identifier, the phone model, when it last connected, and the public key the phone uses to sign recordings, with the phone maker’s attestation of that key.
- Recordings: the encrypted files, when they arrived and their size, and the signatures and timestamps that prove when each piece existed. We cannot decrypt them.
- Diagnostics: the phone and Android version, app version, which permissions and settings are on, and recent error messages. The app sends them so that we can fix problems; they contain no recordings, contacts or location.
- Trusted contacts invited by email (the earlier way to add witnesses): their email address, so that we can send the invitation.
- Technical logs: IP addresses and request times in server logs, used to keep the service secure and working.
Why we use it
Only to run the service: to let you sign in, receive and keep your encrypted recordings, deliver alarms, prove when recordings were made, and fix errors. The legal bases under the GDPR are performing our agreement with you (Art. 6(1)(b)) and our legitimate interest in keeping the service secure and working (Art. 6(1)(f)). We show no ads, use no analytics or tracking, and do not sell or rent data.
Who else is involved
Contabo GmbH hosts our servers. Cloudflare carries traffic to our websites and API. Resend delivers our emails. Google provides Sign in with Google and distributes the app on Google Play. To prove when a recording existed, we send only its cryptographic hash, never its content, to timestamp services (DigiCert, Sectigo and OpenTimestamps calendars). We disclose data to authorities only when the law requires it, and the recordings we hold are encrypted with keys we do not have.
How long we keep it
Recordings are kept until one of your witnesses deletes them or your account is fully deleted. Account and phone data and diagnostics are kept while your account exists. Email links for deleting an account expire after 1 hour.
Deleting your account
You can delete your account in the app (Settings → Account → Delete account) or on our account deletion page, without the app. Your sign-in, email address, diagnostics and unanswered invitations are erased right away, and you can no longer sign in. Recordings you have already sent stay available to your witnesses for up to 30 days, so that nobody can destroy evidence by forcing you to delete the account. After that everything is deleted: the account, your phones, the recordings and their keys.
Your rights
You can ask for a copy of your data, ask us to correct or delete it, restrict or object to its use, and receive it in a portable format. You can also complain to your data protection authority. Write to [email protected]
Children
Recourse is intended for people aged 18 and over.
Security
Everything is sent over encrypted connections (HTTPS). Recordings are encrypted end to end before they leave your phone, and passwords are stored only as hashes.
Changes
If this policy changes, we will publish the new version on this page with a new date.