Sovereignty Scan/Vendors/MeetFox

Risk indicator, not a GDPR compliance verdict. Point-in-time assessment based on public web stack signals.Methodology & LimitationsCorrect listing / submit response

Appointment Scheduling

MeetFox : Datenschutz, & EU Alternatives

The jurisdiction of MeetFox could not be clearly determined. Please check the DPA and the provider's legal notice.

🌍UnklarAnbieterprüfung erforderlichErsetzbar

Last checked: 29 April 2026

Is MeetFox GDPR compliant?

The jurisdiction of MeetFox could not be clearly determined. Please check the DPA and the provider's legal notice.

Vendor Profile

Who is the contractual partner?

Jurisdiction

Unklar

Hosting

AWS (Region je nach Konto)

Owner

MeetFox / TrafftOther

Contract & Subprocessor Chain

1.MeetFox GmbH (ursprünglich Wien)
2.Trafft (Übernahme, aktuelle Eigentümer-Struktur prüfen)

Even if the main provider is based in the EU, a US subprocessor in this chain can trigger a third-country transfer. This is the core pitfall of .

Data Categories

What data does MeetFox process?

In typical use, the following data categories arise. Which ones are relevant for you depends on your setup and scope of use.

Guest name & email address
Appointment and timezone data
Phone number (optional)
Pre-screening answers (lead qualification)
Calendar sync tokens (Google / Microsoft)

Data Subjects

Who is affected by the processing?

Under Art. 30 GDPR, you must document the categories of data subjects per processing activity. In typical use, these include:

Applicants booking an interview slot
Prospects scheduling a demo call
Clients / patients booking a consultation
Existing customers scheduling a follow-up

Concrete Impact

What does this mean in practice?

A US authority could theoretically request a list of all persons who have scheduled an appointment with your company, including applicants, clients or patients. The CLOUD Act allows this without involving German courts.

Note: This is a risk description, not a specific incident. Whether access occurred in your case depends on many factors. What can be documented: the risk must be named in your TIA and mitigated with additional measures.

meetergo Recommendation

MeetFox durch meetergo ersetzen

MeetFox wurde übernommen, die aktuelle Eigentümer- und Hosting-Kette ist nicht mehr durchgehend EU-deklariert. meetergo bietet eine klare DSGVO-Strecke aus Frankfurt.

Time-to-Value: Migration in 1–2 Werktagen

MeetFox-Migration prüfen Check your own domain

GDPR-compliant providers

EU alternatives to MeetFox

Providers based in the EU or EEA. No third-country transfer, simpler DPA situation, TIA generally not required. meetergo fully covers the core workflow.

meetergo

🇩🇪Recommended

Gleicher Funktionsumfang, Server in Frankfurt, DSGVO-konform, inkl. 1-Klick-Import aus Calendly.

Switch in ~9 days

54 Grad Software - Smarte Gemeinschaftskalender

🇩🇪

Open-source community event calendar for municipalities & associations.

Agorify

🇸🇪

Plattform für Ticketing und Event-Management.

amaiko GmbH

🇩🇪

AI assistant that reduces decision fatigue and preserves organisational knowledge.

Appointmind

🇩🇪

Online appointment scheduling software for businesses to manage bookings.

BlueMind

🇫🇷

Europe's #1 open-source enterprise collaborative email and calendar solution.

Migration Plan

How to migrate away from MeetFox

The following steps are the typical path for this tool category. Order and time required depend on your specific setup.

1
Create appointment types and availability in the EU alternative
2
Configure calendar sync (Google / Outlook)
3
Recreate routing rules (round robin, pool)
4
Replace booking links (website, signature, CRM)
5
Import existing appointments via CSV export

We help with migration planning at no cost: 30 minutes with a data protection specialist to prioritise and define a migration sprint. Book appointment

Frequently Asked Questions

MeetFox & Privacy: FAQ

Is MeetFox GDPR-compliant?

MeetFox can be used in a GDPR-compliant way if a valid DPA is in place, Standard Contractual Clauses (SCCs) are signed, and a Transfer Impact Assessment (TIA) has been conducted. However, the provider is headquartered in the US (MeetFox / Trafft), so the CLOUD Act and FISA 702 continue to apply. This is true even when data is stored in an EU data centre. For sensitive data or strict oversight (public authorities, healthcare, large corporates), switching to an EU provider is often preferred.

Who is the contractual partner for MeetFox?

The contract chain includes: MeetFox GmbH (ursprünglich Wien) · Trafft (Übernahme, aktuelle Eigentümer-Struktur prüfen). The legal parent entity is decisive for data protection. Even if an EU subsidiary signs the DPA, a US subprocessor in the chain can trigger third-country transfer obligations.

What EU alternatives are there to MeetFox?

There are several GDPR-compliant EU alternatives. They are listed under "EU Alternatives" on this page. The selection is tailored to the feature set of MeetFox (Terminbuchung). meetergo covers the core workflow and can fully replace MeetFox in many cases.

Where is MeetFox data stored?

According to provider information: AWS (Region je nach Konto). Note: even an EU data centre does not protect against the CLOUD Act when the parent company is in the US. This is the core finding of the Schrems II decision.

What does the CLOUD Act mean for MeetFox users?

The US CLOUD Act (Clarifying Lawful Overseas Use of Data Act, 2018) allows US authorities to request data from US companies regardless of the physical storage location. If MeetFox / Trafft is subject to the CLOUD Act, US law enforcement could theoretically access MeetFox data stored in Frankfurt without involving EU authorities. The EDPB Recommendations 01/2020 therefore require additional safeguards or a switch to an EU provider.

Do I need a TIA for MeetFox?

Yes, in most cases. Since Schrems II (July 2020), a Transfer Impact Assessment is mandatory for US providers when personal data is transferred. The TIA documents US law, practical risks (NSA access, subpoenas) and additional measures (encryption, pseudonymisation). Only a valid TIA makes the use of MeetFox legally defensible.

How much effort is involved in switching away from MeetFox?

Time-to-value according to our migration database: Migration in 1–2 Werktagen.

Related Vendors

More tools in Appointment Scheduling

Next Step

Which tools are running on your website?

60 seconds, no login: the Sovereignty Scan shows all detected vendors with jurisdiction, risk, and matching EU alternatives.

To the Scan Methodology

Note

Hinweis

Risiko-Indikator, keine Rechtsberatung.

Der Sovereignty Scan wertet öffentlich erreichbare Signale aus (HTML der Startseite und Rechtsseiten, DNS-, MX-, SPF- und ASN-Daten) und vergleicht sie mit unserer Datenbank von ca. 3.000 Anbietern. Die Zuordnung von Tool zu Eigentümer und Jurisdiktion basiert auf öffentlichen Quellen (Impressum, Datenschutzerklärung, Wappalyzer, RIPE/ARIN-Registrierungen) und ist als Erstindikation zum Stichtag der Auswertung gedacht, nicht als rechtsverbindliche Bewertung.

Die Note A–E ist ein Risiko-Indikator, kein DSGVO-Konformitätsurteil. Für eine konkrete DSGVO-Bewertung, insbesondere für Auftragsverarbeitungsverträge (AVV/DPA), Standardvertragsklauseln (SCC) und Transfer Impact Assessments (TIA), wenden Sie sich bitte an Ihren Datenschutzbeauftragten oder eine externe Rechtsberatung. meetergo trifft keine Aussage darüber, ob ein konkreter Anbieter in einem konkreten Anwendungsfall DSGVO-konform eingesetzt werden kann.

Korrektur & Stellungnahme: Wenn Sie Domain-Inhaber, Datenschutzbeauftragter oder Pressestelle der bewerteten Domain sind und die hier gezeigten Signale nicht Ihrer aktuellen Tool-Konfiguration entsprechen, nehmen wir Korrekturen auf und passen die Anzeige nach Prüfung umgehend an.

Methodik & Grenzen Listing korrigieren / Stellungnahme einreichen

MeetFox GDPR: Datenschutz, CLOUD Act Risk & EU Alternatives