Privacy Notice
Updated 11 November 2026 · Legal grounds and transfer safeguards remain unconfirmed
1. Data controller and scope
The data controller is Ömer Yiğit Özbey, who operates the independent personal portfolio at omeryigitozbey.com. It does not provide shopping, payments or member accounts. The ordinary contact email for privacy questions is omer@omeryigitozbey.com. This is not a declaration that every email to that address is a valid formal KVKK application; the statutory methods and requirements are explained in section 10.
The written-application address and any formal electronic channel have not yet been confirmed. Section 10 explains the recognised methods; the ordinary contact email does not establish all of them.
2. Data categories and technical metadata
The contact form sends your email address and message, with optional name and subject. Do not include sensitive personal data. Website and submission requests also expose technical information, such as IP address, request time and browser/request headers, to Cloudflare and other infrastructure providers involved in the request. The exact fields recorded depend on their configurations. Language and theme preferences are stored on your device.
Infrastructure providers may process request information for delivery, network operation, abuse prevention and security even when the portfolio does not operate analytics or advertising profiles. Web3Forms may also process submission-related technical metadata; the absence of a browser analytics script does not mean no personal data is processed by providers.
The exact technical fields retained by providers, their settings and the receiving mailbox provider have not yet been confirmed. The owner does not necessarily receive or have access to every technical field processed by infrastructure providers.
3. Processing purposes
Contact details and correspondence are used to respond to inquiries, evaluate requested professional collaboration and manage related communication. Technical request information supports website delivery and security; submission screening supports spam and abuse prevention. Display preferences remember the chosen language and colour theme.
The reviewed project files use self-hosted fonts and EN/TR language switching and contain no Google Fonts or Google Translate resource loading, marketing subscriptions, advertising profiles or portfolio analytics identifiers. This finding is limited to the reviewed implementation: it does not certify the complete deployed website, Cloudflare dashboard features, externally injected scripts, optional provider integrations or providers’ own analytics. Google services or tracking in those settings have not been ruled out.
The currently deployed production implementation observed on 11 November 2026 uses Google as an external service for hosted fonts and translation. Opening the additional-language control requests Google Translate. Browser requests may expose IP addresses, browser/request headers and other technical request information to Google. Removing these connections is implemented in the revised project; deployment and production verification remain outstanding. The Cookie Policy distinguishes the observed production site from this update.
4. Legal grounds under Article 5
The following grounds require assessment for the specified activities; they are not automatic conclusions:
- Ordinary professional inquiries and correspondence: Article 5(2)(f), only where necessary for legitimate interests without infringing your fundamental rights and freedoms, supported by a documented necessity and balancing assessment.
- Requested pre-contractual steps: Article 5(2)(c), only where processing the parties’ data is necessary and directly related to establishing or performing a contract; not every contact message qualifies.
- Website delivery, security and spam/abuse prevention: Article 5(2)(f), subject to activity-specific necessity, proportionality and balancing; security processing is not automatically covered.
- An actual legal obligation: Article 5(2)(ç), only where the specific obligation makes the processing necessary.
- Establishing, exercising or protecting a legal right: Article 5(2)(e), only where processing is necessary for that purpose.
Visitor-selected display preferences also require an activity-specific processing-ground assessment; their functional nature alone does not establish a legal ground. Submitting the form is not blanket explicit consent, and this notice is not a legal basis for processing.
These are activity-specific candidate grounds, not established legal determinations. The applicable grounds and any required balancing assessments remain unresolved; listing candidates does not fulfil the obligation to identify the actual legal basis.
5. Collection methods
Data is collected electronically when your browser requests website resources, when you deliberately submit the contact form, or when you email the owner directly. The reviewed form sends data directly to https://api.web3forms.com/submit with browser credentials explicitly omitted and no referrer, for email delivery. Live delivery and the configured mailbox destination have not been verified. The observed older production form uses the default same-origin credential mode, not explicit omit. The reviewed portfolio code does not store contact messages in a portfolio database or browser storage; this does not exclude Web3Forms submission storage, mailbox storage or infrastructure logs.
The reviewed form uses a local honeypot field for spam prevention and does not load a third-party CAPTCHA widget. This does not disable or rule out Web3Forms’ server-side spam screening.
6. Recipients, subprocessors and distinct activities
The owner receives correspondence. Cloudflare provides portfolio delivery and network/security infrastructure; its actual enabled services need confirmation. Google receives browser requests for hosted fonts and translation in the currently deployed production implementation observed on 11 November 2026; removal in the revised project is not verified as deployed. Web3Forms, operated by Web3Creative, describes itself as a processor of customer form submissions for receipt, processing and email delivery. The receiving mailbox provider is a separate service, not automatically the same as Web3Forms’ email-delivery provider.
The Web3Forms DPA and Privacy Policy, reviewed on 11 November 2026, describe authorised relationships with AWS, Cloudflare and Hetzner for hosting, delivery and storage, and CleanTalk and Automattic/Akismet for spam screening using submitter IP/email information. These published lists are not proof that every provider handles each portfolio submission.
Microsoft Clarity appears in the DPA’s authorised-subprocessor annex for Customer Personal Data, while the Privacy Policy describes its use in Web3Forms’ logged-in dashboard. Whether Clarity receives or processes this portfolio’s form submissions has not been established; the dashboard description alone does not resolve the annex’s scope. Clarity has not been identified as installed on this portfolio. SparrowDesk is described as Web3Forms’ support service, not a confirmed recipient of ordinary portfolio inquiries.
Web3Forms also describes self-hosted Web3Analytics (Umami). That is a provider activity, not verified portfolio analytics. Customer-enabled integrations, including Google Sheets or messaging services, are separate destinations only if enabled; their use for this account is unverified. GitHub is an external destination if you follow a link. Disclosure to authorities requires an applicable legal duty.
The actual Web3Forms account routing, optional integrations, processing regions, receiving mailbox provider and contractual arrangements remain unconfirmed.
7. International transfers — safeguards remain unverified
Cloudflare, Google for currently deployed fonts/translation, Web3Forms/Web3Creative, their relevant subprocessors and the receiving email provider may process personal data outside Türkiye. Google’s actual processing routes and locations remain unverified; its production data flow remains part of the transfer assessment until removal is deployed and verified. Web3Creative’s DPA states that it operates from India; its provider list describes global infrastructure and other overseas locations. The actual routes and regions for this account remain unverified.
No verified KVKK Article 9 transfer mechanism has been established here. The current Article 9 framework requires assessment of applicable processing conditions and transfer arrangements, including a relevant Board adequacy decision or appropriate safeguards where applicable. Safeguards may include the Board’s standard contracts, Board-approved binding corporate rules for qualifying groups, or an undertaking with Board permission; none has been verified for this portfolio. Exceptional transfers under Article 9(6) must be incidental (arızi aktarımlar) and meet their specific statutory conditions; they do not justify routine transfers. A GDPR DPA or EU standard contractual clauses alone do not establish compliance with KVKK Article 9. If a Turkish standard contract is used, the applicable official contract must be signed by the authorised parties and notified to the Authority within five business days of signing; no signed contract or notification has been verified here.
International-transfer safeguards remain unresolved. This notice does not make those transfers lawful or establish compliance; the affected data flows require a lawful arrangement before they can be treated as ready for operation.
8. Retention policy — unresolved periods
Data should be retained only for the applicable legal period or as long as its purpose requires. When processing grounds cease, Article 7 and the relevant deletion rules apply. Separate retention details remain as follows:
- Contact correspondence: the owner’s inquiry/follow-up and justified legal-retention periods or criteria have not yet been established.
- Web3Forms submissions: its Privacy Policy describes a maximum of three years from submission, with shorter periods potentially applying through a plan or earlier deletion. DPA section 8 describes a three-year physical time-to-live and plan-dependent dashboard visibility. How these provisions apply to this account, including earlier physical deletion, remains unconfirmed. Dashboard visibility is not proof of deletion.
- Termination and backups: the DPA describes deletion within 90 days of termination, subject to routine backup cycles and legally required storage. Immediate removal of all backup copies has not been established.
- Email storage: the receiving provider, owner-selected periods for received/sent mail, deleted items and archives, and provider deletion rules remain unconfirmed.
- Technical/security logs and other backups: actual enabled logs, retention, overwrite cycles and deletion/restoration procedures at Cloudflare and other providers remain unconfirmed. Web3Forms says server logs are deleted regularly but specifies no period in the reviewed Privacy Policy.
In the revised implementation, actively selected language/theme preferences expire after 180 days and are removed on the next read; visits do not renew them. The production observation on 11 November 2026 still showed older preferences without expiry; deployment of the change remains unverified. Browser site-data controls can also remove them. Provider maxima are not the owner’s chosen retention policy.
9. Rights under Article 11
You may request to learn whether your personal data is processed; obtain information if it has been processed; learn the purpose of processing and whether it is used accordingly; learn the third parties to whom it is transferred domestically or abroad; request correction of incomplete or inaccurate data; request deletion or destruction under Article 7; request that correction and deletion/destruction be notified to recipients; object to a result against you arising exclusively from analysis through automated systems; and seek compensation for damage caused by unlawful processing.
10. Ordinary contact and formal KVKK applications
For ordinary privacy questions, contact omer@omeryigitozbey.com. You may also ask there for the verified formal application channel. An email from any address, or a contact-form message, is not automatically a duly submitted formal application.
Under Articles 4–5 of the Communiqué on the Principles and Procedures for Requests to the Data Controller, formal applications are made in Turkish and may be submitted in writing; using a registered electronic mail (KEP) address, secure electronic signature or mobile signature; using an email address previously notified to the data controller and recorded in its system; or through software/application specifically developed for this purpose. These are legally recognised methods, not a claim that the owner has established all of them. The ordinary portfolio contact form has not been verified as a dedicated statutory application channel.
The application must include name and surname, signature for written applications, Turkish identity number for Turkish citizens (or nationality and passport number or identity number if available for foreigners), residence or workplace address for service, any available email/telephone/fax for notification, and the subject of the request. Relevant information and documents must accompany it. Do not send an identity-document copy unsolicited; use the confirmed secure channel and provide only what is required by the Communiqué and proportionate identity verification.
Under Article 13 and Communiqué Article 6, requests are concluded as soon as possible and within 30 days, normally free of charge; additional costs may be charged only as permitted by the applicable rules, with a refund if the application arose from the controller’s error. Written applications are received when the document is served on the controller or representative; other methods are received when the request reaches the controller.
No verified written-application address or formal electronic channel is currently published here. You may ask the ordinary contact email for the applicable route; this gap is not resolved by listing the statutory methods.
Legal sources: Law No. 6698 (current Turkish text); Application Communiqué (Official Gazette, 10 March 2018); KVKK’s English translation. Both versions of this notice convey the same information; the official Turkish legal texts govern.