Mezzanine

Data processing terms

How Mezzanine protects the customer information your business keeps in it. These terms are part of the terms of service. Last updated November 7, 2026.

Who these terms cover

These terms apply to every business and Personal space on Mezzanine, with nothing to sign. They sit alongside the terms of service and the privacy policy; where they differ on protecting your data, these terms win.

A business that is itself a financial institution under the FTC Safeguards Rule, such as a tax preparer or bookkeeper, must have its service providers protect its customer information by contract. For that business, Mezzanine (Lumaria, LLC) is a service provider under 16 CFR 314.4(f), and these terms are that contract.

Your data, our instructions

  • Your business controls the customer information it keeps in Mezzanine: its clients, team, payments and linked bank data.
  • We handle it only to run the service for you, never for ads or resale, and never share it beyond the providers below.
  • Our staff open a business’s data only to support or run the service, and the staff console never shows a Personal space.

Our security program

Mezzanine keeps a written information security program under the Safeguards Rule (16 CFR 314), overseen by its owner, Collin Lodato, as its Qualified Individual, and reviewed at least once a year and after any incident. We keep these safeguards on your data for as long as we hold it:

  • Each business’s data is isolated by Postgres row-level security, tested on every change, and inside a business every action is gated by role.
  • Access is removed the same day a person or system no longer needs it.
  • All traffic is encrypted with TLS 1.2 or later and stored data is encrypted at rest; bank, payment and connected-account tokens and vendor tax IDs are sealed again with keys only the app holds.
  • Every staff account on the services that reach our systems from outside the app (Railway, Cloudflare, GitHub, Stripe, Plaid and Google) requires multi-factor authentication.
  • Every sign-in is logged, and so is every view and change made in our staff console.
  • Every change passes a pull request and an automated check before it ships, and security updates land within 30 days, critical ones within 7.
  • A penetration test at least once a year and a vulnerability scan at least every 6 months.
  • Customer information is disposed of no later than 2 years after its last use to serve that customer, unless it is still needed or the law requires keeping it.

Our service providers

We use only providers that run their own security programs, give each only what its job needs, and review the list every year: Railway (hosting, database), Cloudflare (storage, backups), GitHub (code, support requests), Stripe (payments), Plaid (bank data), Twilio (texts and calls), Resend (email), Google and Apple (sign-in, maps, push alerts), Meta (social posting), Intuit (QuickBooks), Sentry (errors), Inngest (background jobs) and Anthropic (the AI agents that help us build and run Mezzanine).

If something goes wrong

If we confirm a breach of your data, we tell your account owner within 72 hours what happened, what data it touched and what we are doing about it, and we notify the FTC and state regulators where the law requires.

Deletion and questions

On your request, or when your account closes, we delete your data, except records the law requires keeping. Requests and questions about how we keep these terms, including a security review your own program needs, go to support@getmezzanine.com and are answered within 30 days.