What Orivo stores and how data is handled

Orivo uses an account-based model for editor access, cloud projects, snapshots, billing and support requests. Some UI preferences still live locally in the browser.

Stored data
  • Account email and profile metadata
  • Projects and project snapshots linked to signed-in accounts
  • Billing references such as Lemon Squeezy order and subscription IDs
  • Support requests, feedback submissions and email delivery events
Deletion and export
  • Projects can be exported as HTML, JSON or ZIP inside the product
  • Projects are linked to a user profile instead of relying on browser-only storage
  • Support requests and billing state can be traced back to the account that created them
  • Data removal can be implemented by deleting the user, project and subscription records in the database