SUB-PROCESSORS

Third-party service providers used by eyre.ai

Last updated: 31/01/2026

 

WHAT ARE SUB-PROCESSORS?

Sub-processors are third-party companies that eyre.ai uses to help provide our secure meeting platform services. Under GDPR Article 28, we must:

✅ Only use sub-processors who provide sufficient guarantees
✅ Inform you about which sub-processors we use
✅ Give you the right to object to new sub-processors
✅ Ensure they meet the same data protection standards as eyre.ai

We take this responsibility seriously. Every sub-processor is:

✓ EU/EEA-based (no US or third-country sub-processors)

✓ GDPR-compliant with signed Data Processing Agreements

✓ ISO 27001 or SOC 2 certified (or equivalent)

✓ Regularly audited for compliance

✓ Subject to the same security standards as eyre.ai

CURRENT SUB-PROCESSORS

Infrastructure & Hosting

Hetzner Online GmbH

Service: Cloud hosting and infrastructure
Location: Germany 🇩🇪
Data centers: Falkenstein (Germany), Nuremberg (Germany)
What they process: All platform data, meeting metadata, recordings (encrypted)

Purpose:

Security & Compliance:

Data location guarantee: All data remains in Germany (EU)

Website: hetzner.com
Privacy policy: hetzner.com/legal/privacy-policy

Content Delivery

BunnyCDN (BunnyWay d.o.o.)

Service: Content Delivery Network (CDN)
Location: Slovenia 🇸🇮 (EU)
PoPs (Points of Presence): EU/EEA only (Germany, Netherlands, France, UK, Sweden, Poland, Czech Republic)
What they process: Meeting media streams (audio/video during transmission only – not stored)

Purpose:

Security & Compliance:

Data location guarantee: All PoPs within EU/EEA, data never routed outside Europe

Website: bunny.net
Privacy policy: bunny.net/privacy

Transactional Emails

Brevo (formerly Sendinblue SAS)

Service: Transactional email delivery
Location: France 🇫🇷
Data centers: Paris (France), Frankfurt (Germany)
What they process: Email addresses, names, email content (meeting invitations, notifications, support communications)

Purpose:

Security & Compliance:

Data location guarantee: All email data processed and stored in EU only

Website: brevo.com
Privacy policy: brevo.com/legal/privacypolicy

SUB-PROCESSOR REQUIREMENTS

Every sub-processor must meet these criteria before we engage them:

1. Location & Jurisdiction

✅ EU/EEA-based company OR

✅ Adequacy decision country (Switzerland, UK) with EU-only data processing

❌ NO US-based companies

❌ NO third-country data transfers

2. Security Certification

At least one of:

3. Legal Compliance

✅ GDPR-compliant Data Processing Agreement (DPA) signed

✅ Commitment to EU-only data processing

✅ No access by third-country parent companies (if applicable)

✅ Audit rights granted to eyre.ai

4. Technical Measures

✅ Encryption in transit (TLS 1.3 minimum)

✅ Encryption at rest

✅ Access controls and authentication

✅ Incident response procedures

✅ Regular security testing

5. Transparency

✅ Public privacy policy

✅ Sub-sub-processor disclosure (if any)

✅ Annual compliance attestations

✅ Security documentation available

NOTIFICATION OF CHANGES

How We Notify You

When we add or change sub-processors, we will:

30 days before engagement:

Notification includes:

Your Right to Object

You have 14 days from notification to object to a new sub-processor on reasonable data protection grounds.

How to object:

  1. Email objection to: privacy@eyre.ai
  2. Include: Your organization name, reason for objection, specific concerns
  3. We will review within 5 business days

If you object:

Option A: We don’t engage that sub-processor (if commercially reasonable alternative exists)

Option B: We discuss alternative solutions with you

Option C: You may terminate your agreement without penalty (if we cannot accommodate objection)

Example valid objection reasons:

SUB-SUB-PROCESSORS

Some sub-processors may use their own sub-processors (sub-sub-processors).

Current sub-sub-processors:

Hetzner:

BunnyCDN:

Brevo:

We require all sub-processors to:

SUB-PROCESSOR MONITORING

How We Oversee Sub-Processors

Quarterly:

Annually:

Continuous:

If Sub-Processor Fails

If a sub-processor:

We will:

  1. Notify affected customers immediately
  2. Work with sub-processor to remediate (if possible)
  3. Migrate to alternative sub-processor (if necessary)
  4. Document and report incident per GDPR requirements

WHAT WE DON’T USE

To protect your data sovereignty, we explicitly do NOT use:

Amazon Web Services (AWS) – US company, CLOUD Act exposure
Google Cloud Platform (GCP) – US company, third-country transfers
Microsoft Azure – US company, jurisdiction concerns
Cloudflare – US company (though we may use EU-only features in future)
Zoom – US-based video infrastructure
Slack – US-based communications
Mailchimp – US-based email
Intercom – US-based support
Any US-based analytics (Google Analytics, Mixpanel, etc.)

Why not?

Our commitment: European infrastructure for European values.

FREQUENTLY ASKED QUESTIONS

Why do you use sub-processors?

No company can build everything in-house. Sub-processors provide specialized infrastructure (data centers, networks, email delivery) that would be inefficient to build ourselves. We carefully select EU-based partners who meet our security and privacy standards.

Can I see the Data Processing Agreements with sub-processors?

Yes. Enterprise customers can request copies of our sub-processor DPAs for their compliance review. Email: legal@eyre.ai

What if a sub-processor is acquired by a US company?

We have contractual protections requiring 90 days notice of ownership changes. If a sub-processor is acquired by a non-EU company:

  1. We assess impact on data sovereignty
  2. If unacceptable, we migrate to alternative (90-day transition)
  3. We notify all customers immediately
  4. No customer data transferred to new owner without consent

Do sub-processors access my meeting content?

No. Your meeting content is end-to-end encrypted. Sub-processors provide infrastructure but cannot decrypt your meetings. They may process:

They do NOT access meeting content (conversations, recordings, shared files).

How do I know sub-processors are really EU-only?

We verify through:

You can also verify independently:

Can I require eyre.ai to use specific sub-processors?

Enterprise customers can discuss custom infrastructure requirements. However:

Contact: enterprise@eyre.ai

What about analytics or tracking?

We do NOT use:

We MAY use (future):

Current: Minimal analytics, processed in-house on our own servers.

Will you ever use US-based sub-processors?

Current policy: No.

We believe European data should stay in Europe. However:

Any such change would require 60 days notice and full objection rights.

CONTACT

General Questions

Email: privacy@eyre.ai
Response time: 48 hours

Sub-processor Objections

Email: privacy@eyre.ai
Subject: Sub-processor Objection – [Sub-processor Name]
Response time: 5 business days

Enterprise/Custom Requirements

Email: enterprise@eyre.ai

Data Protection Officer

Email: dpo@eyre.ai
For: GDPR compliance, data processing questions, audit requests

Legal/Compliance

Email: legal@eyre.ai
For: DPA requests, contractual questions, compliance documentation

 

SUMMARY TABLE

Sub-processor Service Location Data Processed Certification
Hetzner Cloud hosting 🇩🇪 Germany Platform data, recordings ISO 27001
BunnyCDN CDN 🇸🇮 Slovenia (EU PoPs) Media streams GDPR-compliant
Brevo Email 🇫🇷 France Email delivery ISO 27001

Total sub-processors: 3
EU/EEA-based: 100%
Third-country transfers: 0

This page is updated whenever sub-processors change. Bookmark for reference.

Last reviewed: 31/01/2026
Next scheduled review: July 2026 + 90 days

Transparency commitment: We believe you have the right to know exactly who processes your data and where.\

Questions? privacy@eyre.ai