Security

Your numbers are your edge. We guard them like one.

Recipes, costs, and margins are competitive information about your business. Here's exactly how MarginLeaks protects them — and the lines we won't cross.

Last updated July 14, 2026

How we protect your data

Six things that are true the moment you sign in.

No badges we haven't earned — just the controls that are actually in the product today.

Your workspace is isolated

Every restaurant's data lives in its own organization, and isolation is enforced server-side at the data layer — not just hidden in the interface. One organization can never read or write another's rows.

Role-based access you control

Owners, managers, staff, and viewers each see exactly what their job needs. You invite and revoke; revoking takes effect immediately, and revoked access stays revoked.

Encrypted in transit

Every connection to MarginLeaks is encrypted in transit, so your recipes, costs, and margins are never sent in the clear.

Card details we never hold

Payments run on our provider's secure hosted checkout. Your card number is entered there, never on our pages — we never see or store full card numbers.

Document reading has a human gate

When you upload an invoice, menu, or payout statement, automated extraction proposes entries — and you review and confirm before anything is applied. Your documents are never used to train AI models.

Export and deletion, on your terms

Everything exports back out — recipes as CSV, your full account as JSON, anytime. Cancel and it stays exportable for 30 days; request deletion any time and we complete it within 30 days.

Who sees what

Access is role-based, and you hold the switch.

Four roles, enforced at the data layer. Staff never reach the money pages; viewers can read a report and change nothing.

CapabilityOwnerManagerStaffViewer
See the dashboard & weekly report
View & edit recipes and ingredients
Import invoices, settlements & sales
Commit a menu price change
Manage the team, billing & settings
The lines we won't cross

Some things are worth putting in writing.

Trust is mostly about what a vendor refuses to do. Here's ours.

  • We never sell your data.
  • We never use it to train AI models.
  • We never share it with other customers or data brokers.
  • We never see or store your full card number.
Straight talk

If something goes wrong — and how to reach us.

No promises we can't keep

No honest vendor promises unbreakable security. What we promise is behavior: access inside our team is limited to what's needed to support you, and if an incident affects your data we'll tell you promptly and plainly — what happened, what it touched, and what we're doing about it.

Report a security issue

Found a vulnerability, or something that just looks wrong? Email us with enough detail to reproduce it and a human will read it and respond as quickly as we can.

security@marginleaks.com

For what we collect and why, see the Privacy Policy. Anything else, the contact page reaches a real person.

We use cookies to measure our ads. Details