Privacy
What TraceHawk stores, and why.
TraceHawk keeps the account you create and the error events your project sends, so the product can group them and file the work you asked for.
Account
Registration stores your name, email address, organization name, and a hashed password. The workspace stays closed until the email address is confirmed. If you turn on an authenticator app, that secret is encrypted.
Events
A project sends the errors you choose to report: the exception, the stack, the URL, the release, breadcrumbs, and a user id or email if your own code attaches one. TraceHawk uses that to group issues and show the issue page. Request headers whose names look like a cookie, authorization value, token, password, or secret are dropped. Local variables whose names look like a password, secret, token, credential, or API key are stored as [Filtered].
Integrations and billing
A Jira API token or a Slack webhook URL that you save is encrypted before it is stored. Checkout is handled by Paddle. TraceHawk stores the plan and the subscription status. It does not ask for or store a card number.
What this page does not claim
There is no self-serve account deletion in the product yet. Write to support@tracehawk.net if you have a question about your account or the events in a project. TraceHawk does not sell the events you send.