Black-Bay AICX · Security & data
Security and customer data handling
The operator owns its data. Black-Bay AICX uses identity-checked, read-only record retrieval to support customer conversations. The fields transferred, model provider, retention terms and deployment acceptance must be agreed before contract.
Reviewed 21 October 2026
Request a private demoWhat data reaches the model?
A customer's chat and the records retrieved to answer it can reach the contracted model provider. AICX is not a promise that customer data stays outside an AI model. Connector responses should contain only the fields needed for the approved support task and should exclude passwords, API keys and unrelated personal data.
- The operator defines the identity checks, allowed lookups and minimum response fields.
- The connector retrieves approved records through read-only access.
- The relevant chat and retrieved information support the answer or evidence ticket.
- The operator's team receives the conversation and handoff context when human review is needed.
AICX does not use operator data for model training unless the operator opts in. Provider training and retention terms are agreed before contract. One model provider is named in the contract and is not changed without the operator's consent.
Access boundaries and audit records
The implemented foundation includes tenant isolation with row-level security, identity-based retrieval and per-chat resource caps. These controls must be verified against the actual deployment and connector permissions before launch.
No platform-staff conversation viewer is offered. Direct database access requires additional audit procedures. Read-only integration means the connector cannot be used to approve payments, change balances or make account decisions.
Lookup and handoff events remain in the audit trail. Standard terms specify a 24-month audit retention period, with application roles unable to modify audit records. The deployment review must confirm the roles, retention configuration and access procedures that apply.
Retention, export and incident terms
| Topic | Term |
|---|---|
| Data ownership | The operator owns its data. |
| Contract-end export | Export within 30 days of contract end. |
| Contract-end deletion | Deletion within 90 days of contract end. |
| Audit retention | 24 months by default; application roles cannot modify audit records. |
| S1 incident notification | Within 24 hours under the agreed incident process. |
Confirm how deletion obligations, audit retention, provider retention and any required exceptions fit together in the written agreement. These terms do not establish a regulatory certification or guarantee a particular hosting region.
Questions to resolve before launch
- Which fields and conversation content leave each system, and for what purpose?
- Who may access the connector, tickets, audit trail and underlying database?
- Which model provider and retention settings are contracted?
- How will identity failures, timeouts and missing records reach a person?
- Who owns incident notification, export, deletion and acceptance evidence?
Dedicated and Regional deployments are proposed scope and require separate agreement. PAGCOR SSP accreditation remains on the roadmap; Black-Bay does not claim completed accreditation.
Use the integration guide to define the data boundary. For a security review, contact info@black-bay.ai. Do not send credentials or player records in an initial inquiry.