Skip to content

Legal

Terms of Service

Updated 2 October 2026

These terms cover the hosted beta at errclue.com. Creating an account, signing in with GitHub, or sending events with a client key means you accept them.

The agreement

The agreement is these terms plus the Privacy Policy. errclue on this page means the service at errclue.com.

These pages do not name a separate company, a registered address, or a court. If a review needs a signed agreement or a governing-law clause, write to privacy@errclue.com before you send production traffic.

The service

errclue accepts Sentry SDK envelopes. You change the DSN. We store error and message events, group them into issues, and write a short diagnosis from the exception, the stack, and nearby source lines.

An envelope that contains only a session, a replay, or a transaction is answered and not stored. errclue does not offer session replay, tracing, or full application performance monitoring. It does not read a Git repository, and it does not open a pull request.

You can save an HTTPS Slack Incoming Webhook or a Discord channel webhook. A posted message is the issue label, an optional regression or frequency lead, the title, one sentence, and a link to the issue.

Beta and limits

The hosted beta is free. There is no paid plan and no invoice on this site. We can change the product, the limits on this page, or stop the beta. There is no uptime commitment.

A new organization starts with a monthly cap of 100,000 stored events. An organization with no cap set is not limited this way. Past the cap, ingest returns HTTP 429 and does not store the event.

A client key can also have its own rate limit. Past that limit, ingest returns HTTP 429 and does not store the event.

Accounts

You give a name, an email, and a password, or you sign in with GitHub. You are responsible for activity under your account, including client keys, auth tokens, and webhooks saved by owners and admins of your organization.

GitHub sign-in uses the provider default scopes, read:user and user:email. We do not ask for access to your repositories. An existing errclue account is linked only when GitHub reports that same email as verified.

Your events and your users

You choose what the SDK sends. An event can include stack traces, source lines, request URLs, tags, and anything else the SDK attaches, including an identifier or email address of a person using your application. You need the right to send that data, and you are responsible for the notice you give those people.

You keep ownership of the events, source maps, and other project data you submit. We keep ownership of the service, the site, and the errclue name and mark. We process project data to run the service, as the Privacy Policy describes.

Diagnosis

The diagnosis is a model guess. It can be wrong. It is not a patch, a security audit, or legal advice. The console shows confidence as an integer from 0 to 100 and a severity of low, medium, or high.

The prompt for that guess leaves out the request URL. It includes the exception, the stack, and nearby source lines when a source map or the SDK provided them.

Acceptable use

Do not use errclue to break the law, to probe another customer's project, to overload ingest on purpose, or to send data you have no right to send. Do not resell the hosted beta as your own error tracker. We can suspend a client key, a project, an organization, or an account that does this.

Other services

GitHub, Slack, Discord, Cloudflare, Google, and the xAI API are other companies' services. Their terms apply when you use them. A webhook URL you save receives the short message described above.

Availability and liability

The beta runs as available. Ingest, diagnosis, and webhook delivery can fail.

To the extent the law allows, errclue is not liable for lost profits, lost data, or other indirect damages. Our total liability for a claim about the service is limited to the amount you paid us for the service in the 12 months before the claim. During the free beta that amount is zero. Where the law does not allow a limit, the limit does not apply.

Stopping

You can stop sending events at any time. Deleting a project in the console removes it from the project list, turns off its client keys, and detaches its source maps. A source map bundle that is no longer attached to any project is deleted, including the stored files.

There is no button yet to delete an account. Write to privacy@errclue.com and we will delete the account and the organizations you alone own, except where we have to keep a record.

Changes

We can update these terms. The date at the top of the page changes when we do. If you keep using errclue after that date, the updated terms apply. If you do not accept them, stop using the service and write to privacy@errclue.com.

Contact

Questions about these terms go to privacy@errclue.com.