Privacy notice
- Operator
- Zerivex
- Contact
- zerivex.secure@gmail.com
- Country/state for legal review
- Pending — to be confirmed by the operator
Information processed
Zerivex processes OAuth account identifiers, verified email addresses, display names and profile images; organization membership and role information; hashed session and API-key tokens; session IP addresses and user agents; target URLs and ownership proofs; scan findings, response evidence, comments and audit records; subscription identifiers and invoice amounts and statuses.
Why this information is used
Information supports sign-in, access control, target ownership checks, authorized security assessments, reporting, collaboration, billing, abuse prevention and investigation of security incidents. The operator must confirm the legal bases applicable to these activities before public launch.
Providers and destinations
Google and GitHub provide sign-in. The configured PostgreSQL host stores application data. Stripe handles payments when enabled; Zerivex does not collect card numbers through its own forms. Scanning sends requests to the targets you configure. Enabled organization webhooks send selected event information to destinations configured by that organization. Hosting, data locations and any additional monitoring providers must be confirmed for the deployment.
Retention and security
Credentials are restricted to server configuration, session and API-key values are stored as hashes, and scan evidence passes through a redaction pipeline. Redaction does not guarantee that all personal information is removed. Audit and credit ledger entries are append-only. Backup retention, account closure and anonymization schedules require operator review; no automatic deletion period is promised by this draft.
Your requests
Contact zerivex.secure@gmail.com to request access, correction, account closure, deletion or other applicable rights. Requests may require identity verification, and security, legal or accounting retention obligations may limit deletion. The rights and complaint routes that apply depend on the operator’s location and the people served.
Browser storage
Session cookies support authentication. Browser storage retains interface preferences and onboarding state. Interface fonts are served with the application. No advertising or analytics consent claim is made by this draft.