---
title: "Automatic Transmission of Usage Data"
slug: "automatic-transmission-of-usage-data"
updated: 2026-08-07T12:07:37Z
published: 2026-08-07T12:07:37Z
canonical: "help.hyperscience.ai/automatic-transmission-of-usage-data"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.hyperscience.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Automatic Transmission of Usage Data

In v39 and later, on-premise, internet-connected instances send Usage Reports (v41 and earlier) or Usage Bundles (v42 and later) to Hyperscience. These exports are sent daily and contain data on the use and configuration of Hyperscience over the past seven days. To learn more about the contents of this export, see the “Usage Report” or “Usage Bundle” article for your version of Hyperscience ( [v38](/general-information/docs/v38-usage-report) | [v39](/v39/docs/usage-report) | [v40](/v40/docs/usage-report) | [v41](/v41/docs/usage-report) | [v42](/v42/docs/usage-report) | [v43](/v43/docs/usage-bundle) ).

The automatic transmission of usage data is enabled by default. It is not possible to change the frequency or content of the automatic transmissions.

## Instances not connected to the internet

If your instance is not connected to the internet, you need to disable automatic transmissions by entering the following in your “.env” file:

```powershell
HS_AUTOMATED_USAGE_AND_SETTINGS_TRANSMISSION_ENABLED=false
```

> [!WARNING]
> Because automatic transmission is the default method for sending usage data to Hyperscience, you need to send your usage data to Hyperscience through an alternate method that your Hyperscience representative has reviewed and agreed to.

## Instances connected to the internet

Depending on your organization’s security measures, you may need to take additional action to allow the automatic transmission of usage data.

### Configuring a proxy

Your IT team may determine that a proxy is needed in order to transmit usage data. If you’ve already configured a proxy for Hyperscience by following the steps in [Proxy Server](/deployment/docs/proxy-server), that proxy configuration will be used to transmit the data. If a different proxy is required, you will need to enter values for the ".env' variables that are relevant to your organization’s security policies:

```powershell
HS_AUTOMATED_USAGE_AND_SETTINGS_TRANSMISSION_PROXY_USERNAME=<username>

HS_AUTOMATED_USAGE_AND_SETTINGS_TRANSMISSION_PROXY_HTTP=<address in the form proto://host:port>

HS_AUTOMATED_USAGE_AND_SETTINGS_TRANSMISSION_PROXY_HTTPS=<address in the form proto://host:port>

HS_AUTOMATED_USAGE_AND_SETTINGS_TRANSMISSION_PROXY_CERTIFICATE_PATH=<path to certificate>

HS_AUTOMATED_USAGE_AND_SETTINGS_TRANSMISSION_PROXY_KEY_PATH=<path to key>
```

### Configuring a firewall for outbound requests

If your IT team has configured a firewall that prevents the system from issuing outbound requests, work with them to allow requests to be sent to *https://usage-reporting.hyperscience.net.*

### Configure a custom CA bundle

If your instance validates outbound connections against a custom CA bundle, that bundle needs to include the root certificates used by the usage data endpoint. Otherwise, the daily transmission fails certificate validation.

> [!WARNING]
> A custom CA bundle replaces the default set of trusted root certificates.
> 
> When you set the `HS_TLS_CA_BUNDLE` ".env" variable, the application no longer trusts any root certificate that isn't in your bundle. To learn more, see [HS_TLS_CA_BUNDLE](/deployment/docs/security#hstlscabundle-recommended) in Security.

The certificate presented by `https://usage-reporting.hyperscience.net` chains to a root operated by Amazon Trust Services, so you need to add that root to your bundle. Amazon Trust Services recommends including all of its roots in a custom trust store, because the root that a given endpoint chains to can change.

To add the Amazon root certificates to your bundle:

1. Go to Amazon Trust Services' [Repository](https://www.amazontrust.com/repository/#certification-authorities) page, and in the **Certification authorities** section, download the **PEM** version of each root CA certificate.
2. Copy the downloaded files to the `certs` directory used by your deployment (for example, `/mnt/hs/certs`).
3. Append the certificates to the bundle file named by `HS_TLS_CA_BUNDLE`:

```bash
cd $HS_PATH/certs
cat AmazonRootCA1.pem AmazonRootCA2.pem AmazonRootCA3.pem AmazonRootCA4.pem SFSRootCAG2.pem >> <CA_bundle_filename>
```
4. Give the application read access to the bundle:

```bash
chmod 644 $HS_PATH/certs/*
```
5. If SELinux is enabled, restore the file context:

```bash
chcon -t container_file_t -R $HS_PATH/certs/
```