The widget sets nothing on your visitors. It writes no cookies and uses no browser storage — no localStorage, no sessionStorage, nothing. That is not a policy we ask you to trust: the widget bundle is checked for those APIs as part of its build, so a change that introduced one would fail before it could ship.
What that means for you is that embedding it does not add a cookie-banner category, and does not need one.
The one thing consent gates
We do count that a widget was displayed, and that single count is the only thing consent gates. If your site runs a consent platform, the widget reads its signal and stays silent unless functional consent was given.
- Cookiebot
- Iubenda
- Usercentrics
- OneTrust
- Complianz
- CookieYes
- consent.studio
- Google Consent Mode v2
If it finds no consent platform at all, it counts the display — a site running no consent mechanism has no signal to honour. Either way the testimonials render. Consent decides whether the display is counted, never whether your visitor sees your reviews.
Did this answer it?
If not, write in. The reply comes from the person who built the feature.
Message us