How iKamus Protects Your Privacy — A Practical Walkthrough

How iKamus Protects Your Privacy — A Practical Walkthrough

Overview

iKamus uses a combination of end-to-end encryption, local-first data storage, and privacy-by-design principles to minimize data exposure and give users control over their information.

Key privacy features

• End-to-end encryption: Messages and sensitive data are encrypted on the device before transmission; only intended recipients can decrypt content.
• Local-first storage: Primary data (notes, drafts, cached items) is stored locally on the user’s device; cloud sync is optional and encrypted.
• Zero-knowledge architecture: iKamus servers store only encrypted blobs and do not possess decryption keys.
• Minimal metadata collection: The app collects only essential metadata required for service operation; personally identifying metadata is either not stored or is pseudonymized.
• On-device processing: Search, indexing, and some AI features run locally when possible to avoid sending raw data to servers.
• User-controlled sharing: Fine-grained permission and sharing controls let users decide what to share and with whom.
• Ephemeral sessions & keys: Temporary session keys and periodic key rotation reduce exposure if server data is compromised.
• Transparency & audits: Regular third-party security audits and published transparency reports detail practices and findings.

Practical walkthrough (step-by-step)

1. Initial setup: Create a local vault; encryption keys are generated and stored on-device. Optionally enable secure cloud backup — the backup is encrypted with a user-only key.
2. Using the app: When you create or edit content, it’s encrypted locally. If you share an item, the app uses recipient public keys so only they can decrypt.
3. Search & indexing: Local search indexes are stored encrypted; queries run on-device. If cloud search is enabled, queries are transformed to avoid exposing raw content.
4. Syncing across devices: Encrypted data blobs are synced; devices exchange or derive keys using secure protocols (e.g., Diffie–Hellman) so servers never see plaintext keys.
5. Recovering access: Recovery uses a user-controlled passphrase or hardware-based keys (optional). Recovery mechanisms are designed to avoid server-side key escrow.
6. Revoking access: Users can revoke shared links or rotate keys to prevent further access by previously authorized recipients.
7. Account deletion: Deleting an account triggers secure deletion procedures; local keys are removed and server-side encrypted blobs are purged according to retention policies.

Threat model & limitations

• Protected against: Server breaches exposing stored blobs, network interception, casual device theft (if device encrypted and locked).
• Not protected against: Compromised end-user device (malware or keylogging), weak user passphrases, or users mistakenly sharing decrypted content.
• Trade-offs: Local-first design can complicate recovery if keys are lost; some convenience features (cloud AI processing) may require sending limited, protected data to servers.

Best practices for maximum privacy

• Use a strong passphrase and enable device-level encryption.
• Enable two-factor authentication and hardware-backed keys if available.
• Keep software updated to get security patches.
• Prefer local-only features for extremely sensitive data.
• Verify recipients’ keys before sharing sensitive items.

Evidence & transparency

Look for whitepapers, security audit reports, and a published privacy policy from iKamus to verify these claims. If available, review the app’s open-source components and third-party audit findings.