ReadMe security & compliance
An overview of ReadMe's security posture — compliance, penetration testing, subprocessors, and data handling — verified on SOC2C (Listed).
SOC 2 statusSOC 2 Type II · Listed
FrameworksSOC 2 Type II, GDPR
Penetration testNot listed
SubprocessorsNot listed
HostingNot listed
Trust centerView
Security questions about ReadMe
- Is ReadMe secure?
- Security isn't a single yes/no, but ReadMe is SOC 2 Type II compliant and holds SOC 2 Type II, GDPR. SOC2C verifies its compliance posture and shows how strongly each fact is proven.
- Does ReadMe have a bug bounty or vulnerability disclosure program?
- ReadMe hasn't listed a bug bounty or vulnerability disclosure program on SOC2C. Many companies accept security reports at security@readme.com or via a /security page.
- Who are ReadMe's subprocessors?
- ReadMe's subprocessors aren't listed on SOC2C yet. The company can add them so buyers can assess fourth-party risk.
- Where does ReadMe host or store data?
- ReadMe'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 ReadMe's trust center or security page?
- ReadMe's trust center is at https://dash.readme.com/*;trust.readme.com. Its verified SOC 2 status, frameworks, and documents are summarized on its SOC2C profile.