Privacy Policy

Draft of 29 September 2026

This is a draft that has not yet been reviewed by a lawyer. It describes what Lethe Live does today.

On this page
  1. The short version
  2. Who we are
  3. What stays on your phone
  4. What leaves your phone
  5. Cloud Backup
  6. Payments
  7. Why we use your data
  8. How long we keep it
  9. Who else handles it
  10. Your rights
  11. Children
  12. Changes

The short version

  • Your archive — events, memories, notes, photos, videos, tickets, attendance, wishlist and statistics — is stored on your phone.
  • Lethe Live uploads a copy of your archive only if you turn on Cloud Backup. That copy is encrypted on your phone before it leaves, but it is not end-to-end encrypted — here is what that means. Until you turn it on, none of your archive leaves your phone.
  • Your account needs a few details on our server to sign you in, such as your email address and username; they are listed below.
  • There are no ads and no advertising tracking, we don’t use analytics to follow how you use the app, and we don’t sell your personal data.
  • If the app crashes, a technical crash report is sent so that we can fix the problem. It contains nothing from your archive.
  • Nothing is synchronised between your devices.

Who we are

Lethe Live is run by Arsen Kalashian, a private individual, who is responsible for your personal data (the “controller”). You can reach us at support@lethelive.com.

What stays on your phone

Everything you put into Lethe Live: events, venues and dates, the artists you saw or missed, notes, photos and videos, ticket files, your wishlist, statistics, and your profile — your name, city and photograph. Reminders are scheduled on the phone itself; we do not send push notifications.

Lethe Live asks your phone’s operating system not to include the archive in the phone’s own cloud backup (iCloud or Google). A backup file you export yourself goes wherever you put it, and depends on nothing of ours.

What leaves your phone, for every account

Your account

You sign in with Apple, with Google, or with a code sent to your email address. To make that work, our server keeps:

  • a Lethe Live user identifier that we create;
  • your email address, if your account has one, so that we can send you sign-in codes;
  • the identifier Apple or Google gives us for you when you sign in with them, so that the same person reaches the same account;
  • the tokens that keep you signed in;
  • the username you choose, so that signing in on another phone reaches the same account under the same name. Nobody but you is shown it;
  • while you are deleting your account, an identifier for that deletion, so that an interrupted deletion can still be finished. It names the attempt, not you, and keeps nothing about you once the deletion is done.

Sign-in and security email

Sign-in codes and change-of-address notices are delivered by Resend, so your email address passes through them. The messages contain no tracking: link and open tracking are off.

Looking up artists and places

When you type an artist’s name, or search for a city or venue, what you typed is sent from your phone to Wikimedia (Wikidata and Wikimedia Commons) to find matches, and artist images are loaded from Wikimedia Commons. This happens only while you are typing or viewing. Wikimedia receives these requests directly, including your IP address, under the Wikimedia privacy policy. Nothing else about you is sent with them.

Crash reports

When the app crashes, a report of the failure is sent to Sentry: the type of error and where it happened, the app version, your device model and operating system, and — for a crash in native code — diagnostic context and an installation identifier that is not linked to your account. A report never contains your archive, your email address, sign-in tokens, encryption keys, media files or their locations. Nothing is sent while the app is working normally. This is the only technical report the app sends, and it is not used for advertising or to follow what you do.

Directions

If you ask for directions to a venue, the venue is handed to the maps app you choose, under that app’s own privacy policy.

Cloud Backup

Cloud Backup is not sold yet. During the Friends Beta, some testers receive it free of charge; later it will be a paid subscription. Only if you turn it on does a copy of your whole archive leave your phone — events, venues, dates, notes, your wishlist, attendance, your profile, ticket files (which usually show a full name, an order number and a barcode), previews, and full-quality photos and videos.

  • It is encrypted on your phone before it leaves, and our server stores it as data it does not interpret.
  • It is not end-to-end encrypted. So that you can get your archive back by signing in after losing your phone, we hold a way to unlock it. That means we can technically read it. Every use of that recovery is confirmed, recorded and shown to you in the app.
  • Alongside the backup we keep the encrypted key material that protects it, and a record of each recovery: when it happened and which keys were asked for, with no address and no device details.
  • Cloud Backup travels one way. It comes back only when you restore it, and a restore replaces what is on the phone; it is not synchronisation between devices.

Payments

Nothing is sold during the Friends Beta. When subscriptions go on sale, the App Store or Google Play will sell and bill them, and we will not see your payment details. To know which plan you have, our server keeps the purchase records Apple or Google send us, and any complimentary plan we give you.

Why we use your data

  • To provide the service you asked for: your account, sign-in, and Cloud Backup if you use it.
  • Our legitimate interest in an app that works: crash reports, which contain only what is needed to find and fix a failure.
  • To meet legal obligations, where the law requires us to keep a record.

How long we keep it

  • Your account is kept until you delete it. Deleting it removes it from our server first and then erases the archive on that phone — what deletion does and does not reach.
  • Cloud Backup keeps your latest backup and up to three earlier versions. You can delete it at any time in the app; its key material is destroyed first, so what remains cannot be read by anyone, us included. If your Cloud Backup plan ends — a subscription, or a complimentary beta plan — the backup stays readable for 30 days, and the app shows the exact date. After that it is deleted.
  • The record of a Cloud Backup recovery is kept even after the backup or the account is deleted. It holds an account identifier, the time, and which keys were asked for — nothing else.
  • Crash reports are kept by Sentry for the retention period of our Sentry plan, and are then deleted automatically.
  • Email delivery logs are kept by Resend for the retention period of its service.

Who else handles your data

We use a small number of service providers, each only for its stated purpose. Where a provider lets us choose a region, we chose the EU. The full list, with what each receives, is on the sub-processors page. Some of them are US companies, so your data may also be processed outside the EU under their own safeguards.

Apple and Google, when you sign in with them, act under their own privacy policies.

Your rights

You can:

  • get a copy of your archive at any time — Profile → Cloud & Media → Export backup;
  • correct your profile and account details in the app;
  • delete your Cloud Backup (Profile → Privacy & Data) or your whole account (Profile → Account → Delete account), or ask us to — how;
  • ask us what we hold about you, object to how we use it, or ask us to restrict it, by writing to support@lethelive.com.

You may also have the right to complain to the data protection authority where you live.

Children

Lethe Live is not meant for children under 16, and we do not knowingly hold data about them.

Changes

The date at the top shows when this policy last changed.