Privacy Policy

Last updated November 5, 2026

Attendy is a diary for live events. This policy explains what we store, what leaves your phone, and what we never do. It is written to be read.

The short version

What we collect and why

Account. Your email address and a password (stored hashed by our authentication provider), plus the username, display name and optional profile photo you choose. If you use Sign in with Apple or Sign in with Google, the provider gives us your email address (Apple may give a relay address) and a name we only use to prefill your display name; we never see your Apple or Google password. We use these to sign you in, to show you to the people you allow, and to contact you about your account. Account emails — sign-up, password reset — are delivered by Resend, which receives only the recipient address and the message.

Logs you create. The events you log, your ratings, notes, seat, the friends you tag, the days and acts you attended, and the comments and likes you leave. Everything stays on your phone until you publish it (or share a link to it). Unpublished logs sync only a small tile — event, date, venue — so your own profile stays in sync across sign-ins. Your wishlist — the artists you want to see — syncs to your account so it follows you across devices.

Private-log backup (end-to-end encrypted). The private details of an unpublished log — note, seat, tagged friends, which photos belong to it — are backed up to our servers as an encrypted blob (AES-GCM) so you can restore them on a new phone. The encryption key is created on your phone and stored only in your iCloud Keychain; it is never sent to us and is not derived from your password. We store ciphertext we cannot read. The photos themselves are never uploaded for a private log; the backup holds only identifiers that let your new phone re-attach them from your own iCloud Photos library. If the key is unavailable (for example iCloud Keychain is off on a new phone), the backup stays locked until it is back.

Display copies (on your phone). When you attach a photo to a log, Attendy keeps a reduced-size copy of it inside the app on your phone so the log still shows the picture if you later limit or revoke photo access, or if the original is removed from your library. These copies never leave your phone, and you can turn them off or delete them in Settings → Storage.

Media you publish. When you publish a log, the photos and videos you select for it (up to 20) are uploaded to our servers and shown to the people who can see that log, and to anyone holding a share link you create. Your originals stay in your photo library; we store a copy of what you chose to publish, with location and camera metadata (EXIF) removed. Unpublishing a log deletes those copies from our servers.

Community tabs. If your account is public, photos and videos you publish can appear on the artist's or team's Community tab, grouped by the show or game, with your name and a link to your log. Private accounts never appear there. Media leaves a Community tab as soon as you delete it, remove it from your feed selections, unpublish the log, switch to a private account or delete your account, and it is never shown to anyone you block or who blocks you. Before publishing, your phone checks each item with Apple's on-device sensitive-content analysis when you have Sensitive Content Warning turned on; a flagged item stays in your log and feed but is kept off Community tabs. Anyone can report a Community item; an item reported by three different people is hidden from Community tabs pending review.

Photo scanning (MediaMatch and auto-detect). With your permission, Attendy reads the dates and locations of the photos in your library, on your phone, to find nights that look like events. To identify a candidate we send the place and the night to our servers to look up the event catalog. The coordinates are used only to answer that lookup, in the request body (never in a URL), and are not stored against your account or kept afterwards. We do not upload the photos. You can revoke photo access at any time in iOS Settings.

Song recognition. If you tap the Shazam button on a video, a short audio fingerprint of that video is sent to Apple's ShazamKit service to identify the song. This runs only when you ask for it and is covered by Apple's privacy policy.

Crash and performance data. The app sends crash reports and error diagnostics to Sentry (a US service) so we can find and fix problems. These reports contain device model, OS version, app version and what the app was doing when it failed. They carry no account identifier — we never attach your user id or email, and personal details are scrubbed before anything is sent — so they are not linked to you.

Push notifications. If you allow notifications, we store the device token Apple's push service (APNs) assigns to your phone so we can notify you about follows, comments, companion tags, rewards, new tour dates for artists on your wishlist and, if you opt in, occasional news about Attendy. The token is tied to your account, deleted when you sign out, and every category can be turned off in Settings → Notifications.

Phone number. Adding a phone number is optional and US-only. When you add one, we text you a six-digit code to confirm it; the text is sent by our SMS provider, Twilio, which receives your number for that purpose only. Once confirmed, the number is kept on your account so friends who have it in their contacts can find you, and so you can use Find from contacts. You can change it in Settings → Account → Phone number.

Finding friends from your contacts. If you choose Find from contacts, Attendy asks iOS for access to your contacts (you can share all of them or only some) and reads them on your phone. Names, photos and every other contact field stay on your phone. Each phone number and email address is first scrambled on your phone (a one-way SHA-256 hash), and only those scrambled values are sent. Our server scrambles them a second time with a secret key (HMAC) and compares the result with people on Attendy who allow it, and shows you who is already here. Your own confirmed phone number and account email are stored the same way, as keyed scrambled values, so your friends can find you; Apple relay addresses are never used. To tell you when someone you know joins later, we keep the keyed scrambled copy of your contacts while "Friends who join Attendy" is on. It is replaced each time you check your contacts, and we send at most one of these alerts a day. "Let people find me" (Settings → Privacy) is on by default and controls whether others can find you by your number or email; it never changes who can see your logs. Hashing hides the actual numbers and addresses, but it is not anonymity: a hashed phone number can be guessed by trying every possible number, which is why the second, keyed step happens only on our server, the key is stored separately from the data, and lookups are limited per account.

Rewards. If you take part in the rewards program, we record the actions that earn points (for example publishing a log with media) and the reward you redeem. Reward instructions are sent to your account email; if a reward needs a postal address we ask for it by email at that time and keep it only until the reward has shipped.

Reports and moderation. If you report content, we store the report, the reporter and the reported item so a person can review it. Moderation decisions are logged with the reason.

What we don't do

Who can see what

Your profile can be public or private. A public profile's published logs are visible to any signed-in Attendy user; a private profile's are visible only to followers you've accepted. A share link you create can be opened by anyone who has it, without an account, until you unpublish the log or regenerate the link. Blocking someone hides you from each other, including in Find from contacts. Being findable by your phone number or email only lets people see that your profile exists; your logs keep their privacy setting.

Where your data lives

Your account and published content are stored with Supabase in Canada (ca-central-1), on infrastructure operated by Amazon Web Services. Crash reports are processed by Sentry in the United States. Event information comes from catalog partners (JamBase, setlist.fm, ESPN, TheSportsDB, CollegeFootballData); we send them event and artist queries, never your identity.

Third parties that receive data

None of them receives your data for advertising, and none may use it for their own purposes beyond providing the service to us.

How long we keep it

For as long as your account exists. Unpublishing a log removes its media from our servers immediately. The scrambled copy of your contacts is deleted as soon as you tap "Remove my contacts" or turn off "Friends who join Attendy", and automatically if you haven't checked your contacts for 180 days. Deleting your account removes your profile, logs, media, encrypted private-log backups, push tokens, comments, likes, follows and reports, your phone number, the scrambled values used to find you and your scrambled contacts from our servers, and the sign-in itself; crash reports are retained by Sentry for 90 days and contain no account identifiers. Your local diary stays on your phone until you delete the app.

Your choices

Children

Attendy is for people 13 and older. We don't knowingly collect data from anyone younger; if you believe we have, contact us and we'll delete it.

Changes

If this policy changes in a way that matters, we'll say so in the app before the change takes effect. The date at the top is the date of the current version.

Contact

Attendy · support@attendy.live