Security

Last updated 2026-10-27

Pastefront holds store owners' accounts and stores, and the names and addresses of the people who buy from them. This page says how that's kept safe, what isn't done yet, and how to tell us about a problem. Pastefront is built by a solo developer, so it's written by the person who wrote the code.

Your account

  • Sign in with email and password, a link sent by email, Google, or a code texted to a US phone.
  • Sign-in attempts are limited per email, phone and network address, so passwords can't be guessed at speed.
  • You stay signed in for up to 30 days only if you tick “Keep me signed in”; otherwise until you close the browser.
  • Team members sign in with their own accounts. Only the account owner invites them, and they lose access the moment the plan stops including team seats.

Your stores and your buyers

  • Every table in the database has row-level security: an owner can read only their own stores and orders, and a team member only their owner's, while the plan includes seats. Private columns, such as supplier costs and Stripe ids, can't be read from a browser at all.
  • A buyer's private order link can't be read by anyone signed in, the store's owner and team included. Ad pixels never load on pages that carry one.
  • Keys an owner gives Pastefront to use later (Printify, Klaviyo, Meta, Shopify) are encrypted with AES-256-GCM before they're stored, and only Pastefront's servers can open them.
  • An automated test lists every permission the database gives browsers. A change that grants anything new fails until it's added on purpose.

Payments

  • Card details go straight to Stripe. Pastefront never sees or stores a card number.
  • Each store takes payments in its owner's own Stripe account, and payouts go from there to the owner's bank.
  • Every message from Stripe is checked against its signature and recorded once, so a forged or repeated one is ignored.

Store pages

  • Every store is served over HTTPS.
  • Store pages carry a strict content security policy: scripts load only from the store itself and the ad pixels its owner turned on.
  • Checkout, sign-up and review forms check where they were sent from and are limited per network address.
  • Visitors who send Global Privacy Control, or use the store's “Do not sell or share” link, get no ad pixels.

AI

The AI models that write and edit stores receive the store's text, product listings and the owner's instructions, never buyer details, and they change a store only when its owner asks. How Pastefront uses AI has the rest.

Not done yet

  • Two-step sign-in (a second code at sign-in) isn't available yet.
  • Pastefront hasn't had an outside security audit or a certification such as SOC 2.

Reporting a security problem

If you find a way to see or change something you shouldn't, write to hello@pastefront.com with “Security” in the subject: what you found, and the steps to see it. Please don't look at other people's data beyond what shows the problem, and give us time to fix it before telling anyone else.

To report a store rather than a bug in Pastefront, use the report form. Who handles data for Pastefront is on the subprocessors page.