Consent Manager
Try DIMEAI Consent Manager
This is a live demonstration. You will see a consent notice, make your choices, receive a tamper-evident receipt, and then withdraw your consent. It takes about a minute.
This is a demonstration only. The notice is a sample and nothing here is a real data request. We do not ask for your name, phone number, email or any other personal data, and nothing on this page is used for tracking or advertising. The demo records only your Accept or Decline choices against a throwaway demo session. To work, the widget keeps one random identifier in your browser's local storage (it is not a cookie) and sends it with its requests. This page sets no cookies of its own. As with any web server, the demo server's ordinary request logs will see your IP address and browser type.
1. Make your choices
Press the button to open a demo session and show the consent notice.
2. Your receipt
Each choice you submitted was stored as a consent record with its own identifier and a receipt hash that you can keep as your copy of the receipt. A Decline is recorded too.
Proof attached to your decision:
3. Withdraw
Consent has to be as easy to withdraw as it was to give. Open your consents for this demo session and withdraw them. Only choices you accepted can be withdrawn; if you declined everything, there is nothing to withdraw.
What you just did
- The page asked the DIMEAI demo server for a short-lived consent session.
- The consent widget loaded the notice for that session and showed each purpose with its legal basis.
- Your choices were sent to the server and stored as consent records. Where your browser supported it, a passkey check was attached as proof that a person at a real device made the choice.
- You received a receipt for each record. Withdrawing sends a new record that supersedes the earlier one; the history is kept.
How a customer integrates
The customer's own backend creates the session, so the browser never holds long-lived credentials, then the customer's page loads one script and mounts the widget with that session. This page does exactly that against our demo server. Look at the page source to see the full call.
NonaShieldConsent.mount({
baseUrl: 'https://api.diimeai.com',
sessionId, token, // from your backend's session call
publishableKey: WEB_KEY,
mode: 'inline', container: el,
onDone: (r) => r.artefactIds
});For the wider integration model see the integration guide, or write to contactus@diimeai.com to set up consent for your application.