Security, built into the platform.

FFL dealers run payments, customer data, distributor credentials and daily operations through FFL Stack. That only works when security is part of the architecture — not a checkbox added later.

Looking for Bound Book, 4473, NICS and checkout requirements? Explore Compliance →

Payment Security

Raw card numbers never touch our servers

Card data is tokenized in the customer's browser before anything reaches FFL Stack. We process tokens, not card numbers, so a full PAN never transits or rests on our infrastructure.

Payment processing is built for firearms retail, and your merchant relationship and rates stay yours. Stored payment credentials are encrypted at rest, and every transaction is recorded against the order it belongs to.

  • Client-side tokenization — card data is never keyed into our forms
  • Raw card numbers never stored, logged or transmitted by FFL Stack
  • Stored payment credentials encrypted with AES-256
Payments
Data Protection

Encrypted in transit, encrypted at rest, scoped per dealer

Every connection to FFL Stack runs over TLS — website, dealer portal, and admin. Sensitive credentials such as distributor accounts and integration tokens are encrypted at rest with AES-256, so a stored secret is never sitting in plaintext.

Every dealer-facing query is scoped to the dealer identified by the authenticated session and request. Customer, order, pricing and operational data stay within that dealer context.

  • TLS everywhere — encryption in transit on every connection
  • AES-256 encryption at rest for distributor and integration credentials
  • Dealer-scoped application queries throughout the platform
Encryption
Backups & Resilience

Encrypted backups, kept locally and offsite

The database is backed up every day to encrypted local and offsite copies. General snapshots roll for 30 days, with monthly snapshots retained for 13 months. Bound Book and 4473 data use a separate encrypted archive designed for long-term record retention.

  • Automated daily database backups
  • 30-day rolling retention plus 13 months of monthly snapshots
  • Separate long-term archive for Bound Book and 4473 records
  • Encrypted offsite replication independent of the production host
Backups
Platform Security

How the software itself is kept secure

Security isn't a launch-day audit — it runs in the build pipeline and in every login.

01

Controlled builds

Production builds install locked dependencies reproducibly and run inside isolated containers. Releases are promoted through health checks so a failed candidate is not switched into live traffic.

02

Access control

Role-based permissions limit what staff can reach in the dealer and admin portals. Passwords are hashed, sessions use secure cookies, and repeated failed sign-ins trigger account lockout.

03

Email safeguards

Built-in marketing sends enforce unsubscribe handling and the required physical-address footer, supporting each dealer's CAN-SPAM workflow without relying on a pasted footer.

Questions about security?

Ask them during your walkthrough. If you're a security researcher and believe you've found a vulnerability, we want to hear from you.

Request Access

Report security issues to security@fflstack.com