Security posture

You upload financial documents. We treat them with the rigor that demands. Below is exactly what we do — concrete, verifiable, no marketing language.

Encryption

  • In transit: HTTPS/TLS enforced on all endpoints.
  • At rest: AES-256 encryption on all database storage and object storage (managed by Supabase / AWS).
  • Sensitive fields: brand-profile phone numbers are stored encrypted at the column level. We never store card numbers, CVVs, or full billing addresses ourselves — Stripe handles that directly.
  • Documents you upload: processed in-memory in our edge functions; not retained beyond the analysis lifecycle unless you explicitly save them.

Data isolation (Row-Level Security)

Admin access is restricted to a single founder account, gated by a database-level role check (not a client-side flag).

Privacy & PII handling

  • Anonymous analyses are tracked by hashed device fingerprints, IP addresses, and idea content.
  • Email addresses for lead capture are encrypted before storage; we hold a hash for deduplication.
  • You can request export or deletion of your data at any time by emailing privacy@aiwmcquantis.com.

Anomaly detection & abuse prevention

Anonymous endpoints rate-limit by device, fingerprint, and hashed IP. Every entitlement denial (a Free user trying to access a paid feature) is logged for review.

Vulnerability Disclosure

Found a security issue? Email security@aiwmcquantis.com with reproduction steps. Please do not test against other users' accounts.

System status · Privacy policy · Terms