---------------------------
Title: Privacy policies for CMS websites
URL: https://usercentrics.com/guides/privacy-policy-cms-websites/
---------------------------

# Privacy policies for CMS websites

Building and managing a CMS website means taking responsibility for how user data is collected and disclosed. This guide explains privacy policy requirements for platforms like Wix, WordPress, Shopify, and more. It outlines what your policy must include to meet legal obligations under global privacy laws.

## How to create a Wix privacy policy for your website

Most people building a Wix website are focused on the design, the content, and getting it live. The privacy policy tends to come last, if it comes at all. But if your site collects any kind of visitor data, which most do, a privacy policy isn't a formality. It's generally required under major privacy regulations, and the absence of one can create regulatory and trust risks.

Below, you’ll find a practical walkthrough of what your Wix privacy policy should include and how to implement it correctly.

### At a glance

- Most Wix sites collect personal data in some form, which triggers privacy policy requirements under laws like the [General Data Protection Regulation (GDPR)](https://usercentrics.com/gdpr/) and the [California Consumer Privacy Act (CCPA)](https://usercentrics.com/ccpa/).
- Wix's own privacy policy covers Wix as a platform, not your website. You are responsible for your own.
- The laws that apply depend on where your website visitors are, not where you are located.
- A privacy policy and a consent banner serve different legal purposes, and you likely need both.
- The Usercentrics Privacy Policy Generator offers a free, regulation-ready starting point that can be embedded directly on your site.

## What data does a typical Wix website collect?

Wix is widely known as a user-friendly, all-in-one website builder. Its intuitive tools, accessible pricing, and global user base make it a common choice for [small businesses launching their online presence](https://usercentrics.com/knowledge-hub/wix-small-business-website-guide/).

What many site owners don’t realize is that even a straightforward Wix site can process a wide range of [personal data](https://usercentrics.com/knowledge-hub/personally-identifiable-information-vs-personal-data/). Understanding what’s collected is the first step in determining what a privacy policy needs to address.

For example, contact forms typically capture names, email addresses, and any information a visitor chooses to share. If you run an online store, this extends to billing details, shipping addresses, and purchase history. Booking or scheduling tools also process personal information linked to specific interactions.

In addition, tracking technologies collect technical and behavioral data. Analytics tools record information such as IP addresses, browser type, device details, pages visited, and time spent on the site. Advertising pixels from platforms like Meta or Google support audience building and conversion tracking. Even embedded content, including videos or maps, can enable third-party data collection.

Much of this processing happens automatically, without active input from the visitor. This is why data protection laws require clear transparency about what is collected and how it is used.

## Does my Wix website need a privacy policy?

The short answer is yes, you will generally need a privacy policy for your Wix website. The reason comes down to a distinction that often surprises site owners.

Wix’s privacy policy applies to Wix as a platform provider, not to your business. It explains how Wix processes data, but it does not cover how your website collects or uses visitor information. That responsibility sits with you, which means you need to publish your own privacy policy.

The laws that apply are determined by where your visitors are located, not where your business is based. You do not need to operate from the EU for the GDPR to apply. If people in EU Member States visit your site, the regulation can apply to your data processing. A similar principle applies to US laws such as the CCPA for California residents and the [California Online Privacy Protection Act](https://usercentrics.com/us/knowledge-hub/california-online-privacy-protection-act-caloppa/) (CalOPPA) for commercial sites accessible to users in California. Serving visitors across borders does not remove your regulatory obligations.

Many common website features trigger these obligations. Contact forms, newsletter signups, analytics tools, cookie-based tracking, e-commerce functionality, and user accounts all involve processing personal data. If your site includes any of these, a privacy policy is generally required.

### Privacy policy vs. consent banner: what's the difference?

Many website owners assume that if they have a consent banner, they don’t need a privacy policy. However, each item serves a distinct legal purpose.

- A privacy policy is a document that explains what data you collect, why you collect it, how you use it, and what rights visitors have over it. It's a disclosure, and it needs to be accessible on your site at all times.
- A consent banner is an active mechanism. It appears when someone visits your site, informs them about cookie use, and collects their consent before tracking begins. It's how you obtain and record permission, rather than simply disclosing that tracking happens.

Most sites subject to the GDPR or the CCPA need both. They work together, but neither replaces the other.

## What must a Wix privacy policy include?

Now that we’ve clarified why you need a Wix privacy policy, the next step is understanding what your privacy policy itself must cover. While the GDPR and the CCPA have different legal frameworks, their disclosure requirements overlap significantly.

A single, well-structured policy can address both [data privacy laws](https://usercentrics.com/guides/data-privacy/data-privacy-laws/) by covering the areas below.

### Who you are and how to contact you

Start by identifying the business or individual operating the website and providing up-to-date contact details. Include a dedicated contact method for privacy or data protection requests so visitors know where to direct inquiries.

### What personal data do you collect

Next, describe the categories of personal data you collect. This typically includes information provided directly by users, such as names or email addresses, as well as technical and behavioral data collected through cookies, analytics, or embedded services.

### How do you collect personal data

Explain the collection methods in practical terms, for example, through forms, account creation, purchases, tracking technologies, or integrations with third-party tools. This helps users understand when data collection occurs.

### Why do you collect and use this data

Outline the purposes for processing, such as providing services, processing transactions, responding to inquiries, improving site performance, or marketing.
For GDPR coverage, also state the legal bases you rely on, such as consent, contract performance, or legitimate interests.

### How long do you retain data

Provide retention periods or the criteria used to determine them. Users should be able to understand whether data is stored temporarily, for the duration of a contract, or for a defined legal or operational period.

### Third-party sharing and disclosures

List the categories of third parties that receive personal data, such as hosting providers, analytics services, payment processors, or marketing platforms.
For CCPA, clarify whether any data sharing qualifies as a “sale” or “sharing” under the law and explain how users can opt out if applicable.

### User rights and how to exercise them

Explain the rights available to visitors and how they can submit requests.
Under the GDPR, this includes rights such as access, rectification, erasure, restriction, portability, and objection.
Under the CCPA, this includes the right to know, delete, correct, and opt out of the sale or sharing of personal information, as well as the right not to be discriminated against for exercising these rights.

### Cookies and tracking technologies

Lastly, describe, at a high level, the measures used to protect personal data. If you process payments or other sensitive information, include relevant disclosures about secure processing and safeguards.

## How to create a privacy policy for your Wix website?

A Wix website privacy policy needs to include the above nine aspects, and to create a compliant Wix privacy policy, companies have three different options. Each has different levels of effort and risk depending on how tailored you need the policy to be.

### Option 1: Use the Usercentrics Privacy Policy Generator

The Usercentrics Privacy Policy Generator creates a policy based on how your site actually processes data. You answer questions about the information you collect, the tools you use, and where your visitors are located. The result is a policy aligned with your setup rather than a generic template.

The free plan covers GDPR and CCPA requirements. The paid plan extends coverage to the Children’s Online Privacy Protection Act (COPPA) and additional US state laws and includes updates as regulations change. For most Wix site owners, this is a practical and efficient option.

Once generated, you can add the policy to your site as a dedicated page.

## Generate your Wix privacy policy in minutes

Answer a few questions about your site and get a GDPR and CCPA-ready privacy policy for your Wix website.

### Option 2: Use Wix's built-in privacy policy template

Wix offers a basic Wix website privacy policy template in the dashboard under Settings > Privacy & Cookies. It provides a starting structure and reflects common data collection scenarios.

However, it is not tailored to your specific tools, data practices, or legal obligations. It works best as a draft that you review and expand with details relevant to your site.

### Option 3: Write your own from scratch

Creating a policy from scratch is only advisable if you have legal expertise or professional support. Privacy laws set clear disclosure requirements, and gaps, even unintended ones, can create risk.

For most site owners, using a generator or getting a legal review is a more reliable approach.

## How to add a privacy policy page to your Wix site?

Once you have your privacy policy document, adding it to your Wix site takes only a few steps:

1. Create a new page in your Wix editor and title it something clear and findable, such as "Privacy policy" or "Privacy notice."
2. Paste your policy content into the page, making sure the formatting is clean and the text is easy to read on both desktop and mobile.
3. Hit “publish”.

If you used the Usercentrics Privacy Policy Generator, you can embed the policy directly using the provided embed code, which means your policy updates automatically when the document changes rather than requiring you to manually update the page each time.

Once the page is live, make sure it's excluded from any password protection or members-only access settings. Your privacy policy needs to be publicly accessible at all times, not gated behind a login.

## Where to display your privacy policy on Wix?

Having a privacy policy page is only part of the requirement. Regulations and common best practices both expect it to be easy for visitors to locate and review before their data is collected.

Therefore, a common place to link a Wix privacy policy is a website’s footer because it appears consistently across your site and is where users expect to find legal information. Add a clearly labelled link such as “Privacy policy” rather than a broader label like “Legal” or “Terms.” The link should lead to a dedicated page that is accessible on both desktop and mobile, so visitors can return to it whenever they need.

There are also moments where visibility matters most. Contact forms and newsletter signups should reference the privacy policy close to the submit button so visitors understand how their data will be used before sharing it. For e-commerce sites, the same principle applies within the checkout flow, where personal and payment details are provided.

If you use a [cookie banner](https://usercentrics.com/knowledge-hub/cookie-banner/), include direct links to both your privacy policy and cookie policy. This supports transparency expectations and helps users access more detailed information at the point where consent choices are presented.

> Do you have a Wix website? Learn [how to set up a cookie banner for your site](https://usercentrics.com/knowledge-hub/wix-cookie-banner/).

## Keeping your Wix privacy policy up to date

A privacy policy is not a static document. As your website evolves, so do the tools you use, the data you process, and the regulations that apply. Any of these changes can make an existing policy incomplete if it is not reviewed regularly.

Therefore, aim to revisit your policy whenever you introduce a new third-party service, adjust how you collect or use personal data, or start serving audiences in new regions with different legal requirements. Even without visible changes, an annual review is a sensible baseline, as regulatory guidance and expectations continue to develop.

If you created your policy using the Usercentrics Privacy Policy Generator on a paid plan, updates driven by regulatory changes are applied automatically. This reduces ongoing maintenance, but it’s still a best practice to review the policy when your own data practices change so it continues to reflect your setup accurately.

When updates are made, consider informing existing users or subscribers, especially if the changes affect how their data is processed. Under the GDPR, significant changes may also require obtaining renewed consent.

## Turn your Wix privacy policy into action

A clear, accurate Wix privacy policy shows visitors what happens to their data and why. It sets expectations, outlines their rights, and documents your responsibilities. For most Wix site owners, that alone is a major step toward compliance.

The next step is making sure your site’s behavior matches what your policy says. If you reference cookies, analytics, or marketing tools in your privacy policy, your Wix setup should reflect that in practice. Aligning documentation and implementation helps reduce risk and builds trust with your audience.

If you are using Wix, you can extend your setup with a consent solution that works directly within your site environment, so your privacy policy is supported by the right technical controls.

## How to Create a Squarespace Privacy Policy for Your Website

A privacy policy is rarely the reason a website gets launched. It sits somewhere between the contact page, the cookie banner, and the terms no one wants to think about. But for most Squarespace websites, it’s one of the most important pages to have in place.

Analytics tools, contact forms, newsletter signups — even simple websites collect personal data. A privacy policy explains what information is being collected, why it is being collected, and what visitors can expect when they use the site.

Getting it right doesn’t have to be complicated. With the right information in place and a clear location on the site, a privacy policy can be simple, compliant, and easy for visitors to understand.

### At a Glance

- Most Squarespace sites collect personal data in some form, which triggers privacy policy requirements under laws like the GDPR and the CPRA.
- Squarespace's own privacy policy covers Squarespace as a platform, not your website or business.
- Any Squarespace site that uses contact forms, analytics, or ecommerce is collecting personal data and needs its own privacy policy.
- The laws that apply depend on where your website visitors are, not where you are located.
- Squarespace's built-in cookie tools do not manage third-party scripts or provide the granular consent required under GDPR.

## What Data Does a Typical Squarespace Website Collect?

Squarespace is a popular all-in-one website builder used by small businesses, freelancers, portfolio creators, and online stores. Its ease of use means most site owners get up and running quickly. But Squarespace data collection starts the moment the site goes live.

Built-in features process data by default, including contact forms collect names, email addresses, and any information submitted by visitors. Additionally, Squarespace commerce, booking tools, and analytics all collect information without any action from your website visitors.

Third-party tools can expand that data collection further. Google Analytics and Meta Pixel add tracking, email marketing tools like Mailchimp or ConvertKit process subscriber data, and payment providers such as Stripe and PayPal handle financial information. Each integration adds new data flows that should be disclosed in your privacy policy.

It’s also worth noting that Squarespace is a U.S.-based company, and visitor data is processed on servers in the United States. For visitors from the EU or EEA, this constitutes an international data transfer. Squarespace relies on Standard Contractual Clauses (SCCs) and the EU–U.S. Data Privacy Framework to cover these transfers. Your privacy policy should reflect that.

## Does My Squarespace Website Need a Privacy Policy?

The short answer is yes. Squarespace's privacy policy explains how the company handles its own data. But it does not cover your website or your business. That responsibility is up to businesses using the platform, which have to publish their own policies.

In addition, the data privacy laws you need to comply with depend on where your visitors are located, not where you are based. If people in EU Member States visit your site, the [General Data Protection Regulation (GDPR)](https://usercentrics.com/knowledge-hub/the-eu-general-data-protection-regulation/) can apply to how you process their data.

U.S. laws work similarly: the [California Privacy Rights Act (CPRA)](https://usercentrics.com/us/knowledge-hub/california-privacy-rights-act-cpra-enforcement-begins/) applies when you serve California residents, and the [California Online Privacy Protection Act (CalOPPA)](https://usercentrics.com/us/knowledge-hub/california-online-privacy-protection-act-caloppa/) applies to commercial sites accessible to California users.

Common Squarespace features trigger these requirements. Contact forms, newsletter sign-ups, analytics tools, cookie-based tracking, ecommerce checkouts, and Acuity booking pages all process personal data. So if your site includes any of these, a privacy policy for your Squarespace website is generally required.

## What Must a Squarespace Privacy Policy Include?

The GDPR and CPRA have different legal frameworks, but their disclosure requirements overlap significantly. A well-structured policy can address both [data privacy laws](https://usercentrics.com/guides/data-privacy/data-privacy-laws/) by covering the following areas.

### Who You Are and How to Contact You

Identify the business or individual operating the site. Provide contact details for privacy or data protection requests so visitors know where to direct inquiries.

### What Personal Data You Collect

Describe the categories of data collected. This can include information submitted through forms, technical data gathered through cookies, and behavioral data collected through analytics or third-party tools, for example.

### How You Collect Personal Data

Explain the collection methods in plain terms: via forms, purchase transactions, account creation, tracking technologies, or third-party integrations. Visitors should understand when data collection happens.

### Why You Collect and Use This Data

Outline the purposes: providing services, processing orders, responding to inquiries, improving the site usability, or marketing. For compliance under the GDPR and other regulations that require it, state the legal basis for each purpose, e.g., consent, contract performance, or legitimate interests.

### How Long You Retain Data

Provide retention periods or explain the criteria used to set them. Visitors should understand whether data is held temporarily, for the life of a contract, or for a defined legal period.

### Third-Party Sharing and Disclosures

Name the categories of third parties that receive data: hosting providers, analytics services, payment processors, and marketing platforms. Under the CPRA, clarify whether any data sharing qualifies as a "sale" or "sharing" under California law, and explain how visitors can opt out.

### User Rights and How to Exercise Them

Under the GDPR, this includes access, rectification, erasure, restriction, portability, and objection. Under the CPRA, it includes the right to know, delete, correct, and opt out — plus the right not to be discriminated against for exercising those rights.

### Cookies and Tracking Technologies

Describe the types of cookies and tracking tools in use, what they collect, and the legal basis or consent mechanism you rely on.

## How to Create a Privacy Policy for Your Squarespace Website?

A Squarespace website privacy policy needs to include the eight elements listed above. Also, to collect compliant Squarespace cookie consent and develop an accurate privacy policy, companies have three different options.

Each has different levels of effort and risk depending on how tailored you need the policy to be.

### Option 1: Write Your Own

This is not recommended unless you have, or have access to, legal expertise. A compliant Squarespace policy requires you to track every data processing activity, identify all third-party tools, document the legal basis for each purpose, and update the policy as regulations, your tools, and your business change.

Gaps, even unintentional ones, create risk. Therefore, for most site owners, this is not the most practical path.

### Option 2: Use a Squarespace Privacy Policy Template

Using a template is another common approach that balances efficiency with the need for a formal document. To assist with this, Squarespace offers its own sample language designed to cover platform-specific functions like system data, functional cookies, and customer accounts.

However, because templates and samples are designed to be broad, they will require manual adjustment to accurately reflect your specific use of tools like Acuity Scheduling or third-party marketing integrations. They are also not tailored for specific data privacy laws. So they carry their own risks if used without customization. And the need to maintain it remains.

### Option 3: Use the Usercentrics Squarespace Privacy Policy Generator

The [Usercentrics Privacy Policy Generator](https://usercentrics.com/privacy-policy-generator/) creates a policy based on how your site processes data. You answer questions about what data you collect, which tools you use, and where your visitors are located. The result is a Squarespace policy aligned with your setup.

The free plan covers GDPR and CPRA requirements. Paid plans extend coverage to additional U.S. state laws and include automatic updates when regulations change.

Lastly, the generated policy can be embedded directly on a Squarespace page using the provided embed code. So when the policy updates, your site reflects that automatically without manual edits.

## Generate your Squarespace privacy policy in minutes

Answer a few questions about your site and get a GDPR and CCPA-ready privacy policy for your Squarespace website.

## How to Add a Privacy Policy Page to Your Squarespace Site?

Once you have your policy document, adding it to Squarespace takes only a few steps.

1. In your Squarespace editor, go to Pages and create a new page.

2. Give it a clear, findable title, such as "Privacy policy" or "Privacy notice."
3. Paste your policy content into the page, check that the formatting is clean, and publish it.

If you used the Usercentrics Privacy Policy Generator, paste the embed code into a Code block on the page. This keeps the policy up to date automatically. Any updates appear on your site without manual edits.

Once the page is live, make sure it’s not protected by a password or restricted to members only. Your privacy policy must be publicly accessible at all times.

## Where to Display Your Privacy Policy on Squarespace?

Publishing the page is only part of the requirement. Regulations and privacy best practices require that visitors can easily find your policy, including before any personal data is collected.

Here are the most common places to add it.

### Website Footer

The footer is typically the most important placement for your privacy policy.

To add your privacy policy to your Squarespace website footer, **enter Edit mode on any page, scroll to the bottom, and click Edit Footer**. Add a **Text Block** or **Menu Block** and link to your Privacy Policy page. This makes the link visible on every page of your site.

Use a clear label like “Privacy Policy” rather than something vague like “Legal.”

### Cookie Banner

Your [cookie banner](https://usercentrics.com/knowledge-hub/cookie-banner/) is another key place to include the policy.

Go to **Settings → Cookie and Visitor Data → Cookie Banner** and link directly to your Privacy Policy page. Visitors making consent decisions should be able to read the full policy immediately, without having to search for it.

### Contact and Sign-Up Forms

Contact forms and newsletter sign-up forms should reference your privacy policy near the submit button.

Within the **Form Block settings, you can add a Disclaimer or a Checkbox field**. A short note like, “By submitting this form, you agree to our Privacy Policy,” with a direct link to the page, is standard practice.

For Squarespace GDPR compliance, using a checkbox to ensure active, voluntary consent is required.

### E-commerce Checkout

If you run an online store, include a link to your privacy policy during the checkout process.

Go to **Commerce (or Settings) and select Checkout**. Look for the **Service Agreement section**. Here, you can require customers to acknowledge your Privacy Policy and Terms of Service before completing a purchase.

### Email Subscription Forms

Newsletter blocks benefit from the same transparency. In the **Newsletter Block** settings, use the **Post-Submit** or **Disclaimer** fields to include a link to your policy. This demonstrates transparency about how you store and use subscriber information from the moment they sign up.

## Squarespace's Built-In Cookie Tools: What They Cover (and What They Don't)

Squarespace includes a set of privacy controls that give site owners a useful starting point, but they only cover Squarespace's own tools and tracking.

By default, Squarespace enables you to add a basic cookie banner with a link to your privacy policy. You can enable opt-in mode, so Squarespace analytics cookies do not load until a visitor gives consent.

There’s also an option to disable the visitor activity log, which stops Squarespace from collecting IP addresses and similar backend data. If needed, you can turn Squarespace analytics cookies off completely.

These settings can help reduce the amount of data collected through Squarespace itself, but they do not cover third-party tools added to your site.

That is where the biggest compliance gaps appear. Scripts added through code injection, such as Google Analytics, Meta Pixel, or advertising tags, can still load before consent is given. Squarespace's native banner also does not offer granular consent categories such as Analytics, Marketing, and Functional cookies.

It also doesn’t keep auditable consent records, and it does not support [Google Consent Mode v2](https://usercentrics.com/knowledge-hub/google-consent-mode/), which affects how Google Ads and Google Analytics behave when a visitor declines tracking.

Lastly, for sites that target visitors in the EU and use third-party tracking tools, Squarespace's built-in banner is usually not enough for GDPR compliance. In those cases, you will generally need a dedicated [consent management platform (CMP)](https://usercentrics.com/knowledge-hub/cmp-definition/), such as [Usercentrics Web CMP](https://usercentrics.com/website-consent-management/). A CMP can manage consent across all scripts on the site, not just Squarespace's own tools.

## Get a compliant cookie banner for your Squarespace site

The Usercentrics Web CMP can be added directly to your Squarespace site in minutes and manages consent for all scripts on your site.

## How to Keep Your Squarespace Privacy Policy Up to Date?

A privacy policy is not something you publish once and forget. As your website evolves, so do the tools you use, the data you process, and the regulations that apply. Any of these changes can make an existing policy incomplete if it’s not reviewed regularly.

Therefore, aim to review your policy whenever you add a new third-party service, change how you collect or use personal data, or start serving visitors in regions with different legal requirements. Even without visible changes to your setup, an annual review is a sensible baseline.

If you generated your policy using the Usercentrics Privacy Policy Generator on a paid plan, updates driven by regulatory changes are applied automatically. This reduces ongoing maintenance, but doesn’t replace the need to update the policy when your own data practices change.

When you make significant updates, particularly ones that affect how visitor data is processed, consider notifying existing users and customers. Under the GDPR, material changes may require renewed consent from users whose data is affected.

## Turn Your Squarespace Privacy Policy Into Action

A clear, accurate privacy policy for your Squarespace website shows visitors what happens to their data and why. It sets expectations, documents their rights, and records your responsibilities. For most site owners, getting this in place is a significant step toward compliance.

The next step is making sure your site's behavior matches what the policy says. If you reference cookies, analytics tools, or marketing integrations, your Squarespace setup should reflect that with appropriate consent mechanisms in place. A policy without the right technical controls is incomplete.

---

## Footer

### Products
- [Usercentrics Web CMP](https://usercentrics.com/website-consent-management/)
- [Usercentrics App CMP](https://usercentrics.com/in-app-sdk/)
- [Usercentrics CTV CMP](https://usercentrics.com/usercentrics-ctv-cmp/)
- [Usercentrics Privacy Policy Generator](https://usercentrics.com/privacy-policy-generator/)
- [Server-side Tagging Solution](https://usercentrics.com/server-side-tracking-solution/)
- [Usercentrics Preference Manager](https://usercentrics.com/preference-management/)
- [Audience Unlocker](https://usercentrics.com/audience-unlocker/)
- [Integrations](https://usercentrics.com/integrations/)
- [Web compliance scan](https://usercentrics.com/privacy-compliance-scanner/)
- [App compliance scan](https://usercentrics.com/app-data-privacy-audit/)
- [ROAS Calculator](https://usercentrics.com/roas-calculator/)

### Solutions
- [Data Privacy Regulatory Compliance](https://usercentrics.com/data-privacy-regulatory-compliance/)
- [Marketing Performance Optimization](https://usercentrics.com/marketing-performance-optimization/)
- [Migration](https://usercentrics.com/migration/)
- [Media & Publishing](https://usercentrics.com/media-publishing/)
- [Retail & Ecommerce](https://usercentrics.com/retail-ecommerce/)
- [Banking, Finance & Insurance](https://usercentrics.com/banking-finance-insurance/)
- [Healthcare & Pharmaceuticals](https://usercentrics.com/healthcare-pharmaceuticals/)
- [Gaming](https://usercentrics.com/gaming/)
- [Education](https://usercentrics.com/education/)
- [Automotive](https://usercentrics.com/automotive/)
- [Travel & Hospitality](https://usercentrics.com/travel/)

### Regulations
- [GDPR (EU)](https://usercentrics.com/gdpr/)
- [GDPR (UK)](https://usercentrics.com/uk-gdpr/)
- [CCPA (California)](https://usercentrics.com/ccpa/)
- [TCF v2.3 (IAB)](https://usercentrics.com/cmp-for-publishers/)
- [DMA (EU)](https://usercentrics.com/digital-markets-act-dma/)
- [Amazon Consent Signal](https://usercentrics.com/usercentrics-cmp-and-amazon-consent-signal/)
- [Google Consent Mode (EU)](https://usercentrics.com/usercentrics-cmp-and-google-consent-mode-v2/)
- [Microsoft UET Consent Mode (EU)](https://usercentrics.com/usercentrics-cmp-and-microsoft-consent-mode/)
- [Microsoft Clarity Consent Mode](https://usercentrics.com/usercentrics-cmp-and-microsoft-clarity-consent-mode/)
- [View all regulations](https://usercentrics.com/regulations-and-frameworks/)

### Resources
- [Blog](https://usercentrics.com/knowledge-hub/)
- [Whitepapers](https://usercentrics.com/whitepapers/)
- [Checklists](https://usercentrics.com/checklists/)
- [Courses](https://courses.usercentrics.com)
- [Case studies](https://usercentrics.com/case-studies/)
- [Privacy-Led Marketing](https://usercentrics.com/privacy-led-marketing/)
- [Events](https://usercentrics.com/webinar/)
- [CONSENTED podcast](https://usercentrics.com/consented/)
- [Guides](https://usercentrics.com/guides/)
- [Release notes](https://releases.usercentrics.com/en)
- [Developer documentation](https://usercentrics.com/docs/)
- [RFI template](https://usercentrics.com/resources/usercentrics-rfi-template/)
- [Customer directory](https://usercentrics.com/usercentrics-customer-directory/)

### Company
- [About us](https://usercentrics.com/about-us/)
- [Press](https://usercentrics.com/press/)
- [Our offices](https://usercentrics.com/contact/)
- [Trust center](https://trust.usercentrics.com/)
- [Careers](https://usercentrics.com/career/)
- [Open positions](https://apply.workable.com/usercentrics/)
- [Diversity and inclusion](https://usercentrics.com/dei/)

### Support
- [General support](https://support.usercentrics.com/hc/en-us)
- [Contact sales](https://usercentrics.com/book-a-consultation/)
- [Technical support](https://support.usercentrics.com/hc/en-us/requests/new)
- [Billing and account](https://support.usercentrics.com/hc/en-us/categories/12253804608156-Account-and-billing)
- [Suggest a feature](https://support.usercentrics.com/hc/en-us/requests/new?ticket_form_id=10610312381340)
- [Partner login](https://partnerportal.usercentrics.com/)
- [Partner program](https://usercentrics.com/partner-program-overview/)
- [Affiliate program](https://usercentrics.com/affiliates/)