How Cookiebot and Usercentrics’ Privacy Policy Generator Work Together 07/09/26 | Joe Gastler There are several reasons why we chose Usercentrics’ solutions to tackle this problem—their reputation, the recommendation of a trusted developer, and the clean interface just to name a few—but the best reason is ongoing updates. These laws change regularly. You don’t want to spend your time chasing this down, and neither do we. These solutions, working in combination, use code to place your Privacy Policy on the site, and code to inject the list of cookies managed by Cookiebot into your Privacy Policy. That might sound small, but that’s a huge step in the right direction on several fronts. Part I: Privacy Policy Generator This is the tool that writes the policy, and it does so using a “Wizard” tool—you answer questions about your business and how you handle data, and it spits out a “finished” policy as a snippet of code that we then drop on your Privacy Policy page. Once it’s there, it stays connected. If the law changes or you update your answers, the policy changes automatically without further action from us. Part II: The Cookie Declaration Within Cookiebot (what you see as “just your consent banner”), there’s an auto-generated table that lists every cookie and tracker running on your website. Cookiebot scans the site, finds them, sorts them and keeps the list current on its own every month. It’s a big part of the reason we think it’s such a great option. VERY IMPORTANT: Free vs. Paid The free version of the Privacy Policy Generator only covers GDPR (EU law) and only in English. U.S. coverage is only included in the paid version, which is pretty inexpensive (~$2 per month). If you try and use the free one, you will not have handled the problem. What Is Left For The Lawyers? Checking Your WorkThe Privacy Policy the tool can generate is only as accurate as your answers. If you don’t mention a tool that touches data, the wizard won’t know that. A lawyer (or 4C, on the parts we actually touch) can help with that. Edge CasesIf your business is pretty standard, this probably doesn’t apply to you, but if there’s anything strange about how your data flows or anything non-standard about your implementation (ex. You run e-commerce through a third-party service.), a lawyer should check that everything is stated appropriately. Industry SpecificsIf you’re in healthcare, finance or anything that touches the federal government, there are requirements that a general-purpose generator like this can’t (and shouldn’t) touch. What We’re Doing For Ourselves at Four Columns (not legal advice) Using the paid Usercentrics Privacy Policy Generator Tool Answering the Wizard questions as completely and honestly as we can. Embedding the output (plus Cookiebot Cookie Declaration) on the Privacy Policy page of our website. Referring the entire Privacy Policy to our attorney. Updating the Privacy Policy based on their feedback when we get it. What To Do Next We are not going to force you to make a decision. At the end of the day, the stance you choose is your decision to make, but we strongly encourage you to take action, particularly if you have known customers outside of the United States. Please fill out the form below to let us know how you’d like to proceed. FacebookThis field is for validation purposes and should be left unchanged.Name(Required) First Last Company(Required)Email(Required) PhoneWebsite URL(Required)Check All That Apply: I’m on board with Cookiebot for Consent Management, sign us up. I’m on board to use the Privacy Policy Generator, let us know what comes next. I'm on board to use both Cookiebot and the Privacy Policy Generator I’d like to schedule time to talk about this further with the 4C team. I’m not interested in addressing this issue at this time. Δ Want to learn more about the legal implications? Here's a quick rundown of what we found.