Skip to content
Bloom POS

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.

Security program

How we operate

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.

Security questionnaire

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

Request the security overview →

Report a vulnerability

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

security@bloompos.io →

See Bloom configured for your business

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

We reply within one business day.

  1. 01Pick a time that suits you
  2. 02Tell us how you run service
  3. 03See Bloom set up your way