Security & trust

Your data, your staff, your rules

Bloom is built with control and accountability in mind — who can see what, what changed, and where payments are processed.

In the product

Controls you can use today

Role-based access
Admin, manager and kitchen roles see only what they need. Staff sign in on personal phones with a role and PIN.
Audit log
Changes are recorded so you can see who did what, and when.
Branch isolation
Each location keeps its own menu, orders, staff and payments.
Established processors
In-person card payments run through Square and Clover.
Customer privacy
Phone numbers and addresses stay masked on screen. Admins reveal one only when needed, and every reveal is logged.
Device codes
Shared devices sign in with your restaurant's codes. Change a code and every device is signed out.
Locked-down kiosk
The self-order kiosk stays pinned to ordering, and guests can't change prices or mark orders paid.
Staff time records
Clock-ins and hours are recorded per person, so timesheets match who actually worked.

Security program

Our security practices, stated plainly. We'll never claim a certification we don't hold.

Hosting

PLACEHOLDER — where the platform and data are hosted (for example, Google Cloud region).

Encryption

PLACEHOLDER — confirm encryption in transit (HTTPS/TLS) and at rest.

Backups & recovery

PLACEHOLDER — backup frequency and recovery process.

Payment data

PLACEHOLDER — confirm card data is handled by the processor and never stored by Bloom.

Compliance

PLACEHOLDER — current status (for example, PCI scope via processors; SOC 2 plans). State only what's true.

Evaluating Bloom for a group or franchise? Ask for our security overview and we'll answer your questionnaire.

Found a security issue? Email us and we'll respond promptly. Please don't access data that isn't yours.

A 30-minute walkthrough with your menu, your floor and your workflow. No obligation.

We reply within one business day.