Privacy Policy

Who this covers

Resto Intelligence LLC, a limited liability company organized under the laws of the State of Georgia, United States, provides Resto Intelligence, a restaurant operations platform used by restaurant owners, managers, and staff, together with Resto Shift staff surfaces and guest-facing booking and table-assistance pages.

For information about a restaurant's employees, guests, and operations, the restaurant is the controller (or business) and Resto Intelligence LLC acts as its processor (or service provider), handling that information on the restaurant's instructions. For our own account administration, security, fraud prevention, billing, support, and service operation, we act as controller. Jurisdiction-specific terminology differs; the written agreement with each restaurant governs.

Information we handle

• Account and sign-in data: email address, display name, account status, and the identity provider that authenticated you. Sign-in is provided through Clerk, which supports Google, Apple, and Microsoft accounts and email codes.
• Session and device security data: session records, registered-browser records, a coarse client label such as "Chrome on Windows", and a keyed one-way digest derived from your IP address. We do not store the raw IP address alongside your session, and the digest is pseudonymized rather than anonymous.
• Workspace and membership data: which restaurants and locations you may access, your role, and your permissions.
• Workforce data supplied by the restaurant or synced from its point-of-sale system: employee names, job assignments, schedules, availability, time-off requests, clock records, and wage values used to compute labor cost.
• Employee operational analytics: activity the point-of-sale system attributes to a team member, such as sales on assigned checks, presented for the selected period. It is listed alphabetically, is not ranked or scored, and is not an employment evaluation.
• Restaurant operations data synced from Toast, Square, or Clover: orders, order lines, payments, refunds, discounts, voids, menu and catalog records, and labor records.
• Inventory and supplier documents: invoices you upload, and the vendor and line-item details read from them.
• Guest data the restaurant collects: reservation and waitlist name, optional phone and email, party size, and free-text notes such as a seating request.
• Free-text you type: seating requests, reservation and staff notes, time-off reasons, availability reasons, and kiosk notes. We do not ask for health information in these fields, and we ask that you raise allergies and medical needs with restaurant staff directly rather than in a form.
• Communications data: message intents, delivery attempts, masked destinations, consent records, and opt-out suppressions.
• AI prompts and outputs: the questions you ask Resto AI, the evidence retrieved to answer them, the answers returned, and the prompts and brand fields you enter for image generation.
• Content you upload: restaurant logos and other brand assets, and images generated through AI features.
• Support and audit records: platform operator access grants with a stated reason, and immutable audit events.

Information we do not handle

These are product facts, not aspirations. If any of them changes, this policy changes first.

• No payment card numbers, security codes, or cardholder names. Card data stays with the restaurant's point-of-sale and payment providers; Resto receives only amounts, tip totals, tender type, status, currency, and timestamps.
• No biometric identifiers. There is no fingerprint, face, or voiceprint recognition, and no biometric clock-in.
• No audio recording, ambient listening, or stored voice recordings.
• No date of birth or age field. We do not collect a birth date to administer the age rules in our Terms.
• No advertising or tracking technology, no analytics or tag-manager scripts, and no third-party cookies.
• No sale of personal information and no sharing of personal information for cross-context behavioral advertising.

Why we handle it

• To provide the service the restaurant has asked us to provide, and to follow its instructions.
• To authenticate users, protect accounts, detect and investigate abuse, and keep tenants isolated from one another.
• To operate, monitor, and repair the service, including error diagnosis.
• To bill for the service and to answer support requests.
• To meet legal obligations and to establish, exercise, or defend legal claims.

Third-party AI

Three features can send information outside Resto to an AI provider. Each is disclosed separately, each requires its own decision recorded for you in that workspace, and the server blocks the transmission before any provider request when a current accepted decision is absent. Accepting our Terms does not grant this consent, and consent in one workspace never authorizes another.

• Resto AI assistant: your question, the relevant conversation context, and the operational evidence retrieved to answer it are sent to a third-party generative AI processing chain, reached through a model router.
• Invoice scanning: the invoice document you upload is sent in full to Google Document AI for extraction, together with the vendor and line-item content it contains.
• AI image generation: your prompt, campaign context, and any brand fields you explicitly complete are sent to the configured image-generation provider. Guest and point-of-sale data are not sent by this feature.
• Before sending assistant evidence, Resto removes person names and contact details from the operational evidence it assembles. This is structural minimization, not a guarantee of anonymity: free text you type can still contain personal data.
• Declining or revoking stops future sending. It cannot recall information a provider has already received.
• We do not use Customer Data to train general-purpose foundation models. We do not make retention or training promises on behalf of our AI providers beyond what we have contractually confirmed.

AI is decision support, not a decision maker

Resto AI assists with operational questions. It is not employment, payroll, legal, tax, medical, food-safety, or financial advice, and it can be wrong. A person must review its output before relying on it.

Resto enforces this in the product rather than only in policy: a deterministic server-side control refuses requests that ask the assistant to decide or recommend hiring, firing, termination, discipline, promotion, demotion, compensation, wage changes, or shift and hour reductions for a named or identifiable person, and refuses to rank or score people. The control runs before any AI provider is contacted and also inspects returned output. Consent to third-party AI never authorizes a prohibited employment use.

Who we share information with

We share information with the service providers listed on the Subprocessors page, with the restaurant that controls the workspace, and where required by law. Point-of-sale providers are integrations the restaurant chooses and connects; information flows between them and Resto at the restaurant's direction.

• Amazon Web Services: hosting, database, cache, queues, object storage, encryption keys, content delivery.
• Clerk: authentication, including Google, Apple, and Microsoft sign-in and email codes, and delivery of invitation and sign-in-code email.
• Sentry: error monitoring, with request bodies, headers, cookies, and message content scrubbed, and browser session replay recorded only on error with text, inputs, and media masked.
• Google Document AI: invoice extraction, where the feature is enabled and consent is recorded.
• Google generative image models: AI image generation, where the feature is enabled and consent is recorded.
• Nous Research and the model vendor routed through it: Resto AI reasoning, where the feature is enabled and consent is recorded.
• Twilio: outbound transactional text messages for restaurants assigned a messaging number.

Security

We enforce tenant isolation in the database itself, encrypt data in transit and at rest with managed keys, store provider credentials in a dedicated encrypted secret store rather than in the application database, require explicit reason-coded and audited access for platform support staff, and mask guest contact details in operational surfaces. Error reports are scrubbed of request bodies, headers, cookies, and message text before they leave our systems.

No service can promise perfect security, and we do not. To report a vulnerability, contact security@restointelligence.com.

Retention and deletion

You can delete your personal Resto identity from Account Security inside the product, or through the Account Deletion page. Deleting your identity revokes your sessions and workspace access; it does not delete the restaurant's workspace or its business records.

Some records are deliberately retained after an identity is deleted: legal acceptance evidence, security and privacy audit records, the restaurant's business records, and immutable point-of-sale source evidence used for reconciliation and dispute handling. Workforce source evidence may include contact details supplied by the point-of-sale system, and we will not claim those values were erased when they were not.

Backups are replaced on their own cycle, so a deleted record can persist in a backup until that backup expires.

A records retention schedule with specific periods is being finalized. We will publish it here once approved rather than state a period we do not yet apply. Questions: privacy@restointelligence.com.

Your choices and rights

Depending on where you live, you may have rights to access, correct, delete, or obtain a copy of personal information, and to appeal a decision about such a request. Because most workforce and guest information is controlled by the restaurant, we will usually refer a request to that restaurant and support it in responding.

Where consent is the basis for third-party AI processing, you can withdraw it at any time in Settings under Legal and privacy. Withdrawal stops future transmission for that feature in that workspace.

To make a privacy request, contact privacy@restointelligence.com.

Cookies and local storage

We use cookies that are strictly necessary to sign you in, protect against cross-site request forgery, remember your active workspace, and recognize a registered browser. We also store your theme and language preference and which dashboard cards you have hidden. There are no advertising, analytics, or third-party cookies, so there is no tracking to consent to or opt out of.

Age

Resto Intelligence is a business tool and is not directed to children. Only an adult, at least 18 years old, may accept our agreements or bind a business. A restaurant may grant product access to an authorized employee who is at least 16, where its own policies and applicable law permit. Users under 16 are not supported.

We do not collect a date of birth to administer this. The restaurant is responsible for verifying the age of its staff and for complying with the employment rules that apply to them.

Changes and contact

We will update this page when our practices change, and the version and effective date above will change with it.

Privacy questions and requests: privacy@restointelligence.com. Security reports: security@restointelligence.com. Product help: support@restointelligence.com. Legal notices: legal@restointelligence.com.

Resto Intelligence LLC, a limited liability company organized under the laws of the State of Georgia, United States.

Business Mailing Address: Resto Intelligence LLC, 5155 Atlanta Highway, Ste 101 PMB 1002, Alpharetta, GA 30004, United States. Written notices may be sent to this address. It is a mailing address only, and is not a registered agent address, a registered office, or a statement of our principal place of business.