DianDot EPOS
Privacy policy
This Privacy Policy explains how DianDot collects, uses and protects information when a restaurant or hospitality team uses DianDot EPOS, its web services or its companion iOS app.
1. Who this service is for
DianDot is a business operations service for restaurants and hospitality teams. Restaurant admins and authorised staff use it to manage reservations, tables, orders, kitchen workflows, payments recorded in the EPOS, reports and connected devices.
2. Information we handle
- Account information: name, email address, password credentials stored in protected form, verification and session records.
- Restaurant information: restaurant name, location, contact details, opening hours, menus, tables, staff permissions, printer and KDS settings.
- Reservation information: guest name, telephone number, email address, party size, booking time, notes, table assignment, deposit and cancellation status.
- Operational information: orders, order lines, discounts, refunds, VAT and service-charge settings, payment method selected in the EPOS, and reports.
- Technical information: session, device and service diagnostic information needed to keep the service secure and reliable.
3. How we use information
- To provide the requested restaurant workspace and connected operational features.
- To authenticate users, enforce permissions and protect money-sensitive actions.
- To send account verification, password-reset and reservation notification emails.
- To process reservation deposits when a restaurant chooses to connect its own Stripe account.
- To maintain service security, troubleshoot failures, prevent abuse and meet legal obligations.
4. Payments
DianDot EPOS records the tender selected by the restaurant, such as cash or card. It does not ask the app user to enter card details for an in-store EPOS payment. Online reservation deposits may be handled by Stripe Checkout through the restaurant's connected Stripe account. Stripe's own privacy policy and terms apply to that payment flow.
5. Service providers
We use infrastructure and service providers to host the application and database, store operational files where configured, deliver transactional emails and support connected payment flows. Providers receive only the information needed for the relevant service and must protect it under their own contractual and legal obligations.
6. Retention
Restaurant admins control operational retention settings where the product provides them. We retain account, security, financial and operational records only for as long as needed to provide the service, resolve disputes, meet legal requirements or protect the service. Deleted records are not intended to be recoverable through normal product use.
7. Your choices and rights
Depending on your role, you may be able to view or update information through the product. Account holders can request access, correction or deletion by contacting us. Some restaurant records may be controlled by the restaurant admin or retained where required by law; in those cases we will explain the limitation.
8. Security
We use access controls, protected password storage, short-lived sessions and encrypted connections designed to reduce unauthorised access. No internet service can guarantee absolute security, so please use unique credentials and report suspected compromise promptly.
9. Children
DianDot is a business service and is not directed to children. It is intended for authorised adults working for a restaurant or hospitality business.
10. Contact
For privacy questions or a data request, email [email protected]. Please do not include passwords, payment card details or other unnecessary sensitive information.