Skip to main content
Loading… Still loading…

Data Residency & Subprocessors

ThirdSectorIntel.ai  ·  Last updated: 3 November 2026

This page describes where ThirdSectorIntel.ai stores and processes data, and which third parties act as subprocessors on our behalf. It is intended to pre-answer the data-protection and security questions UK charity-sector buyers ask during procurement. A signed copy with effective dates is available under NDA — contact [email protected].

1. Primary data residency

All customer data — user accounts, session state, CRM records synced from Loxo, saved searches, shortlists, exports, and audit logs — is held on a dedicated server that we own and operate in the United Kingdom. Backup copies are also kept in the UK and the EU, as set out in Section 4.

Data categoryLocation at rest
Application database (SQLite, primary)Our own server, UK
Analytical data store (DuckDB / Parquet)Our own server, UK
Customer CRM sync (Loxo records)Our own server, UK
Session cookies / identity tokensCustomer browser + server memory, UK
Application logsOur own server, UK
BackupsUK and EU (see Section 4)

Connections to the service use TLS 1.2 or higher, and backups are sent over encrypted connections. The production server's disk is not encrypted at rest; access to the server is limited to our own administrators. Cloudflare and Google encrypt the backups they store. We do not add our own encryption to the database backups held on Netcup or on our UK backup devices.

2. International transfers

Three categories of subprocessor process data outside the UK:

  • Backup storage (EU, US) — copies of the application database, which includes customer data, are held with Netcup in Germany and in a Google Shared Drive. Archived data is held with Cloudflare in the EU.
  • AI model providers (US, EU, Singapore) — prompts and the immediate context required to answer them are sent to large-language-model APIs for enrichment of public charity-sector data, for user-facing natural-language search, and for the candidate and outreach tools described in Section 3.2.
  • Public-data / enrichment APIs (US, EU) — for sector signals (news, regulatory, sanctions, government datasets).

All transfers outside the UK rely on UK adequacy regulations where available, or on the International Data Transfer Agreement (IDTA) / EU Standard Contractual Clauses together with the UK Addendum and any supplementary measures required after the Schrems II decision. Moonshot AI is based in Singapore, which has no UK adequacy regulations, so one of these safeguards must be in place before we send it personal data.

3. Subprocessor list

The table below names every third party that processes personal data on our behalf, the purpose, and the location of processing. We notify customers under contract of any material change before a new subprocessor goes live.

3.1 Infrastructure & identity

We run the production server ourselves, so no hosting company holds the primary copy of your data.

SubprocessorPurposeRegion
NetcupBackup server: copies of the database and data files, and the long-term archiveGermany (Frankfurt)
CloudflareDNS, CDN, DDoS protection, WAF, the encrypted tunnel to our server, and backup storage (R2)Global edge; UK ingress; R2 storage in the EU
Google (OAuth 2.0)Sign-in identity providerUS / EU
Google Workspace (Gmail API, Drive API)Customer-authorised mailbox and document ingest; nightly backup of the application database to a Shared DriveUS / EU

3.2 AI model providers

We use third-party large-language-model APIs to enrich public charity-sector data (annual reports, news, public profiles), to power natural-language search inside the product, and to support our candidate and outreach tools. Anthropic is our main provider, and Google AI drafts some organisation briefs. Moonshot AI is listed below as a named alternate so we can route to whichever model is best-suited to a given task without a separate disclosure cycle. Adding any provider not listed here triggers customer notice under contract.

SubprocessorStatusPurposeRegionData sent
Anthropic (Claude)In useDocument enrichment, summarisation, natural-language search, candidate and outreach toolsUS (no-training API terms)Public charity data, the user's query text, and the candidate and contact details described below
Google AI (Gemini API)In useDrafting organisation briefsUS / EUPublic charity data
Moonshot AI (Kimi)Named alternateSame as Anthropic when selectedSingaporeSame as Anthropic when selected

We use Anthropic under its no-training API terms — prompts and completions are not used to train its models. Moonshot AI's published privacy policy lists training its models among the ways it uses information, so that statement does not apply to it. Provider-side retention follows each vendor's standard API terms.

CVs and candidate notes are sent to the AI provider in use when a user runs a candidate tool and when we index CVs for search. This includes the person's name and contact details. National Insurance numbers, passport numbers and dates of birth are removed first where they are labelled in the document. When a user drafts an outreach email, the recipient's first name, job title and organisation are sent. Enterprise customers may, by contract, pin processing to a single named provider.

3.3 Data sources & enrichment

SubprocessorPurposeRegion
Charity Commission for England and WalesPublic charity register, accounts, trustee dataUK
OSCR (Scotland) · CCNI (Northern Ireland)Public charity registersUK
Companies HousePublic company register, accounts, officersUK
NewsAPINews aggregation for sector signalsEU
DerrickB2B contact enrichment for public professional profilesEU / US
Bright DataCompany and people data from public LinkedIn profilesIsrael
HunterFinding and checking work email addressesBelgium (servers); US company
FindymailFinding and checking work email addressesEU (France)
People Data LabsLicensed dataset of professional profiles; we send it no dataUS
LoxoCustomer-authorised CRM sync — data flows in from the customer's tenancy at their directionUS

4. Backups, retention, and deletion

We back up the primary database and data files every night to the locations below.

LocationWhat it holdsKept for
Our own backup devices, UKDatabase and data files14 to 30 days
Netcup server, FrankfurtDatabase and data files14 days
Netcup server, Frankfurt (long-term archive)Application databaseUp to 2 years
Google Shared DriveApplication database14 days
Cloudflare R2, EUEncrypted server credentials and older snapshots of our sector dataCredentials 14 days; snapshots kept as a long-term record
  • Recovery — if the production server is lost, we rebuild the service from these backups, with a target of no more than 4 hours.
  • Logs — web server access logs are retained for 14 days and application logs for up to 24 months.
  • Account deletion — on customer request or contract termination, we delete or return customer data from our live systems within 30 days. Copies in backups are removed when those backups expire, on the schedule above, so a copy can stay in the long-term archive for up to two years. AI provider-side retention follows each vendor's published API terms.
  • Data subject requests — subject access, rectification, and erasure requests are handled within the statutory 30-day window. See our Privacy Policy for the process.

5. Changes to this page

Material changes — a new subprocessor, a change of processing region, or a change in the categories of data sent to an AI provider — are notified to customers under contract at least 30 days before they take effect. The “Last updated” date at the top of this page reflects any non-material change (clarifications, typo fixes, links).

6. Contact

For data-protection questions, security review, or a signed copy of this statement under NDA: [email protected]. See also our Privacy Policy and Data Processing Agreement.