Privacy

Privacy Policy

Effective date: 2026-05-11

We built keni around a simple promise: we can't read your messages. The architecture below makes that a technical fact, not a marketing line.

What we collect

Compliance archive (be aware)

Honesty over slogans: we encrypt every outgoing message twice. Once with your peer's public key (the E2EE copy your peer alone can read), and once with keni's platform public key (the compliance copy). The compliance copy exists so we can respond to lawfully served subpoenas / law enforcement requests, and so PhotoDNA can hash uploaded images for CSAM detection.

The platform private key is held in HSM-grade storage and access requires multi-party authorization documented in our internal incident log. We do not mine the archive for ads, summaries, or product analytics. If this trade-off is unacceptable to your threat model, keni is not the right tool — Signal makes a different choice and we won't argue with it.

AI features (what leaves your device)

AI features (keni assistant, intent routing, summarization, moment-caption suggestions) are different from peer-to-peer chat: to answer, the cloud LLM must "see" your prompt. By default we route through our ai-service which:

Names, addresses, personal events and other non-pattern PII cannot be detected by rules — please be mindful of what you ask AI to summarize or generate.

What we do NOT collect

Content moderation

Images uploaded to public-facing surfaces (Moments) are hashed with Microsoft PhotoDNA against known CSAM datasets. Image plaintext is ephemeral on our servers for the duration of the hash computation. See Safety for details.

Data retention

Identity keys & cloud sync

The private keys that decrypt your E2EE messages are generated on your device. On iOS we store them in Keychain with default kSecAttrAccessibleAfterFirstUnlock + cloud sync attribute, which means iCloud Keychain will replicate them across devices signed into the same Apple ID. On Android we use EncryptedSharedPreferences with allowBackup excluded by default — no auto-sync.

Separately, keni offers an optional passphrase-based backup (Settings → Privacy → Backup identity key). Your private key is encrypted on your device with a passphrase-derived KEK (PBKDF2-SHA256, 100k iterations, AES-256-GCM) and uploaded to our server. We never see the passphrase; the upload is opaque to us. Lose the passphrase = lose decryption ability for old chats.

Your rights (GDPR / PIPL)

Three rights are wired directly into the app, no email needed:

For any request our team can't process via in-app tooling, we respond within 30 days of receiving your email.

Children

keni is not intended for users under 13 (COPPA) / 16 (GDPR member states). If we learn we hold data on such a user, we delete it. To report a minor's account, email safety@hikeni.com.