OYO.DEV // COOKIES

Cookie Policy

Updated 11 November 2026

This notice distinguishes the production website observed on 11 November 2026 from the revised implementation in this update. The production home page was inspected in a fresh Chromium browser, including its resource requests, response cookie headers, browser cookie storage and the additional-language control. The production /privacy and /cookies pages could not be retrieved in that check. Account/dashboard settings and other visitor conditions remain unverified.

Preference expiry and your controls

localStorage is browser storage, not an HTTP cookie, and these values are not automatically attached to requests. In the revised implementation, each saved choice includes an expiry timestamp. Page visits, automatic language detection and language URL parameters do not create or renew a saved choice. Expired, malformed and old values without a verifiable expiry are discarded on the next read; the page falls back to browser language or the default dark theme. Stored expired bytes may remain until the next read or until you clear site data.

Use the EN/TR and theme controls to save or renew a choice. Delete preferences through your browser’s site-data controls. With storage blocked, the page still works and choices last only for the current page. The 180-day behaviour is enforced in this update, but has not been verified as deployed on the production domain; the last production observation still showed the old no-expiry implementation.

Observed Cloudflare security cookie

No other cookie remained in that browser context at the end of the production check. Cookie-setting response headers were observed from the portfolio domain and a Google translation endpoint; absence from the final cookie jar does not prove no third-party cookie was attempted, blocked or transient. Cloudflare and other infrastructure providers may process IP addresses, request headers and other technical metadata independently of cookies or portfolio analytics.

Google resources and tracking verification

Google is an external service used by the currently deployed production implementation observed on 11 November 2026 for hosted fonts and translation. The observed website requested fonts from fonts.googleapis.com and fonts.gstatic.com. Opening its additional-language control requested Google Translate scripts and supporting resources from translate.google.com, translate.googleapis.com, translate-pa.googleapis.com, www.google.com and www.gstatic.com. These connections disclose technical request information to those providers. Google services have therefore not been verified as removed from production.

The revised project uses self-hosted fonts and EN/TR switching without that Google translation widget. This is a change in this update, not proof of production removal. No separate advertising pixel, analytics tag or session-replay script was detected in the observed production home-page flow or reviewed project files. That bounded observation does not certify every deployed page, dynamic interaction, Google/provider-side activity, historical site data or dashboard-injected service.

Web3Forms and the Privacy Notice

Web3Forms is contacted when a visitor submits the contact form. A browser check of the production form, with synthetic input and transmission intercepted before sending, found the default fetch credential mode (same-origin), not an explicit omit setting. That default does not normally send credentials on this cross-origin request, but is not the same as an enforced omit mode. In the revised implementation, the same intercepted browser check verifies explicit credentials: omit. No real inquiry was transmitted and live delivery was not verified.

Omitting browser credentials does not anonymise the submitted email, message, optional fields or technical request information. Clarity is listed in Web3Forms’ DPA annex for Customer Personal Data, while its Privacy Policy describes logged-in dashboard use; whether it processes this portfolio’s submissions remains unestablished. This does not show Clarity is installed on this portfolio. Processing, published subprocessors, spam screening, the separate mailbox provider and unresolved transfer safeguards, including production Google requests, are explained in the Privacy Notice. The canonical production notice address is https://omeryigitozbey.com/privacy; its availability was not confirmed during this production check.

Consent position and unresolved verification

No decorative consent banner has been added. For visitor-selected interface preferences and genuinely strictly necessary security technologies alone, an optional-tracking consent mechanism is not required merely for appearance. This conditional position is not a blanket exemption for the older production Google widget or any undiscovered non-essential technology. The revised project has no optional tracking identified; the complete production position remains unconfirmed.