MIORVE
TRUST

Security

Last updated: 2026-05-26

Miorve is built like a private studio: minimal surface area, deliberate defaults, and clear boundaries between accounts.

At a glance
Encrypted in transit (TLS).
Strict account boundaries enforced in the database (RLS).
Payments are processed by Stripe; card details never touch us.
Access is tied to your authenticated session; protected areas require sign-in.
Data isolation

Workspace content (ideas, drafts, planner entries) is scoped to your account. Database policies are designed to prevent cross-account reads and writes.

Billing

Stripe manages checkout and billing portal flows. Miorve stores only the subscription metadata required to reflect membership inside the app.

Reporting an issue

If you find a security issue, email support@miorve.com with details. Please do not share sensitive data beyond what’s needed to reproduce.