Restaurant knowledge stays controlled, explainable, and manager-approved.

Restaurant knowledge stays under your control

The Restaurant Brain is RestaurantCue's operational source of truth. Recipes, procedures, policies, guides, training material, and other restaurant knowledge retain their approval state and location context.

AI can help retrieve, compare, explain, organize, and draft from available evidence. Where approval is required, managers decide what becomes approved employee-facing knowledge. AI does not receive authority to silently approve or overwrite the restaurant's operating standard.

Access controls and restaurant isolation

RestaurantCue uses authenticated accounts, role-aware application controls, company and location scope, and database authorization policies to separate restaurant data. Manager, employee, and platform-administration functions have different permissions.

Private Restaurant Brain content is not intended for public marketing pages, sitemaps, search metadata, or other public discovery surfaces.

Service providers

RestaurantCue uses specialized service providers to operate parts of the platform. Current implementation paths include Supabase for hosted application data and authentication, Railway for application infrastructure, Stripe for subscription billing, OpenAI for configured AI capabilities, Resend for email delivery, Sentry for error and diagnostic reporting, and Google Cloud Document AI for OCR when that workflow is used.

Information sent to a provider should be limited to what is needed for the requested function. Use of a provider does not change RestaurantCue's authorization or approval rules.

RestaurantCue does not currently claim SOC 2, HIPAA, PCI DSS certification, or another formal compliance certification unless and until the applicable status has been independently established. Stripe handles payment-card collection and processing through its payment services; RestaurantCue does not operate its own payment-card vault.

Documents and OCR

You can select a Google Drive file for import into the private document review workflow. Google access and refresh tokens stay in an encrypted server session, and imported guidance requires manager approval before employee use.

RestaurantCue can preserve source references for material imported through supported document workflows. Source references help keep knowledge traceable to its origin.

When OCR is required, the selected document bytes and file type may be sent to the configured Google Cloud Document AI processor for text extraction. The result returns to RestaurantCue's document workflow for review and processing. OCR does not make extracted material approved Restaurant Brain knowledge.

Supported document types may also be parsed without third-party OCR when the workflow allows it.

Evidence-grounded AI

RestaurantCue's AI features are designed to use Restaurant Brain evidence relevant to the task. Where LLM reasoning is used, the application is designed to validate expected outputs and use safe fallback or manager-review behavior when evidence is insufficient or a provider response cannot be used reliably.

Employee Ask is designed not to present unapproved generated material as an approved restaurant fact. When approved evidence does not establish an answer, the safer outcome is to identify the knowledge gap rather than invent a restaurant procedure.

Customer content may be transmitted to a configured AI provider when an AI function requires it. Provider retention and training practices depend on the applicable provider arrangement and configuration; see the Privacy Policy for additional information.

Security practices

RestaurantCue uses hosted HTTPS endpoints and keeps privileged credentials and secrets on server-side paths rather than intentionally exposing them through public pages. Access controls are designed around authenticated identity, role and location scope, and database authorization.

Security is an ongoing operational responsibility. RestaurantCue reviews and updates safeguards as the product and its risks change. No internet service can guarantee that a security incident will never occur.

Storage, retention, and deletion

RestaurantCue stores records needed to provide the service, including account and restaurant configuration, Restaurant Brain records and approval state, work and training records, document and source records, billing-state references, and operational records required by product workflows.

Retention varies by record type and purpose. Customers may contact RestaurantCue about account or data deletion. Certain information may be retained for legitimate billing, security, legal, dispute, backup, or recovery purposes, and provider-held information may be subject to the provider's applicable lifecycle.

Report a security or privacy concern

If you believe you have found a security or privacy issue involving RestaurantCue, email hello@restaurantcue.com. Include enough information for us to understand and reproduce the concern, but do not send passwords, API keys, or unnecessary sensitive restaurant data in the initial report.