Data controller
For user accounts, security, support, and improvement of NowOS, the data controller is: EATNOW, a French simplified joint-stock company with share capital of €500, registered with the Paris Trade and Companies Register under number 990 635 096, EU VAT number FR94990635096, with registered office at 60 rue François Ier, 75008 Paris, France. Data protection contact: privacy@eat-now.app. When NowOS processes customer, reservation, order, or sales data on behalf of a merchant using the service, that merchant remains the controller of this business data and EATNOW acts as its processor under the agreement entered into with the merchant. The same applies to hotel guests’ data received from the hotel’s PMS: the hotel and the merchant charging the room remain responsible for it.Data we process
Depending on the features used, NowOS may process the following categories:- Account and permissions: name, work email address, internal identifier, role, organization, and assigned location;
- Device and pairing: device identifier and name, model, operating system and app version, register role, connection status, and technical information required for local-network pairing;
- Point-of-sale activity: catalog, orders, sales, payment amounts and tender types, refunds, business days, cash movements, stock, printing, and fiscal data;
- Customers and reservations: name, telephone number, email address, reservation, visit history, prepayment, internal note and, when supplied, allergies or preferences;
- Hotel guests: name, room number and stay dates, received from the hotel’s PMS when a merchant charges a check to an in-house guest’s room (room charge);
- Invoicing: personal or company name, address, email address, tax identifiers, and VAT number entered to issue an invoice;
- Diagnostics and usage: pseudonymous technical identifiers, screens and actions used, operation durations, app version, performance, errors, crashes, and connectivity state;
- Support: problem category, optional comment, and technical context attached to a report.
Purposes and legal bases
We process this data to:- provide, secure, and maintain the service under the agreement with the merchant;
- enable authorized users to work and allow the register to operate locally;
- synchronize business data and preserve its integrity;
- issue sales documents and comply with applicable fiscal and accounting obligations;
- answer support requests and resolve incidents;
- perform limited measurement of product reliability and usage in order to improve it, based on EATNOW’s legitimate interest in operating a safe and useful service.
Recipients and service providers
Data is available only to authorized people at the relevant merchant and, when necessary, authorized EATNOW personnel. EATNOW uses technical providers for hosting, update distribution, performance measurement, product analytics, and diagnostics, including Railway, Expo/EAS, PostHog, and Sentry. They receive only the data needed to perform their role and are subject to confidentiality and security obligations. Where data is processed outside the European Economic Area, EATNOW applies the safeguards required by applicable law, such as Standard Contractual Clauses or an adequacy decision.Retention
- Account and configuration data is retained for the duration of the contractual relationship and then for the periods needed to handle requests and legal obligations.
- Sales, invoice, and compliance data is retained for the fiscal, accounting, and evidentiary periods applicable to the merchant.
- A hotel guest’s name is erased from search data 7 days after they check out, and from deliveries to the PMS 30 days after those are settled. The room number, the stay and the amounts are kept with the sale, for reconciliation with the hotel. The name is neither printed on the receipt nor kept on the sale.
- Product analytics events, diagnostics, errors, and problem reports are retained for no more than 90 days during the pilot, unless a specific incident must be kept longer to resolve it or establish or defend legal rights.
- Local register data remains on the device until it is synchronized, removed through an available deletion function, or the device is reset, subject to data that must be retained by law.