Security
At DiggAi, security is not a marketing claim — it is architecture. This page shows, verifiably, how your information is protected.
Three stops. Your information is readable only on your own device and at your practice.
This is where your information is encrypted — before anything is sent.
Only accepts the sealed envelope and passes it on. We hold no key for it.
Opens the envelope with its own key — and is the only one who can.
Everything in between is unreadable. After your practice has picked it up — after 30 days at the latest — the package is deleted from the server.
Encrypted before it leaves your device
Your information is end-to-end encrypted directly on your device (X25519 key exchange, AES-256-GCM). Only the practice you selected can decrypt it again.
DiggAi only relays: the server sees and stores nothing but encrypted packages and holds no key to read them. What no one can decrypt, no one can steal.
After your practice has picked it up — after 30 days at the latest — the encrypted package is deleted from the server.
Your record stays with you
Your health record lives on your own device — not in a central database. There is no account, no password and no central health record held by the operator.
You decide which practice receives what, and you can view, export or delete your record on your device at any time.
No ads, no third-party services
diggai.de loads no advertising or analytics services and no content from third-party servers. Fonts and all assets are served by us; there are no tracking cookies.
The optional AI assistance also runs directly on your device — your information does not leave it for that.
Technology at a glance
- Transport encryption TLS with HSTS (preload)
- End-to-end encryption: X25519, AES-256-GCM, HKDF
- Strict Content-Security-Policy, servers in the EU (Hetzner, Helsinki)
- Coordinated vulnerability disclosure per RFC 9116 (security.txt)
Frequently asked questions about security
Who can read my information?
Only you and the practice you send it to. Encryption happens on your device; only the practice holds the matching key.
What does DiggAi store about me?
The server stores only the encrypted package until your practice picks it up — after 30 days at the latest it is deleted. There is no central health record.
Why don't I need an account?
Because there is nothing central that an account would need to protect: your record lives on your device, and your practice identifies itself with its key.
What happens if I lose my device?
Your record exists only on your device. Use your phone's screen lock and the record's export function to keep your own backup.
I found a security vulnerability — where do I report it?
Please report it confidentially by email. The machine-readable contact point is published at /.well-known/security.txt (RFC 9116).
What we do not claim
DiggAi is not a medical device and currently holds no certification (e.g. ISO 27001). This page describes the architecture as actually built — verifiable on the live system.
Evidence · Privacy Policy · Last updated: August 2026