Collectivehealth security & compliance
An overview of Collectivehealth's security posture — compliance, penetration testing, subprocessors, and data handling — verified on SOC2C (Listed).
SOC 2 statusSOC 2 · Listed
FrameworksNot listed
Penetration testNot listed
SubprocessorsNot listed
HostingNot listed
Trust centerNot listed
Security questions about Collectivehealth
- Is Collectivehealth secure?
- Security isn't a single yes/no, but Collectivehealth is SOC 2 compliant. SOC2C verifies its compliance posture and shows how strongly each fact is proven.
- Does Collectivehealth have a bug bounty or vulnerability disclosure program?
- Collectivehealth hasn't listed a bug bounty or vulnerability disclosure program on SOC2C. Many companies accept security reports at security@collectivehealth.com or via a /security page.
- Who are Collectivehealth's subprocessors?
- Collectivehealth's subprocessors aren't listed on SOC2C yet. The company can add them so buyers can assess fourth-party risk.
- Where does Collectivehealth host or store data?
- Collectivehealth's hosting and data-residency details aren't listed on SOC2C yet. The company can add where it hosts (AWS, GCP, Azure) and which data it handles.
- Where is Collectivehealth's trust center or security page?
- Collectivehealth hasn't linked a public trust center on SOC2C yet. Its SOC 2 status and frameworks are summarized on its SOC2C profile.