1. Support
  2. Knowledge base
  3. Checkpoints
  4. Private location data protection

Private location data protection

In this knowledge base article, you will find an explanation on how to implement data protection on your private locations. One of the safeguards implemented in Uptrends' private locations is preventing snapshots from being uploaded to the cloud. You can also disable page content, hide HTTP request and response headers and resolved IP addresses in check results.

Editing the Docker Compose file

First, if you have not already done so, install your checkpoint by following the steps explained in Install a Docker checkpoint.

  1. Make a backup of the extracted Docker Compose file. Please be aware that if you make changes to the provided compose file this is at your own risk. Contact Support if you are not sure.
  2. Open the docker-compose.yml file and add the variable(s) to the Checkpoint service (in this example disabling screenshots by inserting AllowScreenshotsInResults=false):
Checkpoint:
   container_name: Checkpoint
   image: uptrends.azurecr.io/win2022/checkpoint
   depends_on:
     - TransactionProcessor
   deploy:
     restart_policy:
       condition: always
   volumes:
     - .\Certificates:C:\Uptrends\Certificates:ro
   logging:
     driver: "json-file"
     options:
       max-size: 10m
       max-file: "3"
   environment:
    - ServerId=
    - Password=
    - AllowScreenshotsInResults=false
  1. Save your file.
  2. Wait for the Docker container to update or update manually by typing this in the command-line of the used folder where the file lives.

Prevent (error) screenshots and filmstrips from uploading to the cloud

After the setting is active, the check details in Uptrends will display a text to inform you that screenshots are not collected due to your company’s data protection policy.

This holds true for all screenshots, including timeline screenshots (also called filmstrips) and the error screenshot for an HTTP(S) monitor.

To disable screenshots in results, add - AllowScreenshotsInResults=false to the (list of) Checkpoint environment variables.

Important: Disabling screenshots means just that. No screenshots will be made. So, when troubleshooting an error, this source of information will not be available.

Disable page content

This setting will make sure no content is being shown in the page source and console log. Data URLs will always be displayed without data in the results.

To disable page content in results, add - AllowPageContentInResults=false to the (list of) Checkpoint environment variables.

Hide HTTP request and response headers

After this setting is active, the check details waterfall chart will not show any HTTP request and response headers.

To hide HTTP request and response headers add - AllowHttpHeadersInResults=false to the (list of) Checkpoint environment variables. Data protection hidden HTTP request and response headers in Waterfall Chart

Disable resolved IP addresses for request and response headers

This setting makes sure that the report header in a waterfall’s check result does not show any resolved IP addresses. Please note this will not work if there is an actual IP address in an URL. (Read more about the results of the waterfall report in our knowledge base.)

To hide resolved IP addresses add - AllowResolvedIpAddressesInResults=false to the (list of) Checkpoint environment variables.

Disable resolved IP addresses in check details

This setting controls that the FPC’s check details do not show any resolved IP addresses listed at Resolved IP address. (At the check details top summary of the monitor, above the Core Web Vitals details).

To hide resolved IP addresses add - AllowResolvedIpAddressesInResults=false to the (list of) Checkpoint environment variables.

Please note: Private locations Beta data protection is still in development. Not all settings cover every monitor type, e.g., for basic HTTP(S) monitors only error screenshots will work, the resolved IP settings are not applicable to this type of monitor.
By using the Uptrends website, you consent to the use of cookies in accordance with our Cookie Policy.