@valerio_n ❤️

@nikenn 👋

@carriere4 Hi Charles, I'm happy to inform you we've already completed development of a Terms and Conditions generator which is going to launch later this year as we clear up the pipeline from the post-GDPR tasks : )

Nick you're one of those few people I would want to have a chance to hug at least once a month 🤗

@vladkorobov Thanks for your questions, I'll try to tackle all of your points: # On how to collect consent for cookies Consent to cookies must be informed and based on an explicit affirmative action; subject to the local authority, these actions may include continued browsing, clicking, scrolling the page or some method that requires the user to actively proceed. In all EU countries there was debate with the authorities around how to actually enable businesses, especially online publishers, to be compliant with the Cookie Law without losing big chunks of revenues and thus putting jobs in danger. This is why most national authorities have been open to ways of collecting cookie consent other than an "accept" button, like continued browsing, as long as the cookie notice is sufficiently big that it's not possible for the user not to notice it. Differently from the GDPR, we don't have a single Cookie Law for the whole of Europe, but in our experience we've never received a complaint from the authorities on this specific point, out of the hundreds of thousands of websites that use our solution. That said, the iubenda Cookie Solution (www.iubenda.com/en/cookie-solution) allows you to have users accept cookies only when clicking an accept button, but don't forget that this may have an impact on your business, and that the law does give you some room for alternative. This article goes more in depth: https://www.iubenda.com/en/help/... # On multiple buttons for granular cookie consent We've collected here (https://www.iubenda.com/en/help/...) all of the legal references on why this is not strictly necessary. Many customers would like this feature, despite the extra burden it adds in terms of implementation, so we've added them to the next months' roadmap. # On Cookie Solution vs Consent Solution While the Cookie Solution responds to the ePrivacy law requirements, the Consent Solution (www.iubenda.com/en/consent-solution) is all about storing proof of consent in contexts like forms, email opt-ins etc, as required by the GDPR. As of Cookie Law and storing consent, we explain here (https://www.iubenda.com/en/help/... -> under "Proof of consent vs Records of consent") our take on why our solution is compliant without taking any extra steps.

@facens thank you for detailed answer, so what about the case when person willing to close the website – but we already save marketing cookies, what our actions here? How this situation is supposed to be handled?

@vladkorobov Before the consent has been provided, you always have to block the scripts that install cookie, so that the user has a chance to leave without being tracked. We explain more on the topic here: https://www.iubenda.com/en/help/...

@facens thank you for detailed scripts and GTM tutorial https://www.iubenda.com/en/help/.... From what I see so far iubenda for GDPR is the best solution with appropriate pricing

@vladkorobov 🙇 Let us know if you have feedback on that specific guide, as it's been getting some changes and we would appreciate any feedback on whether the procedure is optimal or could be improved

@voneff We love your love ❤️

@mikinacucchi happy to help :)

@ali_siam Hi Ali, we're a bootstrapped company and feedback like yours is what keeps us going and pushing! Thank you 🙇

@giovannialemans Thanks for the question! Today: In addition to writing to the API, you can use the /subjects endpoint to read the latest consent and preferences for each subject Within days: a method for listing consents from the API Within a few weeks: a dashboard for managing/displaying consents from the interface

@facens Thanks for your answer The dashboard that you will release in a few weeks, will be easy to use and integrate into websites as the privacy policy and cookie policy without having special technical skills? I mean maybe selecting the elements to trace in the dashboard --> save --> and inserting a script on the website? And after that we can see the registered consents in the dashboard? Many Thanks

@giovannialemans Implementing the API will still require a little bit of technical work, but if you have some specific ideas on how it could be made a little simpler, please let us know. The JS library already goes in that direction, but we're eager for feedback on how it could be made better!

@facens yes if it were simple to implement as the cookie policy and the privacy policy (as described above) would be ideal even for those who are not too technically qualified. Will you create webinars in which you will explain how to implement the API or a simple guide as it is in the current state? Thanks again!!

@giovannialemans Webinars: absolutely yes! We're also creating a video guide which will be up soon. As of the general feedback on making things simpler, it's not as easy as the Privacy and Cookie Policy, but we're going to do our best!

Thank you Scott! If you have any feedback or feature requests, you have our ears ^_^

Thank you Anthony!

@jarrodfath Being in your same situation almost 10 years ago is what made me start iubenda. Knowing that we're helping other founders focus on their own projects, by taking some hassles away, is our greatest source of motivation. Thank you Jarrod!

@alice_marmieri 🤟

@alice_marmieri Totally agree! I wish this was available earlier in our GDPR journey, would have saved us many hours!!! (Perhaps I just wasn't aware it was available earlier!)

@m_rlons We've got you covered 👊

Thanks for the review! We're actually working on the ToS, though GDPR was first in line :)

@matthew_pritchard working hard to ship them ASAP