Explicit Consent Text
Last updated: November 11, 2026
This Explicit Consent Text is provided by DURBAY OTOMOTİV MİMARLIK İNŞAAT TİCARET LİMİTED ŞİRKETİ as data controller under Law No. 6698 on the Protection of Personal Data (“KVKK”). It is separate from our KVKK Privacy Notice, which explains what we process and why. Here we list only the processing for which we ask for your explicit consent (KVKK Article 5(1)). Consent is voluntary: you can use Rotascore without giving it, and you can withdraw it at any time.
1. Website analytics
What: Google Analytics and Yandex Metrica cookies (_ga, _ga_*, _ym_uid) and the page, referrer, browser/device and approximate location (country or region) data described in our Cookie Policy. Why: to measure and improve how rotascore.com is used. How you consent: choose “Accept all”, or turn on the analytics option, under “” on the website. The first-party full-mode browser ID stays in local storage until you delete it; anonymous-mode IDs stay in memory only. Clarity's _clck cookie keeps a user ID/preferences for 1 year; _clsk joins page views into a session for 1 day. These belong to Analytics and send data to Microsoft; other Microsoft cookies follow the provider's current rules. Raw-event retention and cookie lifetime are different. Microsoft Clarity analyses taps/clicks, scrolling and screen interactions in the app and on the website through session replay and heatmaps. Text inputs other than search, chat messages, account/email and purchase screens, support forms and all in-app WebViews are masked or excluded; search text may be visible, so do not enter personal information. Microsoft processes recordings in the United States and also acts as a controller for Clarity under its own policy. Recordings may be linked to a pseudonymous installation/browser ID.
2. Website advertising cookies and pixels
What: the Meta Pixel (_fbp), the TikTok Pixel (_ttp) and Google advertising storage (_gcl_au), which process your IP address, browser/device information, the pages you view, the page that referred you and clicks on our App Store and Google Play buttons. Meta and TikTok may also use this data for their own purposes as independent controllers. Why: to measure our advertising campaigns and show more relevant ads. How you consent: choose “Accept all”, or turn on the advertising option, under “” on the website.
3. App usage analytics
Usage and diagnostics data. Our first-party analytics measures product use and quality: event name/ID and time, session and consent mode; installation or browser ID; platform, device class (phone/tablet/desktop), app version/build, operating system, device model/tier, language, theme, Pro status and network type; current/previous screen, match and other content IDs, views, taps, search text (up to 64 characters), favourites, notification/permission, purchase/ad interactions, errors, performance measurements and foreground activity signals. In full mode, a signed-in account ID is sent to our server, which stores only its keyed HMAC-SHA256 hash; these records are pseudonymous, not anonymous. We do not store names, email addresses or IP addresses in these analytics records; country is derived from IP (Cloudflare country information). Google Firebase Analytics/Crashlytics and Google Analytics on the website also process usage, crash and performance data under their own rules. Manage choices under “” on the website and the app's privacy settings. Microsoft Clarity analyses taps/clicks, scrolling and screen interactions in the app and on the website through session replay and heatmaps. Text inputs other than search, chat messages, account/email and purchase screens, support forms and all in-app WebViews are masked or excluded; search text may be visible, so do not enter personal information. Microsoft processes recordings in the United States and also acts as a controller for Clarity under its own policy. Recordings may be linked to a pseudonymous installation/browser ID. Analytics and diagnostics: first-party raw events are kept for 6 months, presence counts for 7 days; statistics stripped of identifiers are kept indefinitely. Records containing account/device links are also subject to erasure. Under Microsoft's Clarity retention policy, session playback is kept for 30 days; labelled/favourited sessions and heatmap/click data for 9 months. Other providers' diagnostics follow their own retention rules. We also use Yandex Metrica on the website and AppMetrica in the app for analytics: IP-derived country, traffic sources, device information, pseudonymous identifiers, sessions, page/screen views and product interactions. They follow your existing analytics choices and regional consent rules. We do not send emails, Rotascore account IDs or raw search text; precise location, AppMetrica advertising identifiers and crash collection are disabled. Yandex stores data in the European Union and Russia (Yandex privacy). Click, scroll and form-interaction statistics and masked session recordings of public pages start only after you explicitly allow analytics; entered text and private content, including account, sign-in, search and chat content, are excluded or masked. App-install attribution. When app analytics is enabled, Kochava processes app-install and session data, device and app information, approximate location derived from IP address, and campaign/referrer information to help us measure which ads lead to installs. We do not send your Rotascore account ID to Kochava. Kochava may share this measurement data (IP address, device and app information, install and in-app events) with advertising networks, including Meta, to measure the results of our ad campaigns. On iOS, even if you do not allow cross-app tracking, this data may be processed for aggregated, non-targeting measurement without using your advertising identifier (IDFA). The iOS app also includes Meta's App Events SDK (Facebook SDK): when app analytics is enabled, it sends install and app-open, registration-completed, onboarding-completed and subscription-purchase events directly to Meta, together with device and app information, IP address and an anonymous app ID generated by the SDK, to measure the results of our ad campaigns. Your advertising identifier (IDFA) is used only if you allow cross-app tracking; we do not send your Rotascore account ID, name or email address to Meta. You can turn app analytics off in Settings → About → Privacy. On iOS, permission for cross-app tracking is managed separately by Apple's ATT prompt.
4. Occasional transfers abroad
We transfer personal data abroad on the bases in KVKK Article 9 described in the KVKK Privacy Notice — principally an adequacy decision or an appropriate safeguard such as the standard contract. The consents above do not cover a transfer abroad. If an occasional transfer ever depends on your explicit consent under Article 9(6)(a), we will ask you separately and in advance, naming the recipient and the country and informing you of the possible risks. Our first-party analytics is hosted on Netcup servers in Germany. Microsoft (Clarity, United States) and Google (Firebase, United States and other countries) are also data recipients. Ongoing international transfers require an appropriate legal safeguard; an analytics choice alone is not a KVKK transfer safeguard.
Regions and default settings
Regions and defaults. First-party analytics and Clarity are on by default outside the EEA/United Kingdom/Switzerland, including Türkiye. In the EEA, United Kingdom and Switzerland, only first-party anonymous counts run before consent: the ID resets on each app launch/browser session and stays in memory; there is no persistent ID, on-device queue, account link or Clarity recording. Full mode and Clarity require consent (the app consent form or “” on the website). Google/Yandex analytics storage and advertising wait for permission in these regions or when the website region is unknown; Google Consent Mode remains denied. GPC/DNT and explicit refusal are respected everywhere; switching off usage sharing also stops anonymous counts.
What we do not ask consent for
We do not send marketing messages (commercial electronic messages), we do not sell personal data and we do not process special categories of personal data. Notifications you turn on in the app, such as goal alerts, are part of the service you ask for and are not used for marketing.
Withdrawing consent
Withdrawing is as easy as giving consent: use “” on the website or the privacy settings in the app, or email help@rotascore.com. Withdrawal applies from that moment and does not affect processing carried out before it. Your rights under KVKK Article 11 are described in the KVKK Privacy Notice. In the app and on the website, turn off Settings → Privacy → Share usage data to stop first-party analytics and Clarity. This also queues deletion of first-party records matching the relevant account hash or installation/browser ID. Account deletion removes records that can be linked to that account; other unlinked devices may require opting out on that device or a deletion request. Statistics stripped of identifiers remain; Microsoft's retention and rights-request rules apply to its data.