Docs
Sign in
Concepts

Platform

Inth separates consent UX from consent infrastructure. Your app owns the React components and visual experience. Inth hosts the runtime services that resolve policy, store consent, and serve the backend API that c15t clients call.

Core pieces

Application

Your site installs a c15t client package, mounts ConsentManagerProvider, and renders a banner, dialog, widget, or headless UI. The app also configures scripts, iframes, and other integrations that should wait for consent.

Inth dashboard

The dashboard stores project configuration: trusted origins, runtime region, enabled features, branding, policy packs, IAB settings, and custom translations when enabled.

Hosted runtime

The hosted runtime checks trusted origins, resolves the active project configuration, and connects c15t clients to managed consent services.

c15t backend

The backend resolves the visitor's policy, returns banner/dialog data, stores consent records, and supports server-side awareness for applications that need consent state outside the browser.

  1. The client initializes and requests backend data.
  2. The backend resolves location, jurisdiction, translations, policy packs, and the active consent model.
  3. The UI decides whether a banner or dialog should be shown.
  4. The visitor accepts, rejects, or customizes choices.
  5. Consent is saved locally, synced to the backend, and applied immediately to scripts, iframes, network requests, and app code that subscribes to consent changes.

Production defaults

Use hosted mode for production. It gives you centralized policy resolution, durable records, location-aware behavior, and backend synchronization. Offline mode is useful for demos and local prototypes, but it does not provide the backend guarantees that production consent programs usually need.