Dootsa South African Compliance-Alignment Brief

Internal customer-facing handout for enterprise and public-sector procurement teams.

Value Proposition

Frequently Raised Security And Compliance Concerns

ConcernDootsa Position
Data residencyPrimary residency can be set to South Africa, with transfer controls tracked through compliance settings and processor inventory governance.
Cross-border processingCross-border transfers are controlled through policy and operator agreement requirements, including transfer mechanism tracking.
Access control and MFARole-based access and privileged MFA controls are enforced with auditable change logs.
Sensitive data exposureUploaded media uses signed internal URLs and private storage by default.
Encryption postureTLS verification is hardened for database connections; sensitive MFA material is protected at rest.
AuditabilityOperational and security changes are logged with evidence artifacts available for due diligence workflows.
Incident response and continuityRunbooks, backup/restore test templates, and access review templates are maintained in the readiness pack.

Current Readiness Deliverables

Framework Positioning (External)

FrameworkApproved Positioning
SOC 1Not currently attested. SOC-style governance and control evidence available for customer risk review.
SOC 2Not currently attested. SOC 2-aligned controls and readiness evidence are maintained.
PCI-DSSNot currently represented as certified/attested. PCI obligations are managed based on scope and contract requirements.
ISO 27001ISO 27001-aligned controls and audit engagement planning are in place; certification status is shared per audit stage.
HIPAANot a default HIPAA-covered production environment; HIPAA scope is enabled when PHI and BAA requirements apply.
EU Model Clauses (SCCs)Supported via SCC legal workflows and transfer safeguards, subject to signed agreements.

What Customers Can Request

Support Escalation

Any additional concerns not covered in this brief are handled through the Dootsa support and security review process.

Claim guardrail: Use "compliance-aligned" language and avoid "certified", "attested", or "fully compliant" unless current external evidence confirms that status.