Security and compliance overview for in-app purchase platforms
Use this page to assess how a subscription platform describes its safeguards before you share customer data with it.
It separates independent audit evidence, privacy roles, infrastructure controls and day-to-day operational practices so procurement, legal and engineering reviewers can each find the relevant questions to ask.
What to verify first: audit and privacy role
A credible review starts by distinguishing what is independently tested from what is internally operated. SOC 2 Type II evidence, when available under NDA, addresses controls for security, availability and confidentiality as audited annually by an independent CPA firm. Privacy commitments should be read separately: the captured description covers EU and UK data-protection laws, California CCPA/CPRA and Brazil LGPD, and states that end-user personal data is processed only as a data processor under a DPA and documented instructions. That processor role matters because it limits the provider's authority to use personal data to what the customer instructs.
Infrastructure: protect data, code and detection together
Look for protection both while data moves and while it is stored, rather than a single encryption claim. The captured controls describe encryption in transit and at rest using industry-standard protocols, automated alerting with log aggregation and round-the-clock on-call response, and cloud security services that continuously scan for vulnerabilities, misconfigurations, anomalies and threats. For software delivery, every change is described as passing peer review, static analysis and CI security checks before deployment. Together these form a chain: prevent defects in code, detect problems in the cloud environment, and respond when alerts fire.
Operations: suppliers, people and continuity
Technical controls fail if people and suppliers are unmanaged. The captured practices include security and privacy reviews for third-party providers, with critical vendors holding equivalent certifications. Staff are described as undergoing background checks, annual security awareness training and mandatory multi-factor authentication on company systems. Continuity is addressed through daily encrypted backups, redundant services and tested disaster-recovery plans. Ask how each practice is evidenced — for example, vendor review cadence, training completion and recovery test results — instead of accepting the practice name alone.
Reporting findings and requesting assurance documents
Researchers need a clear, safe route for reporting findings. The captured page directs vulnerability reports to a dedicated security contact, states that valid reports are investigated and remediated promptly, and references a HackerOne bounty program for responsible disclosure. Enterprise reviewers can separately request the SOC 2 report, a completed questionnaire such as CAIQ or SIG, or the Information Security Policy through the sales contact. Keep these two routes distinct: disclosure for suspected vulnerabilities, procurement contact for assurance documents.
| Review area | What the captured evidence describes | Evidence to request |
|---|---|---|
| Independent audit | SOC 2 Type II controls for security, availability and confidentiality, audited annually by an independent CPA firm | Current report under NDA, including period and scope |
| Privacy role | Compliance described for EU/UK laws, CCPA/CPRA and LGPD; personal data processed only as data processor under DPA and documented instructions | Current DPA, sub-processor list and regional scope |
| Data and cloud protection | Encryption in transit and at rest; continuous cloud scanning for vulnerabilities, misconfigurations, anomalies and threats | Encryption standards, scanning scope and remediation timelines |
| Detection and response | Automated alerting, log aggregation and 24x7 on-call response | Alert coverage, on-call model and incident-notification commitments |
| Secure delivery | Peer review, static analysis and CI security checks before deployment | Pipeline controls and exception process |
| People, vendors and continuity | Vendor security/privacy reviews, background checks, annual training, mandatory MFA, daily encrypted backups, redundant services and tested recovery plans | Vendor review cadence, training/MFA enforcement and recovery test evidence |
Captured description only; confirm current documents and periods with the owner before relying on them.
Frequently asked questions
How can I review the SOC 2 Type II evidence?
Controls covering security, availability and confidentiality are audited annually by an independent CPA firm. The current report is shared under NDA on request; confirm the request route with the owner before publishing a contact address.
Which privacy regimes are described, and in what role is personal data processed?
The captured description states alignment with EU and UK data-protection laws, California CCPA/CPRA and Brazil LGPD, with end-user personal data processed only as a data processor under a DPA and documented instructions. Confirm the current DPA and regional scope with the owner.
How should a suspected vulnerability be reported?
Use the responsible-disclosure route supplied by the owner and the HackerOne program referenced in the captured evidence. Do not publish a direct email address until the owner confirms the current disclosure contact.
What documents can enterprise reviewers request?
Enterprise reviewers may request the SOC 2 report, a completed questionnaire such as CAIQ or SIG, or the Information Security Policy through the owner-confirmed sales contact.