TPP Privacy Badges

Yandex

Badge: ⚠️ Caution

This work is licensed under CC BY-SA 4.0

Yandex

FeldWert
Gruppe / Parent ServiceNative Advertising
Badge⚠️ Caution
Service-TypParent service
Sub-service / Relationship Note[nicht dokumentiert]
Infrastructure Only?No
Kontakt (DPO / Privacy)privacy@yandex-team.com
Bewertungsdatum06/08/2026
Versionv2 (06/08/2026) | v1: 22/06/2026

Badge & Risikobewertung
  • Badge: ⚠️ Caution
  • Red Flags:
    • RF1 — Own advertising / cross-service profiling
    • RF2 — High-risk third-country exposure without meaningful mitigation
  • Risk Indicators:
    • Own-purpose data use (advertising); high-risk international transfers (Russia); government access risk
Begründung & Quellen

Key Facts: Yandex is a Russian technology company. Any data transferred to or accessed from Russia is subject to Russian surveillance legislation (Federal Law No. 374-FZ and related laws), which provide Russian security services broad access to telecommunications and internet data without meaningful judicial oversight — a clear RF2. Yandex also operates its own advertising ecosystem with cross-service profiling (RF1). European operations reduced following 2022 geopolitical changes but residual Russia exposure remains.

Framework Note (v2.2): FRAMEWORK NOTE (v2.2): RF2 (high-risk third-country exposure) is recorded here as a significant risk factor and lowers the domain E score. Under the revised framework, RF2 alone does not trigger Caution — the Caution badge for this service is driven by RF1 / RF3 / RF4 (as noted above). The US transfer risk (where applicable) is covered by DPF participation and/or SCCs, which GDPR treats as a compliant transfer mechanism.

Quellen:

  • Yandex Privacy Policy (yandex.com/legal/privacy)
  • Russian Federal Law No. 374-FZ
  • Yandex corporate restructuring announcements (2022–2023).
Verarbeitungszwecke (Consenter)
  • Support marketing analytics
  • Receive personalised marketing offers
  • Customise online ads (non-TCF)
Benachrichtigungs- & Widerspruchsstatus
  • TPP Notified?: Not yet notified
  • Decision Contested?: [nicht dokumentiert]

Prüfbedarf

Kein Prüfbedarf identifiziert.

Shape Consenter Together

Consenter is built on an open and participatory process that grows through community collaboration. Whether you share feedback, improve the documentation, or contribute to the Risk Configuration Guides or Technical Integration Guides, your expertise helps make Consenter more privacy-friendly, interoperable, and useful for everyone—including your own users and services: Get finally your benefits and control the risks when sharing personal data.

Last updated on

On this page