Snapshot 298837

Document
Subprocessor list
URL
https://trust.testingbot.com/#subprocessors
Fetched
HTTP status
200
Content type
text/html; charset=utf-8
Fetch mode
static
Size
159313 bytes
SHA-256 (raw)
30d556ce53df7d8fa992a532bf951d948553dc7e6ee7dfa5d3e71bcfb3098436
SHA-256 (normalized text)
3c5aa71603dc4463849a6aed393adcb61ad16948dc973eb602c36d92d1a059e4

Raw (normalized text)

Scripts and page chrome removed; this is what change detection compares.

Skip to main content
Security & compliance
TestingBot Trust Center
TestingBot runs your cross-browser and mobile tests on infrastructure built in Europe. Encrypted at rest and in transit, GDPR & CCPA compliant, CSA STAR registered and audited from the network layer up.
Status & uptime Privacy policy Security whitepaper
Uptime SLA
99.9%
Hosting
EU only
Operating since
2012
Compliance trust.testingbot.com
CSA STAR L1
GDPR
CCPA
ISO
ISO 27001 datacenters
Europe‑hosted
DORA
DORA Art. 30 pack
AA
WCAG 2.1 AA
Bitsight rated
Encrypted · audited · monitored
Audited & certified
CSA STAR Level 1 GDPR ready
CCPA compliant
Regulation (EU) 2022/2554
DORA Art. 30 pack for financial entities
Filing a Register of Information, or adding TestingBot to a critical or important function? Our DORA pack states our Art. 30(2) and 30(3) position clause by clause and gives you the register data, sub-processor chain and incident-notification commitments you need to discharge your own obligations.
View the DORA Art. 30 pack
Clause-by-clause Art. 30 positions
Register of Information data
Sub-processor chain (CSV)
Incident-notification commitment
European data sovereignty
100% European infrastructure.
Every byte of your test data stays in Europe. TestingBot operates exclusively from European datacenters in the EU and Switzerland, giving you full GDPR compliance and data sovereignty by default.
Test logs & reports
All test execution logs and reports stored in European datacenters.
Video recordings
Test session videos recorded and stored within Europe.
Screenshots & artefacts
All test artefacts securely hosted in European infrastructure.
Test execution
Tests run on browser and device fleets located in European datacenters.
How we protect your data
Security controls
The technical and organizational controls we operate every day. TestingBot is not certified to ISO/IEC 27001 or SOC 2; our control set is modelled on ISO/IEC 27001:2022 Annex A, and our datacenter operators hold ISO 27001 certification.
Infrastructure security
AES-256 encryption at rest
TLS 1.2+ encryption in transit
European datacenters (EU and Switzerland) and data residency
Unique production authentication
MFA enforced on administrative access
Encrypted, monitored backups
Network segmentation and firewalling
Product security
Single-use VMs and devices, wiped after every session
Encrypted TestingBot Tunnel for private networks
Vulnerability scanning and dependency monitoring
Detectable secrets and PII masked before AI Insights, the AI assistant and AI region names process test data
Least-privilege access to customer data
Organizational security
Role-based, least-privilege access control
Access granted on onboarding, removed on offboarding
Asset inventory maintained
Security awareness across the team
Vetted, EU-first subprocessor selection
Data & privacy
30-day default retention for logs, video and screenshots
Configurable or immediate deletion on enterprise plans
Data deleted when an account is closed
No source code or passwords collected; any end-user PII in tests is processed only under the DPA
Data Processing Addendum with EU SCCs available
Resilience & monitoring
24/7 infrastructure monitoring and public status page
Documented incident response process
Business continuity & disaster recovery plan
Regular, tested backups
Independent security rating (Bitsight)
Vendors & suppliers
Subprocessors
The third parties TestingBot uses to deliver the service. We pick suppliers that align with our EU-first stance and that you would expect a SaaS vendor to use.
View the change log and subscribe to update notifications
Latest updates
August 16, 2026: Added Billit (Belgium), which registers the invoices we issue for our own accounting and was engaged before this notice. Billit receives the billing details printed on an invoice; it does not deliver invoices to customers and receives no test data.
July 29, 2026: Added Flow Swiss AG (Switzerland), which hosts our Swiss Mac mini fleet and was engaged before this notice. Clarified that Hetzner object storage is located in Helsinki, Finland. Removed Paddle.com Market Ltd, which was listed in error on July 27, 2026 and is not used to process any customer data.
July 27, 2026: Expanded the register for DORA Art. 28(3): added Bright Market, LLC / FastSpring (USA) and Vonage America, LLC (USA), which were engaged before this notice; clarified that transactional email (Postmark) is provided by ActiveCampaign, LLC; surfaced Cloudflare R2 and Hetzner object storage; corrected the AWS storage region to eu-west-1 (Ireland).
General subprocessors
Applicable to all TestingBot products.
Vendor	Purpose	Location
Sentry
Functional Software, Inc., 45 Fremont Street, 8th Floor, San Francisco, CA 94105, United States
Error tracking
Application error reports; may include an account email or IP address in stack-trace context. No test artefacts.
🇪🇺 Europe
Cloudflare
101 Townsend Street, San Francisco, CA 94107, United States
CDN, security and object storage (R2)
Request metadata and IP addresses for CDN and WAF; cached static assets; encrypted test artefacts in R2 object storage (EU jurisdiction).
🇺🇸 USA
Unix-Solutions
Hoge Wei 37, 1930 Zaventem, Belgium
Hosting
Hosts our EU infrastructure; account and test data at rest, encrypted.
🇪🇺 Europe
Hetzner
Industriestr. 25, 91710 Gunzenhausen, Germany
Hosting and object storage
Hosts our EU infrastructure; account and test data at rest, encrypted; encrypted test artefacts in object storage (Helsinki, Finland).
🇪🇺 Europe
Flow Swiss AG
Dufourstrasse 49, 8008 Zürich, Switzerland
Hosting (Swiss macOS device infrastructure)
Hosts our Swiss Mac mini fleet; account and test data at rest, encrypted.
🇨🇭 Switzerland
Amazon Web Services, Inc.
410 Terry Avenue North, Seattle, WA 98109, United States
Storage (S3, EU region)
Encrypted test artefacts (video, screenshots, logs) stored in the EU region (eu-west-1, Ireland).
🇪🇺 Europe
Google LLC (Google Cloud)
1600 Amphitheatre Parkway, Mountain View, CA 94043, United States
Geolocation Testing + AI Testing
Geolocation test routing; for codeless AI test runs, the test description and the content and screenshots of the pages the AI browser agent visits, not masked. Used only when a codeless AI test runs.
🇺🇸 Europe and USA
Stripe Inc.
354 Oyster Point Boulevard, South San Francisco, CA 94080, United States
Payment processing
Billing contact and card handled by Stripe; we store the last 4 digits only, never the full card.
🇺🇸 USA
Bright Market, LLC (FastSpring)
801 Garden Street, Santa Barbara, CA 93101, United States
Payment processing
Billing contact and payment details for purchases processed through FastSpring.
🇺🇸 USA
Vonage America, LLC
101 Crawfords Corner Road, Holmdel, NJ 07733, United States
SMS delivery (two-factor authentication and alerts)
Phone numbers and SMS message content for account verification and alerting.
🇺🇸 USA
ActiveCampaign, LLC (Postmark)
1 North Dearborn Street, 5th Floor, Chicago, IL 60602, United States
Transactional email delivery (Postmark)
Account name and email address for transactional and product emails.
🇺🇸 USA
Intercom
55 2nd Street, 4th Fl., San Francisco, CA 94105, United States
Customer support
Name, email address and the content of support conversations.
🇺🇸 USA
Billit
Oktrooiplein 1/302, 9000 Ghent, Belgium
Invoice generation and accounting
Billing contact name, billing email address, VAT number and postal address on the invoices we register for our own accounting. No test artefacts. Billit does not send invoices to customers; the invoice PDF comes from us.
🇪🇺 Europe
Feature-specific subprocessors
Used only by specific features within TestingBot products.
Vendor	Purpose	Location
OpenAI, L.L.C.	Codeless AI testing and documentation search
Codeless AI: the plain-language test description and the HTML of up to five public pages it names, to generate test steps, not masked; also a fallback model for codeless AI test runs. Used when someone creates or runs a codeless AI test, which has no account switch. AI assistants: documentation search queries. No model training.
🇺🇸 USA
Anthropic, PBC	AI test failure analysis (AI Insights), the AI assistants and AI region names for visual tests
AI Insights and the in-app AI assistant: masked, text-only test logs and the messages you send; on by account-owner consent, except the failure summary on GitHub pull request checks, which runs for failed pull request runs when the GitHub App is installed. AI region names: small crops of visual test screenshots around changed regions, sent unmasked, with masked page text; its own owner consent. Documentation assistant on the support pages: what the visitor types. No model training; deleted within 30 days.
🇺🇸 USA
Responsible AI
AI at TestingBot
TestingBot offers optional AI-powered features. Nothing is sent to an AI provider until one is used, the features that read your test results stay off until the account owner turns them on, and each is built to share as little of your data as possible.
AI Insights
Explains why a test failed and suggests fixes.
Codeless AI testing
Turns plain-language intent into automated test steps.
AI / MCP integrations
Connect TestingBot to AI agents through our MCP server.
Read how AI Insights handles your data
Our AI data guarantees
Owner consent for test data
AI Insights, the in-app assistant and AI region names stay off until the account owner turns them on, and can be turned off any time. Two features have no switch: the AI failure summary on GitHub pull request checks, and codeless AI, which is used only for tests someone writes as a plain-language description.
No model training
TestingBot does not train models on your data. Anthropic and OpenAI do not use data sent through their commercial APIs to train their models.
Minimized & masked
Only what a feature needs is sent: a small, text-only slice of the test for failure analysis, and small screenshot crops around each change for visual region names. Detectable secrets and PII in that text are masked before it leaves our servers; screenshot crops are not, so that feature has its own consent. Codeless AI reads the pages it tests, unmasked.
Short retention
Anthropic deletes failure-analysis and region-name inputs and outputs within 30 days; the generated analysis is pruned with the test on our side.
Named subprocessors
Anthropic, OpenAI and Google Cloud, under their Data Processing Addenda with EU Standard Contractual Clauses.
Downloads
Security & compliance documents
Everything procurement and security-review teams typically ask for, ready to download.
Data Processing Addendum (DPA)
pdf · download
Security Whitepaper
pdf · download
Technical & Organizational Measures (TOMs)
pdf · download
TestingBot CAIQ
xlsx · download
ISO 27001 certificate (Unix-Solutions datacenter)
pdf · download
ISO 27001 certificate (Hetzner)
pdf · vendor site
ISO 27001 certificate (Flow Swiss)
pdf · vendor site
Bitsight Report
pdf · download
Service Level Description (SLA)
pdf · download
DORA Art. 30 Clause Schedule
pdf · download
Register of Information Data Sheet
pdf · download
Exit Plan
pdf · download
Incident Notification Commitment
pdf · download
Privacy by default
Data we collect — and don't.
We keep the data footprint as small as possible. Below is the explicit list.
Employee business-card information
Name, email, phone. Used to manage your account.
Customer personally identifiable information (PII)
We don't extract or use end-user PII from your tests. Any that is present is processed only as your processor under the DPA.
Credit card information
Processed directly by Stripe. We never see your card.
Personal health information
Out of scope. We are not a healthcare service.
Source code
Not collected. Your test code stays in your CI/CD.
End-user passwords
Not collected, not logged, not transcribed.
Accessibility
We build the TestingBot dashboard to be usable by everyone and target conformance with the Web Content Accessibility Guidelines (WCAG) 2.1 level AA. Accessibility is an ongoing effort: if you encounter a barrier or need an accommodation, email info@testingbot.com and we will work with you on an alternative.
Responsible disclosure
Found a security issue? We welcome responsible disclosure. Email info@testingbot.com with the details and steps to reproduce. Every report is reviewed by our security team. We do not run a paid bug bounty, but we credit researchers in our hall of fame. Our machine-readable contact is published at /.well-known/security.txt.
Frequently asked
Trust & security FAQ.
Quick answers procurement, security and engineering teams ask us most.
Where is TestingBot hosted and where does my data live?
TestingBot is built and hosted exclusively in Europe. All test execution, video recordings, screenshots, logs and account data stay on European infrastructure, in the EU and in Switzerland (covered by a European Commission adequacy decision), and never leave the region. The exception is TestingBot's AI features: when one is used, the data described below for that feature is sent to our AI subprocessors in the United States.
Is TestingBot GDPR compliant?
Yes. TestingBot is fully GDPR compliant. We provide a Data Processing Addendum (DPA) on request, support EU data residency by default and operate under the EU's data-protection regime.
What certifications does TestingBot hold?
TestingBot is registered with the Cloud Security Alliance STAR Level 1 program (a published self-assessment), is GDPR and CCPA compliant, and operates from datacenters whose operators hold ISO 27001 certification. TestingBot is not itself certified to ISO 27001 or SOC 2; our control set is modelled on ISO/IEC 27001:2022 Annex A. Under the EU Digital Operational Resilience Act (DORA), TestingBot is an ICT third-party service provider, is not a designated critical ICT third-party provider, and offers a DORA Art. 30 pack with an Art. 30(2)/(3) contractual addendum.
Do you encrypt data at rest and in transit?
Yes. All data is encrypted at rest using AES-256 and in transit using TLS 1.2+ with modern ciphers. Test traffic between your network and our grid can be additionally tunnelled through the encrypted TestingBot Tunnel.
Do you use my test data to train AI models?
No. TestingBot does not train AI models on your data, and nothing is sent to an AI provider unless an AI feature is used. Anthropic and OpenAI do not use data sent through their commercial APIs to train their models.
Which AI subprocessors do you use, and are AI features opt-in?
Our AI subprocessors are Anthropic, OpenAI and Google Cloud, under their Data Processing Addenda with EU Standard Contractual Clauses. Not every AI feature has an account switch. AI Insights (test failure analysis) and the in-app AI assistant stay off until the account owner gives consent in the account settings; they use Anthropic, and the assistant uses OpenAI to search our documentation. One exception: when the TestingBot GitHub App is installed and a run started from a pull request fails, up to three of its failing tests are analysed by Anthropic for the AI summary on the pull request check, also without that consent. AI region names for visual tests have their own owner consent and use Anthropic. Codeless AI tests have no account switch: they are used when someone on the account creates or runs a test from a plain-language description. Generating its steps sends the description and the HTML of up to five public pages to OpenAI; running it lets an AI browser agent read the pages it visits, through our AI testing subprocessors. The documentation assistant on our support pages sends what you type to Anthropic. The account owner can withdraw either consent at any time.
How do you protect secrets and personal data when AI features run?
Before test data is sent for AI Insights, the in-app AI assistant or AI region names, an automated masking step redacts detectable secrets and personal data such as API keys, tokens, passwords, authorization and cookie headers, private keys, email addresses and card-number-shaped values. Failure analysis sends only a small, text-only slice of the test. AI region names for visual tests, a separate consent, also send small crops of the screenshot and baseline around up to eight changed regions per run; the text sent with them is masked, but the crops are not. Anthropic deletes these inputs and outputs within 30 days. Codeless AI tests are different: they work on the pages you point them at, and the test description and page content are sent without masking, so keep secrets out of a codeless test description.
How long do you retain test artefacts?
Default retention is 30 days for test logs, video recordings and screenshots. Enterprise plans can configure custom retention windows per asset type, including immediate deletion after the test if required.
Do you have a bug bounty program?
We don't run a paid bug bounty program, but we welcome responsible disclosure. Please reach out to info@testingbot.com, every report is reviewed by our security team and we credit researchers in our hall of fame.
Can I access TestingBot via SSO and enforce 2FA?
Yes. Enterprise plans support SAML 2.0 SSO with Okta, Azure AD, OneLogin and any SAML provider, plus organisation-wide 2FA enforcement.
More questions for our security team?
Send your security review, vendor questionnaire or DPA request to info@testingbot.com. We typically respond within one business day.
Contact security View status page