TRUST CENTER
We test your defenses. Here's how we protect you while we do.
Hayrok runs offensive validation in customer environments, so we hold ourselves to a higher bar. This page covers our compliance, security practices, data handling and how every test is governed.
AT A GLANCE
Tests run only inside approved scope Every run
Every action approved and recorded Every run
Sensitive fields redacted before storage By default
Private Runner for internal scopes Available
SOC 2 Type I attested Current
COMPLIANCE
Frameworks and Attestations
SOC 2 Type I Design of security, availability and confidentiality controls. Attested
ISO/IEC 27001 Information security management system. Certified
GDPR EU data protection requirements. Compliant
CCPA California consumer privacy requirements. Compliant
CSA STAR Cloud security assurance registry. Listed
HIPAA Safeguards for health information. Compliant
Reports and certificates available on request under NDA
SECURITY PRACTICES
How We Secure Hayrok
DATA HANDLING
What We Collect, and What We Don't
WE KEEP+Scope definitions, approvals and run history+Validated results and risk scores+Redacted evidence needed to prove a finding+Account and billing details
WE DON'T×Use customer data to train shared models×Store unredacted sensitive fields by default×Keep evidence longer than the finding needs×Sell or share customer data
Need raw captures to stay in your network? See the Private Runner →
SUBPROCESSORS
Third Parties That Process Customer Data
Customers are notified before a new subprocessor is added.
DOCUMENTS
Request Security Documents
Public documents open directly (links to be added). Select restricted ones and request access; some require an NDA.
SELECT DOCUMENTS Use your company email. Requests are reviewed by our security team.
RESPONSIBLE DISCLOSURE
Found a vulnerability in Hayrok?
Tell us privately and we'll work with you to fix it. We won't pursue good-faith research that follows our disclosure policy.
security@hayrok.com Disclosure policy and PGP key on request