packsSign in

Security

Last updated 17 November 2026. Version 2.

This page explains how we protect your packs and the people who read them. If it doesn't answer your question, email hello@packs.co.

Where your data is stored

Your account, packs, files and reading records are stored in London, in the UK region on Amazon Web Services.

Encryption

  • In transit: every connection to Packs uses HTTPS (TLS), including packs on your own domain.

  • At rest: our database and file storage are encrypted with AES-256.

  • Passwords: account passwords and pack passwords are stored as one-way hashes. Nobody at Packs can read them.

Keeping accounts separate

Row-level security is switched on for every table in our database. Each request is checked against the signed-in account, so one customer can't see or change another customer's packs, files or reading records.

Readers never get direct access to the database. They open a pack through a small set of checked functions, which only return what that pack's settings allow.

Files

Files you add to a pack are kept in private storage. Readers get short-lived links to them, and only after passing any password or email check on the pack. Logos and brand images are stored publicly, because they appear on pack pages and in emails.

Controlling who sees a pack

  • Passwords: available on every plan. After repeated wrong tries, the visitor has to wait 15 minutes before trying again.

  • Email gate and invite-only packs: available on Pro and above. Invite-only packs send readers a one-time code by email before the pack opens.

  • Expiry dates: a pack stops opening after the date you set.

  • Search engines: packs are kept out of search results unless you choose to list one.

Payments

Stripe handles every card payment. Stripe is certified to PCI DSS Level 1. Your card details go straight to Stripe, and Packs never sees or stores your card number.

AI features

When you or your readers use an AI feature, we send the relevant pack content to our AI provider, Anthropic. Under its commercial terms, Anthropic doesn't use this content to train its models. You can switch off "Ask this pack" for any pack.

Integrations

HubSpot, Slack and Google Chat receive data only after you connect them, and you can disconnect them at any time in Account.

Our team's access

Only a small number of Packs staff have admin access. Admin tools check permissions on every request, and we log every change staff make to a customer account.

Backups

Our database is backed up every day. Backups are kept for 7 days.

Suppliers

These companies help us run Packs. Each one handles data for us under a contract that protects it.

  • Stripe: payments and invoices. Certified to PCI DSS Level 1.

  • Supabase: database, file storage and sign-in. Holds a SOC 2 Type II report.

  • Vercel: hosts the website and app. Holds a SOC 2 Type II report.

  • Resend: sends our emails.

  • Anthropic: AI features.

  • HubSpot, Slack and Google Chat: only if you connect them.

Our Privacy policy has more detail, and our Terms include our data processing terms.

Certifications

Packs doesn't hold its own SOC 2 or ISO 27001 certification. We build on suppliers who hold theirs, and we're happy to answer security questionnaires. Email hello@packs.co.

Reporting a security problem

If you think you've found a security problem in Packs, email hello@packs.co. We'll reply within two working days.

If something goes wrong

If a breach affects your information, we'll tell you without undue delay, and tell the Information Commissioner's Office where the law requires.