Data processing
Data processing agreement
This DPA forms part of the contract under the client terms.
Version: 1.0
Effective date: 19 November 2026 (Europe/London)
This Data Processing Agreement forms part of the Kitbox-Websites Client Terms.
Kitbox-Websites Data Processing Agreement (UK GDPR Article 28)
I-OSCC Ltd (company no. 17005013, registered in England and Wales, registered office 9 Penntiow Golf, Cott Road, Lostwithiel PL22 0FB), trading as Kitbox-Websites.
Registered office: 9 Penntiow Golf, Cott Road, Lostwithiel, PL22 0FB.
ICO registration: ZC286917
Customer email: [email protected]
Services site: https://kitbox-websites.co.uk
Version: 1.0
Effective date: 19 November 2026 (Europe/London)
This DPA: https://kitbox-websites.co.uk/dpa
Client Terms: https://kitbox-websites.co.uk/terms
This Data Processing Agreement (DPA) forms part of the contract between I-OSCC Ltd (company no. 17005013, registered in England and Wales, registered office 9 Penntiow Golf, Cott Road, Lostwithiel PL22 0FB), trading as Kitbox-Websites ("Kitbox-Websites", "Processor", "we", "us", "our") and the Client named in the Order Form ("Controller") under the Kitbox-Websites Client Terms (the "Main Terms"). Terms such as controller, processor, personal data, processing, data subject and personal data breach have the meanings in the UK GDPR and the Data Protection Act 2018 (together, "Data Protection Law").
1. Roles and scope
1.1 Where Kitbox-Websites hosts or manages the Client's site, or otherwise processes personal data for the Client in providing the Services, the Client is the controller and I-OSCC Ltd is the processor of the personal data described in Schedule 1.
1.2 Each party will comply with Data Protection Law. The Client is responsible for having a lawful basis for the processing, for its privacy notice and cookie consent, and for the lawfulness of its instructions.
1.3 I-OSCC Ltd is a separate controller (not a processor) for its own business contact data about the Client and the Client's staff, used to manage the relationship.
2. Processor obligations (Article 28(3))
2.1 Instructions. Kitbox-Websites will process personal data only on the Client's documented instructions (the Main Terms, this DPA and written instructions given later), including on transfers outside the UK, unless required by law to do otherwise; in that case it will tell the Client first unless the law prohibits this. Kitbox-Websites will tell the Client promptly if it believes an instruction breaks Data Protection Law.
2.2 Confidentiality. Kitbox-Websites will ensure that anyone authorised to process the personal data (including the director and any subcontractors) is bound by a duty of confidentiality.
2.3 Security. Kitbox-Websites will take the technical and organisational measures required by Article 32, as set out in Schedule 2.
2.4 Sub-processors. The Client gives general written authorisation for Kitbox-Websites to use the sub-processors in Schedule 3. Kitbox-Websites will give at least 14 days' notice by email of any intended addition or replacement, and the Client may object on reasonable data protection grounds. If the parties cannot resolve the objection, the Client may end the affected services without an early-termination charge. Kitbox-Websites will impose data protection obligations on each sub-processor that are in substance the same as those in this DPA (Article 28(4)), and remains liable to the Client for each sub-processor's performance.
2.5 Data subject rights. Taking into account the nature of the processing, Kitbox-Websites will help the Client by appropriate measures to respond to requests from data subjects (for example, access, erasure or objection) and will pass on any request it receives promptly, and in any event within 5 Business Days, without responding itself unless authorised.
2.6 Breaches. Kitbox-Websites will notify the Client without undue delay, and in any case within 48 hours, after becoming aware of a personal data breach affecting the Client's data, with the information the Client reasonably needs to meet its own obligations (including notifying the ICO within 72 hours where required under Article 33). Kitbox-Websites will take reasonable steps to contain the breach and help the Client.
2.7 Other assistance. Kitbox-Websites will help the Client meet its obligations under Articles 32 to 36 (security, breach notification, data protection impact assessments (DPIAs) and prior consultation with the ICO), taking into account the nature of the processing and the information available to Kitbox-Websites. Assistance beyond a reasonable level may be charged at the rate in the Main Terms.
2.8 End of processing. On termination, Kitbox-Websites will, at the Client's choice, return or delete the personal data (and delete existing copies) within 30 days, unless the law requires it to be kept. Backups will be deleted in their normal cycle. The handover in the Main Terms is the usual way of returning data.
2.9 Audit and information. Kitbox-Websites will make available all information reasonably needed to show compliance with Article 28 and allow for and contribute to audits, including inspections, by the Client or an auditor it appoints, on at least 30 days' notice, no more than once a year (unless following a breach or a regulator's request), subject to confidentiality. The Client will pay reasonable costs of on-site audits.
These clauses are intended to meet Article 28(3)(a) to (h). https://www.legislation.gov.uk/eur/2016/679/article/28 and https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/accountability-and-governance/contracts-and-liabilities-between-controllers-and-processors-uk-gdpr/
3. AI tools and model training
3.1 Kitbox-Websites will not use Client personal data to train, fine-tune or improve AI models, and will configure AI tools so that personal data is not used for training by the AI provider, where the provider allows this.
3.2 Kitbox-Websites will use only AI providers whose commercial terms state that customer inputs and outputs are not used for training (or which allow this to be switched off), and will check those terms before use and when they change. Cloudflare's official Workers AI data-use terms, checked on 19 November 2026, state that Cloudflare does not use Customer Content to train or improve AI models, and that a standard inference request is not retained after the response is returned, except for limited legal or security reasons, or if we ourselves enable storage (we do not use AI Gateway logging, and we do not store Kitbox-Websites chat messages in KV, D1, R2 or Durable Objects): https://developers.cloudflare.com/workers-ai/platform/data-usage/. The Kitbox-Websites chat uses Google Gemma 4 26B (`@cf/google/gemma-4-26b-a4b-it`), which Cloudflare lists as Cloudflare-hosted: https://developers.cloudflare.com/workers-ai/models/gemma-4-26b-a4b-it/. Because AI Gateway is not used, chat content is not sent on to another AI provider under those terms. Google is not listed on Cloudflare's Workers AI sub-processor list (CoreWeave, Inc. and Nebius BV are): https://www.cloudflare.com/gdpr/subprocessors/cloudflare-services/. Google supplies the model under the Apache License 2.0: https://ai.google.dev/gemma/docs/gemma_4_license. Official Cloudflare pages do not contain a sentence that says "Google does not receive the data"; this DPA follows the hosted-model and sub-processor position above. If we use any other AI provider on a client's work, we will check its terms first and name it in the Order Form or an updated Schedule 3, with the notice required by this DPA.
3.3 Kitbox-Websites will minimise the personal data put into AI tools, and will avoid putting special category data into AI tools unless the Client has expressly instructed it in writing and a DPIA supports it.
4. International transfers
4.1 Kitbox-Websites will not transfer personal data outside the UK (or allow a sub-processor to do so) unless: (a) the destination is covered by UK adequacy regulations (including the UK-US Data Bridge for certified US organisations); or (b) appropriate safeguards are in place, such as the ICO's International Data Transfer Agreement (IDTA) or the International Data Transfer Addendum to the EU Standard Contractual Clauses, with a transfer risk assessment where required.
4.2 The Client authorises the transfers described in Schedule 3 on that basis.
5. Liability and precedence
5.1 Each party's liability under or in connection with this DPA is subject to the exclusions and limits in the Main Terms (clause 15 of the Client Terms), except where Data Protection Law does not allow this. There is no separate, higher cap for data protection claims.
5.2 If this DPA conflicts with the Main Terms on data protection matters, this DPA prevails. This DPA lasts as long as Kitbox-Websites processes Client personal data.
Schedule 1: Details of processing
| Item | Details |
|---|---|
| Subject matter | Personal data handled while building, hosting, maintaining and supporting the Client's website, online shop or apps, and (where agreed) managing its Google Business Profile. |
| Duration | The term of the Main Terms, plus the return or deletion period in clause 2.8. |
| Nature of processing | Collection through site forms, storage, hosting, backup, retrieval, configuration, testing, migration, transfer at handover, deletion; operation of chat assistants; import or management of contact lists; limited processing through AI tools to draft or summarise. |
| Purpose | To provide the Build, hosting, Care Plan and related Services to the Client under the Main Terms. |
| Types of personal data | Names, email addresses, phone numbers, postal addresses; enquiry and message content; booking details (dates, times, service chosen); quote calculator inputs; chat assistant transcripts; contact or mailing lists; reviewer names and review content (Google Business Profile); technical data such as IP addresses and cookie identifiers collected by the platform; shop order and customer details where Kitbox-Websites hosts or manages an online shop for the Client. |
| Special category data | Not expected. If a client's site would collect special category data (for example health data in a booking form), the Client must have an Article 9 condition, update its privacy notice, consider a DPIA, and tell Kitbox-Websites in writing before go-live. Forms should collect only what is necessary. We will only process that data where it is agreed in the Order Form. |
| Categories of data subject | The Client's website visitors, enquirers, customers and prospective customers, people booking appointments, chat assistant users, people on the Client's contact lists, reviewers, and the Client's staff where named on the site. |
Schedule 2: Security measures (Article 32)
- Access: multi-factor authentication on all Kitbox-Websites accounts and platform logins; a business password manager; unique passwords; least-privilege collaborator access instead of shared logins where the platform allows; access removed promptly when no longer needed.
- Credentials: client passwords are never requested or sent by ordinary email; secure sharing methods only.
- Devices: encrypted devices, screen locks, supported operating systems with automatic security updates, and anti-malware protection.
- Platforms: reputable hosting platforms (typically Wix, Shopify or Cloudflare, as named in the Order Form) using HTTPS/TLS; platform and plugin updates applied under the Care Plan; only trusted apps and plugins installed.
- Backups: regular backups as set out in the Order Form, with restore tested at the frequency set out in the Order Form.
- Data minimisation: forms collect only necessary fields; test data used instead of real data where possible; minimal personal data put into AI tools.
- People: confidentiality commitments from all who access data; the director reviews AI-assisted output before it is delivered.
- Incidents: a documented breach response process, including a log of incidents and notification under clause 2.6.
- Review: these measures are reviewed at least once a year. Cyber Essentials certification is not required at launch and can be considered later.
Schedule 3: Authorised sub-processors
The sub-processors below are authorised for personal data that I-OSCC Ltd processes in providing the Services. A client platform is authorised only where the Order Form names it. If we need to add a sub-processor, we will give you the notice in this DPA.
| Sub-processor | Purpose | Location / transfer basis |
|---|---|---|
| Cloudflare, Inc. (and UK/EU affiliates as applicable) | DNS, content delivery, security, hosting or Workers, including Cloudflare Pages, Turnstile (spam checks) and, where used, Email Routing or Email Sending, for processing in I-OSCC Ltd's Cloudflare account (including a client site hosted or processed there, as recorded in the Order Form) | Cloudflare's global network. Transfer safeguards: Cloudflare's Data Processing Addendum v6.4 (effective 3 April 2026), which forms part of the Self-Serve Subscription Agreement (section 6.1) and includes the UK Addendum (Version B1.0) to the EU Standard Contractual Clauses; Cloudflare is also certified under the UK Extension to the EU-US Data Privacy Framework. Official DPA: https://www.cloudflare.com/cloudflare-customer-dpa/. GDPR FAQs: https://www.cloudflare.com/en-gb/trust-hub/gdpr/. I-OSCC Ltd accepted Cloudflare's DPA v6.4 on 4 November 2026. A copy is on file. |
| Cloudflare, Inc. (Workers AI; Google Gemma 4 26B, `@cf/google/gemma-4-26b-a4b-it`, running in I-OSCC Ltd's own Cloudflare account) | Operation of the Kitbox-Websites chat assistant (Kori), and, where the Order Form says so, a chat assistant on a client site | Processing on Cloudflare's global network. The model is listed as Cloudflare-hosted: https://developers.cloudflare.com/workers-ai/models/gemma-4-26b-a4b-it/. Official data-use: no training on Customer Content; zero retention for standard inference (except limited legal or security reasons, or storage we ourselves enable — AI Gateway is not used, so chat content is not sent on to another AI provider; chat messages are not stored in KV, D1, R2 or Durable Objects): https://developers.cloudflare.com/workers-ai/platform/data-usage/. Workers AI sub-processors disclosed by Cloudflare include CoreWeave, Inc. (United States) and Nebius BV (England), not Google: https://www.cloudflare.com/gdpr/subprocessors/cloudflare-services/ (last updated 1 October 2025). Google supplies the model under the Apache License 2.0: https://ai.google.dev/gemma/docs/gemma_4_license. Transfer safeguards: as in the Cloudflare row above. |
| Google Cloud EMEA Limited (Google Workspace) | Hosting of the [email protected] mailbox and related Google Workspace services used to receive and reply to enquiries, briefs and client email | For a UK Google Workspace customer, the contracting entity is Google Cloud EMEA Limited (70 Sir John Rogerson's Quay, Dublin 2, Ireland): https://cloud.google.com/terms/google-entity and https://cloud.google.com/terms/. The Cloud Data Processing Addendum (Customers) is incorporated into the Google Cloud Terms of Service: https://cloud.google.com/terms/data-processing-addendum. UK transfers: the UK International Data Transfer Addendum (Version B1.0) in that addendum, and Google's Alternative Transfer Solution for UK personal data to the United States (Google LLC's certification under the UK Extension to the EU-US Data Privacy Framework): https://cloud.google.com/terms/alternative-transfer-solution. |
|---|---|---|
| Tide Platform Limited | Our business bank account, used to receive bank transfers and to issue Tide payment links | United Kingdom. Tide administers the Tide Business Account. |
| Adyen N.V. | Processing of card and digital-wallet payments (including Apple Pay and Google Pay) made on a Tide payment link. Card details go to Adyen; I-OSCC Ltd does not receive the full card number | The Netherlands (an adequate country for UK GDPR transfers). Tide's official Payment Links terms name Adyen N.V. as the payment processor: https://www.tide.co/terms/payment-links-terms-and-conditions/. Tide also states that, for Payment Links, customer payment details are securely stored and visible only to Adyen: https://www.tide.co/accept-payments/. |
If your Order Form names a website or shop platform (for example Wix or Shopify), that platform is an authorised sub-processor for your site only, on the terms of that platform's data-processing agreement as it applies to I-OSCC Ltd's account. Those details will be recorded on your Order Form before we start processing on that platform.