Privacy Policy
Last updated October 29, 2026
klk is a private, invite-only app for sharing photos and video inside small groups, which the app calls klks. This policy describes what the app collects, why, who can see it, and, just as important, what I can still see myself.
The honest version, up front. Your photos, videos, captions and comments are end-to-end encrypted. They are locked on your phone before they leave it, and only the devices of the people in that klk hold the keys to open them. klk's servers store them, but cannot read them, so not even I can see them. Your profile photo is encrypted the same way, so only people who share a klk with you can open it.
That covers what you post, not everything about it. To run the service, klk's servers still see who you are, which klks you are in, and who posted, liked, viewed or commented on what, and when. The full list is below.
What I collect
Account information
- Email address and password. Used only to sign you in. Your password is handled by Firebase Authentication and is never visible to me. Your email is not shown to other users anywhere in the app and is not part of your visible profile.
- Display name. Visible to people who share a klk with you. It is not encrypted, so invites and notifications can show who they are from.
- Profile photo, if you set one. Your phone shrinks it, which removes its embedded metadata (EXIF) including location, then encrypts it so only people who share a klk with you can open it. I store it, but cannot see it.
- A user id generated at sign-up, used to attach your content and klk memberships to you.
Content you share
- Photos and video you post as Posts, Moments or Clips, with their captions and the comments on them. All of these are end-to-end encrypted. I store them, but only the klk can open them.
- Likes, views and activity: who liked or viewed what, who commented and when, and who was mentioned. These are not encrypted.
- Which klks you belong to, who created each klk, its name and its colour. These are not encrypted.
- Before a photo or video is encrypted, the app reduces it to a sensible size on your phone. Photos are re-encoded, which removes their embedded metadata (EXIF), including location. Videos are re-encoded without metadata, unless they are already small enough and carry no location, in which case they are uploaded as recorded and may keep details such as when they were filmed. Either way, whatever is left is encrypted along with the file, so I cannot see it. Only the other members of that klk can.
Device and diagnostic information
- A push notification token for each device you sign in on, so klk can tell you about activity in your klks. It is readable only by you.
- Crash and error reports, sent to Sentry when the app fails. These include the error, technical details of the device and app version, and your user id, email address and display name so a report can be tied back to an affected account. They never include your photos, videos, captions or comments.
If you request beta access
- Your email address, if you ask for access on this website. It is stored in Firebase and used only to email you the links to install the beta. It is kept until you ask me to remove it. Email privacy@klkapp.com.
What I do not collect
- No advertising identifiers, and no advertising of any kind.
- No behavioural analytics or usage tracking product is installed in the app.
- No contacts, no address book access, no location permission.
- No data is sold, rented, or shared with third parties for their own purposes.
How encryption works
Each klk has its own key. It is shared only with the devices of the klk's members, and an invite link carries it to the person being invited in the part of the address that is never sent to a server. Everything you post to a klk is encrypted with that key on your phone before it is uploaded, and decrypted on the phone of whoever opens it. When someone leaves or is removed from a klk, the klk gets a new key, so they cannot open anything posted after they left. What they could already see before then stays readable to them.
When you set up klk, you choose a recovery passphrase. It locks a copy of your keys that I store, so you can sign in on a new phone and still open your klks. I never see the passphrase, and I cannot reset it. Because that locked copy is only as strong as the passphrase, choose one nobody could guess.
How encryption works explains all of this with pictures, and gives the full technical details.
What I can still see
End-to-end encryption hides what you share, not the fact that you share it. klk's servers can see:
- Your email address and display name.
- The names and colours of your klks, and who is in each one.
- When something was posted, by whom, and to which klk; whether it is a photo or a video, and its size and layout.
- Who liked, viewed or commented on it, when, and who was mentioned.
- Your push notification tokens, and crash reports as described above.
Push notifications say who did something, never what they said or shared. The server has nothing readable to put in them.
Who can see what
- Other members of a klk can see everything posted to that klk, and can see your display name and profile photo.
- People you share no klk with cannot see your content and cannot see your profile at all. They cannot search for you, mention you, or find that your account exists.
- The public sees nothing. klk has no public profiles, no explore feed, and no web-visible content.
- I cannot see your photos, videos, captions or comments. I can see the information listed under What I can still see, and access it only where necessary to operate the service, to investigate a specific abuse or safety report, or where legally required. If I am legally compelled to hand over data, encrypted content is all I would have to give.
Reports and blocks
You can report a post, comment, moment, clip or person from inside the app. Because I cannot open anything in a klk myself, a report includes what you choose to send me: the caption or comment, and for photos and videos the key that opens only those files, so I can review them. I keep a copy of the reported files with the report, along with who filed it, who it is about, the reason and any note, until I have reviewed it. Reporting does not give me access to anything else in the klk.
When you block someone, your list of blocked people is stored where only you and klk's servers can read it, so the app can hide their content from you and stop their notifications to you. They are not told. I receive a notification that a block happened, so I can look for abuse.
How invites work
Joining a klk is only possible through an invite link created by the klk's creator. Each link is a single-use, unguessable, expiring token, and it is redeemed on the server. The app cannot add anyone to a klk on its own. The creator can revoke every unused link at once. There is no directory to browse and no way to request access to a klk you were not invited to. Because an unused link also carries the klk's key, treat it like a key: send it only to the person it is for.
Service providers
I use a small number of processors, and only for the purposes listed:
- Google Firebase (Authentication, Firestore, Cloud Functions, Cloud Storage) hosts accounts and encrypted content, profile photos included. Data is stored on Google Cloud infrastructure in the United States.
- Cloudflare (R2) stores the encrypted files of the photos and videos you post. It receives them already encrypted and cannot open them. Data is stored in North America.
- Expo delivers push notifications to your device. They carry no content.
- Sentry receives crash and error reports.
- Resend sends the beta invite email to the address you request access with.
Retention and deletion
Content stays until it is deleted. You can delete your own posts, moments, clips and comments at any time, and deleting one removes its media from storage. Deleting a klk deletes everything posted to it. Leaving a klk removes your access to it; content you already posted there remains visible to that klk unless you delete it first.
You can delete your account and everything attached to it in the app, under Settings → Delete account. If you no longer have the app, email privacy@klkapp.com from the address on the account. I delete your account, profile, push tokens and the content you posted, and remove you from your klks. Backups may retain copies for up to 30 days before they age out. Deleting your account lists exactly what is deleted and what is kept.
Children
klk is not directed at children under 13, and I do not knowingly create accounts for them. Parents commonly share photos of their own children inside a family klk. That content belongs to the adult who posted it and is governed by this policy. If you believe a child under 13 has created an account, contact me and I will remove it.
Your rights
Depending on where you live, you may have the right to access, correct, export or delete your personal information, and to object to certain processing. Email privacy@klkapp.com and I will act on it. I do not discriminate against anyone for exercising these rights. Because your content is end-to-end encrypted, I hold it only in a form I cannot read, so the information I can export or correct is what is listed under What I can still see.
Security
Photos, videos, captions, comments and profile photos are end-to-end encrypted with widely used, openly reviewed algorithms (XChaCha20-Poly1305 and X25519), so a breach of klk's servers would expose encrypted content, not what you shared. Everything is also transmitted over TLS, and server-side security rules check klk membership on every read and write. No system is perfect, and I will notify affected users of a breach that puts their information at risk.
Changes
If this policy changes materially, in particular if what I collect or what I can see changes, the date at the top will change and the app will tell you.