Consent Lab
Preferences users trust, compliance teams approve
Channel and topic controls, quiet hours, and audit history. Built to respect consent by default and stay export-ready.
Controls that ship fast
Everything you need to manage consent
Topic-level opt-in
Granular toggles by category and channel.
Quiet hours & snooze
Time windows and snooze with fallbacks.
Audit history
Trace every change per user and tenant.
Schema sync
Keep preferences mirrored in your datastore.
Brandable UI
Embed and theme with your design tokens.
Compliance-first
Consent defaults, exports, and deletion flows.
How it works
Collect, enforce, and surface consent
- Drop in the preference UI with your brand tokens.
- Sync choices to your backend (or let us store them).
- Honor quiet hours and snooze automatically in flows.
- Export proof of consent for audits in one click.
Email + push; quiet hours 10pm-7am; audit trail stored.
Bundled into Pulse Digests with opt-out per category.
Consent Lab FAQ
What teams ask about preferences
Can we host preferences ourselves?+
Yes. Use our UI and store choices in your DB, or let Nimbus persist them—your call.
Do quiet hours work per tenant?+
Yes. Quiet hours and snooze are stored per user/tenant and enforced in flows automatically.
How do we export proof of consent?+
Export a dated audit trail per user or per tenant directly from the dashboard or API.