On this page
ScopeInformation we collectCustomer service dataHow we use itHow we shareIntegrations & third partiesCookies & analyticsRetentionInternational transfersYour rights & choicesContactPrivacy Policy
What we collect, why, who we share it with, and the controls you have. This policy distinguishes the account data we control from the telemetry you send us and remain the controller of.
01Scope
This policy covers errorgap.com, the Errorgap dashboard, and our APIs. It distinguishes two categories of data with different roles.
| Category | What it is | Our role |
|---|---|---|
| Account data | Names, work emails, org and billing details you give us. | We are controller |
| Service data | The error events, logs, traces, and metadata your apps send. | You are controller |
02Information we collect
Account and usage data we collect directly to run the service.
- Identity — name, work email, password hash, org membership.
- Billing — plan, billing contact, and a token from our payment processor. We never store card numbers.
- Usage — dashboard activity and feature usage for reliability and product analytics.
- Device — IP and user-agent for security, abuse prevention, and clickwrap records.
03Customer service data
Service data is the telemetry your applications transmit. You decide what to send and you remain its controller; we process it on your instructions.
04How we use information
We use data to provide, secure, and improve the service — never to sell it.
- Operate the product: ingest, correlate, alert, and display your telemetry.
- Secure the platform: detect abuse, enforce limits, investigate incidents.
- Support and billing: respond to requests and process payment.
- Improve the product: aggregate, de-identified usage analysis.
06Integrations & third parties
When you connect GitHub, GitLab, Jira, or Slack, data flows to those services under their terms and the scopes you grant. You can revoke a connection at any time.
- Only the data needed for the action (e.g. an issue body) is sent.
- Scopes are visible on the project Integrations settings page.
- Revoking a connection stops future sharing immediately.
07Cookies & analytics
We use a small set of first-party cookies. Detail and choices live in the Cookie Notice.
| Type | Purpose | Status |
|---|---|---|
| Essential | Sign-in session and security. Cannot be disabled. | Always on |
| Analytics | First-party, aggregate product usage. | Opt-out |
| Advertising | No third-party ad or tracking cookies. | None |
08Retention
Account data is kept for the life of the account; service data follows the retention you configure. See the Security page for the full retention table.
Service-data retention is set per project and enforced automatically. When you delete data or request a deletion, it is removed from primary storage; copies in encrypted backups persist until the hosting provider's backup retention window elapses.
09International transfers
Today the service runs in the US. We rely on standard contractual clauses for transfers from the EU/UK; an EU data-residency region is planned.
10Your rights & choices
Subject to your local law, you can access, correct, export, or delete your data. Org admins can act on most of this self-service.
- Access & export — self-service org export, or email privacy@errorgap.com.
- Deletion — delete projects, telemetry, or the whole account from settings.
- Objection & complaints — contact us; you may also complain to your supervisory authority.