Currents Documentation
Currents.devGitHubChangelog
  • Getting Started
    • What is Currents?
    • Playwright
      • Playwright: Quick Start
      • Troubleshooting Playwright
    • Cypress
      • Your First Cypress Run
      • Integrating with Cypress
        • Compatibility
        • Alternative Cypress Binaries
      • Troubleshooting Cypress
    • Jest
      • Your First Jest Run
      • Detox + Jest
      • Troubleshooting Jest
    • Others
    • CI Setup
      • GitHub Actions
        • Cypress - GitHub Actions
        • Playwright - GitHub Actions
        • Jest - GitHub Actions
        • Node.js - GitHub Actions
        • Commit data for GitHub Actions
        • Custom Docker runners
        • Named Runners
      • GitLab
        • Cypress - GitLab CI/CD
        • Playwright - GitLab CI/CD
        • Custom Docker runners
      • Jenkins
        • Cypress - Jenkins
        • Playwright - Jenkins
      • CircleCI
        • Cypress - CircleCI
        • Playwright - CircleCI
      • Bitbucket
        • Cypress - Bitbucket Pipelines
      • Azure DevOps
        • Cypress - Azure DevOps
        • Playwright - Azure DevOps
      • AWS Code Build
        • Cypress - AWS Code Build
        • Playwright - AWS Code Build
      • NX
        • Playwright - NX
        • Cypress - NX
  • Guides
    • Record Key
    • CI Build ID
    • Reporting
      • Reporting Strategy
      • Reporting in CI
      • Step-Level Reporting
    • CI Optimization
      • Playwright Parallelization
      • Orchestration Setup
      • Fully Parallel Mode
      • Re-run Only Failed Tests
      • Cloud Spot Instances
      • Failing Fast
      • Load Balancing
    • Code Coverage
      • Code Coverage for Playwright
      • Code Coverage for Cypress
    • Currents Actions
      • Setup Currents Actions
      • Using Currents Actions
      • Reference
        • Conditions
        • Actions
    • Playwright Component Testing
    • Playwright Visual Testing
    • Playwright Annotations
    • Playwright Tags
    • MCP Server
  • Dashboard
    • Projects
      • Projects Summary view
      • Project Settings
      • Archive and Unarchive Projects
    • Runs
      • Run Status
      • Run Details
      • Commit Information
      • Tags
      • Run Timeouts
      • Cancelling Runs
      • Deleting Runs
      • Run Progress
    • Tests
      • Spec File Status
      • Test Status
      • Flaky Tests
      • Test History
    • Test Suite Explorer
      • Test Explorer
      • Spec Files Explorer
      • Error Explorer
      • Reference
  • Automated Reports
  • Insights and Analytics
  • Administration
    • Email Domain Based Access
    • SSO SAML2.0
      • SAML2.0 Configuration
      • SCIM User Provisioning
      • IdP-initiated Sessions
      • JumpCloud
        • JumpCloud User provisioning
      • Okta
        • Okta User provisioning
      • Troubleshooting SSO
    • Billing & Usage
  • Billing and Pricing
  • Resources
    • Reporters
      • cypress-cloud
        • Batched Orchestration
        • Migration to Cypress@13
      • @currents/cli
      • @currents/playwright
        • Configuration
        • pwc
        • pwc-p (orchestration)
        • Playwright Fixtures
      • @currents/jest
      • @currents/node-test-reporter
      • @currents/cmd
        • currents api
        • currents upload
        • currents cache
        • currents convert
      • Data Format Reference
    • Integrations
      • GitHub
        • GitHub App
        • GitHub OAuth
      • GitLab
      • Slack
      • Microsoft Teams
      • HTTP Webhooks
      • Bitbucket
    • API
      • Introduction
      • Authentication
      • API Keys
      • Errors
      • Pagination
      • API Resources
        • Instances
        • Runs
        • Projects
        • Spec Files
        • Test Signature
        • Test Results
    • Data Privacy
      • Access to Customer Data
      • Data Retention
      • Cloud Endpoints
    • Support
Powered by GitBook
On this page
  • What types of data does Currents have access to?
  • Team / Administration
  • Register Survey - Onboarding Form
  • Test Results
  • Artifacts
  • CI Environments
  • Integrations

Was this helpful?

  1. Resources
  2. Data Privacy

Access to Customer Data

Overview of Customer Data that Currents collects during its execution

PreviousData PrivacyNextData Retention

Last updated 1 year ago

Was this helpful?

If you have any concerns or questions, please refer to or contact us through our support channels.

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

  • 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.

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.

https://currents.dev/security
https://github.com/apps/currents-bot