00

Send a file that deletes itself after reading.

ParaSend · sending files without leaving a copy behind

Your file is locked on your own device before it is sent, and our copy is wiped after its last read. Servers in Germany, under EU law.

For offices that email client documents, contracts and personal data today, and would rather not leave them sitting in a mailbox.

In the web app you send a link that the other person opens when it suits them, to one person or, with Firm, to several people at once. With Extra safe you and the receiver are both online and compare a short code, and the file is handed over live. You can also send with the API or the SDK.

Send a file → See pricing →

Free on the Community plan, forever: 50 transfers a month, 500 MB a file handed over live, 5 MB by one-time link, links that last an hour, and a web app link gone after one read.

Sending needs a free account. Receiving does not: the person you send to opens the link, gets the file, and the copy is wiped after its last read. Keep your own copy, because a file that is gone cannot be fetched again.

01 / Free for everyone

Free for everyone. Paid for organisations.

The Community plan is free, forever. It is not a trial and not a funnel. Businesses pay for the higher limits (longer links, more reads through the API, more devices, a dedicated relay), not to unlock features, and that is what keeps the Community plan free. More reads is not a weaker promise: it is one link a whole team can open, or a counterparty reopening it after a misclick, instead of you sending the file a second time.

Every plan gets the same encryption, the same post-quantum signatures and the same public proof log. Pay for volume, never for security. And pay per organisation, not per user.

The plans and what each one costs are further down this page. Checkout and the full comparison are on the pricing page.

02 / What it does

Encrypted on your device, deleted after its last read

ParaSend is the transfer half of Paramant. It runs on the same servers as ParaSign. Your file is encrypted before it leaves your device: with AES-256-GCM for a one-time link or a send to named recipients, and for Together with ML-KEM-768 plus ECDH P-256 to the receiver's key. So our servers keep no readable file they could hand over or lose.

Locked before it leaves you

Your browser locks the file on your own device. Our servers only ever hold the locked version, never the file itself. With a one-time link they never get the key either. With a send to named recipients the key travels wrapped, and the token that unwraps it passes through the relay once so it can be emailed: that route is therefore not zero-knowledge.

Gone after its last read

Nothing is written to disk. The file sits in server memory and is wiped after the last read the link allows. The web app and the extensions delete the file after the first read on every plan. Through the API a paid link can allow more reads: up to 10 reads on Firm and 100 on Enterprise. The file is also wiped when the link expires, whichever comes first.

No account for receivers

The recipient opens the link, gets the file, and that is the whole flow. No account, nothing to install.

It opens on their device, or nowhere

The file is locked to a key registered on the recipient's device, so it opens there and nowhere else, and a file altered on the way does not open at all. The send screen you use for this is the ParaSend web app.

Lock a file for yourself

No recipient, no account: lock a file into a .prmnt container with a passphrase. The file and the passphrase never leave your browser.

Your own server, if you need one

A larger organisation can run its own instance, on our hardware or on its own, with its own limits. That is the Enterprise plan.

03 / How to begin

Three steps to a file that disappears

Sending needs a Paramant account. Receiving needs nothing at all.

  1. Create a free account. No card, no time limit. On the Community plan a link lasts 1 hour, and the web app deletes the file after the first read.
  2. Open the ParaSend web app and pick your file. It is encrypted in your browser before anything is uploaded. Our servers receive only an unreadable copy, and they keep it in memory only.
  3. Share the link. The recipient opens it and the file is wiped after its last read. On the Community plan the link expires after an hour whether it is opened or not.
04 / Who is behind it

Built in Harderwijk, in the Netherlands

Paramant is a product of Paramantis Solutions B.V. in Harderwijk, the Netherlands. The product is built on choices you can check for yourself: post-quantum signatures, a public transparency log, offline-verifiable documents, and source code you can read.

The Community plan is free and stays free; the business plans pay for the servers and keep it that way. Paramantis Solutions B.V. is the contracting and responsible party.

More about Paramant →

05 / The plans

What each plan gives you

Free for everyone · anyone with a browser
Community
€0
Forever · no card required
  • Encrypted in your browser, key never sent
  • 50 transfers a month
  • 500 MB per file over the live hand-over, on every plan
  • 5 MB per file over a one-time link, on every plan
  • 1 hour link expiry
  • Burn on first read
  • One recipient per send
  • Up to 50 retrievals an hour through the API
  • Up to 5 registered devices for the ParaSend web app
For organisations · the business plans
Firm
€29/mo
excl. btw · charged €35.09/mo incl. 21% btw
Annual €290 excl. · 16.7% off
  • Everything in Community
  • 100 signatures a month on ParaSign, in the same payment
  • 500 transfers a month
  • 24 hour link expiry
  • Up to 10 reads per link through the API
  • Up to 30 recipients per send, each with their own one-time link
  • Up to 500 retrievals an hour through the API
  • Up to 50 registered devices
  • Send history and link management
  • Webhooks on upload and download
  • Email notifications (only the address and the link, never the file)
Enterprise
Custom
Per organisation
  • Everything in Firm
  • 7 day link expiry
  • Up to 100 reads per link through the API
  • No hourly cap on API retrievals
  • Dedicated relay on our infrastructure or yours
  • IEC 62443 / NIS2 / NEN 7510 documentation as input for your own compliance process, not third-party certification
  • Custom DPA terms negotiated in the contract
  • SLA 99.95%, priority incident response

What the hourly figure counts: fetching a transfer back yourself with your own API key, the route the SDKs and scripts use. A recipient who opens the link you sent goes through the download token instead, and that path is not counted against your hour. Past the ceiling the relay answers 429 until the hour rolls over. The number is outbound_per_hour in relay/lib/tiers.js, the same table the transfer, file size and link limits above come from.

Every tier stores transfers in RAM and every tier uses the same cryptography. There is no lesser encryption at lower tiers. Cryptography is not a paywalled feature at Paramant.

Prices shown excl. btw (VAT). Checkout charges incl. 21% btw: Firm €35.09/mo or €350.90/yr. Checkout and the full comparison are on the pricing page.

06 / The proof

Every claim has a place to check it

You should not have to trust us. You should be able to check. Each point below links to where you can.

We never had it

AES-256-GCM with a key your browser generates. The relay only ever holds ciphertext, never the plaintext. With a one-time link it never holds the key either. With a send to named recipients the relay sees the token that unwraps the key once, when it emails it in the invitation, and keeps only a hash of it afterwards. The relay holds the data in RAM until its last read burns it. The relay does see roughly how large it is: a one-time link is not padded to a fixed size. The retention row is on the security page.

The wire format, in full

The ParaSend web app uses ML-KEM-768 plus ECDH P-256 hybrid key exchange. The register lists the webapp on the pre-v1 hybrid wire, signature n/a, migrating to v1; ML-DSA-65 signed receipts are live on the v1 wire in sdk-py 3.0.0 and sdk-js 3.0.0. Read the register on the crypto agility page.

You own your keys

Generated on your device, never sent. We see only the public half. Read our rules.

EU soil, EU law

Hetzner Germany, Bunny DNS (Slovenia). The encrypted files sit only on our servers in the EU. Email still goes through Resend in the United States for now, as our privacy policy sets out; we are moving to a Dutch provider. For a send to named recipients that email carries the link with the token, and the pickup code is emailed too: whoever reads both can open the file. If you do not want that, send a one-time link, which we do not email. The subprocessors are listed there, and rule 5 states the same claim in full on our rules page.

No third-party requests

Your browser talks only to us. No fonts, CDNs, analytics or pixels. Open your browser's developer tools and check.

Quantum-ready by default

FIPS 203/204 today, not “soon”. The algorithm register is on the crypto agility page.

Dedicated relays, on the same rules

Enterprise customers run a dedicated relay on our infrastructure or their own, with limits configured per tenant within its RAM budget. The tiers are on the pricing page.

Source-available code

The relay is source-available. Read it on GitHub and run it yourself.

What the compliance documentation is. Architecture documents, security controls mappings and technical reference materials aligned to IEC 62443, NIS2 and NEN 7510. This is documentation you can use as input for your own compliance process. Paramant does not hold third-party certification for these frameworks.

What burn-on-read costs you. A file is wiped after its last read, or on expiry, whichever comes first. There is no disk storage, so a file that is gone cannot be fetched again. Keep your own copy.

Send a file → See pricing →
07 / Developers

Send from your own code

There is an open SDK in JavaScript and Python and a self-host installer. Read the documentation, or run the relay yourself from GitHub.