How this is secured
Concretely, and without the words “bank-grade” or “military”. What is done, and what is not done yet.
Last updated: 16 September 2026
Accounts
- Passwords are never stored as you typed them. What is stored is a one-way encrypted form, so a copy of our database does not hand anyone your password.
- You can switch on a second step at sign-in, from your account page.
- A session runs on a cookie that our server can revoke. Signing out revokes it immediately.
- Forms carry a token that makes it impossible for another website to submit something in your name.
Traffic and servers
- The whole site runs over HTTPS. Plain HTTP is redirected, not accepted.
- The servers stand in Frankfurt, inside the European Union. The database is not reachable from the internet; only the application itself can talk to it.
- Cloudflare sits in front of the site and absorbs the traffic that is not meant for it.
- Backups are made regularly and kept encrypted.
Who can see your data
Only the small team that maintains this platform, and only when there is a reason — answering a support question, or investigating a fault. Access is logged.
What is not yet in place
Being honest about this is worth more than a complete-looking list. As of 16 September 2026, payments are not yet switched on, so no payment data exists. The plain-language write-ups are still being written, so the archive currently shows the researchers' own abstracts. And this platform has not yet had an external security review.
Found a weakness?
Tell us before you tell anyone else, at office@proofdigest.com. Describe what you found and how to reproduce it. We will not take legal action against anyone who reports a problem in good faith, who does not go further into the system than necessary to demonstrate it, and who gives us a reasonable chance to fix it before publishing.