Privacy Policy
Last updated August 14, 2026 · applies to the MNE
application, API, and email briefs · see also the
terms of service
Draft — pending legal review
MNE exists to read a restaurant's operational numbers so the owner
does not have to. That job requires holding business data we take
seriously. This policy says exactly what we collect, what we do with it,
where it goes, and what we will never do — in plain language,
because a policy the owner cannot read protects nobody.
What we collect
- Account data. Your email address and, optionally, a display
name. Your password is stored only as a salted one-way hash —
we cannot read it, ever. Two-factor secrets are encrypted at rest;
recovery codes are stored only as digests; passkey private keys never
leave your device (we hold only the public half).
- Business operational data. What the product is for: daily
sales and labor aggregates, order and menu-item detail when you
connect it, supplier invoice lines, inventory counts, and the
forwarded point-of-sale summary emails that carry those numbers.
- Camera frames, only while you run a video inventory count.
Frames are processed into item detections and are not retained.
- Operational logs. Sign-in attempts (with IP address) for
rate limiting and a tamper-evident audit trail of security events.
What we deliberately do not collect
- No guest or consumer data. Your diners are not our concern
and never become our records.
- No payment card data. MNE never connects to your POS and
never touches a payment.
- No advertising trackers. Our pages contain no third-party
analytics, no pixels, no fingerprinting — nothing loads from
anyone else's servers.
How your data is used
To do the job you hired MNE for: computing your weekly brief and
findings, watching supplier prices, reconciling inventory, alerting you
when a data feed goes quiet, and — when you use the advisors —
answering your questions and drafting work for your approval. Agent-drafted
actions (a supplier email, a par change) execute only after you approve
them in the app.
Who processes it (sub-processors)
| Service | What it sees |
When |
| ServiceHosting provider |
What it seesThe application and database run
there | WhenAlways |
| ServiceAnthropic (Claude API) |
What it seesThe specific slices of your data
an advisor looks up to answer you — metrics, findings, inventory
detections — and any file you attach to a question |
WhenOnly when AI advisors or
video counting are enabled and used |
| ServiceEmail delivery provider |
What it seesThe briefs and alerts we send
you | WhenWhen email delivery is
configured |
Files you attach to a question
A file attached to a question is not stored. It is read in memory
to answer that one question, sent to the AI provider as part of it, and
discarded when the answer comes back. It is not written to the database, it
is not in your backups, and it is not searchable later — ask again and
you attach it again.
An attachment also never changes your numbers. Nothing read this way
reaches your sales, labor, inventory, the Monday brief, or the Findings
screen. The only route into those is importing a file on the Upload screen,
which is a separate, deliberate action.
How it is protected
- Encrypted in transit (TLS) between you and MNE.
- Two-factor secrets are sealed with authenticated encryption; the key
lives in the platform secret store, separate from the database.
- Database backups are encrypted with the same key before they are
written.
- Tenant isolation is tested on every release: our test suite
attacks every data route with one customer's credentials and another
customer's identifiers, and the release does not ship unless every
attempt is denied. Another customer cannot view, change, or confirm
the existence of your data.
- Sessions expire, can be revoked everywhere at once, and are stored
only as digests. Security events land in a hash-chained audit log
that makes silent tampering detectable.
Your data is yours
- Ownership. Your business data belongs to your business. We
claim no rights in it beyond operating the service for you.
- Portability. Export your data any time: CSV downloads and
live spreadsheet feeds are built into the product.
- Deletion. Ask, and your organization's data is deleted from
the live database; encrypted backups age out on a fixed retention
cycle (default fourteen days).
- No selling, no sharing. We do not sell your data, share it
with advertisers, or use one customer's data to advise another.
If something goes wrong
If we learn of a breach affecting your data, we will notify you
promptly with what we know, what it affects, and what we are doing
— not a euphemism weeks later.
Changes and contact
If this policy changes materially, you will be told in the app before
the change takes effect. Questions and requests:
privacy@expo.app.