Security & data governance
Security Built for Multi-Brand Operators.
Every brand's data is isolated from every other business on the platform. Internal access is by a named person, for a named reason, and logged. Your data stays yours, with a clean export anytime. Card payments run through a PCI-DSS-compliant provider. And the detailed documentation your diligence team needs — controls, data handling, subprocessors, and current certification status — is available under NDA.
Diligence Shouldn't Stall on the Software.
When you acquire and roll up brands, the operating system becomes a diligence line item — who can see the data, whether each brand is isolated, whether you actually own it, and whether payments are handled cleanly. Amplify is built so those answers are short, consistent, and documented — the same on the tenth acquisition as the first.
Security Controls in Place Today
| Control area | How Amplify handles it |
|---|---|
| Tenant isolation | Each brand is a separate tenant; its data is walled off from every other business on the platform — competitors included. |
| Internal access | Access is by a named person, for a named reason, and every entry is logged and customer-auditable. Parties with a competing interest are excluded from behind-the-scenes access by policy. |
| Role-based permissions | Franchisor, manager, and staff scopes — people see only what their role allows, across one location or the whole brand. |
| Identity at the point of action | Facial-recognition login ties every session and clock-in to a real, present person — no shared logins, no buddy-punching. |
| Audit trail | Every edit, void, comp, discount, and refund is attributable and immutable — nothing changes without a name attached. |
| Payments | Card data is handled by a PCI-DSS-compliant payment provider, so sensitive card details don't sit inside Amplify. |
| Data ownership & export | Your data is yours. Export it cleanly anytime — we never sell it and never market to your clients. |
Every Action Has a Name on It.
Most platforms can tell you what changed. Amplify tells you who — because identity is captured at login and every change writes to an immutable log you can audit yourself. It's the same architecture that keeps each brand's data isolated and keeps competing interests out of the back office.
The Documentation, Under NDA.
Qualified buyers get the full security package during diligence, not a sales sheet: access-control and data-handling policies, retention and deletion, our subprocessor list, encryption practices, incident response, and current certification status. Ask, and we'll share it under NDA.
We don't publish certification claims we can't stand behind. What's architectural — isolation, attributable access, the immutable audit trail, and a PCI-DSS-compliant payments provider — is in place today and shown in the walkthrough.
Amplify Security: FAQ
Is each brand's data isolated from the others?
Who at Amplify can see our data, and is it logged?
How are card payments secured?
Do you have SOC 2 or other formal certifications?
Bring Your Diligence Team.
We'll Bring the Documentation.
A walkthrough for operators and their diligence team — how isolation, access, audit, and payments actually work, on your portfolio.