TraceClaw · updated October 20, 2026

Privacy and data handling

01

Preliminary policy — pending owner approval. TraceClaw is a proprietary MVP. This page describes current processing and does not certify enterprise readiness.

02

TraceClaw reads signed GitHub pull-request events, repository identifiers, commit identifiers and changed-file patches. Local deterministic rules generate findings. Analysis identifiers, timestamps, findings, file locations and minimal matched operational constructs for new findings are stored in PostgreSQL. Historical findings may still contain short source snippets until operator cleanup. Full patches and source files are not persisted by the analysis pipeline.

03

GitHub receives findings and check results in the originating repository. GitHub sign-in protects analysis details, and repository access is checked on each request. Authentication tokens are protected by server-side cookie encryption. No external AI provider is implemented or active. Public GitHub profile identifiers can still be personal data; private repository code and production metrics remain customer-confidential, even when they contain no personal data.

04

Optional production telemetry requires a separately approved server-side configuration. An approved adapter may query aggregate metrics in the configured Datadog region. It must not upload source code or complete traces. Credential values must never appear in public configuration.

05

Essential browser storage: an HTTP-only authentication cookie holds the protected GitHub session and token; its authentication ticket has an eight-hour sliding expiry. OAuth uses a short-lived correlation cookie to validate sign-in. The application uses no analytics or advertising cookies, pixels, localStorage or sessionStorage and loads no external fonts. There are no optional tracking preferences to accept or reject in the current application. Infrastructure cookies and network logging are controlled separately by the deployment operator.

06

Hosting, GitHub and an enabled Datadog integration may process data outside Brazil. The operator must confirm actual processing regions, suppliers, transfer safeguards and contractual terms. No international-transfer approval is implied by this page.

07

You may request confirmation of processing, access, correction, information about sharing, or deletion where applicable through the configured support channel. Requests require proportionate identity and repository-authority verification. Deletion does not automatically remove copies in GitHub, backups or infrastructure logs. If no contact is configured, request intake is unavailable.

08

The responsible legal identity, privacy contact, lawful bases per activity, retention periods and supplier agreements still require owner confirmation and legal review. No consent is requested merely to browse this site or as a generic substitute for an appropriate legal basis.

09

The MVP does not enforce automatic data expiry. The operator must confirm retention, backup deletion and incident procedures before broad enterprise availability. Uninstalling stops future collection but does not delete existing analyses, logs or backups automatically. Contact support to request access or deletion.

Support contact is awaiting operator configuration.

Install TraceClaw · Data handling