B.O.L.T.

A Separate Encrypted Database for Each FFL

B.O.L.T. gives each FFL its own encrypted tenant database for its business records. A&D entries, Form 4473 data, and other tenant records are kept in that FFL's database rather than mixed into one shared table of every customer's records.

What is shared across the platform?

The service still needs a shared platform database for accounts, sign-in, subscriptions, and the mapping from a user to an FFL. That platform metadata is separate from the encrypted tenant databases. Database separation describes where tenant records are stored; it does not mean that no shared platform information exists.

Backups and your copies of records

Tenant backups protect a restorable copy of the database. Portable records exports serve a different purpose: giving a licensee readable copies of selected records. Review the backup documentation for what each download contains, how restores work, and what copies the licensee must maintain.

Separation is one security control. Access rules, encryption keys, backup handling, and correct operation of the service matter as well. B.O.L.T. documents those controls without describing the shared sign-in database as encrypted tenant storage.