Cravd Studio — Guest Privacy Notice

Cravd Studio (“Cravd”, “we”) provides software restaurants use to run their menu and take orders (“the Restaurant”). For a guest ordering at a table, the Restaurant is the data controller and Cravd is a data processor acting on its instructions. For a staff account (restaurant admin/kitchen, or Cravd’s own operators), Cravd is the data controller.

Guests ordering without an account:

• Two strictly-necessary session cookies — one identifying which restaurant you’re ordering from, one binding your browser to your table for your visit. These cookies do not directly contain a guest’s name or contact details.
• What you add to your cart and any note you type. A note may describe an allergy — treated as sensitive data. A note written in any language may be automatically translated into the operating language of the restaurant’s country/establishment, so kitchen staff can read it. A translation failure never blocks your order, and your original wording is always kept alongside any translation, never overwritten.
• Your IP address and basic device info, in standard server logs only.
• Anonymous product activity counts — menu views, dish views, confirmed adds and orders sent. Those four counts are all we record. They carry no guest, table, diner label, note or payment detail, and no persistent browser identifier, so nothing in them can be traced back to you or joined to your order. The allergen and dietary filters you choose while browsing are applied on your own device and are never sent to us or recorded.
• Order-related information is different from those counts, and is stored with the order itself: the table number, anything you type as a note, and any ingredient you untick. The Restaurant needs this to cook and serve what you asked for, so the kitchen sees it with your table. The Restaurant’s aggregate reporting shows removed ingredients as a count per dish, without the table or the diner label.
• Removing an ingredient is a request passed to the restaurant and stored with the order. It does not guarantee that a dish is safe for someone with an allergy or intolerance, including from possible cross-contact. If you have an allergy or intolerance, please speak directly to restaurant staff before ordering.

No advertising or tracking cookies, and no third-party analytics in the guest menu. No guest account, email or payment collection. Product activity is measured first-party and without a persistent browser identifier, so the counts cannot be joined back to a person or followed between visits.

Staff:

• Email and password (hashed) to sign in, via Supabase Auth.
• Your role and restaurant, for access control.
• Menu content, photos and videos you upload.

• Supabase — database, file storage, staff authentication.
• OpenRouter / Cerebras — only the text of a guest’s order note, to translate it into the restaurant’s own operating language. OpenRouter routes this specific translation call to Cerebras as the model-inference provider, so Cerebras — not only OpenRouter — receives the note text. Nothing else about the order (no name, table number, or other order detail) is sent.
• Cloudflare — operates as a network-level/CDN layer in front of our domains, handling guest and staff web traffic in transit.
• Render — hosting.
• Resend — staff emails only (password reset, workflow notifications). Guests are never emailed.

We don’t sell data. Where a provider processes data outside your own country, that processing is subject to that provider’s own published safeguards.

Guest session data doesn’t persist as a profile after your visit — there’s no account to delete. Order records are the Restaurant’s own history; ask the Restaurant directly about a specific order. Staff accounts persist until deactivated.

We do not currently apply a fixed retention period per data category — guest session data, as described above, does not persist as a profile after your visit in any case. Product activity counts are kept while the Restaurant’s account is active, so it can report over any period up to a year; because those counts identify nobody, keeping them does not keep anything about you.

You can ask for access, correction, deletion, or export of your data, and object to certain processing. For an order, start with the Restaurant; for a staff account, contact us directly. You can complain to the ICO (UK) or your local authority (EU) at any time.

The guest app sets two strictly-necessary cookies, described above — both required for ordering to work, so neither needs a separate consent banner. The staff portal uses Supabase Auth’s own session cookie for the same reason. The anonymous product activity counts described above do not set another cookie.

The app doesn’t verify age. It’s not directed at children and doesn’t knowingly collect data from them beyond what’s described above, which identifies a table, not a person.

Data controller (staff accounts, and the platform generally): CRAVD STUDIO LTD, trading as Cravd Studio, a company registered in England and Wales (company no. 17390868). Registered office: 27 Old Gloucester Street, London, WC1N 3AX, United Kingdom.

Email: [email protected]