Appearance
Personal Data Protection & Privacy Policy
Effective 17 November 2026.
This policy explains the personal and account data EasyTrace processes when you visit easytrace.dev, sign in, use the dashboard, create an organisation or project, upload test results, or contact us about the service.
Data we process
EasyTrace processes the information needed to authenticate users, control access, receive uploads and show test history.
| Category | Examples | Purpose |
|---|---|---|
| GitHub account data | GitHub ID, username, display name, email and avatar where GitHub provides them | sign-in, account display and access control |
| Organisation and project data | organisation and project names, membership, project settings and token metadata | managing workspaces, projects and credentials |
| Run metadata | test framework, CI provider, build URL and ID, branch, commit SHA and message, operating system, Node version and uploader | grouping, displaying and troubleshooting runs |
| Test data | test names, files, statuses, durations, retries, failure messages, output and steps | showing results, history, flaky tests and new failures |
| Coverage and artifacts | coverage paths and metrics; optional screenshots, video, trace, log and attachment files | displaying coverage and the artifacts you choose to upload |
| Technical data | timestamps, token-use times, security and error logs, browser or device characteristics | operating, protecting and improving the service |
| Site analytics | pages viewed, referrer, approximate location, device and browser, from easytrace.dev | understanding which documentation and pages are read |
Do not upload passwords, access tokens or other secrets in a report, log or artifact. EasyTrace does not need them to provide the service.
How we use data
We use data to authenticate and authorise users; accept and display uploads; calculate run, coverage and retention information; maintain the security and reliability of the service; diagnose faults; prevent abuse; and comply with legal obligations where applicable.
We do not sell personal data or use uploaded test data to advertise to you. We process uploaded data only to provide, maintain, secure and improve the EasyTrace features you use.
Analytics cookies
easytrace.dev, including this documentation, uses Google Analytics to count page views and see which pages are read. On your first visit a banner asks whether you allow analytics cookies. Until you accept, no analytics cookie is set; Google Analytics receives only cookieless signals, such as the page viewed and the time, that cannot tell your visits apart. If you accept, Google Analytics sets first-party cookies that recognise your browser across visits, for up to two years. Advertising features are always off, and we do not combine analytics data with your EasyTrace account or uploaded data.
Your choice is kept in your browser. To change it, use Cookie settings in the site footer, or clear this site's data in your browser.
Who can see data
Members of an EasyTrace organisation can access that organisation's projects and run data according to their role. Organisation administrators manage membership; project credentials upload only to their assigned project. EasyTrace personnel may access data when needed to operate the service, investigate an issue or provide support.
We may share data with providers where needed to operate EasyTrace, such as GitHub for sign-in, your CI provider where you choose to link to a build, Google Analytics for measuring visits to easytrace.dev, and infrastructure, hosting, storage, monitoring and security providers. We may also disclose information where required by law or reasonably necessary to protect EasyTrace, its users or the public, enforce our terms, or investigate fraud or a security incident.
Retention and deletion
EasyTrace automatically removes run history after the retention period of the organisation's plan. The current plan limits are 30 days for Free, 180 days for Team and 365 days for Business. Deleting a project immediately and permanently removes its runs, results, coverage, test history and associated artifacts from EasyTrace.
Artifacts are retained for the project's configured retention period, up to the plan limit: 14 days for Free, 30 days for Team and 90 days for Business. When an artifact expires, its stored file is deleted; its metadata may remain with the run while that run is retained.
Revoking a project token or CLI session immediately prevents it from being used. Refresh-session and CLI-session records expire or are revoked according to the service's authentication rules. We may retain limited data for longer where necessary to meet a legal obligation, resolve a dispute, prevent abuse or protect the security of the service.
Deleting data from EasyTrace does not delete information that GitHub, a CI provider, your organisation or another third party stores independently.
Security
We use reasonable technical and organisational measures designed to protect data from unauthorised access, alteration, disclosure and loss. These measures include authentication, access controls, credential hashing, monitoring and processes for investigating security issues. No internet service or storage system can be guaranteed completely secure.
You are responsible for protecting your GitHub account, managing organisation membership, choosing who receives project tokens, and selecting only data you are authorised to upload. Revoke exposed credentials promptly.
International processing and requests
EasyTrace and its providers may process data in countries other than the country where you live or work. Those countries may have different data-protection laws. Where required, we use safeguards appropriate under applicable law.
Depending on applicable law, you may have rights to request access, correction, deletion, restriction, objection or a copy of your personal data. Email contact@codefilter.dev with your GitHub account, organisation and request. We may need to verify your identity and authority before acting.
Policy changes
For a material change, we will update the effective date and publish the revised policy here or in the app. Your continued use of EasyTrace after it takes effect means that you acknowledge the updated policy. The Terms of Service also apply to your use of EasyTrace.