1. Who is controller
Oakbase acts as controller for administrator and user, account, billing, security, support, visitor and lead data. Contact: privacy@oakbase.ai. Oakbase does not claim to have appointed a data protection officer (DPO); this mailbox is the privacy contact.
For data that an organisation connects, supplies or authorises within the Service, the customer determines the essential purposes and means and Oakbase acts as processor under a signed DPA.
2. Data processed as controller
| Category | Examples and source |
|---|---|
| Administrators and users | Name, business email, organisation, role, account identifiers, preferences, status and access events, supplied by the user, customer or identity provider. |
| Identity and authentication | Identifier, name, email, domain and basic authentication signals from enabled identity providers. Oakbase does not receive the identity-provider password. |
| Contract and billing | Company, contact, order, plan, billable usage, invoices, payments, tax/VAT ID and contractual communications. |
| Security and support | IP, date/time, device/browser, technical event, customer environment, request identifier, administrative action, ticket and communication. Logs and metrics are designed not to include Customer Data or AI inputs and outputs. |
| Leads and demo | First and last name, business email, company, phone number and firm type provided in the contact form; a description of the requested operation, if included; page URL and selected language, plus contact history. Data supplied when contacting Oakbase by email is also processed. |
| Technical website data | Data strictly necessary to deliver and protect the website, and a locally stored language preference. |
Sources are the individual, their company or administrator, enabled identity providers and technical systems used to provide and secure the Service.
3. Purposes and lawful bases
| Purpose | Intended lawful basis |
|---|---|
| Create/manage accounts, authenticate users, support and perform the order. | B2B contract performance and, for users who are not parties, both organisations’ legitimate interests in giving and receiving the Service. |
| Invoice, collect payments and meet accounting, tax and corporate duties. | Contract performance and legal obligation. |
| Protect accounts, prevent abuse/fraud, investigate incidents and maintain traceability. | Legitimate security interests and compliance with legal security duties. |
| Answer enquiries and prepare a requested demo, proposal or order. | Requested pre-contractual steps and legitimate interests in B2B relationship management. |
| Improve reliability using content-free metrics. | Legitimate interests in operating and improving the Service, subject to minimisation and applicable objection rights. |
| Defend claims and comply with valid demands. | Legitimate interests and legal obligation. |
Where Oakbase relies on legitimate interests, it will balance necessity, impact and reasonable expectations. Ask privacy@oakbase.ai for further information.
4. Leads, demos and marketing
Submitting the “Let’s talk” form sends the data listed in section 2 to the contact API hosted on Vercel and records a commercial enquiry in Oakbase’s CRM, which uses Supabase for its database. Oakbase uses this data to answer the enquiry, prepare a demo and manage follow-up. The form is for commercial contact only: do not include documents, the firm’s client data or confidential matter information. You can also contact Oakbase by email. Provider functions are described in the Providers list.
Oakbase may individually follow up an enquiry for up to 12 months after the last relevant interaction. The requested contact does not require newsletter consent. Recurring marketing is sent only with separate, withdrawable consent or, where there is an existing customer relationship, as allowed by law for Oakbase’s own similar services; every message will include an easy, free opt-out.
A demo is not conditional on marketing consent. Withdrawal does not affect prior lawfulness or contact needed to handle a request or agreement.
5. Oakbase as the customer’s processor
In this policy, “Customer Data” means information, documents, instructions and other content that the customer or its users supply, connect or authorise within the Service. It includes context and relationships derived from those sources and incorporated into firm memory under the customer’s instructions.
The customer controls purposes, data, users, connections, permissions, instructions, tools and autonomy levels. Depending on connected services and enabled features, categories may include:
- end customers, employees, collaborators, suppliers and other individuals linked to the customer’s activities;
- identity and contact data, records, documents, communications, calendars, tasks and other professional or business information;
- special-category data, criminal-conviction and offence data, and other sensitive, regulated or confidential information where necessary, lawful and expressly authorised by the customer.
Oakbase processes that data only on documented instructions to provide the Service. It does not use it for its own purposes, sale, advertising, commercial profiling, model training or improvement. The customer must establish a lawful basis, give notices where required and apply minimisation and professional controls.
The signed private DPA contains binding details on subject matter, duration, nature, assistance, return/deletion, audit, measures and subprocessors.
6. AI, connected services and data separation
Oakbase processes Customer Data to provide authorised features and under the customer’s instructions. The context engine may persist selected information from connected sources, relationships between that information and derived context needed to build firm memory and assist its users through Operations Agents. Sources, included content, access and retention are governed by the customer’s instructions, authorised configuration, order and DPA.
Zero Data Retention for AI models: the LLM providers used do not retain inference request inputs or outputs. This measure applies to processing by those providers; it does not remove or prevent the persistent memory Oakbase holds on the customer’s behalf. Content or results incorporated into that memory are retained only under the instructions and conditions above.
- Separation: content processed for a customer is kept separate from commercial data that Oakbase handles for its own purposes.
- Limited use: Customer Data is not sold or used for advertising, commercial profiling or model training.
- Operational records: they are minimised and designed not to include Customer Data or AI inputs and outputs.
- Oakbase personnel access: there is no routine content access by Oakbase personnel; any exceptional access must be authorised, limited and audited.
Oakbase does not make solely automated decisions with legal or similar effects on individuals. Meaningful professional review is required before consequential use of outputs.
7. Recipients, providers and transfers
Oakbase discloses data only to authorised personnel, necessary providers, confidential advisers and authorities where validly required. Functions are listed at Providers.
Customer Data processing is limited to the EU/EEA. For data that Oakbase handles as controller, some providers may involve international access or transfer. In those cases, Oakbase will rely on an adequacy decision or another valid GDPR Chapter V safeguard, such as standard contractual clauses, with supplementary measures where required.
Personal data is not sold. Oakbase requires providers to process data only to deliver their services and does not authorise the use of Customer Data for advertising or model training.
8. Retention and deletion
| Category | Period |
|---|---|
| Firm memory: selected information from connected sources, relationships and derived context | For the customer-authorised period needed to provide the Service, under its instructions, configuration, order and DPA; subject to the active-system and backup deletion periods below. |
| Inference inputs and outputs at LLM providers | Zero Data Retention by the model provider. This does not change authorised memory retention in Oakbase. |
| Integration credentials or tokens | Until disconnection, revocation or termination. |
| Termination-related deletion from active systems | No more than 24 hours from the applicable request/termination. |
| Isolated backups | Expire within 35 days; not restored to production except for secure recovery. |
| Content-free audit records | 12 months. |
| Content-free metrics | 90 days. |
| Leads, demo form and follow-up history | 12 months after the last relevant interaction, unless a later contract or legal duty applies. |
| Contracts, invoices and accounting records | Applicable statutory periods and time needed to bring or defend claims. |
Oakbase may block and retain data required by law or a claim, limiting its use.
9. Individual rights
Where Oakbase is controller, request access, rectification, erasure, objection, restriction, portability or consent withdrawal at privacy@oakbase.ai. Oakbase may verify identity and will respond within the legal period.
For data processed for a customer, contact that organisation first; Oakbase will assist under the DPA and refer the request to the controller rather than independently responding unless legally required.
You may complain to the Spanish Data Protection Agency (AEPD) or your competent supervisory authority.
10. Cookies and changes
Oakbase uses only technical resources necessary to deliver, secure and adapt the website, including a language preference in local storage. The oakbase.ai website is hosted on Hostinger, which processes the technical data required to deliver and protect the site. On the version published on GitHub Pages, GitHub logs and stores the visitor’s IP address for security purposes, as described in its GitHub Pages documentation. Oakbase does not add analytics, advertising or tracking cookies to this website. If this changes, the policy will be updated and consent requested where mandatory.
Oakbase may update this policy on 30 days’ notice for material customer-affecting changes, except urgent legal or security changes. Prior versions will be retained.