Allowing for an additional feature that would allow users to store PII. We are in the financial services sector and using hubspot as as CRM is limited due to the fact we cannot store common information that we need such as our clients account numbers and SSN’s.
I can also see this being of great use for healthcare users who wish to have a HIPAA Compliant platform.
This is a great idea, storing PII on the HubSpot platform would be useful and beneficial for both us and our customers
It would be very helpful for our business to have PII stored for users.
This is a great idea as this would be useful and beneficial for both us and our customers
As part of client verification on phone calls we ask clients to confirm certain PII’s, having it these in Hubspot would allow us to quickly and effectively verify our clients identity keeping their accounts secure
This is a major competitive disadvantage to Salesforce
Vastly important for verification purposes and to keep our data in one place.
Definitely would be a helpful feature!
I agree with all of the comments here. This is a needed feature for certain industries and is a very large competitive disadvantage for Hubspot and for our company.
We are still in the adoption process for Hubspot and are now looking to leave if we cannot solve this issue.
Yes! So crazy they don’t have it. We were considering SF because of it.
This is a must for us too. We are always handling SSN/EIN, Government ID, payment details…etc.
This is a must , many financial and insurance institutions will go to sales force over hubspot for this simple reason.
As a financial services firm, the ability to store and access PII is very important to our day-to-day. Based on Hubspot’s trust center, it seems to be a highly secure platform. However, they restrict users from storing PII. It’s just one other area we need to find a workaround for.
If we could keep PII in Hubspot it would be super helpful for our business. Right now we have to us another system. Having a means to capture, manage and update PII that is secure would a game changer. Hubspot could complete with PerciseFP and other platforms on another level. It would greatly help us as a financial planning firm.
Representing a Financial Institution, I agree. We love HubSpot as a CRM. We’re currently employing a workaround that we are pleased with, but would love to get rid of the workaround and be able to leverage an API connection to update changes between our core operating system and HubSpot in real-time.
Any updates??? The new sensitive information properties available are honestly not usable to us. They only allow for the ‘Last 4 digits’ of paymnet details and Government ID’s etc to be stored.
This does us no good, as we need the full information stored.
Can we get this figured out in a complete manner? This was kind of a half step.
This is definitely a crucial topic — storing PII securely and compliantly is a growing challenge, especially as teams scale their use of HubSpot for sensitive workflows.
While HubSpot doesn’t yet support native field-level encryption or storage of sensitive data like ID documents or personal forms, we’ve built an approach that gives you enterprise-grade protection without leaving the HubSpot ecosystem.
Box Connector for HubSpot by SparkGrid Software allows you to manage and deliver secure files through HubSpot while relying on Box’s encrypted, audit-ready infrastructure behind the scenes.
How it helps:
- Secure file delivery with no exposure in HubSpot’s File Manager
- Access based on membership status or contact properties
- Detailed access logs and version control
- Supports HIPAA/GDPR-compliant storage via Box
- Fully integrated with HubSpot CMS and workflows
This is especially helpful for legal, healthcare, education, and financial orgs where document security and auditability are non-negotiable.
You can find it here on the HubSpot App Marketplace: HubSpot Marketplace
Hope this helps others trying to balance compliance with ease of use.
***UPDATE***
We were just notified that HubSpot’s Sensitive Data Terms were just recently updated! Full account numbers, SSNs, etc. are now out of the beta phase! Just set the sensitive data settings to “Highly Sensitive Data” when creating your properties.