1. Scope of this list
A subprocessor processes personal data for a customer to help Oakbase deliver the Service. An own-data provider supports Oakbase activities such as its website, identity, communications or commercial management. Inclusion in the latter category does not imply access to Customer Data.
Technical architecture, configurations and flow details are kept in internal documentation and, where contractually relevant, in the order or DPA.
2. Service subprocessors
| Provider | General function | Data categories | Scope and safeguards |
|---|---|---|---|
| Amazon Web Services | Managed infrastructure and processing capabilities, including AI inference. | Customer Data and minimum metadata where needed for a requested feature; authorised credentials and configurations. | As set out in the applicable order and DPA; any international transfer requires a valid GDPR safeguard. |
This list identifies only third parties that qualify as subprocessors under the agreements and actual data flows. Technology providers that do not receive personal data are not listed as subprocessors.
3. Providers for Oakbase-controlled processing
| Provider | General function | Oakbase-controlled data |
|---|---|---|
| GitHub Pages | Hosting and delivery of the version published on GitHub Pages. | Visitor IP address, logged and stored by GitHub for security purposes. It does not host firm memory or receive Customer Data through this website’s demonstrations. |
| Hostinger | Hosting and delivery of oakbase.ai. | Technical data required to deliver and protect those pages. |
| Vercel | Hosting of the API that receives this website’s contact form and records the enquiry in Oakbase’s CRM. | Submitted form data, page URL, language and technical metadata needed to handle the request. |
| Supabase | Oakbase CRM database for commercial relationship management. | Contact enquiries, leads and commercial follow-up history. |
| Google Workspace | Corporate email and support. | Contact data and communications. |
| Google and Microsoft | Enabled identity services. | Account identifiers and basic authentication signals. |
These providers support processing for which Oakbase acts as controller; inclusion does not imply access to firm memory. GitHub describes visitor IP logging in its GitHub Pages documentation and its own processing in the GitHub Privacy Statement. Applicable terms, location and safeguards are reviewed before using each provider and following material changes; international transfers are subject to the Privacy Policy.
4. Changes, objections and contact
The DPA provides general authorisation for subprocessors. Oakbase will notify the contractual contact at least 30 days before a new subprocessor starts handling Customer Data or a material purpose or location change.
The customer may raise a reasoned data-protection objection within the stated period. The parties will seek a reasonable good-faith alternative and, if none exists, apply the DPA, order or statutory regime.
Contact for changes or objections: privacy@oakbase.ai.