The short version
We collect only what we need to run Honeybee. We don’t sell personal information. A restaurant’s guest, order and payment records belong to that restaurant, not to us, and full card numbers stay with PaidYET, never with Honeybee.
Overview
Honeybee POS (“Honeybee,” “we,” “us” or “our”) provides point-of-sale software for restaurants: the order screen, kitchen display, floor plan, waitlist and reservations, online menu and ordering pages, payments, tips and reports. This includes the terminal and API at app.honeybeepos.com, the guest pages we host for restaurants at /p/… addresses, and the honeybeepos.com website and demo (together, the “Service”).
This policy explains what information we collect, how we use it and the choices you have. By using the Service, you agree to the collection and use of information described here. If you don’t agree, please don’t use the Service.
Who this policy covers
Honeybee serves three groups of people:
- Restaurants and their staff, who hold accounts to run a restaurant: owners, admins and managers who sign in to the back office, and floor and kitchen staff who use a PIN on a restaurant’s terminals.
- Guests, who order and pay at a restaurant that uses Honeybee, or who view its menu, join its waitlist or request a reservation through its guest pages.
- Visitors to honeybeepos.com, including people who try the demo or email us.
For a restaurant’s own records (its guests, orders, checks, tips and payments), the restaurant is the controller and Honeybee is its processor (a “service provider” under US state privacy laws): we handle that data on the restaurant’s behalf and under its instructions. For restaurant account data, visitors to honeybeepos.com and the way the Service itself runs, Honeybee is responsible for the data.
Information we collect
We collect information you give us directly, information created when you use the Service, and limited technical data from your device or browser.
Restaurant account information
- Names and email addresses of owners, admins and managers, and the logins they invite
- Restaurant and location details such as name, address, phone number, time zone, tax settings, rounding and receipt text
- Payment settings for each location, including the PaidYET pay-page address and API key used to take cards (the key is stored encrypted)
- Messages you send us, including support questions and demo requests
Staff and terminals
- Staff names, roles and permissions, and PINs (stored only as a one-way hash, never in readable form)
- Clock-in and clock-out times
- Terminals paired to a location, and which terminal and staff member took each payment
- An activity log of sensitive actions such as voids, discounts, settings changes and failed PIN attempts, with the IP address they came from
Menus, orders and checks
- Menus, items, modifiers, prices, tax classes, kitchen stations, tables and order types
- Checks and the items on them, with the price and tax rate at the time they were rung in, courses, seats, voids, discounts and kitchen ticket times
Guest information held for the restaurant
- Waitlist entries and reservations: name, party size, phone number, email address (if given), date and time, and any notes the guest or host adds
- A party name or phone number a restaurant attaches to a check
- What a guest ordered and how they paid
Notes are free text. Guests and staff should avoid putting sensitive details in them beyond what the restaurant needs, such as an allergy to plan a meal around.
Payment and tip records
- One record per tender: method (card, cash or other), amount, tax, tip, any cash discount, the time, and the terminal and staff member
- For card payments, the PaidYET transaction ID and the authorization result PaidYET returns, such as an approval code, card brand and last four digits (see Payments)
Usage and technical data
- Server logs, including IP address, browser type, the requests made and timestamps
- Device information needed to pair and run a terminal
How we use it
We use the information we collect to provide, maintain and improve the Service. Specifically, we use it to:
- Create and secure accounts, sign people in and check staff PINs
- Run the order screen, kitchen display, floor plan, waitlist, reservations and guest pages
- Price checks, apply tax and any cash discount, split checks and record tenders and tips
- Send card payments to PaidYET for authorization
- Produce a restaurant’s reports, such as sales, covers, tips by server, tax by class and close-out
- Send service emails such as sign-in codes, staff invitations and ownership-transfer offers
- Answer support and demo requests
- Detect and prevent fraud, abuse and misuse of the Service, and keep it running and backed up
- Meet our legal, tax and regulatory obligations
We don’t sell personal information, and we don’t use guest data to advertise to guests or to build profiles of them.
Your restaurant’s data
When a restaurant uses Honeybee, the restaurant owns the guest, order, tip and payment records it keeps in the Service. We process that data only to provide the Service to that restaurant and under its instructions. We don’t combine one restaurant’s guest data with another’s.
Each restaurant’s records are kept separate from every other restaurant’s, and the database itself refuses to return one restaurant’s rows to another. Inside a restaurant, access is controlled by the roles and permissions the restaurant sets.
Restaurants are responsible for having the right to collect the guest information they enter, for telling their guests how they use it, and for answering privacy requests guests make to them.
If you’re a guest and want your information accessed, corrected or deleted, contact the restaurant first. You can also contact us, and we’ll pass your request to the restaurant and help where we can.
Email and receipts
Honeybee sends service emails that are part of how the Service works: sign-in codes, invitations to join a restaurant’s account, and offers to transfer ownership of an account. These go only to the people the messages are about.
Receipts belong to the restaurant. A restaurant prints or shows receipts with its own name and receipt text. Honeybee doesn’t email or text receipts to guests today. If we add that, a receipt will go only to the address the guest gives for it, and we’ll update this policy first.
We don’t send marketing email or text messages to guests, and we don’t give guest contact details to anyone for marketing. Phone numbers and email addresses on a waitlist entry or reservation are there so the restaurant can reach the guest about that visit.
Payments
Card and bank (ACH) payments in Honeybee run only through our payment partner, PaidYET. Card numbers go to PaidYET for authorization at the terminal or on PaidYET’s payment page. Honeybee never receives or stores full card numbers or bank account numbers; PaidYET stores and protects them.
We keep limited payment details, such as the amount, tip, date, PaidYET transaction ID, approval code, card brand and last four digits, so restaurants can reconcile deposits, void payments, report tips and close out the day. PaidYET handles payment information under its own privacy policy as well as this one.
Cash payments are recorded in Honeybee as a tender on the check. No payment details beyond the amount are collected for them.
Data retention
We keep account and restaurant data while an account is active or as needed to provide the Service. Checks and payments are kept so a restaurant’s past reports stay accurate.
If a restaurant closes its account, we delete or anonymize its personal information within 90 days, except where the law requires us to keep it longer. Transaction records, for example, are kept for the period tax and payment rules require. Sign-in codes expire after 15 minutes and can be used only once.
We make daily database backups and keep them only for a limited period before they are deleted, so deleted data can remain in a backup until that backup ages out. Restaurants can ask us for a copy of their records before closing an account.
Security
We protect data with encryption in transit (TLS), separation of each restaurant’s records enforced by the database, role-based permissions, staff PINs stored only as hashes, single-use sign-in codes that are hashed at rest and lock after repeated wrong guesses, limits on PIN attempts, an activity log of sensitive actions, encrypted storage of each restaurant’s payment API key, and daily backups. Full card numbers never touch our systems.
No method of sending or storing data is completely secure, so we can’t guarantee absolute security. If you think your account or a terminal has been compromised, contact us right away at support@honeybeepos.com. Restaurants should revoke a lost or stolen terminal from their settings.
Your US state privacy rights
Residents of California and of other states with comprehensive privacy laws, such as Colorado, Connecticut, Virginia, Utah, Texas and Oregon, have rights over their personal information. Depending on where you live, you may have the right to:
- Know what personal information we collect, use and disclose, and access it
- Correct information that’s inaccurate
- Delete your personal information, subject to legal exceptions
- Get a copy of your data in a portable format
- Opt out of the sale or sharing of personal information, targeted advertising and profiling
- Not be treated differently for using any of these rights
We don’t sell personal information or share it for cross-context behavioral advertising, we don’t use it for targeted advertising or profiling, and we don’t use sensitive personal information to infer characteristics about anyone. In the last 12 months, the categories we collected are the ones listed in Information we collect: identifiers and contact details, commercial information such as orders and payments, staff role information, and internet activity in our server logs. We disclose them only for the business purposes in Sharing and disclosure.
To use any of these rights, email support@honeybeepos.com. You may use an authorized agent. We’ll respond within 45 days and may need to confirm your identity first. If we decline your request, you can appeal by replying to our answer, and we’ll respond to the appeal within the time your state’s law requires. If your request is about data a restaurant controls, we’ll refer you to that restaurant or act on its instructions.
Children
Honeybee is built for restaurants and the adults who run them. It isn’t directed to children under 13, and we don’t knowingly collect personal information from them. Accounts and staff logins are for people old enough to work at the restaurant under applicable law.
A guest of any age may eat at a restaurant that uses Honeybee, but the guest pages are not meant for children to use on their own. If you believe a child’s information was entered without a parent’s or guardian’s consent, contact us and we’ll work with the restaurant to delete it.
Changes to this policy
We may update this policy from time to time. If we make material changes, we’ll let account holders know by email or in the Service at least 14 days before they take effect, and we’ll update the date at the top of this page. Continuing to use the Service after that means you accept the updated policy.
Contact us
Questions, concerns or requests about this policy or how we handle data:
Email: support@honeybeepos.com
Web: honeybeepos.com
We aim to respond to privacy questions within five business days.
