Privacy policy
Defines what RavenVPN collects, what is excluded, and how long metadata is retained.
Legal center
Commercial-ready legal with clear operator paths.
Use this page as the canonical legal entry for launch reviews, customer due diligence, and support escalation.
2core documents
3language tracks
24hreview rhythm
Core documents
The minimum legal set required for consumer and enterprise rollout.
Terms of service
Defines service scope, acceptable use boundaries, and account responsibility.
Support and status evidence
Incident updates and release posture are published in status/support surfaces for auditability.
Data and security commitments
Legal text is aligned with product controls and release gates.
Data minimization
Only account, device, and billing references required for operation are retained.
No traffic payload logging
Traffic content is not intentionally logged; operational telemetry is aggregate and purpose-limited.
Signed client updates
Desktop update chain requires cryptographic signatures and readiness gates before rollout.
Enterprise readiness
B2B buyers need predictable legal + security interfaces.
Security contact
security@ravennets.com is the escalation contact for vulnerability and trust requests.
Support contact
support@ravennets.com handles onboarding, billing, and pairing lifecycle incidents.
Review cadence
Legal pages are versioned with launch evidence so ops can prove current-policy posture.
Next actions
Open the exact policy or evidence surface your reviewer needs.