Data & privacy
Where your data lives, who processes it, and the agreements that protect it.
You should know what Evonx holds, what stays in your app, and which legal pages bind that split. This page maps the pieces; it does not replace the agreements.
Two roles
Account and usage data — name, email, sign-in, billing, platform logs — Evonx is the controller. That processing is described in the Privacy Policy.
Data inside repositories, Shopify stores, and the content you paste into chat — you are the controller and Evonx is the processor, on your instructions. The Data Processing Agreement applies automatically; you do not have to countersign it to be covered. Procurement that needs a signed copy writes to [email protected].
Where app data sits
The Postgres behind a template app or a custom API Evonx provisioned is the managed database. Live is the published app; Development is what previews use. Preview databases are ephemeral — they reset when the preview goes away.
Project secrets are write-only keys. Repository access is granted through GitHub and revoked there. Shopify theme work is granted through the store connection you turn on — see Shopify.
Who else processes data
Infrastructure and AI providers that run the platform are listed on Sub-processors. GitHub and Shopify only receive data after you connect them.
How changes land in your code — pull requests, isolated previews, encryption in transit — is on Security. Report a vulnerability to [email protected], not to the product inbox.
Related
Last updated: September 4, 2026