How to Build a High-Converting Landing Page: Step by Step
Learn the structure of a landing page that guides visitors toward one action, along with copy and form tips and measurement methods to use after launch.
View →A practical checklist for a KVKK-compliant website (Turkish data protection law): privacy notice, cookie consent, forms, third-party tools and security.

A KVKK (Turkey's Personal Data Protection Law) compliant website clearly explains what personal data it processes, why, and for how long; does not collect unnecessary data; and runs cookies according to the visitor's choice. In practice, this means a properly prepared privacy notice, a cookie consent that actually works, clear information on forms, and a secure infrastructure. This guide walks through the items you can check on the software side, one by one.
This article is general information, not legal advice. For the current state of the legislation and the obligations specific to your business, consult a lawyer or a data protection advisor.
The first step in a compliance effort is knowing what you have. Personal data is any information that identifies a person directly or indirectly. Name, email address and phone number are obvious examples; IP addresses, cookie identifiers and order history often fall under it too. Browse your site from start to finish and note every point where it collects data.
For each line, answer these questions: What data is collected, for what purpose, where is it stored, with whom is it shared, and how long is it kept? This table is the raw material for your privacy notice and internal procedures.
The privacy notice is the information you give to the people whose data you process. It should be easy to find on the site, written in plain language, and accessible from every point where data is collected. As important as the legal wording is that it accurately describes what you actually do; text copied from another site often does not reflect your processes.
The notice is generally expected to cover the following headings:
A privacy notice and explicit consent are not the same thing. The notice is an informational obligation; explicit consent is a specific, informed and freely given approval. Asking for consent for every process is not correct either. Determining which legal basis applies to which process requires expert advice.
Cookies are divided into those the site needs to function and those it does not. Cookies that keep you signed in or remember your basket are essential. Analytics, marketing and tracking cookies should, as a general approach, depend on the user's choice. The most common mistake here is showing a cookie banner while scripts run in the background regardless of the consent given.
To verify, open the network and storage tabs in your browser's developer tools, load the page without giving consent, and look at which cookies are created. Then try the reject option and repeat the check. This test tells you more than the banner design does.
A site whose contact form asks for a date of birth or an address is collecting unnecessary data. The rule is simple: ask only for the fields that are really needed for the purpose. For a quote form, a name, email address and message are usually enough.
Analytics tools, map and video embeds, live chat, advertising pixels and font providers may pass visitor data to parties outside your organization. For each of these tools, find out what it collects, where it processes data and what its contract terms are. Remove the ones you do not need, and put the necessary ones behind a consent mechanism.
Transferring data to servers abroad is a separate issue that needs review. The conditions that apply depend on the current state of the legislation, so if you use services that send data abroad, review them with your legal advisor.
However good the privacy notice is, a site that cannot protect the data is not compliant. The law expects the data controller to provide an appropriate level of security. The core web-side items are:
The law gives individuals a range of rights over their own data, such as the right to learn whether their data is processed, to ask for corrections, or to request deletion. State clearly on the site how such requests can be made, and decide in advance who will respond and how. A request channel should not only exist; it should be monitored regularly.
Set retention periods not by copying a fixed number, but by the reason for each type of data. If there is a legal retention obligation, follow it; if not, apply deletion, destruction or anonymization once the purpose has ended. Confirm the periods with your legal advisor against your business situation.
| Area | Problematic practice | Better approach |
|---|---|---|
| Privacy notice | Copied from another site, on a page nobody can find | Text describing your own processes, linked next to forms |
| Cookies | Banner exists but scripts run before consent | Non-essential scripts load only after consent |
| Forms | Unnecessary fields, a pre-ticked marketing box | Only required fields, a separate and unticked consent box |
| Third parties | Unused pixels and old scripts remain on the site | Inventory taken, unnecessary items removed |
| Security | Outdated software, a shared admin account | Current versions, personal accounts, backups |
If your site is multilingual, remember that the texts must be current and consistent in every language. When planning the technical infrastructure, our website maintenance checklist helps you put these checks on a regular schedule.
Some features that seem technically minor also involve processing personal data. Addressing them one by one prevents surprises.
A newsletter subscription is a separate purpose from a contact form. When people subscribe, state clearly what content they will receive, how often, and how to unsubscribe. Every message should contain a working unsubscribe link, and unsubscribe requests should be processed without delay. Sending marketing messages to purchased email lists is both unethical and legally problematic.
The name and email address of a person leaving a comment are also personal data. State what is stored in the comment form, remove unnecessary fields, and provide a way to handle deletion requests.
A third-party chat tool may hold conversation content and visitor information on its own servers. Before installing it, learn from the provider's documentation where this data is stored and for how long. If necessary, put the tool behind a consent mechanism.
Embedded videos, maps and social media components send requests from the visitor's browser to these providers as soon as the page opens. Loading such content only when the visitor clicks it, or tying it to consent, is a practical way to reduce unnecessary data flows.
KVKK compliance is not a one-time document upload; it is the habit of deliberately managing your site's data flows. If the inventory, privacy notice, cookie consent, simple forms and security are in order, you have taken a major step. If you would like to review the technical changes your site needs, you can contact Erdem Software.
If your site processes personal data through a contact form, membership, analytics or a similar channel, you are expected to inform people. The scope depends on the data you process; if you are unsure, consult a lawyer.
No. A banner is meaningful only if the mechanism behind it works correctly. You should verify in the browser that non-essential cookies are not loaded before consent is given.
No. A privacy notice is an informational obligation; explicit consent is an approval given for a specific process on the basis of information. An expert should determine which one applies to which process.
We do not recommend it. The text must reflect your actual data processing. A ready-made template can serve only as a starting skeleton; you must adapt the content to your own process.
The team can implement technical items such as the cookie consent setup, form changes, security measures and backups. The content of the legal texts should be settled together with your legal advisor.
Tell us briefly about your project, and we’ll get back to you with a roadmap and a quote.
Learn the structure of a landing page that guides visitors toward one action, along with copy and form tips and measurement methods to use after launch.
View →
What the WhatsApp Business API is, how it differs from the Business app, automation scenarios, and the opt-in and template message rules you must follow.
View →
Custom or off-the-shelf software? A guide comparing cost, flexibility, maintenance and hidden costs to help you make the right decision for your business.
View →We would like to use Google Analytics cookies to understand how the site is used. If you decline, no statistics cookies are set. Details