Privacy Policy

Last updated: 2026-07-16 · Privacy by architecture, not by policy — but here is the policy anyway.

1. What we cannot see (architectural guarantees)

· Message, call and file contents: end-to-end encrypted and transmitted peer-to-peer; servers do not relay content — we are technically unable to read it.
· Your face: AegisID processes and stores only a 512-dimensional feature vector; photos and frames are discarded immediately and never uploaded; the vector cannot be reversed into a face image.
· Your behavioral baseline: on-device AI (L3) trains and runs locally; behavioral data never leaves your device.

2. What we process

· Account anchor: AegisID feature vector and an identity blob encrypted with your PIN (we cannot decrypt it).
· Signalling metadata: the minimum required to establish peer-to-peer connections (presence, connection negotiation).
· Rule sync: devices download anti-scam rules and blocklists — a download, not an upload.
· Anonymous scam intelligence: when a user actively reports, only the reported party's public-key hash is uploaded — never conversation content.

3. AegisPay data separation

Once AegisPay launches: we receive only the signals needed for transaction risk assessment, never the identity data of fiat customers — KYC for fiat is performed and retained by regulated ramp providers. Design principle: we know the risk, not the identity.

4. Cookies & analytics

This website uses no third-party tracking cookies and no Google Analytics. If traffic analytics are introduced, they will be a self-hosted, privacy-preserving solution, and this page will be updated.

5. Retention & deletion

Your encrypted identity blob is deleted when you delete your account. Because we cannot decrypt content, data-portability and content-review requests are technically inapplicable to message contents.

6. Contact

contact@aegisrd.com