MANAGER
Privacy, plainly.
This page describes how Manager is designed to handle restaurant data, and what this laboratory demo surface actually does today.
Preview notice
This is product language for demos and design review. It is not counsel-reviewed legal advice, not a signed DPA, and not a substitute for a production privacy policy. Contact contact@mycelliumlab.com for formal terms.
What this Lab demo stores
On mycelliumlab.com, the Manager app surface stores an HttpOnly session cookie after authorized sign-in, and may receive contact-form messages you send. Demo screens show illustrative restaurant data that is not your live POS or inbox unless a pilot integration is explicitly enabled.
What the full product is designed to store
Account email, restaurant membership, forwarded messages, attachments, sales summaries, connection metadata, and the facts used in your daily brief — scoped per restaurant tenant in the product architecture.
How we protect it (design intent)
Each restaurant is designed to operate in its own protected data boundary. Sessions use secure cookies; production passwords are hashed; row-level security is part of the Manager API architecture. This Lab surface is a gated demo, not the full multi-tenant production stack by itself.
Your control
You can request session end (sign out), ask to disconnect sources in a live deployment, or email contact@mycelliumlab.com to request deletion of contact messages or pilot data associated with your restaurant.
Auditable automation
Financial numbers are calculated by deterministic code, not invented by a model. Every number keeps a known operational source, and human correction is designed to always win over reprocessing.
Last updated · August 8, 2026 · Preview language, not full counsel-approved legal text.