Preview terms

Table Buddy runs a restaurant’s point of sale, kitchen display, stock, money, staff and reports in one system. It is operated by Workflow Corporation. While it is in preview, every module is available to every restaurant and the service is free: there is no checkout, and nothing in it asks for card details.

The preview is a working product that is still developing. Features may be added, changed or removed as it does, and screens may look different from one visit to the next.

Each person signs in with their own login. Keep your password to yourself: voids, refunds, discounts, drawer counts and other consequential actions are recorded against the login that took them, in the restaurant’s activity log.

A login is separate from the restaurants it belongs to. Leaving a restaurant, or being removed from one, ends your access to it and keeps your login; deleting a restaurant keeps the logins of the people who worked in it.

A platform administrator at Workflow Corporation can suspend a login, sign it out of every device, or send it a one-time link to choose a new password.

Each restaurant decides who can see and change its records, through the roles it gives its staff. Owners and admins hold every permission; everyone else holds what their role grants.

• Every report downloads as CSV and prints from the browser, built from the same figures as the screen.
• The restaurant’s owner can delete it from Settings, with all of its records.
• Keep your own copies of anything you are required to retain — tax records, for example.

Table Buddy records payments; it does not take them. Cards are charged by your own card terminal or payment gateway, and Table Buddy does not move money through a bank.

Its reports are built from what is recorded in it. While it is in preview, check its figures against your own — your cash count, your bank statement, your card payouts — before you rely on them for tax returns or payroll.

A restaurant can email its guests through Table Buddy once Workflow Corporation switches that on for it. A restaurant that emails its guests is the sender, and responsible for having the right to email them: it chooses who is emailed, and its name and its own verified domain are on every message.

• Every message carries the restaurant’s postal address and a link that unsubscribes the guest at once.
• Nobody who unsubscribes, whose address bounces or who marks a message as spam is emailed by that restaurant again, unless they confirm from their own inbox that they want its email after all.

Anyone with access to a restaurant’s reports can have its daily closing emailed to themselves each morning. Each person turns it on for themselves, and every such email has a link that stops it.

Table Buddy runs on Google Cloud, in the us-east4 region in the United States. Its database is backed up every day. The privacy notice says what is stored and the controls you have over it.

An API key acts for the person who created it, with only the scopes they chose, and stops working if their access ends. Keep keys on your server, give each one only the scopes its job needs, and revoke the ones you no longer use.

Send an Idempotency-Key with each write and reuse it only to retry that write: a retry within 24 hours gets the first answer back instead of acting again. The API reference has the details.

The API reference’s Versioning page says what may change within v1 and what will not.

These terms may change as the preview develops. The date at the top of this page shows when they last changed.

Write to support@workflowcorp.com, or use the contact page.