Skip to content

How Folio protects your data.

Folio holds access to your store and your customers' order details. This page lists what we do to protect them, and where the limits are.

Last reviewed 2026-11-18

  1. Your storeOrder event
  2. FolioVerify, then read
  3. PDF + emailTo your customer
From store event to delivered invoice

1.

Store credentials are encrypted at rest

Access tokens and API keys for your stores are encrypted before they are stored, using libsodium. The encryption key is kept outside the database, in server configuration.

Folio asks platforms for the access it needs to read orders, customers and products, and, for WooCommerce, to register webhooks.

2.

Every webhook is verified before it is read

Shopify and WooCommerce webhooks are checked against an HMAC-SHA256 signature. Wix webhooks are signed JWTs verified with the app's public key. BigCommerce webhooks are checked against a secret header. Stripe webhooks are verified with their signature. Payloads that fail verification are rejected before parsing.

Events are stored with their event id so a repeated delivery is ignored.

3.

Role-based access

Owner, Admin, Finance and Viewer roles control who can change billing, stores, templates and automations, and who can only read. Give each teammate the least access they need.

4.

Your account's data stays in your account

Every request for stores, orders, invoices and templates is scoped to the signed-in account. One customer's data is not returned to another account.

5.

Protections on the web application

These apply to the site and the app.

  • CSRF protection on actions taken in your account.
  • Rate limiting on public forms and sign-in.
  • HTTPS for the site, the app and all platform connections.

6.

Backups

We back up our database so that data can be restored after a failure.

7.

Card details

Subscription payments are processed by Stripe. Card details are entered with Stripe and are not stored by Folio.

8.

Sub-processors

These companies process data on our behalf.

9.

What you can do

  • Use a unique password.
  • Give teammates the lowest role that works.
  • Remove people who leave.
  • Revoke Folio from your store platform if you stop using it.

10.

Report a problem or ask a question

If you find a security issue, email support@folio.mscat1312.store with the subject "Security".

For data protection terms see the privacy policy and data processing agreement.

Cookie preferences

Read our cookie policy