Privacy policy
Last reviewed: beta
What we collect
When a tester submits a report through a Brevwick widget, we receive the tester’s note plus auto-collected context: route, console breadcrumbs, a sanitised network ring, and device information. End users of your app are not identified to us beyond a salted fingerprint; we do not set end-user cookies.
PII sanitisation
Console and network data are sanitised on the client before leaving the browser. We strip obvious identifiers (emails, tokens, and known header names) on a best-effort basis. You are responsible for reviewing formatted reports before sharing them externally.
Retention
Attachments are retained on a rolling window configured per workspace. Deleted reports and their attachments are purged from primary storage on deletion and from backups within a standard rotation.
Your rights
Contact us to request access, correction, or deletion of personal data held on behalf of your workspace. Requests concerning the tester’s end users should be routed through the tenant workspace that owns the data.
Contact
Questions: privacy@brevwick.com.