// FAQ
Frequently asked questions.
The answers we give most often in the first call. Collected from our services and articles.
6 questions
No. The key sits in the part of the link behind the #, which browsers never send to a server. The server stores only ciphertext, a random ID and the expiry. Anyone reading the database or the logs finds no plaintext.
Nothing. Bots fetch links with GET, but reading a secret is a POST behind a button. The secret stays intact for the real recipient.
No. Opening a link or answering a request link works without an account and without software. Only people who create links sign in.
Yes, that is the intended way. ExoSeal runs with Docker Compose using ready-made images, its own database container and your OpenID Connect login. The setup guide and operations manual are in the GitHub repository.
The GNU AGPL-3.0. You may use, inspect and modify it. If you run a modified version as a public service, you must offer the source of your version.
Encryption runs in the browser with established algorithms (AES-GCM, ECDH P-256, PBKDF2). One limit remains: as with any web-based encryption, the server delivers the code that runs. That is why the source is open and the threat model is public. For extremely high stakes we recommend a native tool such as age or GPG.
// QUESTION OPEN?
Your question is not here?
Send us a short note about what you need. We reply within one business day.