Your mail holds some of your most sensitive information, so we build Kloff with security in every layer. This page explains how we protect your account, your data and your domain, what you can do to stay safe, and how to report a vulnerability if you find one.
Security
Last updated November 17, 2026
1Account protection
- Passwords: stored only as a one-way hash. New passwords are checked against known data breaches using Have I Been Pwned; only the first five characters of a hash of the password leave Kloff, never the password itself. New passwords built from predictable patterns, such as keyboard walks, sequences, common passwords, or your own name or username, are also rejected.
- Two-factor authentication: add an authenticator app, with single-use backup codes in case you lose your device. Once it's on, mail and workspace data stay locked until the second step is complete. This is enforced in the database itself, not just in the app.
- Passkeys: sign in with your fingerprint, face or device PIN. Only passkeys that verify you this way are accepted, and a passkey sign-in counts as two-factor authentication.
- Recovery codes: every account gets 10 single-use recovery codes at sign-up, stored only as hashes, so you can get back in without an email address. Resetting your password signs out all of your sessions, and two-factor authentication still applies afterwards.
- Sessions: Account settings shows every device signed in to your account, with its browser, device, rough location and last activity. You can sign out any other device from there.
- Sign-in providers: Google, Microsoft and GitHub can only be connected from Account settings while you are signed in, so someone with the same email address elsewhere can't attach their sign-in to your account.
- Bot and abuse protection: sign-up, password and contact forms are protected by Cloudflare Turnstile, and sign-in, account and API requests are rate limited to slow down password guessing and automated abuse.
2Data protection
- Encryption in transit: Kloff is served only over HTTPS. Mail between Kloff and other mail servers is encrypted with TLS whenever the other server supports it, which almost all major providers do.
- Encryption at rest: the database, file storage and email infrastructure we use encrypt stored data, including messages, attachments and backups.
- Access enforced in the database: who can see which workspace, domain and mailbox is checked by row-level security rules in the database on every request. A bug in one screen can't show you someone else's mail.
- Short-lived file links: attachments and images are served through signed links that expire after minutes, not public URLs, and they are never saved in your drafts or sent mail.
- Least privilege: each part of Kloff gets only the access it needs. For example, the sign-in system uses a database role that can reach account tables and nothing else.
Mail is not end-to-end encrypted: like any webmail, Kloff has to process your messages to show, search and send them. Kloff staff do not read your mail, except where you ask us to for support, where a message is reported to us for review, where it is needed to investigate abuse or a security issue, or where the law requires it. The Privacy Policy explains what we collect and how long we keep it.
3Email security
Your domain
Every domain gets its own 2048-bit DKIM key, so the mail you send is signed and receiving servers can check it really came from your domain. The private key is handed straight to our sending infrastructure when the domain is added and is never stored by Kloff. A domain can only send once its DNS records are verified, which proves you control it.
Reading mail safely
- Cleaned messages: every message is sanitized before it's shown. Scripts, forms and embedded frames are removed, so a message can't run code in your inbox. Designed emails keep their layout but render in a sandboxed frame of their own, so their styling can't change or cover the rest of Kloff.
- Private image loading: images from other servers load through Kloff's servers, so senders never see your IP address, location or browser. Tracking pixels (tiny or hidden images, and known open-tracking addresses) are never loaded. Senders can still tell that other images in a message were loaded; to prevent that, turn off Load images in emails automatically in your account settings and choose per message. Images in spam, from blocked senders or with infected attachments always wait for you to choose.
- Malware scanning: attachments are scanned for malware. Files can only be downloaded, previewed or sent once the scan comes back clean, and infected files stay blocked.
- Spam and blocking: incoming mail is checked for spam signals and filed separately. You can block any sender, and report a message or attachment as spam, phishing or malware for us to review.
Protecting deliverability
Every workspace sends through shared infrastructure, so we protect it for everyone. Addresses that bounce permanently or mark mail as spam are suppressed automatically, sending volume has hourly and daily limits, and mailboxes or workspaces with too many bounces or complaints are slowed down or paused. Mail from Kloff itself, such as account notices, comes only from a dedicated sender that no user can imitate inside Kloff.
4Infrastructure
Kloff runs on established providers rather than our own servers: Amazon Web Services for receiving and sending mail, Cloudflare for file storage and bot protection, Supabase for the database, and Stripe for payments. Card details go straight to Stripe; Kloff never sees or stores full card numbers.
Errors are reported to us automatically so we can fix problems quickly, and product analytics never include mail content or email addresses. The full list of providers and what each one does is in the Privacy Policy.
5Keeping your account safe
Security works best as a team effort. A few steps make the biggest difference:
- Use a strong password you don't use anywhere else, ideally from a password manager.
- Turn on two-factor authentication or add a passkey.
- Keep your recovery codes somewhere safe and offline. Without an email address, they are your way back in.
- Review your active sessions now and then, and sign out devices you don't recognize.
- In a workspace, give admin access only to people who need it, and remove mailbox access when someone leaves.
- Be wary of messages asking for your password or codes. Kloff will never ask for them.
6Reporting a vulnerability
If you believe you've found a security issue in Kloff, please tell us privately so we can fix it before it's disclosed. Email contact@kloff.app with "Security" in the subject, or use the contact form with the Security issue topic.
What to include
- What is affected and what an attacker could do with it.
- Steps to reproduce it, or a proof of concept.
- Any accounts, workspaces or URLs involved.
- How you'd like to be credited, if at all.
Testing guidelines
- Test only against accounts and workspaces you own, or that you have permission to test.
- Don't access, change or delete other people's data. If you come across it, stop and tell us.
- Don't send mail to addresses you don't control, and don't use Kloff to send spam.
- No denial-of-service attacks, heavy automated scanning, social engineering of our team or users, or physical attacks.
- Give us reasonable time to fix the issue before sharing it publicly.
What you can expect from us
We'll confirm we received your report, keep you updated as we investigate, and let you know when it's fixed. With your permission, we're happy to credit you. We won't pursue or support legal action against anyone who researches and reports in good faith and follows these guidelines. Kloff doesn't run a paid bug bounty at the moment.
Reports usually out of scope: findings from automated scanners without a demonstrated impact, missing security headers or best practices with no practical exploit, self-XSS, and rate limits on actions that don't expose data.
7Contact
Questions about security that aren't a vulnerability report? Email contact@kloff.app or use our contact form. If you think your account has been compromised, change your password and sign out your other sessions from Account settings first, then let us know. Our machine-readable contact details are at /.well-known/security.txt.