Privacy compliance,set up by an iubenda partner.

The law obliges every site or app that collects personal data to disclose the details to users. A privacy policy has to cover, at minimum:

• the contact details of the data controller
• which personal data is processed
• the purposes and methods of processing
• where the data comes from
• the legal basis for processing, such as consent

The cookie policy describes the cookies your site installs, the third parties behind them, with links to their documents and opt-out forms, and what each is used for.

Beyond an accurate cookie policy, your site has to show a banner on each visitor’s first visit that links to the policy and lets them accept or reject cookies. Most cookies, including those set by social sharing buttons, should only load after consent.

Many ad networks also limit reach for sites without an industry-standard consent setup, which can cut ad revenue.

When a visitor enters personal data, through a contact form, sign-up or newsletter, you need consent that is freely given, specific and informed, and records that prove it: a user identifier, the privacy policy they accepted, a copy of the form they submitted and the opt-in method used.

The email a form sends you is not enough on its own: it lacks the form as submitted and the version of the policy shown at the time.

Not always required by law, but they set how your product, service or content may be used in a legally binding way: copyright, disclaimers, terms of sale, governing law and mandatory consumer protection clauses.

The CCPA requires businesses to tell California users how their data is used and how to exercise their rights, including the right to opt out. That means disclosures in your privacy policy, a notice at collection on the first visit where it applies, and a “Do Not Sell or Share My Personal Information” link, ideally in the footer too.