Security & Compliance

ABetterChoice's compliance posture follows directly from its Warehouse Native deployment model: your raw data never leaves your warehouse, so the platform's surface area for compliance review is intentionally small.

What you should review

Document	When you need it
Data Residency	Answering "where does our data physically live?" in a security review.
Privacy Policy	Reviewing how ABetterChoice handles account-level personal data.
Cookies Policy	Reviewing browser-side tracking on the ABetterChoice console.

Operational responsibilities

Because ABetterChoice reads data directly from your warehouse, the responsibility model splits along an unusually clean line:

• Customer (you) owns the warehouse, the raw data, the IAM grants, and the lifecycle of warehouse credentials.
• ABetterChoice owns the control plane (console, statistical engine, scheduling, result-table writes), the SDKs, and the API keys you create inside the console.

In practice this means:

• Revoking the IAM role granted in BigQuery Connection instantly cuts the platform off from your warehouse.
• Deactivating an API Key instantly stops the corresponding SDK fleet from reading assignments.
• Deleting a member via User Roles and Permissions revokes their console access immediately.

Areas not yet covered

The following capabilities are on the roadmap but not generally available today; if any of them is required by your security or procurement process, reach out to support before adopting the platform:

• Enterprise SSO and SCIM provisioning.
• A self-service user-data-deletion (GDPR / DSAR) workflow inside the console.
• A signed compliance pack (SOC 2, ISO 27001) downloadable from the console.

For now, the recommended path is to:

1. Pin all sensitive data inside your existing warehouse and its security perimeter.
2. Treat the ABetterChoice console as the control plane only — restrict membership tightly and audit changes via Change Management.
3. Rotate API keys on the same schedule as the rest of your service credentials.