Yes. A banner collects consent, and a cookie policy explains what you collect and why. The scan gives you the cookie inventory the policy needs, and the cookie policy generator turns it into draft text for you to review and publish.
Why the banner is not enough
The banner collects consent and the consent log records it. GrantCookie’s terms say that you still need a cookie policy and a privacy notice that describe what you collect and why, and they make you responsible for publishing an accurate cookie policy and privacy notice on each website.
What the policy needs to describe
- What you collect and why.
- That a consent record is kept and how it is used. The terms make you responsible for telling visitors this in your own privacy notice and cookie policy.
- Anything the banner stores in a visitor’s browser, for example to remember their choice. GrantCookie’s privacy policy says this is stored on your behalf and that your own cookie policy is the place that describes it.
Where the GDPR applies, the GDPR guide lists clear information about what each cookie does and who receives the data among the GDPR’s requirements.
GrantCookie’s own cookie policy covers its website and application. It explains which cookies it uses, why, how long they last, whether it asks for consent and how you can control them.
Using the cookie policy generator
The cookie policy generator runs in your GrantCookie account. It takes the scanner’s inventory, sorted into categories with the third parties named, and turns it into draft cookie policy text. The text is yours: you can use it, edit it and publish it.
Check the inventory and the text before you publish. A scan may not find cookies on pages behind a login, cookies set by scripts that load only in certain conditions, or cookies added since the last scan. Under the terms, you decide whether the generated text is accurate before you publish it.
The generator’s output is not legal advice. GrantCookie provides tooling and defaults. For your specific obligations, talk to a lawyer.