Security
Security you canverify.
The guarantees that matter — who can read your projects and who can change your credits — are enforced by the platform, not by the interface.
Protection
How your work is protected.
Private by default
Every project, version and support ticket is scoped to your account by database access rules, not by browser code. Another account cannot read your work even if it guesses an identifier.
Server-side point deduction
Credits can only be deducted by a trusted database routine. The browser can estimate a cost, but it can never set, grant or reduce a balance.
Append-only usage ledger
Every grant, purchase and deduction is written to a ledger that cannot be edited or deleted, so your usage history is always auditable.
Separated roles
Administrator and support permissions live in a dedicated role table and are verified server-side. Roles are never stored on your profile, so they cannot be escalated from the client.
No stored card data
Payments are handled through a provider abstraction layer. Card data is processed by the payment provider — Azero Code stores only the plan, status and invoice record.
Human verification
Account creation is protected by human verification, keeping automated sign-ups away from free credit allowances.
Project isolation
Generated files, versions and deployments belong to a single project owned by a single account. Nothing is shared between projects by default.
Your data, your decisions
- You can update or remove your profile details at any time from Settings.
- Running out of credits never deletes a project or its version history.
- Cancelling a subscription keeps your projects accessible in your account.
- Support staff can only see tickets you submit, not your project contents.