Skip to content
EN

Security

We cannot read what we never see.

Kriptano is built so that your secret never reaches us in readable form. It is encrypted in your browser, the key travels only in the link, and the encrypted record is deleted as soon as it has been read.

Transparency

What we see and what we do not

We keep only what the service cannot run without – and no longer than necessary.

DataWe see itNote
Secret content and attachmentsNoEncrypted in the browser; the server only has the ciphertext.
Decryption keyNoSits after the # sign in the link, which the browser never sends to the server.
Extra passphraseNoUsed only in the browser to derive the key (PBKDF2).
Encrypted recordYesUntil it is opened, expires or is destroyed – then permanently deleted.
Time, expiry and number of viewsYesNeeded for the link to work and to show the history in your account.
IP addressNoWe store only a one-way hash to limit free usage and prevent abuse.
Account emailYesOnly for registered users – for login, notifications and billing.
Internal secret labelYesVisible only to you; do not put confidential data in it.
Large attachmentsNoEncrypted in chunks in the browser and uploaded directly to object storage; deleted after download or expiry.
Login with Google or MicrosoftYesOnly the account identifier and email – we never see your Google or Microsoft password.
Card detailsNoPayments are processed by Paddle.com; we receive only the plan, amount and invoice number.
Country of accessYesDetermined locally (DB-IP Lite database); only the country code goes into the log.

Cryptography

Standard, proven algorithms

We do not invent our own cryptography. We use the Web Crypto API built into the browser.

EncryptionAES-256-GCM (authenticated encryption), a random 96-bit IV for every secret
Key256 bits from the browser’s cryptographically secure generator (crypto.getRandomValues)
Extra passphrasePBKDF2-SHA256, 600,000 iterations, the key from the link as salt
Opening authorizationA token derived from the key (SHA-256); the server stores only its hash
Secret requestsRSA-OAEP 2048 + AES-256-GCM; the private key stays in your browser
TransportHTTPS only (TLS 1.2+), HSTS
Large attachmentsAES-256-GCM in chunks of 16 to 64 MB, a separate 256-bit key per file, the chunk index in the nonce – chunks cannot be swapped or left out
Two-factor loginTOTP (RFC 6238) with an authenticator app; the secret is encrypted on the server, backup codes stored only as bcrypt hashes

Protections

What happens behind the scenes

One-time deletion

The view counter is updated atomically – two simultaneous openings cannot both get the secret. After the last view the ciphertext is deleted.

Link previews do not burn the secret

Slack, Teams and Outlook open links automatically for previews. Without the key from the link the server does not release the ciphertext, so such a preview “eats” nothing.

Attempt limits

After 5 wrong extra passphrases the secret is permanently destroyed, and attempts per IP address are limited.

Strict page rules

Secret pages send a strict Content-Security-Policy, load no analytics or third-party scripts and are never cached.

Passwordless login

A one-time code and link. After 3 wrong codes, login is locked for 60 minutes; forms are protected against bots.

Automatic clean-up

Expired secrets and requests are deleted automatically, and the log never contains secret content.

Two-factor login

On the Start, Pro and Pro Plus plans, an app code is required in addition to the email code or Google/Microsoft login. Team owners can make it mandatory for all members.

Login with Google and Microsoft

OpenID Connect with PKCE: no code is sent by email, and the account is linked only to a verified address.

Bot protection for forms

Login and the contact form require a small computational task (proof-of-work) that the browser solves in the background, plus a hidden field and daily limits – no CAPTCHA and no third-party cookies.

Geo-blocking and IP allowlist

On Pro Plus, secrets and requests can be opened only from selected countries or IP networks, and the account and API keys can be used only from allowed addresses.

Interrupted uploads resume

If the connection drops, a large attachment upload resumes from the last chunk, and the server checks that all chunks arrived before saving.

Download straight to disk

The recipient decrypts the file as a stream and saves it directly to disk, so even a 10 GB file does not strain the browser’s memory. On iPhone the practical limit is lower.

Honest about limits

What Kriptano cannot prevent

No tool is magic. Here is what you need to watch out for yourself.

  • If someone intercepts the whole link before the recipient, they can open it. That is why you should set an extra passphrase and share it through another channel (text message, call).
  • Once opened, the secret is with the recipient – if their device is infected or they take a screenshot, we cannot prevent it.
  • If the recipient sees a message that the secret does not exist but did not open it, change the password – someone else may have seen it.
  • Kriptano is not a permanent password vault. For long-term storage, use a password manager.

In short

Security in four steps

Kriptano’s security does not depend on whether you trust us. The secret is encrypted with AES-256-GCM (NIST FIPS 197) through the browser’s built-in Web Crypto interface before it ever leaves your computer.

The key is in the part of the link after the # sign, which browsers do not send to the server – that is the zero-knowledge approach. For general guidance on handling secrets we recommend the OWASP Secrets Management Cheat Sheet.

Found a security issue? Write to info@kriptano.com or use the contact form – we check and answer every report. See how it works in practice with a free one-time link.

  1. Kriptano security – enter, AES-256 encryption in the browser, send the link and deleteEnter the secret
  2. Encrypted in the browserEncrypted in the browser
  3. Send the linkSend the link
  4. Opened once, then goneOpened once, then gone

Found a vulnerability?

Please contact us before making it public. We reply within 2 business days and thank everyone who reports a problem responsibly.