Data protection
Your rights over what we hold, where it is, and who else touches it. The list of what that is lives in What we keep; the formal version is the Privacy Policy.
Your rights
See what we hold
Almost all of it is in the app already: your profile under Edit Profile, your prints on your rolls, your friends under Friends, your blocks under Privacy & Safety. For a copy of the rest, write to [privacy@example.com] from the address you signed in with and say which account.
Correct it
Display name, bio, photo and banner are yours to change in the app. A username cannot be changed (see Your account).
Delete it
Settings → Danger Zone → Delete Everything removes the account and everything in it, immediately, with no waiting period. If you cannot get to the app, email [privacy@example.com] from the address you signed in with, with your username. We confirm by replying to that address before deleting.
Take it with you
Every print can be saved to Photos at full size from inside the app. For an export of your profile, captions, comments and friends list, ask at the address above.
Object, restrict, or complain
Write to us first; we would rather fix it. You also have the right to complain to the data-protection authority where you live.
Retention
- Account and profile: while the account exists.
- Prints, voice notes and comments: until deleted, then 30 days hidden before the nightly sweep removes them for good.
- Invites: at most a week live, cleared 30 days after expiry.
- Push tokens: until sign-out or deletion.
- Usage counts: anonymous per-install id and daily counts, kept for the life of the project.
Where it is
The database, authentication and file storage are a single Supabase project in [Supabase region — check Project Settings → General]. The website runs on Vercel and reads only two things without a sign-in: an invite’s preview and a public profile; it never reads a print. Notifications are sent through Apple’s push service from a function in the same Supabase project.
Who else processes it
| Who | For what |
|---|---|
| Apple apple.com/legal/privacy | Sign in with Apple; push notifications (APNs); App Store subscriptions (StoreKit); Apple Wallet for the membership pass. |
| Google policies.google.com/privacy | Sign in with Google, only if you choose it. |
| Supabase supabase.com/privacy | The database, authentication, file storage (prints, voice notes, avatars, banners) and the function that sends notifications. |
| Vercel vercel.com/legal/privacy-policy | Hosts this website: the landing page, invite previews, public profiles and the help centre. |
That is the whole list. There is no analytics vendor, no advertising network and no crash-reporting service in the app.
Security, briefly
- Every table has row-level security switched on with no direct policies; the app reaches data only through functions that each open one door.
- Prints are in a private bucket, served by signed links that expire.
- Invite tokens and contact matches are stored as SHA-256 hashes only.
- Photos are re-drawn on the phone before upload, so no EXIF or location ever arrives.
Contact
Data-protection requests: [privacy@example.com].
Everything else: info.probablylate@gmail.com.
[Company legal name], [Registered address].