Security

What protects the delivery.

Five mechanisms, all of them things you can check: a signed link, a checksum, a licence certificate, gates that run on the delivered zip, and an order page that needs two things to open.

Delivery and licence mechanisms

Signed, time-boxed download links

Time-boxed · fail closed

Pack zips do not live in the site's static folder. The only way to fetch one is /business/download/<pack> with an expiry and an HMAC signature that covers the pack id, its version and the expiry. No signature, a wrong version, or an expired link gets a 403; if the server-side signing key is missing the route refuses to serve at all rather than falling back to a public URL.

Checksums you can run yourself

sha256

Every pack carries checksums.sha256 covering every file inside it, and the delivery manifest repeats the SHA-256 of each pack you bought. The download response also carries the checksum in a header, so a mismatch is visible without opening anything.

A licence certificate with the terms attached

Licence certificate · manifest · receipt

Your order produces a licence certificate: who it is licensed to, the tier, the seats, the packs and versions, the amount, the six licence clauses, and a checksum of the document itself. The delivery manifest and the receipt sit next to it.

Buyer-path gates run on the delivered zip

A1–A7

Before a pack is published, the zip itself is put through seven gates: one clean package, it fills on your machine, the page count is the truth, nothing is missing on the page, the rebrand leaves no old brand colour, the checksums describe the real files, and the terms ship with the pack.

The order page needs two things

Session id + email

Opening an order requires the checkout session id and the email that paid for it. A session id alone shows nothing: the page asks for the email before it shows the packs, the licence or the download links.

A1–A7 in detail

A1 — One clean package

The zip unpacks to exactly one top-level folder named after the skill, with every required member inside — no half-delivered pack.

A2 — It fills on your machine

The README command runs against the delivered zip on a bare python-pptx interpreter, with zero error-level issues: no overflow, no leftover template sentence, no empty title.

A3 — The page count is the truth

The template renders exactly as many pages as the catalogue claims, and a filled deck renders exactly as many pages as your content asked for.

A4 — Nothing is missing on the page

Rendered pages carry no missing-glyph marks and no invisible Chinese characters, and no page fails the fidelity/overflow bench.

A5 — Rebrand leaves no old brand colour

After the one-command rebrand, no colour of the original brand family is left anywhere in the file.

A6 — The checksums describe the real files

checksums.sha256 matches every file actually inside the zip, and nothing inside the zip is missing from the list.

A7 — The terms ship with the pack

A commercial pack must carry LICENSE.md with every promised clause — the page you read is the licence you get.

What we do not claim

  • We do not run your deck for you — the pack runs on your machine, so your content never has to reach us.
  • We do not claim a copy of your files is safe from every conceivable risk; the delivery mechanisms above are the ones that exist, and they are the ones we can show you.
  • The pack zip is signed for a limited window. That window is a delivery convenience, not a licence condition: your licence does not expire when the link does.

Order records are kept for a limited window for accounting and support, then deleted. Your licence terms do not expire with them — what you bought stays licensed.

Next

Tell us what you need to produce.

We send the pack, the licence terms and a sample built from your own material.

Security — signed downloads, licence certificates, buyer-path gates | FXpeek Business