PRIVACY / BETA
R&Dish Privacy Notice
Version 2026-07-20.beta-draft.5. R&Dish currently offers Google sign-in. This notice explains personal-information handling during sign-in and use of the current beta service.
Information from Google and purposes
R&Dish requests only the openid, email, and profile scopes. We may receive your Google account identifier, email address, name, and optional profile image for sign-in, account identification, authentication security, and support. We do not receive your Google password, sell personal information, use it for targeted advertising, or train models for other customers with it.
Account and workspace records
We store basic account information, authentication and security records, workspace projects, and experiment records to provide and secure the service. Some drafts may also remain in the browser before submission.
External processing and minimisation
Google sign-in and account authentication use Google and Supabase infrastructure. Vercel infrastructure may process web hosting, basic request logs, and security logs. Prompts and menu or ingredient context are processed only to the minimum extent needed. The hash-bound external-processing disclosure shown with this document governs Fireworks AI Kimi K2.6 and GLM 5.2, the local Epicure, FoodOn, FlavorGraph, and multilingual E5 boundary, and conditional queries to USDA FoodData Central and Open Food Facts.
Retention and deletion
A project deletion request first archives the project and blocks further writes. Physical erasure from events, memories, provider records, caches, and backups is an operator-run beta process and is not instant. Provider-side retention is governed by the provider’s terms. Request access, correction, deletion, account deletion, or retention status at contact@rndish.com.
Your choices and changes
You may revoke R&Dish access in your Google account. We update this document with appropriate review and notice before materially changing the processing scope or method.