Data and privacy

Product analytics means collecting data about people, so this page states plainly what ErrorDock stores and what control you have over it.

What is collected

• Errors: exception type, message, stack trace, release, environment.
• Performance: operation timings and span names.
• Product usage: named events and the feature they belong to.
• Identity: a user identifier that you choose and control.

User identifiers are hashed on the server. Raw identifiers are stored only if the project turns that on, and it is off by default.

What is not collected

ErrorDock does not collect passwords, authentication tokens, payment details or request bodies by default. Header and body capture is opt-in and allow-listed field by field.

Where it is held

Data is stored in the EU, on a server in Finland. Encrypted daily backups go to object storage in France.

AI requests go to the model provider your organisation chose, Anthropic or OpenAI, using your own key.

Scrubbing

Scrubbing runs inside the SDK, before anything leaves your application, so sensitive values never reach ErrorDock at all. In .NET, BeforeSend sees every event as it would be sent: return null to drop it, or change it and return it. ScrubRequestPath rewrites request paths before they leave the process.

options.BeforeSend = e =>
{
    if (e.Message?.Contains("card number", StringComparison.OrdinalIgnoreCase) == true)
    {
        return null;                      // drop the event
    }

    e.Tags?.Remove("customer-email");     // or remove a tag
    return e;
};

options.ScrubRequestPath = path =>
    path.StartsWith("/invite/") ? "/invite/{code}" : path;

Retention

New organisations start on the default plan, with raw events kept for 7 days and aggregates for 90 days. Longer retention is agreed during beta onboarding. When retention expires, event detail is deleted and aggregate counts remain.

Erasure and export

One person's data can be erased by the identifier you set for them. Organisation configuration and telemetry can be exported, as JSON and NDJSON.

Account security

Dashboard accounts support multi-factor authentication with TOTP and recovery codes, and an organisation can require it. Passwords need at least 12 characters and are checked against known breaches. There are four fixed roles: owner, admin, member and viewer.

Controller and processor

If you send personal data, you are the controller and ErrorDock is the processor. A data processing agreement is available on request. Choose a user identifier that is meaningful to you and no more identifying than it needs to be: an internal account id is usually a better choice than an email address.