Data Processing Agreement

When we host or manage a platform for you, we handle your data on your instructions. This sets out how — the terms UK GDPR requires between a controller and its processor.

Data processing illustration
  • 20+ years professional development
  • Elgin-based, working UK-wide
  • Fixed-price proposals
  • 90-day managed launch care
  • PageSpeed 80+ on every build
  • UK company & ICO-registered
  • Cloudflare-protected
  • Stripe secure payments

This agreement applies when we host or manage a platform for you (a website, system, or application) and, in doing so, handle personal data belonging to your business and your users. For that data, you are the data controller and we are your data processor — you decide why it’s processed, and we process it on your instructions to run the service you’re paying for. It forms part of your care-plan or hosting agreement and sits alongside our Terms & Conditions and Privacy Policy. It’s separate from data where we are the controller (your account, billing, and enquiry records) — that’s covered by our Privacy Policy.

What we process, and why

  • Subject matter: hosting, backing up, securing, and maintaining your platform.
  • Duration: for as long as we host or manage the platform, plus the short wind-down period described under “When we stop” below.
  • Nature and purpose: storage, backup, security scanning and patching, and keeping the platform running — nothing else, unless you instruct it.
  • Types of personal data: whatever your own platform collects (for a typical business site, usually contact and enquiry details, account records, and order or customer data). You decide what your platform collects, not us.
  • Categories of data subject: your customers, users, staff, and contacts — whoever interacts with your platform.

Our obligations to you

  1. Only process on your instructions — your hosting or care-plan agreement is your standing instruction. If a law forces us to do something else, we’ll tell you first unless that law forbids it.
  2. Keep it confidential — anyone with access is bound by confidentiality.
  3. Keep it secure — appropriate technical and organisational measures, set out in Annex B below.
  4. Use only approved sub-processors — the current list is in Annex A. We’ll give you advance notice before adding or replacing one, so you can object.
  5. Help you meet data-subject requests — if one of your users asks to access, correct, or delete their data, we’ll help you respond within the legal timeframe.
  6. Help you stay compliant — with security, breach handling, and data-protection impact assessments, taking into account what we know as your processor.
  7. Tell you about a breach without undue delay — if we become aware of a personal-data breach affecting your platform, we’ll notify you promptly with the detail you need to meet your own duty to report to the ICO within 72 hours. You report to the ICO; we support you.
  8. Return or delete your data when we stop — see “When we stop”.
  9. Let you verify this — we’ll make available the information you reasonably need to show we’re meeting these obligations, and allow for an audit on reasonable notice.

Your obligations to us

You confirm that you have a lawful basis for the personal data your platform processes, that your instructions to us are lawful, and that you’ll tell us in advance if your platform will process special-category data (health, biometric, and similar) so we can agree any extra safeguards.

Where your data is held

Your platform is hosted in the UK (Fasthosts). Some sub-processors listed in Annex A may process limited data outside the UK; where that happens it’s covered by a UK-recognised safeguard — the UK International Data Transfer Agreement (IDTA) or Addendum, or the UK Extension to the EU-US Data Privacy Framework.

When we stop

When our hosting or management of your platform ends, you can request to leave from your client portal (or in writing), and we provide a full handover so you can run the platform elsewhere with nothing held back: your codebase, a database export, your files, and the relevant credentials and configuration your platform needs to run (such as connection strings and API keys), in usable, unencrypted form. This is described on our Support page. After you’ve confirmed receipt, we securely delete our copies — except anything we’re legally required to retain — and confirm deletion in writing on request.

Priority and liability

Where this agreement and our general Terms differ on data-protection matters, this agreement wins. Our overall liability remains subject to the limits in our Terms & Conditions.

Annex A — Sub-processors

The specific providers that make the hosted service work, each under their own confidentiality and security terms.

Sub-processor Purpose Location
Fasthosts UK hosting infrastructure for your platform UK
Microsoft Azure Cloud services and secrets storage (Key Vault) UK / EU, with UK safeguards
Cloudflare Content delivery, DDoS protection, WAF, bot filtering (Turnstile) Global edge, with UK safeguards
Microsoft Graph Sending operational email (reports, notifications) UK / EU, with UK safeguards
Stripe Payment processing (we never see full card details) UK / US, with UK safeguards
HetrixTools Uptime monitoring (platform availability) for plans that include it US, with UK safeguards
Migadu Client mailbox hosting, for plans/add-ons that include managed email Switzerland, with UK safeguards

Annex B — Security measures

Encryption in transit (TLS/HSTS) and at rest; role-based access control with least privilege; continuous automated security scanning and patching to our minimum security standard; a web application firewall and edge protection; daily encrypted off-site backups with plan-based retention; structured operational logging kept to a minimum and free of marketing data; and UK data residency for hosting.

Annex C — Processing details

As set out under “What we process, and why” above, scoped to the platform(s) named in your hosting or care-plan agreement.

This agreement was last reviewed in July 2026.