Send files, agree deals and get paid, with nobody in the middle

1. 01

   Your wallet is the account

   There is no email field, no password and no verification step, because there is no profile for them to belong to. You sign a message with a wallet you already have and that address is who you are. Nothing about you is collected, so nothing about you can be sold, leaked in a breach, or handed over on request.

2. 02

   The data goes browser to browser

   A file transfer or an OTC room is a live connection between two tabs — WebRTC, the same technology behind video calls, encrypted end to end by the standard itself. The bytes go from one browser to the other. They are not uploaded, mirrored, cached or queued, and there is no copy on a disk of ours because the path never passes through one.

3. 03

   The server only introduces you

   Two browsers cannot find each other unaided, so a small server passes the introduction — the network addresses each needs to reach the other. Those messages are deleted the instant the other side reads them, and they never contain the data itself. When the two tabs have shaken hands, the server has nothing further to do with the transfer and could not observe it if it wanted to.

4. 04

   Payments never touch us at all

   A payment link carries the amount and the recipient in the part of the URL after the # — the one part a browser never sends to a server. The payer's wallet transfers to the merchant's address in a single transaction. There is no account of ours in the path, which is also why the fee is zero: taking a cut requires being somewhere in the middle, and we are not.

The honest cost of all this: both people have to be online at once for a file or a room, because there is no stored copy to fall back on. That is not a limitation we plan to remove. It is the same fact as “nothing is stored”, seen from the other side.

Will you ever ask for my seed phrase or private key?

No. Not now, not on any page, not by email, not in a support chat. There is no field on any of these sites that will accept one, and if you ever see something that looks like FastLock asking for it, you are not looking at FastLock. Signing in asks your wallet to sign a text message, which proves you hold an address and cannot move a single coin. Read what your wallet shows you before you approve anything, here or anywhere else.

What can you do with my wallet once I connect it?

See the address, and nothing else. Connecting is a read: your wallet tells the page which address you are using, and the page uses it to look up your plan or to name you in a room. Every action that moves value — a payment, a subscription — is a separate transaction your wallet describes to you in full and refuses to send unless you approve it. Nothing on this project has permission to spend, and there is no approve step anywhere that would grant one.

Can you read my files or my messages?

No, and not by policy — by route. The data goes directly from one browser to the other over an encrypted WebRTC connection and never passes through a server of ours. There is no point in the path where an unencrypted copy exists for anybody to read, which is a stronger statement than “we choose not to look” and a much easier one to keep.

What do you actually store?

For a transfer: a size, an encrypted filename and a short-lived token, deleted when the transfer ends or the sending tab closes. For an account: a wallet address, a plan and an expiry date. For a payment link: nothing at all — it lives in the link. There is no file storage in this project, no message archive and no log of who sent what to whom, because none of that ever reaches a place where it could be written down.

It is free for files up to 100 GB. What is the catch?

There is no catch, and the reason is unromantic: a transfer between two browsers costs us nothing per gigabyte, so pricing by size would be charging for something we do not pay for. What the paid plans sell is what genuinely costs money — a database row for a short link, relay bandwidth when two networks cannot reach each other directly, hosting for a logo. The catch, if you want one, is that both people have to be online at the same time.

Why should I trust this page at all?

Ideally you should not have to, and the design tries to earn that. The payment site is a static export with no server logic that could behave differently for you than for anyone else. Every fact it shows a payer — the recipient, the amount, the token contract — is repeated independently by their own wallet in the signing dialog. If a page and a wallet ever disagree, believe the wallet and do not sign. That rule is worth more than anything we could tell you about ourselves.

What happens to my links if FastLock disappears?

A payment link keeps working as an invoice, because it always was the invoice: the address and the amount are inside it, and anyone holding one can read those two facts and pay them by hand from any wallet on earth. File transfers and rooms are live sessions, so they simply stop — there is nothing held hostage, because there is nothing held. Not depending on our continued existence is the only durable form of trust a tool like this can offer.

Is this anonymous from everybody, or just from you?

From us. Be clear-eyed about the rest: blockchains are public ledgers, so a payment between two addresses is visible to the world for ever, and your internet provider can see that you connected to this site. What FastLock removes is the middleman who would otherwise hold your files, know your customers and be able to hand a list of both to whoever asks. It is not a mixer, it does not hide anything on-chain, and anybody telling you otherwise about any tool is selling something.

Still deciding? Open send.fastlock.pro, otc.fastlock.pro or pay.fastlock.pro and look at it with the network tab open. Every claim on this page is one you can watch not happen.