Browse Error is operated by Reborn Tech India ("we", "us"). This policy explains what we collect through browseerror.com and the Browse Error service, and what our customers' own instrumentation sends to us on their behalf.
Account data
When you create an organisation, we store the organisation name, your email address, and your role within that organisation. We don't use passwords - sign-in is a one-time code emailed to you, so we don't hold a password to lose in the first place.
Cookies
We set exactly one cookie: a session cookie that keeps you signed in. It's essential to the service, not used for advertising or cross-site tracking, and we don't run any third-party analytics or advertising scripts on this site.
Telemetry data (what your projects send us)
If you add a project, the browser SDK and/or your backend's OpenTelemetry exporter sends us error events, traces and logs from your own application - stack traces, request routes, user agents, and whatever custom context your own instrumentation attaches. We process this data on your behalf to provide the service; we don't sell it, and we don't use it for any purpose beyond operating Browse Error for you.
Known secret-shaped values - bearer tokens, card numbers, and sensitive query-string parameters - are redacted before anything is written to our database, across browser events, traces and logs alike.
Data retention
By default, individual events are kept 30 days and issues 90 days, then deleted automatically. An organisation can be configured with different retention windows.
Where data is stored
Browse Error runs on Oracle Cloud Infrastructure, in the Mumbai (India West) region.
Sharing
We don't sell personal data. We share data only with infrastructure providers that run the service on our behalf (currently Oracle Cloud Infrastructure, for hosting, database and outbound email), and only as needed to operate it.
Your choices
You can ask us to export or delete your organisation's account data and telemetry at any time. Deleting a project stops new data from being collected for it; existing data is removed on the retention schedule above or sooner on request.
Changes to this policy
If this policy changes materially, we'll update the date above and, where required, tell account administrators directly.
Contact
Questions about this policy can be sent to the email address you use to sign in to Browse Error, or to your account administrator.
This is a working draft written to match what Browse Error actually does today, not a substitute for independent legal review before relying on it for compliance purposes (e.g. GDPR/DPDP obligations specific to your use case).