---
title: "Licensing and usage reporting"
description: "How Alchemy licensing and usage reporting keep you within the terms of your EULA."
product: "Alchemy"
edition: "Public"
type: "overview"
url: "https://docs.cloudhouse.com/public/licensing-and-reporting/licensing-and-usage-reporting-overview/"
---
# Licensing and usage reporting

Alchemy's Licensing and Usage Reporting features ensure that you are compliant with the Terms and Conditions of your End User Licensing Agreement (**EULA**) for creating and managing Alchemy Compatibility Packages. These features also help you understand application usage patterns within your business, including information on how many people use each application, on which operating system, when, and how often.

Applies to: `Alchemy`

If the website and port requirements are met, Alchemy Compatibility Packages automatically report their usage data whenever the following Compatibility Package-related events occur:

- Deployment.
- Start.
- Uninstall.

For more information, see [Requirements for Deploying and Running Alchemy Compatibility Packages](https://docs.cloudhouse.com/public/deploying-packages/requirements-for-deploying/index.md).

!!! tip

    A valid Online Reporting Token must be present in the Compatibility Package’s root folder upon deployment and prior to the first run. On the first run, a Run Token is copied to the relevant location depending on the deploy type. A Compatibility Package will fail to deploy or run successfully without a valid Online Reporting Token or Run Token.

## Deployment event reporting

A deployment reporting event is recorded each time the `Cloudhouse.Container.Deployment.exe` is triggered, whether by command line, script or deployment tool. The event reports if a Compatibility Package deploy or uninstall operation is performed.

!!! note

    Compatibility Packages can be deployed into a Virtual Desktop Infrastructure (**VDI**) environment using a Golden Image from which computers are created. When the Compatibility Package is deployed into the Golden Image, only a single deployment event is recorded. Deployment events are not reported when the image is cloned.

!!! tip

    Different URLs and behaviour occurred in previous versions of Usage Reporting. See [DEPRECATED: Alchemy Automated HTTPS Usage Reporting](https://docs.cloudhouse.com/public/licensing-and-reporting/deprecated/deprecated-alchemy-automated/index.md) for details.

## Run event reporting

An asynchronous usage event is recorded each time the `Cloudhouse.Container.Run.exe` is triggered during an application start event.

!!! tip

    Different URLs and behaviour occurred in previous versions of Usage Reporting. See [DEPRECATED: Alchemy Automated HTTPS Usage Reporting](https://docs.cloudhouse.com/public/licensing-and-reporting/deprecated/deprecated-alchemy-automated/index.md) for details.

## Data privacy

Although user and machine information is collected (User SID and Machine SID), this is automatically hashed using the `SHA256` algorithm before it is recorded anywhere. Hashing the data ensures it remains private to the customer. No user or computer identifiable information is ever sent to Cloudhouse in usage data.

The following data is collected when usage is reported and sent securely over HTTPS:

`UTC_TimeStamp, UsageId, PackageId, Event, Operating_System, CPU_Core_Count, Deploytype, UserSidHash, MachineSidHash, AAVVersion, DeploymentVersion, TokenType`'

## What happens next?

We will process your usage data against your contracted license agreement, contacting you via the [licensing@cloudhouse.com](mailto:licensing@cloudhouse.com) email address only if your usage has exceeded your contracted usage.