Adapte Dijital
Kurumsal
Müşteri Girişi
Dijital Yönetim
AI SEO
Marka Yönetimi
Danışmanlıklar
Web & App & AI
Ads & Reklam
Kitle Yönetimi
Veri Yönetimi
Amaç & Hedef
Videolar
AINEO
Dijitale Yatırım Yap
Blog
Data Protection Consulting

How do web forms comply with data protection?

AuthorAdapte Dijital Published4 October 2026 Reading Time3–5 dk
How do web forms comply with data protection?

What does your contact form ask for? Name, phone, email, company, budget, date of birth, address… Most forms have more fields than needed, and every piece of data collected is a responsibility. 📝

The web form is a business’s most-used data collection point; it’s where compliance is first visibly tested.

Short answer: a form asks only for data its purpose needs, gives notice at collection, asks marketing permission separately and optionally, and stores data securely. 🧭

Note: this is general information, not legal advice. Regulations and Board decisions change; see the Turkish Personal Data Protection Authority for current guidance and a lawyer for your specific case.

FOUR

Four form rules

BU BÖLÜMÜN ÖZETİ

  • Data minimisation
  • Notice link
  • Separate marketing permission
  • Secure transmission

The foundation. 📋

Data minimisation

Fields the purpose doesn’t need are removed; see the archive’s data-not-to-collect guide. ✂️

Notice link

A visible link near the submit button. 🔗

Separate marketing permission

Newsletter or campaign permission via a separate, unticked box; see the commercial messages guide. ☐

Secure transmission

Form data sent over an encrypted connection. 🔒

WHERE

Where does form data go?

BU BÖLÜMÜN ÖZETİ

  • Email inboxes
  • Site database
  • CRM and sheets
  • Third-party tools

Four stops. 🗺️

Email inboxes

Whose inbox gets form notifications, and how long do they stay? 📧

Site database

Plugin forms save to the site; who has access? 💾

CRM and sheets

Is data moved to other systems? See the archive’s CRM guides. 📇

Third-party tools

Is the form tool abroad? See the transfers guide. 🌍

RETENTION

Retention and deletion

BU BÖLÜMÜN ÖZETİ

  • Set a period
  • Clear old records
  • Access rights
  • Backups too

Four principles. 🗂️

Set a period

How long is form data kept? In writing; see the retention guide. 📅

Clear old records

Years of records in plugin databases are deleted. 🧹

Access rights

Only the people who need form data see it. 👤

Backups too

Deleted data isn’t forgotten in backups. 💾

SPECIAL

Special cases

BU BÖLÜMÜN ÖZETİ

  • File uploads
  • Special category data
  • Children
  • Free-text fields

Four warnings. ⚠️

File uploads

CV or document upload fields carry extra risk; see the CV guide. 📎

Special category data

A legal assessment before asking for data like health. 🔒

Children

Forms aimed at children need extra care. 🧒

Free-text fields

People may write unexpected sensitive details; guide the field. ✍️

FOUR

Four common mistakes

BU BÖLÜMÜN ÖZETİ

  • Asking everything
  • Mandatory marketing box
  • Keeping forever
  • Insecure plugins

All four grow risk. 🚧

Asking everything

“Might be useful” fields are needless liability. 📋

Mandatory marketing box

If the form can’t be sent without permission, it isn’t free. ☑️

Keeping forever

Requests from years ago are still there. 🕰️

Insecure plugins

Un-updated form plugins are an open door. 🔓

WHAT

What should I do today?

BU BÖLÜMÜN ÖZETİ

  • Step 1: list forms
  • Step 2: mark needless fields
  • Step 3: map the data’s route
  • If you want help

Three steps, one hour. 🪜

Step 1: list forms

Every form on the site and its fields; a table. 📋

Step 2: mark needless fields

Every field the purpose doesn’t need; to be removed. ✂️

Step 3: map the data’s route

Where each form’s data goes and how long it stays; one page. 🗺️

If you want help

Let us make your web forms compliant together: use the consult your expert form. For a compliance snapshot of your digital assets see the digital audit; the bigger picture sits on the KVKK consultancy page. 🎯

Related reading from the archive: data you shouldn’t collect · choosing a CRM.

FOUR FORM RULES MINIMISATIONno needless fields NOTICEvisible link SEPARATE PERMISSIONunticked box SECUREencrypted Every piece of data is a responsibility

WHERE DATA GOES Email inboxes — how long it stays Site database — who has access CRM and sheets — transfers Third-party tools — abroad?

RETENTION AND DELETION PERIODin writing OLD RECORDScleared ACCESSwho needs it BACKUPSnot forgotten A mandatory marketing box isn’t free permission

BÖLÜM 07

📝 Notes From the Field

A service firm’s contact form asked for twelve fields including date of birth and full address; its plugin also kept every request for years in the site database. Fields were cut to four, a notice link and a separate unticked marketing box were added, and old records were cleared by the retention period. Form completion rose and data risk fell noticeably.

A service firm’s contact form asked for twelve fields including date of birth and full address; its plugin also kept every request for years in the site database.
BÖLÜM 08

📖 Short Glossary

Data minimisation: collecting only what the purpose needs. Privacy notice: the text informing people about processing. Form plugin: software creating forms on a site. Encrypted connection: a secure data transmission link.

Data minimisation: collecting only what the purpose needs.
BÖLÜM 09

⚡ Quick Summary

The web form is compliance’s first visible test. 📝 It asks only for needed data, links a notice, asks marketing permission separately and unticked, and transmits securely. Know the data’s route through inboxes, databases, CRM and third-party tools. Set retention in writing and clear old records. File uploads, special data and free text need extra care.

The web form is compliance’s first visible test.
BÖLÜM 10

🎯 Next Step

Let us make your forms compliant: use the consult your expert form. Cookies sit in the cookie consent guide; for your setup see the digital audit.

Let us make your forms compliant: use the consult your expert form.
FREQUENTLY

Frequently Asked Questions

Sık Sorulan Sorular

Is asking for a phone number a problem?

If the purpose is a call-back it may be reasonable; whether it’s mandatory should follow the purpose. Needless mandatory fields may breach minimisation.

Does the plugin need to keep records?

If requests already arrive by email, in-plugin records may be unnecessary. If kept, set a period and access.

Who should write the privacy notice?

The team that knows the real data flow, together with a lawyer. Templates may not match real processes.

Source: Turkish Personal Data Protection Authority — guidance and decisions

Bu Konuyla İlgili Diğer İçerikler

Share this article
WhatsAppXLinkedInFacebook

Comments

TREN