Consent Management

Consent Management lets you collect and record consent on your websites. You design banners, decide which banner each visitor sees based on the privacy regulation that applies to them, classify the cookies and scripts on your site into categories, and offer signed-in data subjects a preference center. Every choice becomes a consent receipt you can search and export. Configuration happens in the Neostra UI; your developer adds one script tag to the site.

The building blocks

Collection point. One place where you collect consent, usually one website domain. It belongs to a brand and is the unit of configuration and publishing. Its categories, tracking services, attributes, signals, webhooks, jurisdiction rules, and preference center attachment all live here. Manage them under Collection Points.

Banner. The visual design and wording: layout, theme, buttons, text, languages, and behaviour. A banner is reusable. Several collection points of the same brand can serve the same banner, and one collection point can serve different banners to different visitors. Manage them under Banners.

Tracking services and categories. On each collection point you define consent categories such as analytics or marketing, each with a name, description, consent role, and a Required flag. Cookies, scripts, and iframes are added by hand or discovered by a scan of your domain, then assigned to categories and confirmed. Only confirmed services appear in the banner.

Geolocation rules. Each collection point has a default banner and optional jurisdiction rules that map a regulation to a banner. Regulations, with the countries and states they cover, are managed under Settings > Regulations. Neostra detects the visitor's location from their IP address, finds the regulations that apply, and serves the first matching banner in priority order. If none matches, the default banner is served.

Preference centers, purposes, and preferences. A preference is a single choice, for example a consent to a channel or a frequency setting. A purpose groups preferences and explains why you process data. A preference center presents published purposes to data subjects with a welcome page, a theme, and translations. Manage them under Preference Centers > Manage Centers, Purposes, and Preferences.

Consent records. Every submission from a banner or a preference center creates a receipt with a receipt id, subject id, source, brand, collection point, time, and the accepted or rejected choice for each category or preference. Known data subjects and their consent history are listed under Consent Records > Data Subjects.

Drafts and publishing

Collection points, banners, and preference centers all follow the same model. Editing creates a draft. Visitors keep seeing the last published version until you click Publish. Discard Draft returns you to the published version. Each publish is kept in a Published History list with the version, time, and publisher.

The three objects publish independently, and the collection point is what reaches the site:

• Publishing a collection point takes the banner design as it stands in the banner builder at that moment, whether or not the banner itself has been published, and combines it with the collection point's categories, confirmed services, attributes, and signals into the configuration served to visitors. After changing a banner, publish the collection points that use it.
• A preference center must be published before it can be attached to a collection point. When you publish the preference center again, every collection point that uses it picks up the new content without a further publish.

From configuration to the live site

Who does what

Explore the module