# Licenses and Domains

This page explains how Consent Pro licenses work.

## One license per domain

- Each production domain requires its own license.
- Domains and subdomains are treated as different domains.
- Example: `example.com` and `app.example.com` each need their own license.

## Sites using a reverse proxy

If your site uses a reverse proxy — for example, `example.com` serves content that originates from `foo.example.com` — use the **publicly visible domain** (`example.com`) as the license domain, not the origin domain (`foo.example.com`).

## Update your active domain anytime

You can always update the active domain for a license in [my.finsweet.com/plans](https://my.finsweet.com/plans).

## If you do not have a production domain yet

You can use your Webflow staging domain (`*.webflow.io`) until your production domain is ready.

## If a license stops working after cloning or transferring a site

If you cloned or transferred a site and the license no longer works, you can fix it directly on the [Plans page](https://my.finsweet.com/plans):

1. Remove the connected domain from the license.
2. Connect the correct domain again.

## Live domains vs staging domains

Consent Pro only requires a license on live production domains.

You can test all features on `*.webflow.io` staging domains without consuming a production license.

## Geolocation

**Premium** plans can use region-specific banner instances (for example EU vs Global). Consent Pro detects the visitor's region and loads the matching instance.

**Basic** plans only apply instances configured with `regions: "Global"`. Regional instances (for example EU-only) are ignored on Basic.

If a returning visitor's detected region changes since they last gave consent (for example, they traveled or are using a VPN), Consent Pro discards the stored consent and asks for consent again, so the correct regional banner and consent requirements apply.