This section likewise describes the website. The mobile app contains no error monitoring software — see Section 8.
We use Sentry solely to detect and diagnose software faults, so that broken pages, failed chart generation, and failed payments can be fixed. This is reliability engineering, not analytics and not tracking: Sentry receives no analytics identifier, no account identifier, no user record, and no behavioural event properties, and we do not use it to build any profile of you. Because it is not tracking, it is not governed by the Do Not Track behaviour described in Section 6 — but the categories excluded below are excluded for everyone, regardless of any browser setting.
Error reports are processed by Sentry in the United States and retained for 90 days, after which they are deleted. A report contains the error type and message, the source location in our own code, the normalised route (for example /chart/:id), the HTTP method and status, the runtime, the release, and the support request ID also shown to you when an error occurs.
We deliberately exclude, before any report leaves your browser or our servers: your name and email address; your IP address; birth date, birth time, birth place, coordinates, and timezone; chart data; chat questions, answers, and AI prompts or tool data; contact-form content; request and response bodies; form values; URL query strings and fragments; cookies and authorisation, session, and signature headers; chart, chat, session, and account identifiers; coupon codes; payment, subscription, and signature identifiers; API keys, tokens, and database credentials; and cache keys and values. Diagnostic console output is discarded rather than attached, and expected outcomes — validation failures, sign-in and permission checks, usage limits, and cancelled or stopped requests — are not reported at all.
We do not use Sentry for performance tracing, profiling, session replay, or logging.