Security
Security at ZOREVA-UI
Your code, your account and your agent’s access deserve care. This page lists what we actually do today across the website, the MCP server and the CLI — nothing more.
Last updated Oct 28, 2026
Sign-in without passwords to leak
Email one-time codes, Google or GitHub. Session tokens are checked against published signing keys.
Agents sign in with OAuth
The MCP server uses OAuth 2.1 with PKCE. Access tokens expire after one hour.
The CLI asks before it acts
Diffs before edits, prompts before risky commands, and a network-less sandbox on Linux.
Payments stay with Stripe
Card details are entered on Stripe and never reach our servers.
01Accounts and sign-in
- You sign in to the website with a one-time code sent by email, or with Google or GitHub. ZOREVA-UI never asks you to create a password.
- Requests for a sign-in code are rate limited per network address and per email address.
- The sign-in form gives the same answer whether or not an account exists, so it can’t be used to find out who has an account.
- Session tokens are verified on every request against the published signing keys (JWKS) of our authentication service before any account data is read.
02Connecting your agent (MCP)
- The hosted MCP server uses standard OAuth 2.1 with PKCE and dynamic client registration. You sign in on zoreva-ui.com, review the request and press Allow; your client receives its token on its own.
- Access tokens last one hour and refresh automatically. Nothing needs to be pasted into a config file.
- Clients without OAuth support can use a manual token from your Account page instead. It expires after seven days.
- Each tool call returns a single catalog item. Download links handed to agents are short-lived and can be opened only once.
03The CLI on your machine
- By default the CLI asks before it runs a shell command or writes a file. Only --yes or --autopilot approve those on their own.
- Every file edit is shown as a diff you can accept or reject, and /undo restores the files changed in the last turn.
- On Linux, commands run in a bubblewrap sandbox with no network access and writes limited to the project.
- File paths are resolved before access, so a symbolic link that points outside the project is refused.
- Hooks defined inside a project don’t run until you trust that project, and project instruction files are treated as untrusted context.
- Browser sign-in uses PKCE and a one-time code exchanged over a POST request. Your token is never placed in a URL.
- Your credentials, settings and sessions are stored in ~/.zoreva with permissions that only your user can read.
- Updates are checked against published SHA-256 checksums before the CLI replaces itself.
04Your own API keys
- When you connect your own model provider key in the CLI, it is saved only on your computer, in a file that only your user can read.
- Requests made with your key go straight from your computer to the provider you picked. ZOREVA-UI does not store or proxy that key.
- You can remove a saved key at any time from the CLI. Keys can also come from environment variables, so they never touch disk.
05Infrastructure and data
- All traffic to zoreva-ui.com uses HTTPS. The site sends HSTS, a Content Security Policy, and headers that block framing and content-type sniffing.
- Account data is stored in managed Postgres with encryption at rest provided by the platform.
- Row-level security is turned on for the tables in our public database schema as a second line of defense: any database role other than the application’s own is denied by default.
- Shared secrets between our services are compared in constant time.
- Product files are checked for payment keys and webhook secrets so they don’t end up in the source code.
06Downloads and fair use
- Your plan is always read on the server. A request can’t declare itself Premium.
- Download quotas are stored in the database, not in memory, so they hold across servers.
- Each address has an hourly cap on file transfers, which keeps the catalog from being scraped in bulk.
07Payments
- Checkout and billing run on Stripe. Card numbers are entered on Stripe and never touch ZOREVA-UI servers.
- Billing events from Stripe are accepted only when their signature checks out.
08AI and your data
- Prompts sent to ZOREVA-UI models are used to answer you. What is sent, and what is kept, is described in plain language on our AI and data page.
- CLI crash reports are off by default and never include code, prompts or file contents.
09Deleting your account
- You can delete your account yourself from the Account page by confirming your email address.
- Deletion cancels any active subscription right away, revokes the MCP tokens issued to you, and removes your personal records.
- A few security and billing logs are kept in de-identified form, as the Privacy Policy explains.
10What we don’t claim
- ZOREVA-UI doesn’t hold third-party security certifications today. We’d rather tell you that than imply otherwise.
- We don’t run a paid bug bounty yet, but every report is read and answered.
Report a vulnerability
Found something? Email us with “Security” in the subject, the steps to reproduce it and the impact you expect. Please give us reasonable time to fix it before you disclose it, and don’t access other people’s data or degrade the service while testing.
support@zoreva-ui.com