Read out of the product, not written about it
What is actually done, in plain terms — and at the end, what this page does not claim.
Your buyer pays through a payment processor. Card details are entered on their page, not ours.
A buyer is redirected to Stripe or PayPal to pay and comes back to us with a reference. There is no card form on any Unlockable page, so there is no card number for us to store, log or lose. It is also why we do not claim to be PCI DSS certified: we never handle the data that certification covers.
Access is granted by a server function that retrieves the payment from the processor and checks it is genuinely paid before returning the file. A buyer cannot reach a download by editing a URL or replaying a request — the check runs on the server, against the processor, every time.
The privacy & security fee appears as its own line on the checkout, above the total. A buyer sees what they are paying and why before they pay it.
Money only moves to a person we have verified.
ID verification runs through Veriff rather than through us, so documents go to a company whose entire job is checking them, and we receive a decision rather than a copy of your passport.
After the settlement period, a payout request is reviewed before the money is released. That is slower than an automatic transfer, and it is the reason a compromised account cannot empty itself in a minute.
Earnings settle five working days after a sale. That window is what makes the 30-day money-back guarantee workable: a refund can be honoured from money that has not been paid out yet.
Uploaded content is private by default and delivered deliberately.
Files live under your own account path and are readable only by you. They are not indexed, not browsable, and not reachable by guessing an address.
The link a buyer receives is produced by the server after the payment is confirmed. Before that point there is nothing to find.
Cap a link by date, by number of views or by number of unlocks. When the cap is reached the link stops working, whoever is holding it.
The browser is given as little as possible.
Wallets, payments, payouts, identity records, disputes and settings are reachable only from our servers, not from a signed-in browser session. A creator’s browser can change exactly one thing directly — their own profile photo. Everything else is refused by the database rules themselves rather than by application code that could have a bug.
Staff access requires a specific administrative claim on the account, checked by the database and storage rules. There is no shared master password, and no route that grants access by being on the right network.
Every upload is scanned on arrival and scored across nudity, violence, hate speech, brand risk and illegal content, with anything flagged going to a person.
Three layers, because they fail in different ways.
Seven days of history, so a bad write, a botched migration or an accidental delete can be read back as of a chosen moment rather than guessed at.
A managed backup every day with a fourteen-day retention window, restorable as a discrete snapshot.
A daily export into separate storage, kept for ninety days. The first two layers live inside the same account as the database, which makes them excellent at “something wrote the wrong thing” and useless at “the account is gone”. The export is the only artefact that could be handed to somebody else.
The marketing site is static, which removes a whole category of risk.
The site tells your browser which origins may supply its script, images and data connections, and forbids plugins and framing outright. Script files can only be loaded from this site, and the only outside connection the page can make is to the API that shows live fee figures. Pages cannot be embedded in another site.
Content-type sniffing is disabled, and referrers are trimmed to the origin when you follow a link away.
There is no application server behind these pages, no database connection and no login. The pages are files.
The part most security pages leave out
The sale is yours. We run the payment rail and pay you; sales tax and VAT are your responsibility. A platform that handles them for you is doing something real, and charging for it.
Your balance is a record of what we owe you, not a deposit account, and it is not covered by a deposit guarantee scheme.
Uploads are screened and payouts are reviewed by people, and neither is the same as guaranteeing nothing improper ever gets through. What we will not do is describe a filter as a guarantee.
Card data never reaches us, so we have not been certified as handling it. A platform showing a compliance badge it has not earned is telling you more about its marketing than its security.
Found something wrong here, or a claim you think is overstated? Tell us and we will either fix the product or fix the page.
Identity verification and a bank account are all you need to get paid. Nothing to pay until something sells.