Skip to content

Security

Your work stays yours, until you're paid.

Your client sees previews with your name on them, pays in a Stripe window, then gets the final files. Nothing leaves before that.

Before payment

They see the work. They don't leave with it.

Your client approves on previews built by the server. The full-resolution file, the vector or the PSD stay with you until the last step. An AI or PSD file gets no preview at all: the client sees its name, not its content.

Reduced preview

Never the full-resolution file. A recompressed image of 640, 1,200 or 2,000 px on its longest side, depending on the quality you pick. An SVG becomes an image, a PDF its first pages as images.

Your name as watermark

Burned into the image. Diagonal, repeated across the whole surface: a captured mock-up carries your signature. You can turn it off, the preview stays reduced.

Final files

Unlocked at the last step. Until the client has approved or paid, the server refuses to deliver the originals, even from a copied address.

Payments

Your client pays with Stripe. You are the seller.

A payment window your client already knows, a receipt in your name, and the money in your account. Airlock never touches the card or your IBAN.

  • You are the seller

    Payment goes through Stripe Connect, in your account's name: your client sees your name on their statement and gets Stripe's receipt by email.

  • A Stripe payment window

    Bank card, with 3-D Secure when the bank asks for it. The card number is typed into Stripe's form: it never goes through Airlock.

  • Identity checked by Stripe

    To get paid, Stripe verifies your identity. Your details, IBAN and ID document go from your browser straight to Stripe; Airlock only keeps the bank's name and the last 4 digits.

  • Your money, when you want it

    Payments land in your Stripe account. “Transfer my money” sends the available balance to your IBAN, within 1 to 3 business days.

After sending

A link going around? You close it.

A link's rules are checked by the server on every opening, and you can change them after sending: nothing can be bypassed from the browser.

Revocation

Wrong recipient? One click. The link no longer opens, for anyone, from the next request.

Password

A forwarded link stays closed. You send the code separately. It's hashed, and attempts are limited per link and per address.

DeadlinePro

An end date, and that's it. After that day, the link closes on its own. You can extend it at any time.

Client details

You know who opened it. The link can ask for a name and email on opening, once per device. It is a formality, not a lock: the client can type whatever they like.

You know who opened what.

A notification when a new person opens your link, and the date of the last opening on the project. Before chasing, you know whether the work was seen.

ProThe dated detail of every opening and download, in Analytics.

  • Maud Ferrière approved the preview Mariage_042.jpgyesterday · 5:10 pm
  • Maud Ferrière paid the balance 840 €yesterday · 6:42 pm
  • Elio Ferrière downloaded Selection_finale.zipMon · 9:15 am

Your files

Stored in France, encrypted.

Your files go from your browser straight to storage, in Paris, encrypted in transit and at rest.

PARIS
  • Storage in Paris

    At Scaleway, a French company certified ISO 27001.

  • Encryption

    TLS 1.2 minimum in transit, AES-256 at rest. No file has a public address: access goes through expiring addresses.

  • No backup on your behalf

    A deleted project goes to the trash first. A deleted file is erased for good, with no copy: keep your originals on your side.

Your account

Your account, and what we see of it.

Sign in

Google or email, handled by Clerk. Clerk has a SOC 2 Type II audit report. Two-factor authentication isn't offered yet: a Google account with it turned on stands in.

Alerts on suspicious access

Repeated denials alert us. Wrong passwords in a row, another account's file requested: past a threshold, an alert reaches us immediately.

Our access

A file's name, not its content. Our back office doesn't display your files. We only open one at your request, to fix a problem you report.

GDPRDPA, Article 28
FranceFiles in Paris
AES-256At rest
TLS 1.2+In transit
ScalewayISO 27001 certified host
ClerkAuthentication, SOC 2 Type II report

FAQ

Frequently asked questions.

Can my client get my files without paying?

Not through Airlock. Until the final files step is reached, they only get reduced previews, and the server refuses to serve the originals. If you mark a step as paid yourself (transfer received elsewhere), the files unlock.

Does the watermark stop a screenshot?

No. Nothing prevents a screenshot or a photo of the screen. The watermark makes the image hard to reuse, and carries your name.

Does my client's card data go through Airlock?

No. The card is typed into Stripe's form, embedded in the page: Airlock never sees the number or the code. Likewise, your IBAN and identity go from your browser to Stripe.

Who collects the money, and what does Airlock take?

You: the payment is made in your name and lands in your Stripe account. On Free, Airlock keeps a 2.5% fee (€0.40 minimum), none on Pro; Stripe's fees are yours. Details are on the Pricing page.

Does my client need an account?

No. They open your link in their browser. To pay, they only give their email address, which receives the receipt.

Where are my files stored?

In Paris, at Scaleway. The database (Google Firestore), sign-in (Clerk) and payments (Stripe) are with US companies: not all data is therefore in France.

Are my files encrypted?

Yes: TLS 1.2 minimum in transit and AES-256 at rest.

Does Airlock back up my files?

No. Airlock is for delivering, not archiving: a deleted file is permanently erased. Keep your originals on your drive or your own backup.

Is Airlock ISO 27001 certified or SOC 2 audited?

Airlock itself is not. Scaleway, which stores files, is ISO 27001 certified; Clerk, which handles sign-in, has a SOC 2 Type II audit report.

Is Airlock GDPR compliant?

Airlock applies the GDPR and provides a Data Processing Agreement (DPA, Article 28), which is part of the contract. Any new sub-processor is announced by email to every account 30 days in advance.

Will I be notified of a data breach?

Yes, within 48 hours, with the nature of the breach, the data affected and the measures taken.

How do I report a vulnerability?

Write to security@airlck.com. We reply within 48 hours.

Ready to deliver? Create a free account, and move to Pro to stop paying commission.

A security question? Write to us, we answer in writing.

contact@airlck.com