Why sub-processors matter
Websites and SaaS platforms may use third-party providers for hosting, infrastructure, security, analytics, communication, support, payment, email delivery, backups or operational tooling.
Governance & Legal
This page explains how third-party provider information should be treated for EUAIC website and service contexts.
This page is written for website visitors, procurement teams, compliance reviewers and prospective customers. It is intended to make EUAIC’s website terms and policy position clear without pretending to be legal advice.
Websites and SaaS platforms may use third-party providers for hosting, infrastructure, security, analytics, communication, support, payment, email delivery, backups or operational tooling.
The public website may involve hosting providers, security services, analytics tools, form handling and communication services depending on the live configuration. The privacy and cookie policies should match the technologies actually in use.
For customer services, the relevant sub-processor list should be provided through the applicable agreement, data processing addendum, security pack or procurement response.
Provider lists can change as services evolve. Material changes should be managed according to the customer contract and data processing terms where applicable.
Providers should be reviewed for role, data access, security, location, retention, service importance and contractual protections where relevant.
Relevant supplier categories may include hosting, domain and DNS services, server management, analytics, email delivery, CRM, support desk, payment processing, backup, monitoring, security tools and professional advisers. The exact list should match the live service setup.
Not every supplier has the same access. Review should consider whether the provider stores personal data, only transmits it, has administrative access, processes logs, hosts files, supports the system or merely provides a public resource.
Where customer contracts require notice of new or replacement sub-processors, the notice route, objection period and consequences should be set out in the applicable agreement or data processing addendum.
This page is written for website visitors and corporate reviewers. It should be read together with the Legal Notice, Privacy Policy, Cookie Policy and Terms of Use. Where a customer has a signed agreement, order form, statement of work, data processing addendum or service schedule, that document will take priority over this general website wording for the relevant service.
Questions about this policy can be raised through the EUAIC contact route. A useful enquiry should identify the page, the concern, the affected service or communication, and any relevant reference. Policies should be reviewed when the website, service model, supplier stack, cookie configuration, platform features or customer contracting process changes.
These website policies are written for clear corporate communication. They do not replace a signed agreement, formal legal advice, regulatory advice, security assurance or a customer-specific data processing addendum.
Legal pages
Use these pages to review privacy, cookies, terms, security, accessibility and responsible AI information in a structured way.
Questions
It is a framework page. Customer-specific lists should match the live service.
Yes, where relevant to procurement or onboarding.
Some website tools may involve third parties and should be reflected in privacy or cookie information.