For health and personal data

Error tracking that never sees your users' personal data

Most error trackers send whatever is in the error: the message, the URL, the request, the SQL. In an app that handles health or personal records, any of those can hold a name, a date of birth, or an email. With strict privacy on, ForgeOps never receives them.

Strict privacy is on every plan, including Free. No credit card required.

Who it's for

Healthcare and health tech, fintech, HR and payroll software, legal, education, and anyone with GDPR obligations: teams that have been told they can't send personal data to a monitoring vendor.

What leaves your app, and what never does

Sent to ForgeOps

  • The error's type and stack trace (file, line, and function)
  • Release, environment, and server
  • The route it happened in, as a template like /patients/:id
  • A keyed hash of the user's id, only if you set a key, never a name or email
  • A one-way fingerprint of the message, with numbers, ids, emails, and quoted values taken out first

Stays in your app

  • Error messages
  • Context, tags, and breadcrumbs
  • URLs and query strings
  • SQL statements and captured source code
  • Session replays

When no route matched, only the first part of the path is sent (/patients/:path), since anything after it could name a person.

What still works

Errors are still grouped, by the fingerprint your app computes. ForgeOps still tells you which deploy an error started on, the likely cause, which customers are affected, and when it turns into an incident, with alerts and timelines as usual.

What you give up

Session replay and the AI summaries and search stay off for a strict project, since they need the text strict privacy keeps out. Issue titles come from the error's type and where it happened, such as RecordNotFound in PatientsController#show, not from its message.

Enforced on both ends

Turn it on in the SDK and in the project's settings. ForgeOps applies the same rules again when data arrives, so an app still running an older SDK can't get text stored.

Already using another tool?

Connect Sentry, Honeybadger, Datadog, or Splunk read-only, and the errors ForgeOps imports from it follow the same strict rules. Data already sent to that tool is handled by that tool, not ForgeOps. Read-only connections →


About compliance

ForgeOps doesn't make you HIPAA or GDPR compliant, and doesn't claim to. Strict privacy is designed so that personal and health data isn't sent to ForgeOps at all.

The documentation lists exactly what is sent, so your security or compliance team can check it against your own obligations.

See a strict project for yourself

The live demo has a Pharmacy API project with strict privacy on: open it to see what an issue looks like when no message, URL, or patient detail was ever sent.

Read the strict privacy docs →