---
title: Glossary
description: Common Inth Consent terms and how to use them.
lastModified: "2026-08-21T17:01:05+01:00"
lastAuthor: Kaylee
---
These terms describe the released Consent side of Inth.

## Consent Sessions

Hosted consent checks that resolve the right consent experience for a visitor. Consent Sessions are not the same as page views.

## Consent saves

Durable consent writes created when a visitor accepts, rejects, customizes, or updates preferences.

## Hosted mode

The c15t client mode used when an application talks to an Inth-hosted backend.

Hosted mode is the production default for Inth Consent because it supports policy resolution, backend records, trusted origins, and server-backed synchronization.

## Offline mode

The c15t client mode that stores consent locally in the browser.

Use offline mode for local prototypes, static demos, tests, and fallback scenarios. Do not position it as equivalent to hosted mode for production consent programs.

## Consent project

An Inth dashboard project that connects an application to hosted consent infrastructure.

A consent project stores runtime configuration such as trusted origins, runtime region, policy packs, and enabled consent features.

## Trusted origins

The application origins allowed to call a hosted consent backend from the browser.

Add production, preview, staging, and local origins that need access. Avoid broad wildcards unless they are intentional.

## Policy pack

A managed set of consent policies that determines which consent model, categories, UI behavior, legal links, and actions apply for a visitor.

Policy packs let teams manage region-aware behavior without changing frontend component code for every policy change.

## IAB TCF

The IAB Europe Transparency and Consent Framework.

Use Inth's IAB TCF docs for the hosted platform layer and managed CMP boundary. Use c15t docs for frontend IAB TCF package and component behavior.

## Managed CMP layer

The Inth-hosted platform layer for eligible IAB TCF Consent projects.

The managed CMP layer can help teams use an Inth-managed registered-CMP path for IAB TCF without directly registering, operating, and maintaining their own CMP implementation. It does not replace the customer's privacy program, vendor choices, disclosures, or legal review.

## Runtime region

The region where hosted consent services run for a project.

Choose a runtime region based on your application, users, and data-residency needs.

## Hosted backend

The Inth-managed backend that c15t clients use in hosted mode.

The hosted backend handles policy resolution, consent syncing, trusted-origin checks, configuration, and backend records.

## Automated traffic

Traffic from known automated sources.

Automated traffic can appear in operational analytics, but it is excluded from billable consent usage when detected.

## Usage safeguards

Billing protections designed to avoid treating duplicate delivery, retry noise, and short-lived traffic spikes as separate user interactions.

If usage still looks unusual, contact support so we can help review the usage pattern and next steps.