Encryption in transit
Traffic to and from the platform is encrypted end-to-end.
P2HS operates the secure platform your application runs on. This page states exactly what that covers, what stays your responsibility to configure, and what we don't currently claim.
The infrastructure layer P2HS operates underneath every generated application. See the full Privacy Policy for complete details.
Traffic to and from the platform is encrypted end-to-end.
Data is stored using AES-256 encryption.
P2HS infrastructure is SOC 2 Type II certified.
Regular security audits and penetration testing against the platform.
Build your application. P2HS runs the platform underneath it—the split matters for security ownership too.
Yes. P2HS infrastructure is SOC 2 Type II certified. See the Privacy Policy for full details.
Not currently. If your application handles protected health information, treat HIPAA compliance as a separate requirement to evaluate for your specific use case before launch.
Agent-to-agent (A2A) connections are being implemented and aren't yet advertised as available or compliance-scoped. The live status is published at dashboard.p2hs.com/auth.md.
You configure what your application collects, stores, and who can access it. P2HS secures the infrastructure layer underneath it.
Contact us with your specific requirements—Enterprise plans can include custom security and delivery terms.
Contact us directly rather than filing a public issue, so we can investigate before any details are shared publicly.
Have compliance requirements beyond what's listed here? Tell us before you build, not after.