Enterprise security pack
Security questionnaire
Short answers for a buyer review. Request the underlying evidence for anything your process requires.
Scope and evidence
This page is a starting pack for a buyer security review. It separates the source architecture from account, operational and independent evidence still to confirm. It is not a certification, audit report or warranty.
Where a control depends on a provider account, contract or legal review, the answer says what evidence is required instead of claiming it is complete.
Hosting and residency
The source deployment architecture uses DigitalOcean. Ask for a current environment and data-flow map before relying on a hosting region or data-residency claim.
The architecture includes private object storage. Current regions, access settings and any cross-border processing or subprocessors need verified account and contract evidence.
Encryption
The architecture expects TLS and provider-managed storage encryption. Ask for current transport, storage, secret-management, access and rotation evidence; this page does not certify environment configuration or repository history.
The intended payment boundary is hosted provider checkout. The actual payment-data flow and storage scope still require current evidence.
Access control
Backend APIs own role and capability authority for money, identity and child-safety actions. Current route coverage and access-refusal evidence still need confirmation. Support source uses platform-level customer lookup.
Named operator access, access reviews and join/leave records still need current evidence. Ask for the scope and review date; their existence is not established by this page.
Payments and PCI
Payment integrations use hosted provider checkout. Applicable PCI scope and SAQ eligibility must be confirmed with the acquirer or a qualified assessor; hosted checkout alone does not establish compliance.
Current provider attestations and any applicable scan or payment-page script-control evidence must be supplied for the confirmed scope. Do not treat this page as proof of PCI compliance.
Backups and recovery
The recovery design uses managed database backups and independent object-copy/versioning controls. Current backup availability, retention and recoverable ranges require account evidence.
A live restore drill and published RPO/RTO are not yet proven. The recovery plan and current gaps are documented internally.
Incident response
Ask for current incident contacts, escalation ownership, notification procedures and their review date. This page does not confirm those procedures are approved or rehearsed.
A buyer-specific incident contact and severity matrix can be agreed in the contract.
Subprocessors
Integrations named in source include DigitalOcean, Razorpay, Cashfree, MSG91, Cloudflare Turnstile, Sentry, Google Maps and analytics integrations. This is a source map, not a verified account or subprocessor inventory.
A draft vendor register records proposed owners, data categories, exit paths and unconfirmed account evidence. It is not a verified subprocessor inventory.
Data rights
Ask for the current access, deletion, consent-withdrawal and guardian/child request procedures and evidence. Accountable owners, statutory clocks and operational readiness still need confirmation.
Financial, tax, fraud and safety records may be retained where the law requires it.
PCI SSC guidance on choosing the applicable self-assessment scope
Request evidence
Ask Support for the security pack. Include your company, the product in scope and the specific evidence you need. We will not send secrets or another customer's data.
Contact Support