Privacy Policy

When you create a saved card, Kehdoo stores the card text, names you enter, style choices, creation time, and a randomly generated card ID so the recipient can open the shared link.

If you add a photo, the server resizes it, converts it to WebP, and strips metadata before storing it. If card saving is unavailable, Kehdoo will not create a share link; you can try again once the service is available.

If you sign in with Google, Kehdoo receives the account information needed for sign-in and uses your account ID to show your saved cards in the dashboard. You can create cards without signing in.

Kehdoo does not use analytics, tracking pixels, or fingerprinting scripts. If you sign in, Supabase authentication cookies keep your session active. Card pages also use local browser storage to avoid counting repeated opens from the same session.

Kehdoo uses Supabase for authentication, database storage, and photo storage. Supabase processes this data so Kehdoo can provide saved card links and optional dashboards.

Google provides optional sign-in. Google may process your sign-in request according to its own privacy policy.

When you use the WhatsApp share button or your device's native share sheet, those services handle the share action according to their own privacy policies.

Saved cards remain available through their private link unless they are removed from the service.

To request deletion of a saved card or account-related data, contact us from the email address associated with your account and include the card link when relevant.

Questions? Reach us at [email protected].