Appearance
Security & Data Privacy Policy
Effective 10 October 2026.
EasyTrace receives the output of your automated tests; it does not connect to or clone your repository. This policy explains the current scope of that data. See the Privacy Policy for personal-data processing.
What EasyTrace receives
The EasyTrace CLI reads report files and sends their parsed contents to the EasyTrace API. Depending on the report format and options you use, that may include:
- test titles, source-file paths, browser names, statuses, durations, retries, tags and annotations;
- failure messages, stack traces, standard output, standard error and test steps;
- coverage file paths and aggregate or per-file coverage metrics;
- build metadata such as CI provider, build URL and ID, commit SHA and message, branch, pull request number, operating system and runtime version; and
- optional artifacts that you explicitly upload, including screenshots, videos, traces, logs and attachments.
The CLI also detects CI metadata from its environment and, for local runs, reads Git metadata and the local username where available. It does not need a copy of your source repository to upload a report.
What you control
You choose which report files the CLI uploads, which suites to include, whether to upload coverage, and whether to attach artifacts.
Treat report content as potentially sensitive. Test names, error messages, logs, file paths, commit messages and artifacts can contain application or personal data. Do not upload secrets, passwords, tokens or data you are not authorised to share. Review artifact uploads carefully because they can contain screenshots, traces or files created by the test environment.
Access and credentials
People sign in through GitHub. EasyTrace stores the account information needed to identify users and control their access; it does not store a GitHub access token. Organisation membership controls access to organisation data.
Project tokens are scoped to a single project and are stored as hashes. CLI-session tokens are personal credentials and are also stored as hashes. The complete value of a project token is shown only when it is created. Revoke a token or session immediately if you suspect exposure.
Storage, retention and deletion
EasyTrace stores run metadata, test results, coverage information and uploaded artifacts so that it can show history, flaky-test signals, new-failure comparisons and coverage trends. Run data is deleted automatically when it exceeds the organisation plan's result-retention period. Deleting a project immediately and permanently removes its associated EasyTrace data.
Artifact files expire according to the project's artifact-retention setting and plan limit. Once an artifact expires, its stored object is deleted and can no longer be downloaded. See Privacy Policy for the current retention periods.
Security practices and limits
EasyTrace uses access controls, authenticated requests, hashed credentials, scoped project tokens, encrypted transport and monitoring intended to protect the service and the data it processes. Access is limited to authorised organisation members and personnel who need it to operate or support the service.
No system is completely secure. Keep your CI secrets in the CI provider's secret store, restrict access to your EasyTrace organisation, rotate exposed credentials, and maintain your own security controls and backups. A passing run or an absence of visible failures is not a security guarantee.
Changes and reporting
We may update this policy as the service changes. Material changes will be published here or in the app with a revised effective date. To report a suspected security issue or request help with data access, email contact@codefilter.dev and do not include secrets in the initial message.