1. Scope and governance
The policy covers the Oakbase Service, accounts, integrations, infrastructure, support processes and authorised personnel/providers. Oakbase applies risk-based, least-privilege and defence-in-depth principles and reviews controls at least annually and after material changes.
Security, development and operations responsibilities will be assigned. Exceptions are documented, approved, time-limited and reviewed. Personnel are subject to confidentiality and role-appropriate training.
2. Data protection and separation
- In transit: modern TLS for relevant external and internal communications.
- At rest: encryption for databases, objects, backups and persistent secrets using managed services and key controls.
- Secrets: secret managers; credentials are excluded from source, images, logs and public documentation. Keys are rotated and revoked according to risk.
- Integrations: encrypted credentials and tokens, minimum permissions, customer separation and revocation on disconnection or termination.
- Isolation: authorisation and logical separation prevent cross-customer access.
Connected-service data is processed under customer instructions and kept separate from Oakbase’s own commercial data. Firm memory retains selected information from those sources, its relationships and derived context authorised by the customer. This persistent memory is subject to the encryption, isolation, access controls and retention and deletion requirements set out in the order, DPA and Privacy Policy.
Zero Data Retention for LLMs: the model providers used do not retain inference request inputs or outputs. This protection applies to the model provider; memory held by Oakbase on the customer’s behalf remains under its instructions. Customer Data is not used to train models.
3. Identity, least privilege and break-glass
Administrative access requires individual identity, MFA, least privilege and periodic review. Incompatible duties are separated where team size allows, and access is promptly removed when roles change or end.
Access to Customer Data by Oakbase personnel is prohibited by default. Exceptional need requires break-glass: justification, prior authorised approval, minimum scope/duration, individual identity, MFA and an auditable record. It receives post-event review and customer notice where legally or contractually appropriate. Shared credentials and standing content access are prohibited.
Customers manage users, permissions, connections and autonomy. Oakbase displays purposes associated with each connection and records relevant configuration changes.
4. Secure development and testing
Changes use version control, review, separated environments and risk-proportionate tests. Continuous integration runs:
- static application security testing (SAST);
- dependency/component analysis (SCA);
- secret and known-vulnerability scanning;
- relevant functional, isolation and authorisation tests.
Vulnerabilities are prioritised by impact, exploitability and exposure. Oakbase will commission an independent penetration test at least annually and after material architecture/risk changes. Findings are documented, remediated and retested.
5. Logging, audit and detection
Oakbase records authentication, administration, security, execution and configuration events needed for traceability. Audit records are retained 12 months and operational metrics 90 days.
Alerting and reviews look for anomalous access, authorisation failures, sensitive changes, abuse and degradation. System clocks are synchronised and critical records protected from tampering and unauthorised access.
6. Incident management
Oakbase maintains preparation, detection, triage, containment, eradication, recovery and post-incident review processes. Evidence is preserved and technical, legal and communications owners coordinated.
Where a confirmed incident affects data processed for a customer, Oakbase will notify without undue delay and no later than 24 hours after confirmation, using available information and later updates. Notice will include, when known, nature, data/individuals affected, likely consequences, measures and contact. This enables customer compliance and does not require waiting for every detail.
Report vulnerabilities to security@oakbase.ai under the responsible disclosure policy.
7. Continuity, recovery and deletion
- Target RTO
- 8 hours to restore the Service after a covered interruption.
- Target RPO
- 24 hours’ maximum loss of covered persistent data.
- Backups
- Encrypted, isolated and expiring within 35 days.
- Active deletion
- No more than 24 hours for data subject to deletion in active systems.
RTO/RPO are recovery objectives, not availability guarantees or credits. Plans and restores are periodically tested and deficiencies tracked. Backups are not archives, remain protected and deleted data expires within the maximum cycle.
8. AI security and governance
- Inference services are configured to prevent durable retention and providers’ own use of inputs and outputs.
- Customer Data is not used to train or improve Oakbase or third-party models.
- Connected-service permissions, tool policies and access controls limit sources and actions.
- Customers configure autonomy and relevant changes are audited.
- Professional review is required; solely automated decisions with legal or similar effects are prohibited.
- Input/output validation, tool boundaries, instruction separation and risk-based prompt-injection controls apply.
These configurations are verified, documented and protected against unauthorised change.
9. Provider management
Before onboarding a data-accessing provider, Oakbase reviews purpose, necessity, location, security, privacy, continuity and contractual terms. Minimum access, equivalent duties, change monitoring and secure exit apply.
Subprocessors are governed by the DPA, general authorisation, 30 days’ notice and reasoned objection. Their functions are summarised in the Providers list.
10. Shared responsibility and contact
Customers must secure endpoints/accounts, maintain minimum users/scopes, review outputs, revoke access and report incidents. Oakbase cannot eliminate risks arising solely from customer configuration, credentials or systems outside its control, though it will reasonably cooperate.
Questions: security@oakbase.ai. This policy summarises controls without disclosing details that would increase risk.