> For the complete documentation index, see [llms.txt](https://docs.currents.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.currents.dev/resources/data-privacy/access-to-customer-data.md). # Access to Customer Data {% hint style="info" %} If you have any concerns or questions, please refer to or contact us through our support channels. {% endhint %} ## What types of data does Currents have access to? We collect diverse data from our users' test suites, which are strictly limited to their specific use cases, test executions, or administrative purposes within the organization. Below is a list of the data collected and processed by Currents. ### Team / Administration * Team member emails * Team member names (provided by administrators - might not be real names) * IP addresses used to access the system ### Register Survey - Onboarding Form * Organization name (might not be a real name) * Estimated amount of tests * Estimated organization size * Domain of the organization (based on the registration email) * Project name ### Test Results * Test runner configuration * Test results and timing * Test execution steps details * Test errors and exceptions * Test source code snippets accessible in testing framework results ### Artifacts * Playwright traces * Screenshots * Videos * Terminal stdout and stderr produced while executing a test ### CI Environments * **Git information**: commit message, commit sha, commit branch, commit author, remote origin. * **CI-specific:** Environment variables, build ID, pipeline ID, CI provider type, Pull Request details. * **Machines:** OS type, OS memory, CPU type. ### Integrations * **GitHub**: No access to data or repos source code; we post comments and status check updates for Pull Requests. The integration application is listed here: , and the list of permissions appears as part of the setup. * **GitLab**: We list repositories and projects, refresh oAuth tokens, post notes and status check updates to Merge Requests, fetching Merge Request details. * **BitBucket**: No access to data; we only post status check updates for Pull Requests. * **Microsoft Teams, Slack**: No access to data, just posting messages within the restrictions of the platform's rules. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.currents.dev/resources/data-privacy/access-to-customer-data.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.