Q: Hello, 1) You say "10,000 consents per month" is consents are consents via newsletters, registration forms etc ...
is that correct?
2) In this case these consents are to be recorded and retained?
The following month we can add 10,000 consents which will also be recorded and kept?
So what makes 20,000 consents archived in your database that we can consult and one if so right?
3) Do you take charge of this scenario when requesting cancellation of consent? Are you updating directly from the database so that we don't have to do anything? Do we consume consent in this case?
4) Is Wordpress compatibility supported?
I would like to know how your offer works. Because if I understand correctly you provide what is needed for 10,000 consents per month and cookie banner with tracking?
How do we integrate this famous cookie banner?
Do you offer your own forms? Because if we work in online commerce, for example, it is obvious that we will collect information as much for sales, as for newsletters, and registration forms.
How do you go about synchronizing all your personal data so that we, sellers, developers or bloggers can be sure that the information will be updated, kept, and free for deletion by an Internet user?
5) Take charge of any type of site from online commerce to medical practice sites etc.
6) Do you offer customer support for any additional questions or help?
Thanks in advance for your response, I think it will help a lot of people who seem unclear about the real purpose of your offers.
Best regards
Hello and thank you for your further questions.
Yes, I confirm all the consents are stored and listed in our Consent Solution dashboard.
Regarding the synchronization of consent with your marketing software, that would be something “custom” and it should be developed by the customer himself and his technical team. It may be possible, using our API (https://www.iubenda.com/en/help/6484-consent-solution-http-api-documentation) to create a software integration via PHP or other programming languages that check the marketing software and sends to our consent solution the info when a user changes his preference.
Speaking about the collection of personal information for e-commerce, using our Consent Solution, you can create consent for your checkout page, and when saving the subject of the consent, you’ll need only to save “email” and/or first_name, last_name, full_name, you don’t need to save other specific data.
In any case, in the “proofs” section of consent, we automatically store the HTML of the form the user fills in, so in this case, you can configure the Javascript method in a way that excludes particular fields from our proofs (like credit cards or password). Our technical documentation states that you can exclude certain fields ( i.e. password or fields not related to the consent) in two ways, see this screenshot: https://dsh.re/0b977
More information can be found here: https://www.iubenda.com/en/help/6473-consent-solution-js-documentation#binding-form-fields
Regarding the possibility to limit the number of consents, you can’t decide how many consents save to a specific site/project but you can enable our Consent solution in a specific project in your account and every project will have its own consents, it means that every project/site in your account will have a different public/private key for Consent Solution. Additionally, it's not possible to have different "views" in the same project and all consents coming from different forms are stored in the same dashboard. To filter them you can decide to save the "preferences" using a different name, this is something you must check with your developers.
Our Cookie Solution offers numerous ways to block third-party trackers and scripts before the consent is collected, you can check this guide for more information: https://www.iubenda.com/en/help/3081-prior-blocking-of-cookie-scripts
Our banner is completely customizable via our cookie solution configurator or via HTML code. See this guide for more information: https://www.iubenda.com/en/help/1205-how-to-configure-your-cookie-solution-advanced-guide#text-advanced-settings
Yes, our system is compatible with WooCommerce;
Yes, our interface is already available in Italian, English, Spanish, German, and Portuguese with French coming next.
Yes, all issues reported with slow down of websites have been fixed but if you have issues please drop us a line at info@iubenda.com and we'll help you solve them.
Great thank you for your details but I have trouble understanding this part:
"Regarding the possibility of limiting the number of consents, you cannot decide how many consents to register on a specific site / project but you can activate our consent solution in a specific project in your account and each project will have its own consents, this means that each project / site in your account will have a different public / private key for Consent Solution. In addition, it is not possible to have different " views "in the same project and all consents from different forms are stored in the same dashboard. To filter them you can decide to save the" preferences "under a different name, this is something you need to check with your developers. "
Does this mean that I have 10,000 consents per month for all projects / sites combined, and that I can create a space reserved for a particular site with public / private keys so as not to mix information from one site to another? the other? It is not 10,000 consents per key created, per site but 10,000 consents (and 300k "views") for all sites / projects?
Then concerning the second part on the fact "that it is not possible to have different" views "in the same project and all the consents coming from different forms are stored in the same dashboard" I do not have at all understood that part sorry.
If you could give me at the same time your exact definitions of the word "views" so that I can better understand and estimate the number of supported sites that will be perfect.
In addition I would also like to know, if we are taken care of by your service and an information leak was declared to whom will be the fault? What if this leak comes from your servers? (this is just an informational question)
Thank you for your excellent support, best regards
The limit of 10k consent is the limit of our Consent Solution. I would like to stress that our Consent Solution records consents for forms, (newsletters forms, sign up forms and so on) and and we are not talking about consents related to cookies for which you need to refer to the Cookie Solution product with our Cookie Preference Logs feature that is included within the 3 codes deal for 300.000 pageviews and 300.000 consents for cookie stored each month.
In any case, and if you were referring to consents for cookies, you can create different projects in your account each linked to one website, enable the Cookie Solution for each of them, and use a different cookie solution script for every site. In this case every website has its own “Log collection” available on its specific project.
If you were referring to consent for forms, then you can enable our “consent solution” in your specific site/project and the limit of 10k is for the entire account (not 10k for site/project but for the entire account it means the total of monthly consents you can save are 10k).
I would suggest you to test our solutions to get everything straight and I also remind you that AppSumo allows to ask for a refund within 60 days. If you have further technical questions, do not hesitate to contact us at info@iubenda.com