Trust

Data & privacy posture

A short, accurate summary for operators evaluating Sommetry. Legal detail lives in our policies; this page states how the product is designed to behave.

Tenant-scoped restaurant data

Wine lists, prices, menus, and staff tools are scoped to the business account. Cellara at a venue recommends from that venue’s inventory context - not another restaurant’s list.

Guest taste sharing is opt-in

Personal taste graph personalization at partner venues requires guest intelligence features and the guest’s share preference. Guests can keep recommendations list-only.

Analytics consent

Essential cookies run the product. Optional analytics help improve discovery and Cellara. The public cookie bar lets visitors choose essential-only vs accept analytics. See Privacy Policy.

Cellara voice (optional)

Hold-to-talk and audio upload send short clips to speech-to-text only when you opt in. Spoken replies use text-to-speech of the on-screen answer. Audio is not kept after transcription; wine cards and disclaimers stay on screen. Configure providers via env - see Subprocessors.

AI without scrape-and-fine-tune

Sommetry does not scrape Wine Spectator, blogs, or Reddit into private model weights. Education and story context come from curated platform knowledge, approved tech-sheet outputs, and your tenant data.

For wine theory and regulatory questions, Cellara retrieves from a platform reference corpus - public OIV oenological standards, TTB AVA listings, and WIPO geographic-indication texts - plus hand-authored Sommetry primers. Producer tech sheets and your venue menu stay tenant-scoped.

Third-party marketing analytics

Google Analytics 4 may load on public marketing pages only after you accept analytics cookies, to measure traffic and sources. First-party page views and product events remain the system of record for Cellara and venue KPIs. Listed under Subprocessors.