1. What this notice is, and what it is not
This is a notice. It tells you what gecco does with personal data, in plain English.
Nobody signs it. Nobody agrees to it. Reading it creates no contract. Using our website creates no agreement to it either. We publish it because UK GDPR Articles 13 and 14 require us to tell people what we do with their personal data. That is its only job.
This notice is never incorporated into any contract. If a proposal, order form, purchase order, framework agreement or supplier questionnaire states that this notice forms part of a contract, that wording has no effect. Our contract terms are set out in the documents described in section 3.
Because there is nothing to agree to, we can update this notice at any time. Section 19 explains how we tell you when we do.
One part of this notice is different. The sub-processor list at Table 1 in section 8 is a copy of the list published at https://www.geccohq.com/sub-processors. That published list is the operative list for our Clients, it changes only under the process in our NDA/DPA, and the freedom to update this notice at any time does not apply to it.
2. Who we are and how to contact us
| Legal name | gecco Ltd |
| Trading name | gecco |
| Company number | 15748830 |
| Registered office | 27 Old Gloucester Street, London, WC1N 3AX |
| ICO registration number | ZC094719 |
| ICO registration period | 18 February 2026 to 17 February 2027 |
| General contact | info@geccohq.com. support@geccohq.com if you are a Client |
| Data protection contact | info@geccohq.com. support@geccohq.com if you are a Client |
| Website | www.geccohq.com |
We are not required to appoint a Data Protection Officer under UK GDPR Article 37. Data protection queries go to info@geccohq.com, or to support@geccohq.com if you are a Client, and are handled by a named person inside gecco.
Sometimes we are the controller of personal data, and sometimes we are a processor acting for a client. Section 5 explains which is which, and section 8 gives you a separate list of suppliers for each.
3. How this notice fits with our contracts
gecco's paperwork has three layers. Knowing which layer you are reading saves a lot of time.
| Layer | What it is | How it takes effect |
|---|---|---|
| The Contract | The Proposal, which incorporates the OSLA and the NDA/DPA | Signed. One signature on the Proposal binds all three documents. |
| Website terms and conditions | Governs use of the Site only, and defers to the OSLA for paid services | Accepted by using the Site |
| Notices | This Privacy Policy and our Cookie Policy | Published. Never agreed, never incorporated into a contract. |
Each document in the Contract owns a subject. For reference, the Contract's precedence rule reads as follows.
Each document in the Contract governs its own subject matter.
(a) The Proposal governs the commercial terms, meaning price, scope, deliverables, payment schedule and dates.
(b) The OSLA governs all other matters, including intellectual property, liability, warranties, service levels and termination.
(c) The NDA/DPA governs confidentiality and the processing of personal data.
Where a document contains a term outside its own subject matter, that term has no effect. Where two documents genuinely conflict within the same subject matter, the document that owns that subject matter prevails.
This notice is not one of those documents. It sits outside the Contract. It creates no rights and no obligations between gecco and any client. Where you need the binding data protection terms, meaning our Article 28 obligations, confidentiality, sub-processor approval, breach notification and data subject rights assistance, read the NDA/DPA.
4. Definitions
"gecco", "we", "us", "our" means gecco Ltd, registered in England under company number 15748830, whose registered office is at 27 Old Gloucester Street, London, WC1N 3AX.
"you", "your" means you as an individual, wherever this notice is talking about personal data. "the Client" means the organisation named in the Proposal. This is the one place our documents differ, and it is deliberate: personal data belongs to people rather than organisations, so a privacy notice has to speak to the individual. Everywhere else in our contract documents, "you" means the client organisation.
"Proposal" means the gecco proposal, service order or contract document signed by you, whatever it is titled, which sets out the commercial terms.
"OSLA" means the gecco Online Subscription and Licensing Agreement, published at https://www.geccohq.com/osla.
"NDA/DPA" means the gecco Mutual Non-Disclosure and Data Processing Agreement, published at https://www.geccohq.com/nda-dpa.
"Contract" means the Proposal, the OSLA and the NDA/DPA together.
"AI Solutions" means the skills, projects, artefacts and schedules that gecco designs, deploys or maintains within your Workspace.
"Advanced AI Solutions" means websites, web applications, custom MCP connectors, agent builds and automation builds that gecco designs, builds or maintains for you. They are scoped and priced in your Proposal.
"Solutions" means AI Solutions and Advanced AI Solutions together. gecco uses this word to describe everything it builds. Where this notice describes what gecco does with personal data it names AI Solutions or Advanced AI Solutions, so that it is always clear which is meant.
"Platform" means the third-party AI platform selected for your deployment.
"Platform Provider" means the operator of that Platform.
"Workspace" means the environment in which AI Solutions are built, tested or deployed, whether yours or gecco's.
"Services" means the design, deployment, maintenance, training and consultancy gecco provides under the Contract.
"Privacy Policy" means the gecco privacy notice published at https://www.geccohq.com/privacy-policy.
"Site" means www.geccohq.com.
5. The two ways personal data reaches us
Almost every question we get from a client auditor comes down to one thing. Who is responsible for what, and when. There are two answers, because there are two different data flows. They are separate and we do not merge them.
5.1 Flow A: your own workspace. This is the normal case.
Most gecco work happens inside your own Workspace, on a Platform you licence yourself.
- You buy the Platform licences directly. gecco never buys licences on your behalf and never invoices you for them.
- You are the Platform Provider's customer. You hold the agreement and the data processing terms with the Platform Provider directly. In data protection terms, the Platform Provider is your processor, not ours.
- You are the controller of the personal data your team puts into the Platform.
- gecco holds a licensed seat inside your Workspace, usually delivery@geccohq.com, so we can build and maintain your AI Solutions. For that work gecco acts as your processor, on your instructions, under the NDA/DPA.
- gecco is not the exporter for anything that happens inside your Workspace. Any transfer of data by the Platform Provider is a transfer under your agreement with them, not under ours.
Your use of the Platform is governed by your own agreement with the Platform Provider. We make no statement about where a Platform Provider stores data, how long it keeps it, whether it uses it to train models, or which transfer mechanism it applies. You are responsible for reviewing and accepting those terms and confirming the current position directly with the Platform Provider.
Where the work happens depends on the plan you hold with your Platform Provider.
- If you are on a Teams plan or an equivalent business plan, we may design, prototype and test in our own workspace before deploying into yours. We do not put personal data or sensitive business information into our workspace when we do this. We remove it, or replace it with sample data, first.
- If you are on an Enterprise plan, or you have data residency requirements, we design, build and test only inside your own environment. We do not use our own workspace for your engagement at all. Tell us before delivery starts so we can arrange it.
Some delivery work still happens in our own systems. We hold the documents you send us, we record and transcribe our sessions with you, and we keep our delivery notes and specifications in our own repositories. That work sits in Flow B, and section 8 lists the providers involved.
5.2 Flow B: gecco's own tools. This is where your material sits while we deliver.
Some work happens in gecco's own systems rather than yours. We hold the documents you send us in our own Microsoft 365 tenant. We record and transcribe our sessions with you. We use our own Claude Teams workspace to analyse those transcripts and produce the notes, actions and specifications your engagement needs. We keep those documents in our own private repositories, and we run our own project, file and workflow systems to manage the engagement.
Where personal data belonging to you reaches those tools, the position is different.
- gecco is your processor.
- The providers behind gecco's tools are gecco's sub-processors. They are listed in Table 1 in section 8.
- gecco is the exporter for this flow, and the transfer safeguards in section 9 are ours.
We keep Flow B to what the work needs. Where a task can be done with sample or anonymised data, we use that rather than your real records. Building and testing an AI Solution is one of those tasks, so where we prototype in our own workspace we do not put personal data into it. Delivery working material is different. Your documents, our recordings and transcripts, and our notes and specifications sit in our own systems whichever plan you hold, and section 8 lists the providers involved.
5.3 The two flows side by side
| Question | Flow A: your Workspace | Flow B: gecco's own tools |
|---|---|---|
| Whose Workspace is it | Yours | gecco's |
| Who is the controller | You | You |
| What is gecco | Your processor, working through a licensed seat | Your processor |
| What is the Platform Provider to you | Your own processor, under your own agreement | Not applicable to this flow |
| Whose sub-processors are involved | Yours, not ours | Ours, listed in Table 1 |
| Who is the exporter for international transfers | You, under your agreement with the Platform Provider | gecco |
| Which document sets the rules | Your agreement with the Platform Provider, plus our NDA/DPA for gecco's own access | Our NDA/DPA |
5.4 Website visitors and enquirers
There is a third group of people who are in neither flow. If you visit the Site, download a resource, book a meeting, subscribe to the newsletter or send us an enquiry, gecco is the controller of that data. Nobody instructs us. We decide what to do with it, and this notice tells you what that is.
6. What personal data we handle, and where we get it
6.1 As a controller: website visitors, enquirers, prospects, clients and delegates
- Identity and contact data. Name, job title, organisation, work email address, work phone number.
- Enquiry content. Anything you write in a form, an email or a meeting booking.
- Meeting data. The time you booked, the event type, attendance, and any notes we take.
- Commercial data. Proposals, quotes, orders, purchase order references, contract records.
- Billing data. Billing contact, billing address, invoice and payment records. Card details go straight to Stripe. We never see or store your card number.
- Marketing data. Subscription status, consent records, opt-out records, and whether you opened or clicked an email.
- Training data. Delegate name, work email, organisation, attendance, assessment results and certificates.
- Technical data. IP address, browser and device type, operating system, referring URL, pages viewed, session activity, approximate location at country or region level, and cookie identifiers.
- Session recordings and transcripts. Audio or video of a meeting or training session, and the written transcript produced from it, including anything said while the recording is running.
- Survey and assessment responses. What you tell us in any gecco survey, including the AI Adoption Survey and any adoption, feedback or training survey, or in an AI readiness assessment.
- Delivery working notes. The notes, action lists and specifications we write from a session, which may name you or refer to your role.
We do not seek special category data, meaning data about health, race, religion, sex life, sexual orientation, political opinions, trade union membership, genetics or biometrics. Please do not send it to us through the Site or an enquiry form. If an engagement genuinely requires it, we agree that separately in writing first.
We do not seek criminal offence data, and we do not process it unless a client engagement genuinely requires it and we have agreed the additional safeguards in writing in advance.
6.2 As a processor: personal data inside AI Solutions
When we build and maintain AI Solutions for a Client, we may handle personal data that the Client puts into its own systems. What that data contains is decided by the Client, not by us. In practice it is usually staff names and work contact details, the content of documents and messages the Client asks an AI Solution to work with, and records of the Client's own customers or members.
We process this data only on the Client's documented instructions. The NDA/DPA sets out the subject matter, duration, nature and purpose of that processing, and the obligations we owe.
6.3 Where we get personal data from
Under UK GDPR Article 14 we have to tell you when we did not get your data from you directly. Our sources are:
- You, when you fill in a form, send an email, book a meeting or sign a contract.
- Your employer or a colleague, for example when a Client adds you to an engagement, books you onto training, or names you as a contact.
- Public sources, such as company websites, Companies House, public registers and professional networking profiles.
- Business contact data providers, including Apollo, for bought or supplied lead lists containing work contact details used in business development. Where we contacted you from a list like this, you did not give us your data yourself, and this section is how we tell you where it came from.
- Our own systems, when you use the Site.
If we contacted you and you want to know where we got your details, ask us at info@geccohq.com, or at support@geccohq.com if you are a Client, and we will tell you.
7. Why we process personal data, and our lawful basis
This section covers the processing where gecco is the controller. Where gecco is a processor, the lawful basis is the Client's to identify, not ours.
| Purpose | Data used | Lawful basis | |
|---|---|---|---|
| Answering enquiries sent by form, email or phone | Identity, contact and enquiry content | Legitimate interests. You asked us something and we want to answer it. | |
| Booking and running meetings | Identity, contact and meeting data | Legitimate interests before a contract exists. Contract once you are a client. | |
| Preparing proposals, quotes and scoping documents | Identity, contact and commercial data | Legitimate interests before a contract exists. Contract once you are a client. | |
| Business development contact with people at organisations we think we can help | Work name, job title, work email, work phone, organisation | Legitimate interests, subject to the electronic marketing rules in PECR. We stop as soon as you ask. | |
| Sending marketing emails and the newsletter | Identity, contact and marketing data | Consent. You opted in and you can withdraw at any time. | |
| Delivering the Services and administering client accounts | Identity, contact, commercial and service records | Contract | |
| Running training and issuing certificates | Training data | Contract with the Client, and legitimate interests in giving the named delegate their certificate. | |
| Taking payment | Billing data | Contract | |
| Keeping accounting and tax records | Billing and transaction records | Legal obligation, under the Companies Act 2006 and HMRC record-keeping rules. | |
| Website analytics and improving the Site | Technical data | Consent for setting the cookies, under PECR. Legitimate interests for the analysis that follows. | |
| Measuring our advertising and showing you our adverts on other sites | Technical data | Consent, given on our cookie banner. You can withdraw it at any time. | |
| Security, fraud prevention and keeping the Site available | Technical data, request logs, security events | Legitimate interests | |
| Handling complaints, disputes and legal claims | Whatever is relevant to the matter | Legitimate interests in establishing, exercising or defending legal claims. Legal obligation where a regulator or court requires it. | |
| Recording and transcribing client sessions | Identity, contact, voice as transcribed, session content | Contract with the Client. We tell participants before recording starts, and anyone can ask us not to record. | |
| Recording and transcribing sales and pre-sales meetings | 3.10 | Identity, contact, voice as transcribed, meeting content | Legitimate interests in keeping an accurate record of what was discussed and agreed. We tell participants before recording starts. |
| Analysing session transcripts to produce delivery documents | Session content, job titles, names where mentioned | Contract with the Client. This is how we identify what to build. | |
| Collecting feedback on our training | Identity, contact, delegate feedback | Legitimate interests in improving our service and evidencing outcomes. Answering is optional. | |
| The AI readiness assessment | Identity, contact, and the answers given | Legitimate interests in assessing whether we can help, and in responding to the enquiry. |
Where we rely on legitimate interests, we have carried out a balancing test and concluded that our interest does not override your rights and freedoms. You can ask us for a summary of that assessment at any time.
8. Who we share personal data with: the two tables
8.1 Why there are two tables
We use suppliers for two different things, and the law treats them differently, so we list them separately.
When we handle personal data on behalf of a Client, the Client decides what happens to it and we act on the Client's instructions. The Client is the controller and gecco is the processor, so any supplier we bring in is a sub-processor. Those suppliers are in Table 1, which exists to satisfy UK GDPR Article 28. When somebody visits our website or sends us an enquiry, nobody instructs us. We decide what to do with that data ourselves, so gecco is the controller and the suppliers we use are our own processors. Those are in Table 2, which exists to satisfy Articles 13 and 14.
In short. If you are a client auditing us, or you are working through the NDA/DPA, Table 1 is the one you want. If you are a website visitor or a prospect asking what happens to your enquiry, Table 2 is the one you want. Some data does not touch either table, because in Flow A it stays inside your own Workspace with your own Platform Provider.
8.2 Table 1: sub-processors of client data
This is the Article 28 list. It covers the suppliers who may touch personal data that gecco processes on behalf of a Client, where the Client is the controller and gecco is the processor.
This table is reproduced from the list published at https://www.geccohq.com/sub-processors as a courtesy copy. The published sub-processor page is the operative list for Clients, and it changes only under the notice and objection process in clause 14 of the NDA/DPA. If this table and the published page differ, the published page prevails.
| Provider | Purpose | Processing location, as notified by the provider | Transfer basis |
|---|---|---|---|
| Microsoft Limited, a United Kingdom company, Microsoft Campus, Thames Valley Park, Reading, Berkshire RG6 1WG, VAT GB724594615 | gecco's own Microsoft 365 tenant. SharePoint client folders, Teams client sessions and their recordings and transcripts, OneDrive, email, and Microsoft Forms feedback surveys | United Kingdom for Exchange Online, Microsoft Teams, OneDrive and SharePoint. Microsoft does not publish a location for Microsoft Forms | Covered by UK adequacy regulations. No Article 46 safeguard is required. |
| Google Cloud EMEA Limited, Velasco, Clanwilliam Place, Dublin 2, Ireland | Google Workspace. Email, calendar and document collaboration used to run your engagement, and the gecco shared drives holding client contract records | Europe, where gecco's data region is set to Europe. The policy covers certain core services | Covered by UK adequacy regulations for the EEA. The contracting entity is in Ireland rather than the United States. The data region policy covers certain core services only, so logs and cached content sit outside it and gecco records that rather than estimating a location for them. |
| Google Cloud EMEA Limited, in respect of Google Meet | Recording of client kick-off, scoping, onboarding, advisory and showcase sessions held on Google Meet, and the "Notes by Gemini" document Meet writes of the session whether or not it is recorded. Saved to the meeting organiser's personal My Drive | Europe, where gecco's data region is set to Europe | Covered by UK adequacy regulations for the EEA. The contracting entity is in Ireland rather than the United States |
| GitHub, Inc. | Private repositories holding client delivery material and session transcripts, synchronised between gecco devices | United States. No UK region is offered for this service | Article 46 safeguard, being the EU standard contractual clauses with the UK International Data Transfer Addendum issued by the Information Commissioner under section 119A(1) of the Data Protection Act 2018, incorporated by the provider's data processing agreement. |
| Applications installed on gecco's GitHub organisation | Third-party applications connected to gecco's repositories, which hold client session transcripts, pain-point registers and delivery material. They are Claude and Claude Design Import, published by Anthropic; ChatGPT Codex Connector, published by OpenAI; Netlify, published by Netlify; Supabase; and one application installed for a client's own project | Each provider's own infrastructure. For the Anthropic, OpenAI and Netlify applications, as stated in those providers' entries | The Anthropic, OpenAI and Netlify entries in this table apply to their applications. gecco does not currently use Supabase or the client project's application to process client personal data, so no separate transfer basis is recorded for them |
| Anthropic Ireland, Limited | gecco's own Claude Teams workspace, used to analyse session transcripts and produce delivery documents. Also reached through the Anthropic API from gecco's own automations, for analysis of client session transcripts, extraction of actions and pain points, drafting of client-facing session emails and delivery documents, processing of the files a Client uploads to gecco, evaluation and enrichment of generated documents, session preparation briefs, and mapping of imported lead lists | United States. No UK or EU storage option is offered for this service | Article 46 safeguard, being the EU standard contractual clauses with the UK International Data Transfer Addendum issued by the Information Commissioner under section 119A(1) of the Data Protection Act 2018, incorporated by the provider's data processing agreement. |
| Wispr AI, Inc., trading as Wispr Flow | Recording and transcription of client sessions through Wispr Flow Notetaker, and dictation through Wispr Flow Dictation, on gecco's own Teams plan. When Notetaker is connected, it also reads the calendar, contacts and directory of the gecco Google account that connects it, to identify meetings and participants | United States, as the provider's privacy policy states | Article 46 safeguard, being the EU standard contractual clauses with the UK International Data Transfer Addendum, incorporated by the provider's data processing addendum, which applies when personal data is sent through the service |
| OpenAI OpCo, LLC, a Delaware company, company number 7063675 | gecco's own ChatGPT Business workspace, used to design, prototype and test AI Solutions where ChatGPT is the Platform for your engagement. Also gecco's own account reached through the API from gecco's own automations, for service order generation and document drafting. The sales pipeline and post-meeting processing uses are prospect data where gecco is the controller and are listed in the Privacy Policy's Articles 13 and 14 table | United States by default. The provider offers a United Kingdom option at gb.api.openai.com for storage only, with no regional processing, which must be configured per project. That option is for the API. Data residency is not available on ChatGPT Business | Article 46 safeguard, being the EU standard contractual clauses as amended by the UK International Data Transfer Addendum issued by the Information Commissioner under section 119A(1) of the Data Protection Act 2018, incorporated by the provider's data processing agreement. No Data Privacy Framework certification. API data is not used for model training by default. |
| Google LLC, in respect of the Gemini API | Research and drafting within gecco's own automations, including the core documents pipeline. A different service from Google Workspace above | Any country in which Google or its agents maintain facilities, as the provider's Gemini API terms state | Covered by UK adequacy regulations under the UK Extension to the EU-US Data Privacy Framework. The provider holds a current certification under that framework. |
| Zoho Corporation Limited, registered in England and Wales, company number 13424508 | Client relationship management and client communications used to run your engagement. Client personal data sits in Zoho CRM; in Zoho Sign, which holds signed service orders and the names of the people who signed them; in Zoho Campaigns, which holds the client contact subscribed to the onboarding mailing list; and in Zoho Forms. gecco's own task management may incidentally carry the name of a client contact, and holds no client files or client contact records | Netherlands, with Ireland as secondary. The provider states that support staff in India may access data where gecco grants support access | Covered by UK adequacy regulations for the storage locations. Where support access is granted, the provider's own transfer terms apply. gecco has a United Kingdom data processing addendum with the provider |
| n8n GmbH | Workflow automation used to run the pipelines we build and operate for you | Germany and Sweden | Covered by UK adequacy regulations. No Article 46 safeguard is required. |
| Calendly LLC | Scheduling of onboarding, training and delivery sessions with your staff, including any free text your staff type into the booking questions, and the email addresses of additional guests added to a booking | United States | Covered by UK adequacy regulations under the UK Extension to the EU-US Data Privacy Framework. The provider holds a current certification under that framework. |
| Netlify, Inc. | Hosting of gecco's internal delivery site, whose published walkthroughs carry client staff names and the text of client deliverables | United States | Covered by UK adequacy regulations under the UK Extension to the EU-US Data Privacy Framework. The provider holds a current certification under that framework. |
| Lunaweb GmbH, Grünwald, Germany, trading as CloudConvert | Conversion of service order and contract documents to PDF. The whole rendered document, including signatory and contact details, is sent to the provider | Germany or the United States, the provider's two processing regions, as its API documentation states | Covered by UK adequacy regulations for the contracting entity, Lunaweb GmbH, in Germany. gecco and the provider have signed a data processing agreement that covers the UK GDPR. |
How to read the location column. Each location is either the one the provider publishes or the one set in gecco's own account. Where a provider publishes no location, the cell says so rather than estimating one. gecco keeps the record of where each entry came from and will show it to a Client on request.
Three points about this table.
First, Anthropic and OpenAI appear here because gecco uses its own accounts with them for Flow B work, meaning development, testing and problem solving in gecco's own tools. They are not in this table because of any Platform you licence yourself. If you licence a Platform directly, that Platform Provider is your processor under your own agreement, not gecco's sub-processor, and it does not belong in this table at all.
Second, the data locations shown are the regions configured for gecco's own account with each provider at the date of this notice. Providers change their infrastructure and their terms. We do not make claims about any provider's current arrangements on their behalf. Ask us and we will confirm the position at the time.
Third, we tell Clients before we add or replace a sub-processor, and Clients can object, in line with the NDA/DPA. We give at least 30 days' notice, except where we have to replace a supplier urgently to keep the Services running or to protect security, in which case we tell Clients as soon as we can. The objection right applies either way.
Perplexity is not listed here. gecco uses Perplexity only for marketing research from public sources, and no client personal data reaches it. It appears in Table 2.
8.3 Table 2: processors of website and enquiry data
This is the Articles 13 and 14 list. It covers the suppliers who may touch personal data about website visitors, enquirers, prospects and our own commercial contacts, where gecco is the controller.
| Provider | Purpose | Processing location, as notified by the provider | Transfer basis |
|---|---|---|---|
| Webflow, Inc. | Website hosting and content management. The Site links out to the AI readiness assessment form on gecco's Tally domain; it does not embed or iframe it, so Webflow does not capture that form. Webflow does run ten or more of its own native forms collecting name, email address, company, job title and a consent checkbox, and stores those submissions itself | United States | Covered by UK adequacy regulations under the UK Extension to the EU-US Data Privacy Framework. The provider holds a current certification under that framework. |
| Usercentrics A/S, Copenhagen, Denmark, company number DK34624607, trading as Cookiebot | Cookie consent management across the Site, and the cookie declaration listing on the cookies policy page. The consent banner is deployed site-wide through Google Tag Manager and is shown to a visitor until they answer it. Usercentrics receives a request, and therefore an IP address, from every visitor to the Site | EEA, Denmark | Covered by UK adequacy regulations for the Danish entity. |
| Calendly LLC | Meeting scheduling, routing-form submissions, booking confirmations and the free-text answers invitees type into the booking questions, including reasons given when a booking is cancelled. Calendly also holds the email addresses of additional guests added to a booking by someone else, who never used the booking form themselves | United States | Covered by UK adequacy regulations under the UK Extension to the EU-US Data Privacy Framework. The provider holds a current certification under that framework. |
| Cloudflare, Inc. | Two distinct services. Content delivery, DNS and security for the Site. And Cloudflare R2 object storage with a Cloudflare Worker, which holds the web copy of the AI readiness report and serves it to anyone who has its link | Content delivery is routed to the nearest location on the provider's global network. | Covered by UK adequacy regulations under the UK Extension to the EU-US Data Privacy Framework. The provider holds a current certification under that framework. |
| Google LLC, in respect of Google Analytics | Website analytics | United States and EEA | Covered by UK adequacy regulations under the UK Extension to the EU-US Data Privacy Framework. The provider holds a current certification under that framework. |
| Google Cloud EMEA Limited, in respect of Google Meet | Recording of sales and pre-sales meetings, and of client sessions held before June 2026, whose recordings gecco still holds | Europe, where gecco's data region is set to Europe | Covered by UK adequacy regulations for the EEA. |
| Microsoft Limited, a United Kingdom company, Microsoft Campus, Thames Valley Park, Reading, Berkshire RG6 1WG, VAT GB724594615, in respect of Microsoft Forms | Every gecco survey and feedback form. All of them run on Microsoft Forms in gecco's own Microsoft 365 tenant and the responses are held in gecco's SharePoint. This covers the AI Adoption Survey, sent at the start of an engagement to every member of the client's staff on the user details list, and any adoption, feedback or training survey gecco runs during or after an engagement. A survey may ask for the respondent's name as an optional field, and a gecco workflow records which named individuals have completed the AI Adoption Survey | Not published. Microsoft Forms is not listed on gecco's tenant Data Location Card, so the provider publishes no location for this service and gecco does not state one | Microsoft's own data processing terms apply. Where the respondents are a Client's staff, the same service is also covered by the Microsoft entry in Table 1 |
| Tally BV | Capture of the AI readiness assessment form. Payments and file uploads are not used on that form | Belgium | Covered by UK adequacy regulations. Tally sends no emails to the people who complete the form. gecco has switched off Tally's email notifications and uses neither payments nor file uploads, so none of the optional features that engage providers in the United States is in use. The readiness form is the only Tally form that has collected responses |
| S.A.S.U PDFShift, Paris, France | Converting the AI readiness report to PDF | France, hosted on OVH | Covered by UK adequacy regulations. No Article 46 safeguard is required |
| Zoho Corporation Limited | Records of prospects, enquiries and clients in our CRM, including the AI readiness assessment answers and scores; electronic signature of service orders through Zoho Sign; and marketing email through Zoho Campaigns where a person has consented. | Netherlands, with Ireland as secondary | Covered by UK adequacy regulations. No Article 46 safeguard is required. |
| n8n GmbH | Automation of the AI readiness assessment pipeline | Germany and Sweden | Covered by UK adequacy regulations. No Article 46 safeguard is required. |
| Anthropic Ireland, Limited, in respect of the Claude API | Checking that the name and email address given on the AI readiness form are genuine, and researching the enquirer's company to write the personalised body of the report. Also gecco's own marketing and newsletter automations. A different service from gecco's own Claude workspace in Table 1 | United States. No UK or EU storage option is offered for this service | Article 46 safeguard, being the EU standard contractual clauses with the UK International Data Transfer Addendum issued by the Information Commissioner under section 119A(1) of the Data Protection Act 2018, incorporated by the provider's data processing agreement. |
| OpenAI OpCo, LLC, in respect of the API | The sales pipeline and post-meeting processing. The whole transcript of a prospect meeting is sent, together with the attendee names, the participant roles, the lead's name and company, and in one workflow the lead's email address. A different use from gecco's own ChatGPT Business workspace in Table 1 | United States by default. The United Kingdom storage option is for the API and must be configured per project | Article 46 safeguard, being the EU standard contractual clauses as amended by the UK International Data Transfer Addendum issued by the Information Commissioner under section 119A(1) of the Data Protection Act 2018, incorporated automatically by the provider's data processing agreement at clause 4.2. No Data Privacy Framework certification. |
| Google Cloud EMEA Limited, in respect of Google Workspace | Google Sheets holds a permanent consent and audit log of readiness assessment submissions, being name, email address, company, score and the report link, which is also read back at the start of every later run to prevent duplicate submissions. Google Drive holds the generated PDF report, shared by a link that anyone holding it can open. Gmail sends the completed report to the enquirer and copies it to a gecco mailbox | Europe, where gecco's data region is set to Europe. The policy covers certain core services | Covered by UK adequacy regulations for the EEA. The contracting entity is in Ireland rather than the United States. The data region policy covers certain core services only, so logs and cached content sit outside it and gecco records that rather than estimating a location for them. |
| Companies House | Live lookup of public register data about the enquirer's company during the AI readiness assessment. Companies House is a United Kingdom public authority and acts as its own controller of the public register, not as a gecco processor | United Kingdom | No transfer takes place. No Article 46 safeguard is required. |
| ZenLeads, Inc., trading as Apollo.io | Historic supply of business contact data, being bought or supplied lead lists containing names and work contact details, used for business development. No longer used, and listed because records it supplied may still be held | United States | Covered by UK adequacy regulations under the UK Extension to the EU-US Data Privacy Framework. Apollo's entry on the Data Privacy Framework List, under the name Zenleads Inc. (dba Apollo.io), is active. |
| Kalemi Code, which provides Publer, headquartered in Tirana, Albania and incorporated in Wyoming, United States | Scheduling and publishing of gecco's own LinkedIn content. The data is gecco's own: a named gecco individual's personal LinkedIn profile is the connected account, and the published posts are gecco's. | Frankfurt, Germany, as the provider's privacy policy states | Covered by UK adequacy regulations for hosting in Germany. The provider states that it uses standard contractual clauses where a transfer outside the United Kingdom and the EEA requires them |
| Perplexity AI, Inc. | Marketing content research for articles and LinkedIn posts, from public sources only. No client or prospect personal data reaches this service | United States | Not applicable to this service, because no personal data is sent to it |
| SerpApi, LLC, a Texas limited liability company | Search-results lookup during the AI readiness assessment research step. The query is built from the enquirer's company name | United States. The provider names Amazon Web Services, Digital Ocean and Wasabi as its cloud providers and publishes no storage region | The provider publishes no data processing agreement, no standard contractual clauses, no UK Addendum, no Data Privacy Framework certification and no sub-processor list. gecco relies on the narrow scope of what is sent. |
| LinkedIn Ireland Unlimited Company | The LinkedIn Insight Tag loads on the Site and collects visitor IP address and advertising and retargeting cookies | Ireland and United States | Covered by UK adequacy regulations for the Irish entity. LinkedIn Corporation, which receives the data in the United States, has an active entry under the UK Extension to the EU-US Data Privacy Framework. |
| Google, in respect of Google Ads | The Google Ads conversion and remarketing tag loads on the Site. Advertising conversion and remarketing is a different purpose, and normally a different legal basis, from analytics | United States and EEA | Covered by UK adequacy regulations under the EU-US Data Privacy Framework UK Extension |
| Stripe Payments Europe, Limited, the contracting entity the Stripe Services Agreement names for United Kingdom users, and Stripe Payments UK Ltd, company number 08480771, 9th Floor, 107 Cheapside, London EC2V 6DN, with which gecco's transactions are conducted | Card payment processing for gecco's own invoices, used occasionally and by hand rather than on every invoice. Receives the billing contact, the billing address and the payment record. gecco does not see or store the card number, and no client's own customer data reaches this provider | The United States, India and other countries, as the provider's privacy policy states | Covered by UK adequacy regulations under the UK Extension to the EU-US Data Privacy Framework, which the provider's Data Transfers Addendum applies first. The provider holds a current certification under that framework. If that certification lapses, the UK International Data Transfer Addendum applies |
| Google, in respect of reCAPTCHA | Bot protection on the Site's forms. Receives behavioural signals and the IP address of everyone who uses a form | United States and EEA | Covered by UK adequacy regulations under the EU-US Data Privacy Framework UK Extension |
| Dropcontact SAS | Enrichment of prospect records. Receives email address, first name, last name, company, website, LinkedIn URL and country, and returns job title, LinkedIn URL and telephone number. Live in three workflows including the newsletter signup. A blocklist of personal email domains limits what is sent | France | Covered by UK adequacy regulations. No Article 46 safeguard is required |
| The Phantom Company, a French simplified joint stock company registered in Paris under number 818 723 629, operator of PhantomBuster | Historic supply of scraped business contact data, being names, work contact details and employment history, imported into the CRM for business development. An Article 14 source rather than a live processor | The European Union, as the provider's privacy policy and data processing agreement state | Covered by UK adequacy regulations for hosting in the EEA. The provider's data processing agreement permits onward transfers outside the EEA only under an adequacy decision or standard contractual clauses |
| Xero (UK) Limited, company number 06071722 | gecco's own statutory accounting and invoicing records. Client billing contact first name, last name and email address are written by automation on every structured deal | The United States, on Amazon Web Services, with some processing in New Zealand, as the provider states | The contracting entity is in the United Kingdom, so no restricted transfer takes place. The provider's data processing addendum, which applies automatically, allows its own onward transfers only to adequate countries or under standard contractual clauses |
| Netlify, Inc. | Hosting of gecco's internal site, whose published walkthroughs carry real prospect records as well as client material | United States | Covered by UK adequacy regulations under the UK Extension to the EU-US Data Privacy Framework. The provider holds a current certification under that framework. |
| Lunaweb GmbH, Grünwald, Germany, trading as CloudConvert | Conversion of the service order to PDF before signature. The whole rendered document goes to the provider | Germany or the United States, the provider's two processing regions, as its API documentation states | Covered by UK adequacy regulations for the contracting entity, Lunaweb GmbH, in Germany. gecco and the provider have signed a data processing agreement that covers the UK GDPR. |
Processing locations in Table 2 are as notified to gecco by each provider at the date of this notice. gecco does not warrant that a provider's location or practices will remain the same. Where Table 2 records a specific transfer mechanism, it is the mechanism gecco has verified in that provider's published terms at that date.
Some suppliers appear in both tables because we use them for both jobs. Google is the clearest example. That is not a duplication error. The legal basis, the instructions and the responsibilities are different in each case.
8.4 Other people we may share personal data with
- Professional advisers, such as our accountants, insurers and solicitors, where they need it and are bound by confidentiality.
- Regulators, law enforcement and courts, where we are required to disclose by law, regulation or court order.
- A buyer or successor, if gecco is involved in a merger, acquisition or sale of assets. We would tell affected Clients.
We do not sell personal data, and we do not share it with data brokers. If you accept marketing cookies on our cookie banner, the Google Ads and LinkedIn tags listed in Table 2 use cookies to measure our advertising and to show you our adverts on other sites.
9. International transfers
Some of the suppliers we use are based outside the UK, mainly in the United States. When personal data moves outside the UK, UK GDPR Chapter 5 requires an appropriate safeguard.
The mechanisms we rely on are:
- The UK Addendum to the EU Standard Contractual Clauses, issued by the ICO.
- The UK International Data Transfer Agreement, known as the UK IDTA.
- UK adequacy regulations, where the UK government has decided that a country provides adequate protection.
Ask us at info@geccohq.com, or at support@geccohq.com if you are a Client, and we will tell you the position on the date you ask, and give you a copy of the safeguard we rely on.
For Flow A, gecco is not the exporter. Any transfer of data out of your own Workspace by your Platform Provider happens under your own agreement with them. Your use of the Platform is governed by your own agreement with the Platform Provider. You are responsible for reviewing and accepting those terms and confirming the current position directly with the Platform Provider.
10. How long we keep personal data
We keep personal data only for as long as we need it.
| What | How long | Why |
|---|---|---|
| Personal data inside your own Workspace, Flow A | You control this. It stays for as long as you keep it, under your own Platform settings and your own agreement with the Platform Provider. | You are the controller. |
| gecco's licensed seat in your Workspace | Removed when the engagement ends. | Least privilege. |
| Client personal data in gecco's own tools, Flow B | For as long as we need it to deliver the Services. On completion, on termination, or on your request, we stop processing it and return it or securely delete it at your election, then confirm in writing. | NDA/DPA, retention and deletion clause. |
| Enquiry and prospect records in our CRM | 24 months from the last meaningful contact, then deleted or anonymised. | So we do not sit on contact data we are not using. |
| Marketing consent records | Until consent is withdrawn. | To show we had a lawful basis to email you. |
| Marketing opt-out records | A minimal suppression record, being your email address and the fact that you opted out, kept for as long as we send marketing at all. | So we do not email you again by mistake. The ICO expects a suppression list. |
| Contract and service records | 6 years after the Contract ends. | Limitation Act 1980, the period during which a claim can be brought. |
| Invoices, payments and accounting records | 6 years from the end of the financial year they relate to. | Companies Act 2006 and HMRC record-keeping rules. |
| Training attendance records and certificates | 3 years from the session. | So we can reissue a certificate on request. |
| Website analytics data | 26 months from collection. | Enough for trend analysis, and the analytics platform default. |
| Cookie consent records | 12 months from the consent. | PECR. |
| Meeting bookings and scheduling records | 12 months from the meeting. | Follow-up and record of contact. |
| Security and access logs | 12 months. | Investigating incidents. |
When personal data is no longer needed, we delete it or anonymise it so it can no longer identify anyone. Deleted data may survive for a short period inside encrypted backups. We do not use those copies, and they go when the backup cycle expires. Clause 19.3 of our NDA/DPA says the same thing, so the contract and this notice agree.
11. Automated decision-making, profiling and AI
We do not make decisions about you by automated means alone that produce legal effects or similarly significant effects on you, as described in UK GDPR Article 22.
We use analytics tools, including Google Analytics, to understand how people use the Site. These tools group visitors by behaviour so we can improve the Site and our marketing. That is profiling under UK GDPR, but it produces no decision that significantly affects you. You can switch it off through your cookie preferences.
On AI specifically:
- gecco does not build or train AI models. We configure AI Solutions on top of Platforms that other organisations operate.
- We will not use your personal data to train, fine-tune or improve any AI model without your explicit written consent. gecco has no model of its own to train. This matches clause 11.3 of our NDA/DPA.
- What a Platform Provider does with data inside your own Workspace, including whether it is used for model training, is governed by your agreement with that Platform Provider. Check that agreement and confirm the current position with them.
- If a Client configures an AI Solution to make an automated decision with legal or similarly significant effects, the Client is the controller of that decision and is responsible for meeting Article 22 itself. We will flag it if we see it, and we will help, but it remains the Client's call and the Client's obligation.
12. How we protect personal data
- gecco is Cyber Essentials certified.
- gecco is registered with the ICO under registration number ZC094719.
- Multi-factor authentication is on for every account that can reach client data.
- We work on the principle of least privilege. In your Workspace we work through a single identifiable seat, usually delivery@geccohq.com, so you can see what we did and remove our access in one action.
- We select providers that offer encryption of data in transit and at rest, and we configure encryption where the setting is ours to make. What any individual provider does is set out in that provider's own terms, and you should confirm the current position with them.
- Where a task can be done with sample or anonymised data, we use that rather than your real records.
- When someone joins, changes role or leaves, we change or remove their access across every system they used.
No system is perfectly secure, and we will not pretend otherwise.
If a personal data breach happens:
- Where gecco is a processor for a Client, we notify the Client without undue delay after becoming aware, in line with the NDA/DPA.
- Where gecco is the controller, we report to the ICO within 72 hours where the breach is likely to result in a risk to people's rights and freedoms, and we tell the people affected without undue delay where the risk to them is high.
13. Your rights
Under UK GDPR and the Data Protection Act 2018 you have the following rights.
- Right of access. Ask for a copy of the personal data we hold about you.
- Right to rectification. Ask us to correct data that is wrong or incomplete.
- Right to erasure. Ask us to delete your personal data in certain circumstances.
- Right to restrict processing. Ask us to pause what we do with your data while something is checked.
- Right to data portability. Ask for the data you gave us in a structured, commonly used, machine-readable format.
- Right to object. Object to processing we base on legitimate interests. You can object to direct marketing at any time and we will always stop.
- Right to withdraw consent. Where we rely on consent, withdraw it at any time. That does not make our earlier processing unlawful.
- Rights relating to automated decision-making. See section 11.
To exercise any of these, email info@geccohq.com, or support@geccohq.com if you are a Client.
- We respond within one month. For complex or multiple requests we can extend by up to two further months, and we will tell you within the first month if we need to.
- There is no charge, unless a request is manifestly unfounded or excessive.
- We may ask you for proof of identity before we release personal data.
If your employer is a gecco client
If your data sits inside an AI Solution we built for your employer, your employer is the controller and gecco is only the processor. Send your request to your employer. If you send it to us instead, we will pass it to them promptly and help them answer it. We are not allowed to act on it ourselves without their instruction.
14. Complaining to the ICO
If you think we have handled your personal data unlawfully, you can complain to the Information Commissioner's Office.
| Website | https://ico.org.uk |
| Helpline | 0303 123 1113 |
| Address | Information Commissioner's Office, Wycliffe House, Water Lane, Wilmslow, Cheshire, SK9 5AF |
You can complain to the ICO at any time. We would like the chance to put it right first, so please contact us at info@geccohq.com, or at support@geccohq.com if you are a Client, if you can, but you are under no obligation to do so.
15. Marketing
You can stop marketing emails at any time. Click the unsubscribe link in any email we send, or email info@geccohq.com. We action opt-outs without undue delay and in any event within 30 days.
We may still send you service messages after you opt out of marketing. That covers things like billing notices, changes to the Contract, security notices and delivery updates. Those are necessary to run your account and are not marketing.
16. Cookies
We use cookies and similar technologies such as pixels and tags. We ask for your consent to non-essential cookies through a Cookiebot banner, which keeps a record of your choice.
Full details of every cookie we use and how to change your preferences are in our Cookie Policy at https://www.geccohq.com/cookies-policy.
You can opt out of Google Analytics across all sites using the Google Analytics opt-out browser add-on at https://tools.google.com/dlpage/gaoptout.
Most browsers offer a Do Not Track setting. There is still no agreed standard for how websites should respond to it, so we do not currently act on Do Not Track signals. If a standard is adopted that applies to us, we will follow it and update this notice.
17. Children
gecco sells to businesses. The Site and the Services are not directed at children and we do not knowingly collect personal data about anyone under 18.
If you believe a child has given us personal data, email info@geccohq.com and we will delete it.
18. Other websites
The Site links to other websites, including our providers, client case studies and social media. We are not responsible for how those sites handle personal data. Read their privacy notices before you give them anything.
19. Changes to this notice
We review this notice at least once a year, and whenever we change a supplier, add a sub-processor or change what we do with personal data.
When we update it, we change the version number and the "Last updated" date at the top. Where a change materially affects you, we will post a notice on the Site and, for Clients, tell you by email. Sub-processor changes are notified to Clients under the NDA/DPA, not through this notice.
Version history
| Version | Date | What changed |
|---|---|---|
| 3.26 | 23 September 2026 | Simplified the two supplier tables. No supplier, purpose, processing location or safeguard changed. |
| 3.25 | 22 September 2026 | Rewrote this notice. It now lists the suppliers that handle client data separately from those that handle website and enquiry data, explains when gecco is the controller and when it is the processor, covers our advertising cookies, and states where each supplier processes data and how it is protected. |
| 2.0 | 18 February 2026 | Previous version, last updated 6 July 2026. |
We keep a full record of changes and will share it with a Client on request.
20. Contact us
Questions about this notice, requests to exercise your rights, and requests for a copy of a transfer safeguard all go to the addresses below.
Email: info@geccohq.com, or support@geccohq.com if you are a Client
Post: Data Protection, gecco Ltd, 27 Old Gloucester Street, London, WC1N 3AX
gecco Ltd. Company number 15748830. ICO registration ZC094719.

