Security
Concrete mechanisms, not adjectives: how Mateo protects your account and your data.
Sign-in without passwords
Mateo authenticates exclusively through Google sign-in (OAuth). We never see or store a password for you - there isn't one. Sessions are signed and validated server-side on every request.
Encrypted in transit and at rest
All traffic to Mateo is served over HTTPS with managed TLS. Your data lives in a managed PostgreSQL database on Google Cloud, which encrypts data at rest by default.
Your documents are yours
Generations are keyed to your account, and every read and write is scoped to the signed-in user. The only public surface is a share link you explicitly create - it exposes that single document, read-only, and nothing else.
Least-privilege by construction
The application runs under a dedicated service account granted only the permissions it needs. Credentials and API keys live in a secrets manager - never in code, configuration files, or container images. The runtime database role can read and write data but cannot alter the database schema; schema changes require a separate, more privileged role used only during deployments.
Hardened generation pipeline
Submitted URLs are validated server-side before any analysis: internal addresses, local networks, and non-web schemes are rejected outright. Generation requests are rate-limited and quota-enforced on the server - client-side checks are a courtesy, not the enforcement.
Payments handled by Stripe
Paid plans are processed through Stripe Checkout. Your card details are entered on Stripe's payment pages and never touch Mateo's servers; we store no card numbers.
What we don’t claim
Mateo does not currently hold formal security certifications (such as SOC 2 or ISO 27001). We’d rather tell you exactly what we do than imply an audit that hasn’t happened. As the product matures, this page will change accordingly.
Reporting a vulnerability
If you believe you’ve found a security issue in Mateo, please email support@mateoux.io with the details - steps to reproduce, the impact you observed, and how we can reach you. Reports go straight to the people who build the product, and we’ll respond as quickly as we’re able. Please don’t access other users’ data or disrupt the service while demonstrating an issue.
Related reading: Privacy Policy · Cookie Policy