This page is maintained by AdClosr to answer common security, privacy, and compliance questions about how we operate.
TLS 1.3 in transit. AES-256 at rest. Per-tenant key isolation for sensitive workspaces.
SSO via Okta, Microsoft Entra ID, and Auth0. SCIM provisioning. Granular RBAC.
Immutable audit logs on every admin action, exportable to your SIEM.
A description of capabilities currently enabled on the AdClosr platform. Shared responsibility: AdClosr operates these controls; customers configure access, retention, and integrations for their workspace.
SSO (SAML/OIDC), SCIM provisioning, enforced MFA for admins, configurable session policies.
Role-based access control across offices, teams, and pipelines with deny-by-default semantics.
AES-256 encryption on primary stores. Encrypted backups with point-in-time recovery.
TLS 1.3 across all customer traffic. HSTS and certificate pinning on api.adclosr.com.
Production runs on hardened cloud providers in audited regions with network segmentation and least-privilege IAM.
Continuous dependency scanning, automated patching cadence, and annual third-party penetration tests.
24×7 on-call with documented runbooks. Customer notification per SLA in our DPA.
Immutable, tamper-evident logs of admin and configuration changes, exportable via API.
Customer-specific compliance commitments (such as audit reports, DPA terms, or certification scope) are confirmed in writing during procurement. This page does not assert third-party certification status.
Customers control which region their workspace is provisioned in. AI processing remains within the selected region by default. Personal data handling is governed by the AdClosr DPA.
Request our DPA, subprocessor list, and security overview directly from our team.