Go-To-Market Blog | Quantum Business Solutions

ZoomInfo GDPR and CCPA in HubSpot: Opt-Outs and Deletion

Written by Shawn Peterson | Nov 22, 2026, 4:28:00 PM

TL;DR: Quick Answer

Once ZoomInfo data lands in HubSpot, handling it lawfully is your job, not ZoomInfo's. Turn on HubSpot's data privacy settings, record a legal basis for every ZoomInfo-sourced contact, and run every opt-out and deletion request in both systems, suppressing the person in ZoomInfo so the next export does not bring them back.

  • ZoomInfo's privacy policy puts lawful use and rights requests on the customer when the customer processes data through its services.
  • A HubSpot permanent delete blocks the UI and imports, but HubSpot says a contact can return through an API request, which is how integrations write.
  • This is operational guidance, not legal advice. Have counsel sign off on your legal basis and retention rules.

This page is for the RevOps or sales leader who has to answer when legal asks, "what happens when someone opts out?" It covers what ZoomInfo publishes about its privacy practices, the HubSpot settings that matter, EU and UK contacts, and opt-out and deletion handling across both systems. We are a HubSpot and ZoomInfo partner, not a law firm: treat this as the operating manual your counsel reviews.

Table of Contents

  1. Who is responsible for ZoomInfo data once it is in HubSpot?
  2. What does ZoomInfo publish about its privacy practices?
  3. How do you set up HubSpot for legal basis and consent?
  4. How should you handle EU and UK contacts from ZoomInfo?
  5. Handling an opt-out in both systems
  6. Handling a deletion request in both systems
  7. What changes for California and other US states?
  8. Retention and what ZoomInfo reads from HubSpot
  9. Conclusion
  10. Frequently Asked Questions

Who is responsible for ZoomInfo data once it is in HubSpot?

You are, for practical purposes. ZoomInfo's privacy policy says that when customers use its services they act as the data controller, are responsible for processing personal information lawfully, and are responsible for handling data subject rights requests from the people whose data they process. Once a contact is in HubSpot, your team decides whether to email, call, keep or delete it.

Three consequences follow:

  • You need your own legal basis for each ZoomInfo-sourced contact.
  • Requests come to you, wherever you got the data.
  • ZoomInfo and HubSpot do not sync privacy actions for you. Nothing in ZoomInfo's HubSpot integration guides describes removals in ZoomInfo flowing into your CRM, or HubSpot deletions flowing back. Each system needs its own step.

What does ZoomInfo publish about its privacy practices?

In brief, from ZoomInfo's own privacy and help pages. Policies change, so read the sources before you rely on them.

TopicWhat ZoomInfo publishes
GDPR lawful basisFor EEA, UK and Swiss residents, it relies on bases including legitimate interests, its own and its customers', in direct marketing, sales and recruiting, plus consent, contract and legal obligation.
NoticeIt says it gives notice to data subjects as required by GDPR Articles 13 or 14, and its Trust Center says people may receive a Personal Information Notice by email.
Individual rightsIts Trust Center lets people request removal (described as opting out of sale and sharing), request access, and claim or correct a profile. It also lists privacy@zoominfo.com.
US state rightsA separate statement for residents of specified states covers access, correction, deletion and opting out of sale or sharing, and says ZoomInfo honors Global Privacy Control signals.
Customer controlsAdmins can upload master suppression lists for contacts and companies, which exclude those records from search and exports for every user, and can turn on Do Not Call suppression for federal registries in several countries.

Both customer controls live in the ZoomInfo Admin Portal under Privacy & Security, then Compliance, on the Suppression tab. Do Not Call suppression covers federal registries in the United States, the UK (TPS and CTPS), Ireland, France, Germany, Australia, New Zealand and Canada; ZoomInfo notes that state-level registries are not included, and that matching direct and mobile numbers are masked and suppressed in supported workflows, including exports and integrations.

How do you set up HubSpot for legal basis and consent?

Turn on HubSpot's data privacy settings, then make legal basis part of how ZoomInfo records enter the CRM. The toggle is in Settings, under Privacy & Consent. According to HubSpot, turning it on:

  • Turns on the cookie banner and adds privacy messaging to scheduling pages and new forms.
  • Turns on unsubscribe links for one-to-one and sequence emails for users who do not have them yet.
  • Stops tracking one-to-one email opens and clicks for contacts with no value in Legal basis for processing contact's data.
  • Lets you require a subscription before marketing email is sent, with the "Limit emails to contacts with a subscription" option.

The legal basis property has six values: Legitimate interest (Lead, Customer or Other), Performance of a contract, Freely given consent from contact, and Not applicable. HubSpot lets you set it on import, by bulk edit, by hand or in a workflow.

For ZoomInfo-sourced contacts, set it with a workflow keyed on the ZoomInfo Source tag from our ZoomInfo ROI tracking setup and the contact's country. No exported contact then sits with a blank basis, and the value comes from a rule, not from whichever rep exported it. Map the country fields cleanly first; our ZoomInfo to HubSpot field mapping template covers picklist values.

How should you handle EU and UK contacts from ZoomInfo?

Decide once, write it down, and let HubSpot enforce it. Many B2B teams prospecting EU and UK contacts rely on legitimate interest, which means documenting a legitimate interest assessment and giving people a clear way to object.

  1. Segment by country. Build an active list of ZoomInfo-sourced EU and UK contacts to drive every rule below.
  2. Record the basis. Apply the legal basis your counsel approved, such as Legitimate interest - Lead, through the workflow above.
  3. Tell them at first contact. The UK ICO says you must tell people about their right to object to direct marketing no later than your first communication, clearly and separately from other information. Put it in every first-touch template.
  4. Respect the absolute right to object. The ICO describes objection to direct marketing as absolute, with no grounds to refuse. Route "remove me" replies to the opt-out process the same day.
  5. Suppress phones too. Turn on ZoomInfo's Do Not Call suppression for the UK, Ireland, France and Germany if your team calls into those countries.

Some teams simply exclude EU and UK contacts from exports until this process is live, which is a reasonable first step.

Not sure your opt-out process works in both systems?

We will walk one test opt-out and one test deletion through your ZoomInfo and HubSpot setup and show you where it leaks. Book a free 30-minute fit check.

Handling an opt-out in both systems

An opt-out is a suppression, not a deletion. The ICO says that when someone objects to direct marketing you should usually keep just enough information to respect their wish, and should not delete them from a suppression list. Run these steps on the same day:

  1. HubSpot email. Unsubscribe the contact from the relevant subscription type, or from all email. HubSpot's Unsubscribed from all email property then reads true, its email tools will not send, and a call needs a one-time legal basis first.
  2. Active outreach. Unenroll the contact from sequences and any outbound tool fed from HubSpot.
  3. ZoomInfo. Add the email to your master contact suppression list in the Admin Portal so no rep exports the person again. ZoomInfo allows one active contact list at a time, so keep a single running file and re-upload it.
  4. ZoomInfo search filter. If your org uses HubSpot filters in ZoomInfo Advanced Search, turn on the option to exclude contacts who have opted out of email.
  5. Log it. Record the date and channel of the request on the contact so you can show when you acted.

Handling a deletion request in both systems

Here the two systems can undo each other. HubSpot's permanent delete adds the email to a blocklist that stops the contact being re-added through the HubSpot UI or an import. But HubSpot's own article lists three ways a permanently deleted contact can come back: a form submission, an email to a connected team inbox, or an API request. Integrations like ZoomInfo's write through the API, so a later export could recreate the person.

So the order matters:

  1. Confirm the request. Verify identity and log the date.
  2. Suppress in ZoomInfo first. Add the email to the master suppression list before you delete anything in HubSpot.
  3. Clear other tools. Remove the person from sequencing, calling and email platforms that hold a copy.
  4. Permanently delete in HubSpot. Open the contact, choose Actions, then Delete, then Permanent delete. It works one record at a time, not in bulk or by workflow, removes engagement history, and can take up to 30 days to purge.
  5. Point them to ZoomInfo. Your deletion does not remove them from ZoomInfo's directory, and a ZoomInfo removal does not reach your HubSpot copy. Tell the person they can request removal through ZoomInfo's Trust Center.
RequestHubSpot actionZoomInfo actionResponse deadline
Opt out of marketingUnsubscribe, unenroll from sequencesMaster suppression listUK GDPR objection: one month. CCPA opt-out of sale or sharing: up to 15 business days
Delete my dataPermanent deleteSuppress, then point to ZoomInfo's Trust CenterUK GDPR: one month. CCPA: 45 calendar days, extendable once
What do you hold on meExport the contact record and activityPoint to ZoomInfo's access requestUK GDPR: one month. CCPA: 45 calendar days

What changes for California and other US states?

Business contacts count. The California Attorney General's office states that the CCPA's exemptions for employee and business-to-business personal information expired on December 31, 2022, so a California prospect pulled from ZoomInfo has CCPA rights like any other consumer. The deadlines in the table above come from the same page.

California also now has a single deletion channel for data brokers. The California Privacy Protection Agency says that beginning August 1, 2026, registered data brokers must access its Delete Request and Opt-out Platform (DROP) at least every 45 days and process consumer deletion requests. That duty sits with data brokers, not a typical HubSpot customer, and it never touches the copy in your CRM.

Other states have their own laws and timelines; check ZoomInfo's statement for residents of specified states and your counsel's view for the states you sell into.

Retention and what ZoomInfo reads from HubSpot

Keep ZoomInfo data only as long as it serves a sales purpose, and know what flows the other way. HubSpot keeps records until you remove them, so the retention rule has to be yours.

  • Our planning rule: review ZoomInfo-sourced contacts with no engagement, no open deal and no customer relationship after 18 months, then delete or re-justify them in batches.
  • People who moved: if you map ZoomInfo's Person Has Moved field, treat Yes as a trigger to stop outreach to that record and review it.
  • Data flowing to ZoomInfo: ZoomInfo's HubSpot integration guide says its import is on by default, runs hourly, reads contacts, companies, deals, tasks, users, deal history, products and deal stages the connected user can access, and stores matched and non-matched records. Limit it with the connected user's HubSpot permissions and Import Rules, and review the Data Sharing page under Privacy & Security in the Admin Portal.

Retention reviews go faster on a clean portal; our HubSpot data cleanup checklist before connecting ZoomInfo and the monthly ZoomInfo HubSpot health check cover the duplicate and stale-record steps. An outside review of the whole setup is part of our ZoomInfo consulting work.

Conclusion

Privacy handling for ZoomInfo data in HubSpot comes down to a few habits: a legal basis on every sourced contact, a first-touch notice for EU and UK prospects, and opt-outs and deletions run in both systems in the right order. The built-in tools do most of the work once someone owns them.

Test it before a real request arrives: push one test deletion through, then try to export the same person from ZoomInfo again. If the export is blocked, the process works. For how the two platforms connect, see our ZoomInfo HubSpot integration guide.

Want your opt-out and deletion process checked end to end?

We will review your HubSpot privacy settings, ZoomInfo suppression lists and request log, and tell you what to fix first. Book a free 30-minute fit check.

Frequently Asked Questions

Is ZoomInfo GDPR compliant?

ZoomInfo's privacy policy says it processes EEA, UK and Swiss personal data on lawful bases including legitimate interests, gives notice under GDPR Articles 13 or 14, and honors data subject rights. Whether your own use of ZoomInfo data is compliant depends on your legal basis, notices and processes, so have counsel review them.

Who handles a deletion request for a contact we got from ZoomInfo?

You do, for the copy in your HubSpot. ZoomInfo's policy places responsibility for handling rights requests on customers for data they process, and the person can separately ask ZoomInfo to remove them from its directory.

Does deleting a contact in HubSpot stop ZoomInfo from re-adding it?

Not on its own. HubSpot's permanent delete blocks re-adding through the UI and imports, but HubSpot says a contact can return through an API request, so add the person to your ZoomInfo master suppression list first.

What legal basis should we use for ZoomInfo contacts in HubSpot?

Many B2B teams use legitimate interest for prospecting EU and UK contacts, backed by a documented assessment and a clear right-to-object notice at first contact. HubSpot records it in the Legal basis for processing contact's data property, and your counsel should approve the choice.

Does the CCPA apply to B2B contacts?

Yes. The California Attorney General states that the CCPA exemptions for business-to-business and employee information expired on December 31, 2022, so California business contacts have CCPA rights.

Sources & References

Related Reading from Quantum

Ready to put any of this into practice? See how ZoomInfo as a Service works →

About the Author — Shawn Peterson

CEO · Quantum Business Solutions · HubSpot Platinum Solutions Partner

Shawn has spent 20+ years architecting revenue operations for B2B organizations across office equipment, MSP and IT services. Quantum is a HubSpot Platinum Solutions Partner and a ZoomInfo Diamond partner that builds HubSpot, runs outbound email and calling programs, and helps companies get found in search and AI answers. Connect on LinkedIn →

No call required

Would a deleted contact come back on your next ZoomInfo export?

Tell us how opt-outs and deletion requests are handled in your HubSpot and ZoomInfo today, and we will reply with the gaps we would close first. If your process already holds, we will say that.