Security

How your photos are protected

Photos and videos are end-to-end encrypted for everyone who uses Kin Album, in the app or on the website. They are encrypted on your iPhone before they are uploaded. Each file gets its own encryption key; that key is wrapped under your family’s album key, and the album key is only ever granted to your family members’ devices — sealed to keys held on their iPhones, on their Android phones, and in the web browsers they use to open the album. Our servers store ciphertext and wrapped keys. We cannot decrypt your photos or videos. Two things below work differently: the optional email photo previews, and invitations sent by email. One limit applies to all of this: the first time a new phone opens an album, it trusts what our servers show it about the album key until someone in the family compares security codes with that phone, so until then a dishonest server could in principle hand that phone a key of its own.

A few things sit outside that encryption so the product can work, and we say so plainly:

Separately, a photo or video you choose to attach when you use Contact us in the iPhone app goes to our support team as it is — it isn’t end-to-end encrypted — with its location removed on your phone first.

The full design, including key rotation and what happens when someone is removed from an album, is documented and available to security researchers on request.

The encryption uses standard, well-studied primitives: Apple’s CryptoKit on the iPhone; Android’s built-in cryptography and Google’s open-source Tink library (for the key exchange) on Android; and the browser’s built-in Web Crypto on the web. On an Android phone, the phone’s own key is stored encrypted under a key kept in the Android Keystore, and is left out of the phone’s backups. We do not invent our own ciphers. Findings from good-faith security research are welcome below.

Reporting a vulnerability

If you believe you have found a security issue in Kin Album, email security@kinalbum.com. Include enough detail to reproduce the issue. We will acknowledge your report within 3 business days, keep you informed as we investigate, and credit you when a fix ships if you would like credit.

We will not pursue or support legal action against good-faith security research that respects our users: do not access other families’ data beyond what is needed to demonstrate the issue, do not degrade the service, and give us reasonable time to fix before public disclosure. Machine-readable details live at /.well-known/security.txt.