Privacy Policy

Last updated October 20, 2026

ConTROLL provides guest-intelligence software to restaurants and hospitality operators. This policy explains what information we collect, how we use it, and the choices available to you. We designed ConTROLL to keep each venue's guest data private to that venue — operators never see another venue's guests, and cross-network signals are anonymized.

1. Who this policy covers

This policy applies to two groups: operators — the restaurant staff and owners who use ConTROLL — and the guests whose reservation, review, and visit information an operator imports into the platform. Operators are responsible for having a lawful basis to provide us their guests' information and for honoring any guest requests under applicable law.

2. Information we collect

Operator account data: name, work email, venue name and address, and authentication details.

Guest data provided by operators: guest names and contact details, reservation and visit history, no-show and cancellation records, post-visit survey responses, and staff notes — as imported from your reservation platform (e.g. Resy, OpenTable) or guestbook.

Public review data: publicly posted reviews (e.g. Google, Yelp, TripAdvisor) that we aggregate and, where possible, match to a guest record for your venue.

Usage data: standard logs and device information generated when you use the app, used to operate, secure, and improve the service.

Public website analytics

On our public marketing pages, Vercel Web Analytics records page views, selected button and form interactions, and video-player activity. Reports include approximate region, referrer, browser and device categories. Anonymous visitor estimates are not a list of identified people.

Our marketing instrumentation omits private application pages, account identifiers, form contents and URL query strings. It does not collect card details or restaurant guest records. We do not send marketing events from a signed-in ConTROLL session or when the browser provides a Do Not Track or Global Privacy Control signal.

Embedded YouTube videos load the player after you choose to play. Video opening, confirmed playback and playback-position milestones are measured separately. Vercel and YouTube process data needed to provide their respective services.

3. How we use information

  • To provide the core service — building each guest's timeline, VIP and risk signals, daily briefings, and review matching.
  • To generate the deterministic, explainable scores and tags shown in the product.
  • To authenticate operators and secure venue data.
  • To provide support and to maintain, debug, and improve the platform.

We do not sell guest data, and we do not use it for advertising.

4. Per-venue data silo

Each venue's guest data is fully isolated. An operator can only ever see guests associated with their own venue; row-level security enforces this at the database. The only information that crosses venues is anonymized, PII-free network signals (described next).

5. Anonymized network signals

ConTROLL can surface anonymous, cross-network reputation tags (for example, a no-show or negative-review history) tied to an opaque token rather than to a name, email, or phone number. These signals never reveal which other venue a guest visited or any identifying detail — they exist only to help operators prepare. Operators always make the final decision; the platform does not take action on a guest's behalf.

6. Service providers

We use a small set of vetted providers to run the service — including cloud hosting and database infrastructure, a public-review data source, and an AI model provider used to draft briefings and power the in-app assistant over your data. Providers process data only to perform services for us and under confidentiality obligations.

7. Data retention

We retain operator and guest data for as long as the operator's account is active or as needed to provide the service. ConTROLL keeps an append-only history of facts (a correction adds a new record rather than overwriting), so we can show what was known and when. On account closure, we delete or de-identify guest data within a reasonable period, except where retention is required by law.

8. Security

We protect data with industry-standard measures, including encryption in transit, access controls, and the per-venue isolation described above. No system is perfectly secure, but we work continuously to safeguard the information entrusted to us.

9. Your choices and rights

Depending on your location, guests may have rights to access, correct, or delete their personal information. Because operators control the guest data in their venue, please direct guest requests to the operator; we will support operators in fulfilling valid requests. Operators may contact us at any time to access or delete their account data.

10. Children's data

ConTROLL is a business tool and is not directed to children. We do not knowingly collect data from children.

11. Changes to this policy

We may update this policy from time to time. We'll revise the "last updated" date above and, for material changes, provide additional notice within the product.

12. Contact us

Questions about this policy or your data? Email reports@controll.tech.

This page is provided for transparency and is not legal advice. Operators should consult their own counsel regarding their obligations to guests.