Privacy policy

This policy explains what information Bloom POS (operated by ARV systems INC, “Bloom”, “we”) collects through the bloompos.io website, the Bloom POS web portal at app.bloompos.io, and the Bloom POS mobile apps for iPhone, iPad and Android (together, the “Service”), and how we use and protect it.

In short: restaurants use Bloom POS to run their business. We process their staff, order and customer information only to provide the Service. We don't sell personal information, we don't use it for advertising, and the apps contain no third-party tracking or ads.

Who is responsible for the data

Each restaurant (our “customer”) decides what it records in Bloom POS about its staff and its own guests, and is the controller of that information. Bloom processes it on the restaurant's behalf. If you are a guest of a restaurant that uses Bloom POS, please contact that restaurant first about your information; we will help them respond. For information you send us directly (for example a demo request), Bloom is the controller.

Information the Service collects

• Staff accounts: name, phone number, role and permissions, and a sign-in PIN that is stored only as a salted hash. We also record sign-in times, the device type and IP address of sign-ins, and an audit log of administrative actions.
• Restaurant devices: shared tablets and phones sign in with the restaurant's device code. We store which role a device signed in as and when.
• Orders and payments: items, amounts, order type, table, notes and payment status. Card payments are processed by the restaurant's payment provider (such as Square or Clover); Bloom never receives or stores full card numbers.
• Restaurant guests: when a restaurant enters them, a guest's name, phone number, email address, delivery address, order history and store-credit (wallet) balance.
• Business settings: menu, branches, inventory, suppliers, and credentials for integrations the restaurant connects (for example delivery or payment providers). Integration secrets are encrypted at rest.
• Website forms: name, work email, phone, business name, business type and message when you request a demo.
• Diagnostics: basic server logs (time, request path, IP address, error details) used to keep the Service secure and reliable.

The mobile apps do not collect your location, contacts, photos, health data or advertising identifiers, and do not track you across other companies' apps or websites. The camera is used only when you choose to take a photo (for example a menu item image).

How we use information

• To provide the Service: taking and routing orders, kitchen and delivery workflows, reports, receipts and customer records.
• To secure the Service: authenticating staff and devices, enforcing roles, rate-limiting sign-in attempts and keeping audit logs.
• To send messages the restaurant asks us to send, such as order-tracking links or store-credit reminders by SMS.
• To respond to support and demo requests.

We do not sell or rent personal information and do not use it to build advertising profiles.

Service providers we use

We share information only with providers that help us run the Service, under contracts that limit their use of it:

• Google Cloud (hosting, in the United States) and MongoDB Atlas (database).
• Payment and delivery providers the restaurant chooses to connect (for example Square, Clover, DoorDash, Uber Eats).
• SMS and mapping providers used for order messages, address validation and delivery routing.

We may also disclose information if required by law or to protect the rights and safety of our users and the Service.

Security

• All traffic is encrypted in transit with HTTPS (TLS).
• Every request to the portal and apps requires a signed, expiring session; access is limited by role and branch.
• PINs and device codes are stored only as hashes; integration secrets are encrypted at rest.
• Sessions can be revoked: signing out, changing a device code, or disabling an account ends affected sessions.

Retention

We keep a restaurant's data for as long as it has an active account, then delete it within 90 days of the account closing unless the law requires us to keep it longer. Restaurants can delete individual staff accounts and guest records at any time.

Your choices and rights

You can ask to access, correct or delete your information. Staff members can ask their restaurant's administrator, who can edit or delete their account in Users. You can also email us at get@bloompos.ioand we will respond within 30 days. Depending on where you live (for example California or the EU/UK), you may have additional rights, which we will honor.

Children

The Service is a business tool and is not directed to children under 13. We do not knowingly collect information from children.

Changes

If we change this policy, we will update the date above and, for material changes, notify restaurant administrators.

Contact

ARV systems INC (Bloom POS), Bloomington, Illinois, USA · get@bloompos.io