Third Party Cookie Provider

Third Party Cookie Provider Purpose Type
    Strictly Necessary Cookie
Facebook Inc. 1601 S. California Ave, Palo Alto, CA 94304, USA Facebook is used by Tricentis for advertising, display ads and retargeting. For more information on Facebook’s cookie practices, please visit www.facebook.com/policies/cookies/ Following types of cookies are in use Facebook Pixel Facebook Seite Facebook Custom Audiences Optional Cookie Third Party Cookie Provider
Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA Google Analytics is an ad management and ad serving technology. Google Analytics places cookies on the Tricentis Sites so that Tricentis can record how many signups and leads originated from its marketing activity. For information on how to reject or delete this cookie, please visit: https://www.tools.google.com/dlpage/gaoptout Following types of cookies are in use Google Ads Google Conversion Tags Google Remarketing Tags Google Analytics (Senden von PageViews, Senden von PageViews) Google Tag Manager Google DataStudio (Übertragung von Tools in Datastudio —> Problem ist das Hosting in US) Google Optimize Google Search Console (hat keinen direkten Connex von SpecFlow zum User) YouTube Optional Cookies Third Party Cookie Provider
Twitter Inc. 1355 Market Street, Suite 900, San Francisco, CA 94103, USA Twitter is used by Tricentis for advertising, display ads and retargeting. For more information on Twitter’s cookie practices, please visit https://help.twitter.com/en/rules-and-policies/twitter-cookies  Following types of cookies are in use Twitter Pixel (Wird beim Relaunch aber entfernt) Twitter Page Optional Cookies Third Party Cookie Provider
LinkedIn LinkedIn is used by Tricentis for advertising, display ads and retargeting. For more information on LinkedIn’s cookie practices, please visit https://www.linkedin.com/legal/cookie-policy  Following types of cookies are in use LinkedIn Pixel (Wird beim Relaunch aber entfernt) LinkedIn Page Optional Cookies Third Party Cookie Provider
Sub-Processors Purpose Type
Microsoft

We use Azure Application Insights, an analytics platform provided by Microsoft to improve the quality of our tools . Only anonymous usage data is transferred to Azure Application Insights, for further details, please see Microsoft’s documentation. You can disable these analytics if you do not wish to share this information.

Tracking in SpecFlow:

  • Unique anonymous user identifier
  • Target framework(s) of projects that uses SpecFlow
  • Operating system platform
  • Project GUID of projects that uses SpecFlow
  • MSBuild Version
  • SpecFlow version in use
  • Unit test provider
  • Running as build server flag
  • Build server identifier
  • Hashed assembly name (SHA256)

Tracking in SpecFlow for Visual Studio:

  • Unique anonymous user identifier
  • Name of the IDE
  • Visual Studio version
  • Target framework(s) of projects
  • Extension version
  • Previously installed extension version
  • Running in Docker container flag
  • Unit test provider

Tracking in SpecFlow for Rider:

  • Unique anonymous user identifier
  • Name of the IDE
  • Rider version
  • Extension version

Tracking in SpecFlow+ Runner:

  • Unique anonymous user identifier
  • Target framework in use
  • Operating system
  • Platform Version
  • Running as build server flag
  • Build server identifier
  • Running in Docker container flag

Tracking in SpecFlow+LivingDoc and SpecMap:

Our products installed as extensions on Azure DevOps or Azure DevOps Server store user created data on the hosting infrastructure where the extension is installed. All data stored by the extensions remains within the host infrastructure. For further details, please see Microsoft’s privacy policy by clicking on this link. The following data is automatically collected by Azure Application Insights:

  • Web server telemetry: HTTP requests, URI, time taken to process the request, response code, client IP address. session ID.
  • Web pages: Page, user and session counts, page load times, exceptions, Ajax calls.
  • Performance counters: Memory, CPU, IO, network occupancy.
  • Client and server context: OS, locale, device type, browser, screen resolution.
  • Exceptions and crashes: Stack dumps, build ID, CPU type.
  • Dependencies: Calls to external services such as REST, SQL, AJAX. URI or connection string, duration, success, command.
  • Availability tests: Duration of test and steps, responses.

We track the following additional anonymous data:

  • Unique anonymous user identifier
  • Host GUID
  • Collection GUID
  • Project GUID
  • Extension version
  • Platform (Azure DevOps or Azure DevOps Server)
  • Platform version
  • License information (SpecMap)

Tracking in SpecFlow Gherkin Editor:

SpecFlow Gherkin Editor is a hosted online service provided by SpecFlow. We collect both anonymous and non-anonymous usage data, which is transferred to Azure Application Insights, for further details, please see Microsoft’s documentation by clicking on this link. · User-created Data. Content (.feature files) created and saved with the SpecFlow Gherkin Editor is stored stored on Microsoft Azure servers in the EU.

Anonymous data:

  • Unique anonymous user identifier
  • Text field activations
  • Sign-in to save
  • Save. feature file
  • Download as .feature file
  • Copy to clipboard

Non-anonymous data:

  • last sign-in date
  • last modified date
  • number of .feature files per account

We store the following user created data:

  • .feature file content
  • Sharing status of the .feature files

We are not processing or analyzing the content of the uploaded .feature files in SpecFlow Gherkin Editor. We use Microsoft Azure servers in the EU for storage and hosting of this service.

Tricentis Sub-Processor
MailChimp Sending subscriber data from website to MailChimp Creation/management of different mailings Hosting of mailing data Tricentis Sub-Processor
Kinsta Website-Hosting Server Log-Files Tricentis Sub-Processor
Zendesk Support ticketing system for Tricentis Products: SpecFlow, SpecFlow+ Runner, SpecFlow+LivingDoc, SpecMap, SpecFlow Gherkin Editor Support tickets are handled using Zendesk. Information on how Zendesk complies with the GDPR can be found here. Access to the ticketing system is restricted to those employees at Tricentis who require access to the tickets in order to respond to customer inquiries, complete purchase orders and provide technical support (including troubleshooting and reproducing issues). Tricentis  Sub-Processor
HotJar Implementation of a HotJar-Pixels Different user surveys Depending on survey data this data may contain contact details Tricentis Sub-Processor
RedTheDocs Usage manuals of SpecFlow software Hosted by ReadTheDocs  
Discord Chats between SpecFlow and its user community  
GitHub Interactions with our code repos