Security Policy
Security is a core design principle of Zegi.
Last updated: 2026-10-09
Data in transit
All traffic is served over HTTPS in production, with strict transport security.
Upload safety
Uploads are validated by content (magic bytes), sanitized, size-limited and rate-limited.
Credentials and access
Secrets belong in protected configuration, not public code or logs. API secrets and passwords are stored as hashes. Scope checks, subscription entitlements and role controls restrict access. Google identity tokens are verified before sign-in. Revoke or rotate exposed keys and keep credentials out of browser code, public repositories and support messages.
Reporting
To report a security issue, contact security@zegi.ae.
Shared responsibility
Keep your devices, email account, integrations and downloads secure and retain independent originals. No service guarantees zero vulnerabilities or uninterrupted availability. Security controls and dependencies require continuing maintenance. Validation does not certify document accuracy or safety in every external application.
Responsible disclosure
Report the affected URL and minimal reproduction steps with secrets and personal information redacted. Do not disrupt the service, extract customer documents or publish exploit details before coordination. A report does not authorize further testing. No bounty or fixed response time is promised unless separately agreed.