Qwaiting security & compliance
An overview of Qwaiting's security posture — compliance, penetration testing, subprocessors, and data handling — verified on SOC2C (Domain Verified).
SOC 2 statusSOC 2 · Domain Verified
FrameworksSOC 2 Type II, HIPAA, GDPR, CCPA, PCI DSS
Penetration testNot listed
SubprocessorsNot listed
HostingAWS
Trust centerNot listed
Security questions about Qwaiting
- Is Qwaiting secure?
- Security isn't a single yes/no, but Qwaiting is SOC 2 compliant and holds SOC 2 Type II, HIPAA, GDPR, CCPA, PCI DSS. SOC2C verifies its compliance posture and shows how strongly each fact is proven.
- Does Qwaiting have a bug bounty or vulnerability disclosure program?
- Qwaiting hasn't listed a bug bounty or vulnerability disclosure program on SOC2C. Many companies accept security reports at security@qwaiting.com or via a /security page (Qwaiting lists a security contact).
- Who are Qwaiting's subprocessors?
- Qwaiting's subprocessors aren't listed on SOC2C yet. The company can add them so buyers can assess fourth-party risk.
- Where does Qwaiting host or store data?
- Qwaiting hosts on AWS. Data residency details are on its trust center.
- Where is Qwaiting's trust center or security page?
- Qwaiting hasn't linked a public trust center on SOC2C yet. Its SOC 2 status and frameworks are summarized on its SOC2C profile.