Delete your account

For the Sesh app by Kelvin Benedict. Effective August 22, 2026.

You can delete your Sesh account and its data yourself, in the app, without asking anyone. This page explains how, what gets deleted, and what happens after.

How to delete

• In the app: go to Settings → Danger zone → Delete account. You'll be asked to type your account email to confirm — deletion is irreversible, and we don't want a misclick to be how you leave.
• If you can't sign in: Sesh has no password. Signing in emails a one-time code to your account's address, so as long as you can read that inbox you can get back in and use the button above. If you can't — the inbox is gone, or the account has been deactivated — email hello@sesh.bike and ask us to delete it. Send it from the account's own address if you still can; that is how we confirm the account is yours, and if you can't, we'll have to ask you for something else that proves it before we delete anyone's rides. Sesh is one person, so allow a few days for a reply.

Take your data with you first

Before you delete, you can grab everything: Settings → Danger zone → Export my data downloads a ZIP with your profile, ride and run summaries, your friend list (as names), and your GPS tracks rebuilt as standard GPX files — one per ride day. Export works any time, not just before deletion.

What gets deleted

Deletion is a hard delete, not a deactivation. There is no hidden copy of your account flagged "deleted" — the rows come out of the database and the files come off the disk. When you confirm, we erase:

• your account, your email address, and your profile
• every ride day, run, and GPS track
• the raw recording streams from your sessions
• the original GPX files you imported, as you uploaded them — we keep a copy of the file itself, not just the track we read out of it, and both go
• any recorder diagnostic logs you sent us, which contain location readings
• your tags and ghost data
• your friendships and friend requests, in both directions
• your notifications, and notifications your activity created for others
• your bug reports and app telemetry, as they are stored in Sesh
• your sign-in tokens and any waitlist entry under your email

What your deletion also takes with it

One thing belongs to other people and still cannot survive your account. We would rather name it here than have you find out afterwards.

• RSVPs on group rides you hosted. A ride you organised has you as its host and cannot outlive your account, so the ride is removed and every RSVP on it goes too, including other riders'. RSVPs those riders placed on anyone else's rides are untouched.

What's not deleted

• Shared map data: parks and community segments are shared infrastructure. If you created one, it stays for other riders — but the record that you created it is cleared.
• Other riders' accounts and rides: untouched, apart from the case above. Anything else pointing at you — like who invited whom — is unlinked rather than deleted.
• Moderation reports involving you, in both directions, with your name removed: a report names the rider who filed it and the rider it is about, and your account can be either one. The complaint itself survives your deletion — its reason, its note, whether it was reviewed and what was decided — but both of those links are cleared, so the surviving record does not name you. A complaint someone filed about you therefore cannot be erased by deleting your account, and one you filed about someone else stands after you go. We keep a reviewed report for two years after it was reviewed, then delete it. An unreviewed one is kept until it is reviewed. Until 2026-08-30 the report was destroyed with the account, in both directions.
• Admin audit records: if an admin ever took an action on your account — deactivated it, minted a one-time sign-in code for it, imported a ride on your behalf — one row per action survives your deletion, and it holds the email address of both the admin and the rider. That is deliberate: those rows are the record of what was done and by whom, and an account able to erase them could erase the evidence of its own misuse, or of ours. Each row holds the action, when it happened, the two addresses, and a short note about the action itself (for an import, the filename). If no admin ever acted on your account, no such row exists.
• Bug reports already copied to our issue tracker: a bug report you send from the app is copied into our issue tracker so it can be worked on, and the first line of your message becomes the title of that copy. Deleting your account removes the report from Sesh, but nothing in Sesh reaches into the tracker to remove the copy, and today we have no way to make it. The tracker is private, so no one outside Sesh can read it — but the copy is still your words, kept after you asked us to erase them. If that matters to you, email hello@sesh.bike and we'll remove the copies by hand.
• Encrypted backups, for up to 90 days: we take an encrypted backup of the whole database every night and keep each one for 90 days, so that a failure on our side doesn't lose everybody's rides. A backup taken before you deleted still contains your rows. Deleting your account does not reach back into backups that already exist; instead they expire on their own, so the last one holding your data is gone within 90 days of your deletion. A backup is only ever restored to bring the whole service back from a disaster — never to return one account to the live service.

How long it takes

Deletion happens immediately, in a single operation, when you confirm. You're signed out on the spot and your login stops working. There is no grace period and nothing to undo: the app offers no way to bring the account back, and neither do we. The one place your data outlives the deletion is a backup already taken, which expires as described above.

It is all-or-nothing on purpose. If any part of it fails — including erasing your stored files — the whole thing stops and you get an error rather than a half-deleted account, so you can simply try again. We would rather tell you it didn't work than tell you it did when it didn't.

Retention outside deletion

Some data ages out on its own even if you never delete anything: app telemetry events are removed 90 days after we receive them, screenshots attached to a bug report after 30 days, the bug reports themselves after 180, and recorder diagnostic logs after 14. Raw recording streams have no clock of their own — we keep them for as long as your account exists, because they are what lets a ride be re-analysed when we improve how rides are detected. The exception is your home zone: if you set one, fixes inside it are removed from the raw stream too, including for rides you had already recorded. The full picture is on the Privacy page.

Deletion vs. deactivation

These are different things. Deletion is yours: permanent, self-service, erases your data. Deactivation is an administrative switch used for account issues or terms violations: sign-in stops working, but nothing is deleted. A deactivated rider can still have the account deleted — email hello@sesh.bike from the account's own address and ask.

← Back to Sesh