Icon

You are viewing the documentation of TeamCity 2018.x, which is not the most recently released version of TeamCity.
View this page in the latest documentation or refer to the listing to choose the documentation corresponding to your TeamCity version.

 

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

In relation to the TeamCity product, JetBrains does not collect any personal data of the final op-premises TeamCity installation users. The related documents governing relationship of users customers with JetBrains are available on the official web site: privacy policy, terms of purchase, TeamCity license agreement.

...

  • full name and username - stored in the database and shown on the user's profile and whenever the user is referenced. When a user triggers a build, these are also stored in the build's parameters and passed into the build
  • user's email - stored in the database and shown on the user's profile, used to send out notifications
  • IP adderss address of the clients accessing the server - can appear in the internal logs

...

If you want the users to accept a special ageement agreement before using your TeamCity instance, you can install a dedicated plugin developed by JetBrains for this purpose. Refer to the pluginsplugin's documentation for more details.

...

If you want to encrypt the data used by TeamCity, it is recommedned recommended to use generic, non-TeamCity-specific tools for this as TeamCity does not provide dedicated funcaionalityfunctionality.
TeamCity stores the data in the SQL database and on the file system.
You can configure the database to store the data in encrypted form and use secure JDBC-backed connection to the database (configured in the database.properties).
Also, you can configure encryption on the disk storage on the OS level.

...