Last updated: 27 Oct 2026
Cookie policy
Essential technical storage, optional visit measurement and Google advertising serve separate purposes. You can change your measurement and advertising preferences at the bottom of the site.
Participation control
The HttpOnly, SameSite=Strict cookie named “trends-participation-v1” holds a random participation key, not a party preference. It is sent only to the participation API. Unused keys expire after one day. After participation, the cookie is retained for 400 days and refreshed when you visit the participation page. Cookie expiry does not delete the response on the server. Thirty days is only the interval for changing a preference. The “trends-participation-until-v1” browser entry stores only the next eligible date; it no longer blocks participation after that date. If cookies are completely blocked, responses cannot be submitted because repeat-participation control cannot be established.
Advertising
Google AdSense loads only when advertising is enabled and you have allowed “Google advertising”. Google advertising code does not load before permission is given. Ad requests remain paused until the Google consent system returns a result. In applicable regions, you can also choose through Google's certified consent message; ads are not shown without the required permissions. We request non-personalised ads. These may still use cookies or technical data for measurement and invalid-traffic detection. Google and its advertising partners may process IP addresses, device information, cookies and similar technologies. Your selected party is not sent to the advertising provider.
To withdraw permission, open “Change cookie preferences” and choose “Reject all”, or save your choices with “Google advertising” disabled. If advertising code has already loaded, the page reloads. This does not automatically delete existing third-party cookies; you can remove them in your browser settings. A separate option to change Google's consent choices is available after its message loads. For providers' cookie names, purposes and durations, see Google's cookie information and advertising technology information for details.
Advertising content
We do not accept political advertising. The “Politics” sensitive category is blocked in AdSense. Google's automated classification cannot guarantee that every political ad is caught. If you encounter an unsuitable ad, please send a screenshot and the page link, without clicking the ad, through our contact channel to let us know.
Sign-in is closed
The former preview sign-in cookie is no longer used and is deleted when the old session API is requested. Sign-in, email verification and phone verification are unavailable. The participation cookie is not account or identity verification; clearing browser data can bypass this control.
Further information
Privacy policy and KVKK privacy notice. For cookies, see Official KVKK guidance.
Visit measurement and stored preferences
If you allow “Visit measurement”, aggregate visit and page-view counters are stored by day and page. The measurement database does not record IP addresses, user identifiers, party preferences, provinces, URL queries or referrers. No third-party analytics service is used. “Manage preferences” lets you allow measurement without ads, or ads without measurement. “Allow all cookies” enables both purposes; “Reject all” disables both. Rejecting does not prevent you from using the site.
Consent choices and their timestamp are stored in localStorage under “trends-privacy-preferences-v2” for up to 180 days, after which you are asked again. This entry contains no party preference. The legacy “trends-measurement-consent” entry is retained only for measurement compatibility; an old measurement permission never authorises advertising. The last activity time is stored in sessionStorage under “trends-measurement-last-active” for the tab session and is removed when measurement is rejected. A 30-minute gap within the same tab counts as a new visit; this does not measure unique people. Daily totals are retained for 400 days; expired records are cleaned on the next measurement request. Infrastructure logs are subject to separate provider settings.