Privacy policy

Last updated: April 27, 2026

Kard (the "app") is operated by RocketCode. Respecting your privacy is part of the product, not a tagline. This policy explains exactly which data is processed when you use Kard, and which never is.

1. What we don't collect

The app requires no account, no email, no password. We do not collect:

• any directly identifiable personal data (name, address, phone) ;
• any location data ;
• any advertising identifier (IDFA, etc.) ;
• any third-party tracking data (no third-party analytics, no pixels) ;
• your contacts, photos or calendar.

2. Data stored on your iPhone

The bulk of your data lives only on your device, in the app's local database:

• your profile (first name, photo if you add one, short bio) ;
• your categories and items (music, films, anecdotes…) with your notes ;
• your preferences (theme, language) ;
• an anonymous identifier (UUID) stored in iOS Keychain, which links your shared kards to your device without revealing your identity ;
• the AES-256 keys used to encrypt each shared kard.

Uninstalling the app removes this data from your iPhone. You can back it up at any time via "Export my data" (a local JSON file, never sent to our servers).

3. Data stored on our servers

When you share a kard, we store on our server only:

• an encrypted blob containing the kard content. We have no way to decrypt it (see section 4) ;
• a short identifier (8 chars, e.g. aB3dEfGh) used as the URL ;
• your anonymous UUID linking you to your kards (never linked to an email or name) ;
• public meta in clear, containing only: chosen theme, kard title, and a boolean indicating whether a profile photo is included. The title is in clear to power link previews (Open Graph) — do not include sensitive info there ;
• an optional handle (public alias, e.g. jules) if you reserve one for readable URLs like kard.you/jules ;
• view counters and the last viewed date ;
• creation / update / revocation timestamps.

If you sign up to the website waitlist, we additionally store your email address, language, and a SHA-256 hash of your IP (for spam deduplication, without storing the IP itself). These are used only to notify you at launch, and removed on request.

4. End-to-end encryption

When you share a kard, the content is encrypted on your iPhone before transmission, using AES-GCM-256. The decryption key is never sent to our servers: it lives only on your iPhone and in the #k=... fragment of the URL you share. By design of the HTTP protocol, the fragment is never transmitted in requests to our servers — only the recipient's browser reads it to decrypt the kard client-side.

The direct consequence: we technically cannot read the content of your kards, even under a legal request. The most we can hand over is the encrypted blob, which without the key is unreadable.

5. Sharing and revocation

You choose exactly what each kard contains before sharing. When you use the share feature, the recap is sent only to the app you choose (iMessage, WhatsApp, email, etc.) — we have no visibility into what is sent.

You can revoke a kard at any time from the app. Revocation permanently invalidates the decryption key and marks the blob as inaccessible: the web page becomes instantly unusable, even for someone who kept the URL.

6. Deleting all your data

You can delete all your server-side data from the app ("Settings → Delete my account"). This action:

• deletes all your shared kards (encrypted blobs + meta) ;
• frees your public handle if any ;
• removes your anonymous UUID from the server.

Local data on your iPhone remains, and is removed by uninstalling the app.

7. Your rights (GDPR)

Under the General Data Protection Regulation, you have the right to access, rectify, erase and port your data. Since virtually all data lives on your device, exercising these rights is instant: edit, export or delete from the app. For server-side data (shared kards, waitlist), email us at [email protected] or use the account deletion described above.

8. Security

Your local data benefits from iOS hardware encryption (Secure Enclave) and your passcode / Face ID. Server blobs are end-to-end encrypted (see section 4): a database leak would not allow reading a single kard.

9. Changes

This policy may be updated to reflect product or legal changes. The date at the top of the page indicates the last revision. Substantial changes are surfaced on the app's home screen.

10. Contact

For any question about this policy: [email protected].