Pick the right route
Send confidential security reports to [email protected]. Use the published disclosure process for technical findings.
SECURITY CONTACT
Contact the security team.
Send confidential security reports to [email protected]. Use the published disclosure process for technical findings.
Context
The situation
Send confidential security reports to [email protected]. Use the published disclosure process for technical findings.
Sales, support, privacy, and security requests are separated so each message reaches the accountable team.
On this page
What you get from this
Do not send destination records
Support needs a stable error code, client version, and operating system — not telemetry rows or account secrets.
Security findings
Report privately to [email protected] using the published disclosure process.
Collection boundary
The boundary
We observe here
Byte and packet counts, protocol, an encryption indicator, destination country, network operator, registrable domain, the app or browser that opened the connection, timestamps, and direction.
We never collect here
Communication content, URLs, paths, query strings, DNS names beyond the registrable domain, headers, cookies, tokens, files, screenshots, form data, keystrokes, usernames, email addresses, hardware serial numbers, or precise location.
Coverage is not complete. Some traffic paths are not observable from the interfaces we use, and geolocation is advisory rather than authoritative.
Availability across plans
Personal
Included
Pro
Included
Team
Included
Enterprise
Included