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

Analytics & Tracking

AI LOG : Datenschutz, & EU Alternatives

AI LOG is located outside the EU. An adequacy decision must be verified; otherwise SCCs and a TIA are required.

🌍SonstigeDrittlandtransfer prüfen

Last checked:

Is AI LOG GDPR compliant?

AI LOG is located outside the EU. An adequacy decision must be verified; otherwise SCCs and a TIA are required.

Vendor Profile

Who is the contractual partner?

Jurisdiction
Sonstige
Hosting
Japan
Owner
Unbekannt (Japan)Other

Contract & Subprocessor Chain

  1. 1.Unbekannt (JP)

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 AI LOG process?

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

  • User behaviour on your website (clicks, scrolls, navigation)
  • IP address and device fingerprint
  • Referrer URL and UTM parameters
  • Conversions and funnel data

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:

  • All visitors to your website
  • Including non-logged-in and anonymous users

Concrete Impact

What does this mean in practice?

Behavioural data of all website visitors (including government contacts, journalists, whistleblowers) is stored in the US.

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

Japan-Analytics: TIA und Vertragsgrundlage prüfen

AI LOG ist ein japanischer Analytics-Dienst. Japan hat einen EU-Angemessenheitsbeschluss (2023), Vertragsgrundlage und DPA dennoch prüfen. EU-Alternative: Matomo oder Plausible.

Migration Plan

How to migrate away from AI LOG

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

  1. 1

    Replace the tag snippet on the website

  2. 2

    Redefine goals and conversions in the EU alternative

  3. 3

    If needed: export historical data via API

  4. 4

    Parallel tracking for 30 days for data validation

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

AI LOG & Privacy: FAQ

Is AI LOG GDPR-compliant?

AI LOG is an EU/EEA-based provider and generally well-suited for GDPR-compliant setups. The usual obligations still apply: DPA, check the subprocessor list, document technical and organisational measures.

Who is the contractual partner for AI LOG?

The contract chain includes: Unbekannt (JP). 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 AI LOG?

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 AI LOG (Web Analytics (Japan)). meetergo covers the core workflow and can fully replace AI LOG in many cases.

Where is AI LOG data stored?

According to provider information: Japan. 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.

How much effort is involved in switching away from AI LOG?

Migration effort depends on your specific setup: typically between a few business days (booking, forms) and several weeks (CRM, hosting). The roadmap below shows the typical order.

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.

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.