finilog was designed around an uncompromising principle: your most sensitive information must remain absolutely protected throughout your lifetime – yet remain reliably recoverable by authorized legacy contacts when it truly matters.
Most digital handover systems force users to make a painful compromise between convenience and true security. Passwords or documents often sit in plaintext on third-party servers.
finilog breaks this paradigm. We combine cutting-edge client-side encryption standards with smart, decentralized recovery mechanisms into a single platform that guarantees maximum protection without the complexity.
We have zero mathematical or technical means to access your data. Your password is the sole key.
All confidential data is encrypted before it leaves your device. Our servers never see your real files or passwords.
Privacy is not an afterthought or a feature; it is the architectural baseline of every single line of code.
Our strategic goal is a 100% European infrastructure – for maximum independence and the strictest GDPR enforcement.
Reliable transfer of assets to legitimate legacy contacts without ever weakening cryptographic security beforehand.
The code that encrypts and decrypts your data runs in your browser, not on our servers. That makes it visible: your browser’s developer tools show what actually executes when you unlock your vault. This is not an invitation to trust us — it is the option not to have to.
Since 7 September 2026 it is published: @finilog/crypto under Apache-2.0 — no framework, no network calls, not a single runtime dependency, and its own tests alongside.
Open-source cryptographyThat page has the three addresses, the real code excerpt, the checksum to recompute and the core's own tests.
Every legacy contact gets their own keypair – no password or secret is ever shared between you and your legacy contacts. Your entries are individually encrypted for each legacy contact, directly to their own public key.
Decrypts your own vault. Backed by a one-time generated, printable Recovery Kit code – not a second password to remember.
Every legacy contact with a finilog account gets a personal keypair, protected by their account password, optionally a Passkey, and their own paper Recovery Kit code – any single factor is enough.
Access is never granted by a password or paper code alone. finilog must first independently confirm the handover event and complete the waiting period.
For Legacy Contacts Without Their Own Account
Anyone who doesn't want to create a finilog account instead receives a printed access code. That code alone is never enough on its own – access only becomes possible together with an independent release triggered by finilog once the waiting period has passed.
Initial deployment leveraging established global networks (Cloudflare) to scale while strictly maintaining client-side Zero-Knowledge encryption.
Complete migration of all servers, databases, and core infrastructure components to purely European hosting providers for ultimate digital sovereignty.
Conducting deep, independent security reviews, penetration testing, and continuous code audits by expert external security firms.
By utilizing WebAuthn and Passkeys consistently, social engineering attacks fall flat.
Even in the event of a full server breach, attackers only capture meaningless ciphertext chunks.
No accidental cleartext exposure: for vault entries, documents and files we never hold your key at any point. The one exception we name explicitly.
Unlike your vault entries, personal messages are not readable by you alone. They are delivered later as an email — at a moment when you can no longer take part. That requires the key to sit on our server.
So technically we could read these messages. We do not, but "we cannot" would be a lie here. For everything else in the vault — credentials, documents, files — it still holds without qualification.
finilog operates with 100% transparency. We believe that a true digital legacy can only be built on a foundation of absolute trust. That is why we fully disclose our architecture, encryption workflows, and operations, ensuring you know exactly how your family's future is being protected.
In a real browser, with real PBKDF2 over a million iterations and multi-minute waits — because that is precisely what is being tested. A run therefore takes 20 to 30 minutes.
Against a real database: permission checks, locks and deadlines exactly as the server enforces them.
Pure logic without a browser: derivations, formats, deadlines, message mapping.
These are our own tests, not an external review and not an audit — they show that the software does what we expect of it, not that our expectations are complete. The independent checks are below. If a value is older than 30 days it disappears here rather than lingering as a seemingly current number.
Instead of a badge to look at: every result below links to the real, live report — anyone can re-run the check themselves at any time.
Worth knowing: these tests evaluate transport security (HTTPS/TLS) and server configuration — not the security of our end-to-end encryption itself. A good result here says nothing about how well your vault's contents are encrypted; our disclosed encryption architecture is the more honest proof of that. How our encryption works →