HubSpot Strategy, CRM Architecture & Marketing Automation Blog | Campaign Creators

HubSpot Sensitive Data for Financial Services: Where Account Numbers and Tax IDs Should Live

Written by Campaign Creators | 11/20/26

Full account numbers and tax IDs belong in your system of record, such as your custodian, core banking platform, or loan origination system. HubSpot holds a reference ID, a masked value, or a status flag, and HubSpot sensitive data properties, field-level permissions, and audit logs protect anything sensitive that does live in the portal.

That design gives advisors, loan officers, and client service teams full client context in HubSpot, and it keeps the most damaging identifiers in one protected home. The stakes are high. IBM's 2026 Cost of a Data Breach Report put the average financial services breach at $6.3 million.

As a HubSpot Elite Solutions Partner, Campaign Creators designs CRM architecture for regulated businesses, including the data model, permission structure, and integrations behind it. This guide walks through each regulated data element, where it should live, what HubSpot holds in its place, and which HubSpot controls to apply.


Key Takeaways

  • Keep full account numbers, tax IDs, and SSNs in the system of record, and give HubSpot a reference ID, the last four digits, or a status flag.
  • HubSpot sensitive data properties need an Enterprise subscription and come in two levels, Sensitive Data and Highly Sensitive Data.
  • HubSpot permits the last four digits of an account number as Sensitive Data, and full SSNs and full bank account numbers as Highly Sensitive Data.
  • Full card numbers and card security codes sit outside both permitted lists, and HubSpot prohibits using the portal to process payments directly.
  • Pair field-level permissions with object and tool permissions, and review the HubSpot audit log on a set schedule.

Table of Contents

  1. Where Should Account Numbers and Tax IDs Live?
  2. What Counts as Sensitive Data in a Financial Services CRM?
  3. Which HubSpot Controls Protect Sensitive Data?
  4. Step 1: Decide What HubSpot Holds
  5. Step 2: Use HubSpot Sensitive Data Properties
  6. Step 3: Restrict Visibility With HubSpot Field-Level Permissions
  7. Step 4: Track Access With the HubSpot Audit Log
  8. Step 5: Keep Identifiers Out of Emails, Notes, and Forms
  9. Step 6: Sync Safe Values From Your System of Record
  10. How Should You Govern Sensitive Data Over Time
  11. Frequently Asked Questions

Where Should Account Numbers and Tax IDs Live?

Account numbers and tax IDs should live in the system that creates and governs them, and HubSpot should hold only the reference your teams need to act. Each regulated data element gets one protected home, restricted visibility, and an audit trail.

Data element Recommended home What HubSpot holds Controls to apply Sign the design is working
Full bank or brokerage account numbers Custodian or core banking system Custodian account ID and the last four digits Sensitive Data property for the last four, field-level permissions No full account number shows up in a HubSpot export or search
Routing numbers Core banking or payments system A funding status flag, if teams need one Read-only status field Routing numbers never appear in HubSpot
SSNs and tax IDs (EIN, ITIN) Identity verification, loan origination, or core system An identity verified status and verification date Read-only status for most roles A search of notes and emails for 9-digit patterns comes back empty
Dates of birth KYC or core system An age band, if marketing or suitability needs one Sensitive Data property, field-level permissions Teams segment by band without seeing the full date
Balances, holdings, and AUM Custodian or portfolio system A household value band and expected AUM on the deal Field-level permissions, one-way sync Advisors prioritize households without opening statements
Loan and application data Loan origination system Milestones, dates, loan type, and loan amount One-way sync, field-level permissions on amounts Borrower documents stay in the LOS
Card numbers and security codes Payment processor The processor's customer or transaction ID No card fields in HubSpot Card data never enters forms, notes, or imports
Statements and tax returns Document system or system of record A link or reference to the source document Highly Sensitive Data file property only with a documented need Files with identifiers live outside the files tool

This placement follows HubSpot's Product & Services Catalog, which lists the data types its Sensitive Data features support. The catalog permits the last four digits of bank and card numbers as Sensitive Data, and full SSNs, full bank account numbers, IBANs, and bank statements as Highly Sensitive Data. Full card numbers and card security codes appear in neither list, and the catalog names no category for EINs or other tax identifiers, so the conservative placement keeps those in the system of record.

HubSpot gives you a protected option when a workflow needs the full value. Use it for a documented need, and default to the reference ID everywhere else.

Want a second look at your data model? The Architecture Blueprint maps your current HubSpot setup against where it needs to be, including where regulated fields should live.

What Counts as Sensitive Data in a Financial Services CRM?

Sensitive data in a financial services CRM is any client detail that could enable fraud, identity theft, or account takeover if exposed. That covers identifiers, financial profile data, and the files that contain them.

The FTC's Safeguards Rule guidance defines customer information as any record with nonpublic personal information about a customer, in paper, electronic, or other form. Grouping that information by risk tells you where each field belongs.

Risk group Examples Default placement
Identity and account access Full account and routing numbers, SSNs, tax IDs, card numbers, government ID numbers, security questions System of record only, with a reference ID or status in HubSpot
Financial profile Balances, holdings, AUM, income, credit details, loan application data System of record, with bands, milestones, or amounts in HubSpot
Personal context Dates of birth, household members, employment history, demographic data HubSpot when teams need it, protected as Sensitive Data
Files with identifiers Statements, tax returns, ID scans, signed applications Document system or system of record, with a link in HubSpot

The first group carries the highest risk, so it gets the strictest default. The third group often belongs in HubSpot, since advisors and service teams use it to personalize every conversation.

Which HubSpot Controls Protect Sensitive Data?

Five HubSpot controls protect the sensitive data that stays in the portal: sensitive data properties, protected attachments, field-level permissions, object and tool permissions, and the audit log. Each one covers a different way data gets seen, changed, or moved.

Control What it does Where to find it Tier
Sensitive Data and Highly Sensitive Data properties Adds encryption to property values and limits unencrypted access to designated HubSpot apps and approved private apps Settings > Security > Sensitive Data tab, then the Sensitive Data tab on each property Enterprise
Protected attachments Adds encryption to files uploaded on records, notes, file properties, forms, and imports after Sensitive Data is on Record attachments and file type properties Enterprise
Field-level permissions Sets which users and teams can view or edit a property's value Settings > Properties > Manage access Enterprise
Object and tool permissions Controls access to records and to tools such as workflows, imports, and exports Settings > Users & Teams Varies by permission set
Audit log Records user actions, exports, sensitive property value updates, and views of Highly Sensitive values Settings > Account Management > Audit Logs Starter, Professional, Enterprise (sensitive value logs on Professional and Enterprise)

Tiers reflect HubSpot's knowledge base as checked on November 19, 2026. The steps below link to each source article.

Step 1: Decide What HubSpot Holds

Start with data minimization: store the least data each team needs to act, and represent everything else with a safe stand-in. A field earns a place in HubSpot when a team filters, reports, automates, or personalizes on it.

List each team's decisions, then the smallest field that supports each one.

Team Decision they make in HubSpot Safe representation
Advisors Which households to review this quarter Household value band, review date, custodian account ID
Client service Is this the right account on the call? Last four digits, identity verified status
Marketing Who gets which campaign Age band, lifecycle stage, product interest
Loan officers Where each application stands Milestone, loan type, loan amount
Compliance Was the client verified and approved? Verification date, approval record

Anything outside that list stays in the system of record. Our guide to tying financial services campaigns to revenue applies the same rule to lending: HubSpot gets the milestones, dates, amounts, and loan type, and borrower documents stay in the LOS.

Step 2: Use HubSpot Sensitive Data Properties

HubSpot sensitive data properties are custom properties flagged as Sensitive Data or Highly Sensitive Data, and they add a layer of encryption and access limits to the values they hold. They're available on Enterprise subscriptions of Marketing Hub, Sales Hub, Service Hub, Data Hub, Content Hub, and Smart CRM.

Turn On Sensitive Data

A Super Admin turns on Sensitive Data under Settings > Security > Sensitive Data, selects the data categories the account will store, such as Financial Data, and accepts HubSpot's Sensitive Data Terms. Per HubSpot's guide to storing sensitive data, a category can't be removed once selected, and a property's sensitivity setting is fixed once the property is created. A beta lets Super Admins convert existing custom text, number, date, email, URL, and file properties.

A few property types can't hold Sensitive Data: calculation, rollup, property sync, and HubSpot user properties. Sensitive Data properties also can't require unique values, so keep your custodian account ID in a standard property if you dedupe on it.

Choose the Right Level

Use Sensitive Data for the last four digits, payment history, income, and demographic details. Reserve Highly Sensitive Data for the full values HubSpot permits, such as a full SSN or full bank account number, and only with a documented need. Users with access must click to decrypt a Highly Sensitive value before they can view or edit it.

How Sensitive Data Works Across HubSpot

HubSpot's article on how Sensitive Data is used in HubSpot tools and the Covered Services list set the behavior below.

HubSpot tool Sensitive Data Highly Sensitive Data
View and edit values on records Supported Supported, with click to decrypt
Forms and file uploads Supported Supported
Import and export Supported Supported
Lists, workflows, search, and reporting Supported Not supported
Data sync apps Supported Supported, treated the same as Sensitive Data
Personalization tokens, chatbots, playbooks, and sandboxes Not supported Not supported
Breeze AI Property values excluded Property values excluded

In workflows, Sensitive Data properties work in filter-based enrollment triggers and branches. Copy property actions, personalization tokens, and event-based triggers on these properties aren't supported, so plan automations around status flags. Turning on Sensitive Data also opts the account out of HubSpot AI model training, and HubSpot employees can't view Sensitive Data values during support sessions.

Step 3: Restrict Visibility With HubSpot Field-Level Permissions

HubSpot field-level permissions set which users and teams can view or edit each property, so a role sees only the sensitive fields its work needs. Super Admins set them on Enterprise subscriptions of Marketing Hub, Sales Hub, Service Hub, Data Hub, Content Hub, and Revenue Hub.

Each property gets one of four access settings: private to Super Admins, everyone can view and edit, everyone can view, or access assigned to specific users and teams. Users without view access see a restricted icon in place of the value.

Design Permission Sets by Role

Build access around roles, then assign teams to those roles. Here's a starting design for a wealth or lending firm.

Role Last four digits Household value band Identity verified status Highly Sensitive values
Advisor View only View only View only No access
Assistant View only No access View only No access
Marketing No access View only No access No access
Operations View and edit View and edit View and edit Named users only
Compliance View only View only View only View only

Pair Property Access With Object and Tool Permissions

HubSpot's guide to managing view and edit access for properties notes that users can still set a restricted property's value through the API or when creating a record manually. Pair field-level permissions with object and tool permissions for imports, exports, and workflows, as HubSpot recommends.

Three more details shape the design:

  • Default properties such as email, first name, last name, and lifecycle stage can't be restricted, so keep sensitive values in custom properties.
  • Granting a nested team access also gives its parent team the same access.
  • Super Admins can't restrict another Super Admin, so keep that group small.

Step 4: Track Access With the HubSpot Audit Log

The HubSpot audit log records user actions in your account, including exports, property value changes, and views of Highly Sensitive values, so you can show who touched sensitive data and when. Super Admins open it under Settings > Account Management > Audit Logs.

What the HubSpot Audit Log Records

The log's All Logs, Login History, and Security Activity views each cover the last 30 days. Per HubSpot's guide to viewing and exporting account activity history, Professional and Enterprise accounts log sensitive property values, and filtering by the View action shows who opened Highly Sensitive values. Enterprise accounts add more categories, extra metadata on each event, and an Analyze tab with daily logins, deletions, and exports.

The log records actions taken by HubSpot users. Updates not made by a user, such as a form submission, don't show up there, so keep the system of record's own logs for values it sends to HubSpot.

Review and Export on a Schedule

  1. Turn on audit log notifications for multiple exports and removed admin permissions.
  2. Each month, filter for exports and Highly Sensitive views, then confirm each one matches a business need.
  3. Export the filtered view and store it with your compliance records. HubSpot emails the export to the Super Admin who runs it.
  4. Each quarter, export the security activity history, which covers the last year of logins, user changes, and integration installs.

Those exports give compliance a clean answer when an examiner asks who could see client identifiers and who did.

Step 5: Keep Identifiers Out of Emails, Notes, and Forms

Identifiers most often reach a CRM through free text and files, so close those paths with three moves: prevent, detect, and remove. A client who emails a statement or reads an account number on a call can put a regulated value into HubSpot without anyone planning for it.

Files carry real weight here. When Lab 1 analyzed the unstructured files exposed in nearly 1,300 breach incidents, ABA Banking Journal reported that 93% included financial information, 51% included Social Security numbers, and 49% included bank statements.

Leak point Prevent Detect Remove
Client emails Ask clients to send documents through your secure portal, and use the Never Log list for addresses that shouldn't sync Monthly search of logged emails for account and SSN patterns Delete the logged email and confirm the source copy lives in the system of record
Call and meeting notes Train reps to log identity verified in place of the number they confirmed Spot-check notes and call summaries each month Edit the note and record the correction
Forms and file uploads Collect identifiers only on secure forms mapped to Sensitive Data properties Review form fields during each quarterly access review Archive fields that collect beyond the stated need
Chat and ticket threads Route identity checks to a secure channel Review ticket attachments on a schedule Delete the attachment and note why
Imports and exports Strip identifier columns before import Audit log export alerts Delete the stray file and the property it created
Integrations Map only approved fields Compare field mappings against your data placement table Remove unapproved mappings and clean the values they wrote

Turning on Sensitive Data also helps here. Files uploaded to records, notes, file properties, forms, and imports after the setting is on get an added layer of encryption, and notification previews of note bodies are hidden by default. Files hosted in the files tool keep standard security, so store documents with identifiers somewhere else. HubSpot also offers a scan that finds unsecured sensitive information so you can redact it.

Notes and transcripts are unstructured data, and our guide to structured vs. unstructured CRM data covers how HubSpot AI reads them.

Step 6: Sync Safe Values From Your System of Record

The system of record owns each regulated value, HubSpot mirrors only the fields your teams use, and the sync runs one way into HubSpot wherever possible. That pattern keeps HubSpot current without making it a second copy of your custodian or loan system.

Set the Sync Rules

  1. Name the system that owns each field in your data placement table.
  2. Sync identifiers, statuses, and bands one way, from the system of record into HubSpot.
  3. Transform values before they land: mask an account number to its last four digits, and turn a balance into a value band.
  4. Map any sensitive source field to a Sensitive Data property in HubSpot.
  5. Give each integration only the access scopes its job needs.
  6. Alert an owner when a sync fails, so stale values don't sit unnoticed.

HubSpot's data sync field mappings set which fields sync, in which direction, and which app wins a conflict. HubSpot treats Sensitive Data and Highly Sensitive Data properties the same in data sync apps, and a field the source app marks as sensitive can't sync into a non-sensitive HubSpot property. Custom apps reach these properties through dedicated Sensitive Data scopes, and HubSpot reviews Marketplace apps before granting them.

Match the Integration to the Job

Integration type When it fits What to confirm
Native HubSpot data sync The source app offers a HubSpot data sync connection Field mappings, sync direction, and conflict rules
Marketplace app A listed app connects your custodian, core, or LOS The scopes it requests and the fields it writes
Middleware Several systems feed HubSpot on a schedule Where values are stored in transit and who can see logs
Custom API connection Values need masking, tokenizing, or reshaping first Scopes, error alerts, and an owner for upkeep

Standard connectors, native features, and configuration fit our HubSpot integration development services. When an integration needs to mask, tokenize, or transform values before they reach HubSpot, Brainstem Ventures by Campaign Creators adds custom capabilities that connect to your existing systems. It's a specialized software engineering capability within Campaign Creators, built on one idea: keep the systems that work, and engineer what's missing.

How Should You Govern Sensitive Data Over Time?

Govern sensitive data with a written classification policy, a named owner for every regulated field, and a quarterly review of access, mappings, and audit exports. Placement decisions drift as teams add forms, fields, and integrations, so governance keeps the design intact.

Practice What it covers Owner Cadence
Data classification policy Which risk group each data element falls in and where it may live Compliance with operations Yearly, and before any new regulated field
Field ownership One named owner per sensitive property and integration Operations When a field or integration is created
Retention and deletion How long HubSpot keeps each value and how it's removed Compliance Yearly
Access reviews Permissions granted or removed as people join, change roles, or leave HubSpot admin Every hire, role change, and departure
Quarterly review Field-level permissions, sync mappings, audit log exports, and a sensitive data scan HubSpot admin with compliance Quarterly

This cadence lines up with the expectations regulators describe. The FTC's Safeguards Rule guidance under the Gramm-Leach-Bliley Act asks covered firms to review access controls periodically, keep a data inventory, and dispose of customer information no later than two years after its last use, with limited exceptions. For broker-dealers, investment companies, registered investment advisers, and transfer agents, the SEC's 2024 amendments to Regulation S-P added a required incident response program and notice to affected individuals.

HubSpot's Sensitive Data Terms also make each customer responsible for assessing its own compliance obligations and managing the sensitive data in its account. Treat this table as a starting framework, and confirm your firm's specific obligations with your compliance and legal advisors.

Sensitive Data Placement Checklist

Use this checklist to confirm every regulated field has one home, restricted visibility, and an audit trail.

  • Every data element in the placement table has a named system of record and owner.
  • HubSpot holds reference IDs, last four digits, status flags, or bands for identifiers.
  • Sensitive Data is on, with the Financial Data category selected.
  • Every sensitive value sits in a custom Sensitive Data or Highly Sensitive Data property.
  • Each Highly Sensitive Data property has a documented business need.
  • Field-level permissions match your role design, with object and tool permissions to back them up.
  • Audit log notifications are on, and monthly exports are stored with compliance records.
  • Forms, notes, emails, and attachments have prevent, detect, and remove rules.
  • Integrations sync one way where possible and map only approved fields.
  • A quarterly review is on the calendar.

Questions to Bring to Compliance and Technology Teams

  1. Which systems are the official record for account numbers, tax IDs, and loan data?
  2. Which HubSpot teams need each sensitive field, and for which decision?
  3. Do we have a documented need for any full identifier in HubSpot?
  4. Which integrations write to HubSpot today, and which fields do they touch?
  5. Who reviews the audit log, how often, and where do the exports live?
  6. What do our retention rules require for data held in HubSpot?

Recap

Full account numbers and tax IDs live in your custodian, core banking, loan origination, or identity verification system, and HubSpot holds a reference ID, the last four digits, or a status flag. HubSpot sensitive data properties, field-level permissions, and the audit log protect what stays in the portal. Prevent, detect, and remove rules for emails, notes, and files, plus a quarterly review, keep the design working as your firm grows.

How Can Campaign Creators Help You Design a Sensitive Data Model in HubSpot?

Campaign Creators designs the data model, permission structure, and integrations that keep regulated values in their system of record and give your teams the context they need in HubSpot. As a HubSpot Elite Solutions Partner, we apply CRM architecture expertise to the placement decisions financial services firms face first.

We map each data element to its home, set up Sensitive Data properties and role-based permissions, build one-way syncs from your custodian, core, or loan system, and set the audit and review routine your compliance team can run.

Not sure where your portal stands today? The free HubSpot AI Readiness Scorecard is a 12-question diagnostic that takes about three minutes.

Ready to design your sensitive data model? Book a consultation with our HubSpot architecture team.