Security

How we protect the data our platform and this website handle.

⚠ REVIEW NEEDED: This page describes real, currently-implemented practices only — it deliberately does not claim any formal certification (SOC 2, ISO 27001, etc.) since none has been completed yet. Update it if/when that changes, and have it reviewed before publishing alongside any specific claims a customer or insurer might rely on.

Encryption in transit

All traffic to this site and to the MenuVerse platform is encrypted over HTTPS/TLS. Passwords are never stored in plain text — they're hashed before being saved, and are never visible to us in a form we could read even if we wanted to.

Access controls

Administrative areas require authentication, and access to dealership data is scoped — each account can only see and act on the data it's actually authorized for. The MenuVerse platform supports optional two-factor authentication (TOTP) for every account.

Application hardening

Public-facing forms are rate-limited to prevent abuse. Security headers (HSTS, X-Frame-Options, and related protections) are applied across this site. We treat security issues we find as a priority, not an afterthought — fixes are verified against real, live testing before shipping, not assumed to work.

Data handling

We don't sell your data. See our Privacy Policy for what we collect and why.

Reporting a security issue

If you believe you've found a security vulnerability in our platform or this website, please report it to security@menuverse.ai. We ask that you give us a reasonable opportunity to investigate and address a report before disclosing it publicly. See /.well-known/security.txt for the machine-readable version of this contact.

⚠ REVIEW NEEDED: Confirm security@menuverse.ai is an actual monitored inbox before this page (or security.txt) goes live — an unmonitored disclosure address is worse than none, since a real report could sit unseen.