SOC2C

Kidu security & compliance

An overview of Kidu'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
Penetration testNot listed
SubprocessorsNot listed
HostingNot listed
Trust centerView

Security questions about Kidu

Is Kidu secure?
Security isn't a single yes/no, but Kidu is SOC 2 Type II compliant. SOC2C verifies its compliance posture and shows how strongly each fact is proven.
Does Kidu have a bug bounty or vulnerability disclosure program?
Kidu hasn't listed a bug bounty or vulnerability disclosure program on SOC2C. Many companies accept security reports at security@kidu.mom or via a /security page.
Who are Kidu's subprocessors?
Kidu's subprocessors aren't listed on SOC2C yet. The company can add them so buyers can assess fourth-party risk.
Where does Kidu host or store data?
Kidu'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 Kidu's trust center or security page?
Kidu's trust center is at https://kidu.mom. Its verified SOC 2 status, frameworks, and documents are summarized on its SOC2C profile.

See Kidu's full SOC 2 profile →