Skip to main content

Security and privacy

This page says what data reaches Collector, what the SDKs leave out, and what's kept. It describes what the software does today; if something isn't here, don't assume it.

What the SDKs send​

Errors​

An event carries the error (type, message, stack trace and the lines of code around it), the environment, the release, the server's name, the breadcrumbs (what happened just before) and, if your application says so, the user's id. That id is yours (4812), not an email or a name: Collector doesn't need one.

If the error happened during a request, the event carries the method, the URL and the headers. Collector drops cookie, authorization, set-cookie and proxy-authorization even if they arrive, and the SDKs don't send them:

  • Elixir (Collector.Plug): never sends cookie, authorization, set-cookie, proxy-authorization or x-api-key.
  • Node: never sends cookies, Authorization, API keys, any header with token, secret, session, auth or password in its name, or the ones carrying the client's IP. Nor request bodies.
  • Browser: sends no cookies or headers, only the user agent. Removes usernames and passwords from URLs.

The JavaScript SDKs remove the query and the #hash from URLs (stripQuery: false keeps them). The browser's click breadcrumbs describe the element (form.checkout > button#buy), never its text or what was typed. Console breadcrumbs keep a short summary of what was logged; if your application logs personal data, turn them off with breadcrumbs: { console: false }.

Every SDK offers beforeSend, which sees each event last and can change it or drop it.

Signals​

The browser's signal carries only the SDK's name and version, your application's release and the environment: no user, URL, user agent or browser id. The day it was sent is kept in localStorage. Turn it off with heartbeat: false.

Speed​

Each page view carries its route (without query or fragment), its Web Vitals and the requests it made. On arrival, Collector derives the country, the browser, its version and the device type, and keeps only those: never the IP or the full user agent. The tab's session lives in sessionStorage, with no cookie. Page views are kept for 90 days.

Logs​

Logs, on the other hand, keep what's sent as is, for a year: Collector doesn't mask anything in log lines, so what your application logs is its responsibility. Requests keep method, path (without query), status, duration, IP and user agent, but never headers or bodies. Sign-ins keep what the person typed to sign in, usually an email. See Logs.

The keys​

  • The DSN's key is public: it only sends events, so it can go in browser code. What keeps it in line is the server: the allowed domains and the sending limits.
  • The server key, the upload token and the access token are secret. They're shown once when created and can be revoked at any time. A server key sent from a web page is refused.

See Core concepts and Keys and tokens.

The domains​

Collector records every web page domain a project's events come from. A new one is pending: its events are kept, and the project's owners and admins are asked, by email and in the project, whether it's their site. They can allow it or block it; a blocked domain's events are refused from then on. Requests from servers are never recorded or blocked. See Allowed domains.

Your account​

  • Every account has a passkey: Collector asks for one before showing any page. You can also sign in with an email link or a password.
  • Your account settings and approving the CLI need a recent sign-in; otherwise you sign in again before going on.
  • Changes to the organization, its members, its projects, their keys and their issues go into the audit log.