A purpose register drives the notice; the widget shows each purpose with the data it needs and a switch that starts off. People choose; Nyvika records exactly what they saw and in which language.
Most organisations have a privacy policy, a cookie banner and a tick-box. The Act asks for something else: a notice per purpose, a choice per purpose, and proof of both.
Describe each purpose once. Everything downstream, from the widget to the record of processing, follows from that description.
Each purpose carries its lawful basis, data categories, retention period, recipients and translations.
A notice is published as a frozen version. Changing it creates the next version and, if you choose, asks people again.
One script tag. The notice appears on the right screen, in the person's language, and cannot be configured into a dark pattern.
Web and app journeys use the widget; IVR, kiosk, call centre and paper use the API with their own wording.
Consent is only useful if the systems that send the email or share the data check it first. Nyvika answers that question in one call, and pushes withdrawals to the systems that would otherwise keep going.
A server asks whether a person's consent for a purpose is active, withdrawn or never given; the widget asks on sign-in.
A withdrawal is queued to every connected processor: CRM, engagement platform, email tool, WhatsApp provider, ad audience.
Status for a person needs your secret key or that person's own session. Nobody can enumerate your customers from the browser.
Every module writes to the same registers and the same hash-chained evidence, so nothing is re-keyed and nothing is lost between teams.
The Privacy Centre shows each consent with its notice version and lets the person withdraw in one click.
See privacy centre & rights →Withdrawals and erasures reach the processors named on the purpose.
See processors & connectors →Every decision is a hash-linked ledger entry you can verify.
See ledger, reports & audit →No. You add translations for the languages your customers use; a purpose without a translation falls back to English. Rule 3 asks that the notice be available in the person's chosen language, and the widget switches languages per person.
Colours, fonts and placement, yes. The rules the Act requires cannot be switched off: switches start off, the reject and accept actions are equally prominent, and closing the notice is never treated as consent.
You can import earlier decisions through the API with their original time and source, marked as imported. Most customers instead ask people again on their next visit, which produces a clean, provable record.
Yes. The widget runs in a web view, and native apps call the same API with their own screens. Business processes let an app ask for exactly the purposes a screen needs.
Still have a question? Write to us.
In a demo we register three of your real purposes and publish a notice on a test page in the first half hour.