On most sites, an entry from a quote form is copied to at least five different places: the plugin table, the sales mailbox, the CRM, the SMTP service’s log and the nightly backup. When a deletion request arrives, nobody remembers half of these copies. The contact form on corporate sites is the most visible door through which personal data enters the company, and the KVKK side doesn’t end with a link to a text. Why each field is requested, where the data is copied, how long it’s kept and how it’s deleted are part of the technical design. This guide explains the form’s data lifecycle at the implementation level for web teams, IT managers and data protection officers. It isn’t legal advice; processing conditions and text content should be determined with your legal counsel. Assess how your data processing preferences on the web align with retention and access processes within the scope of KVKK technical and administrative measures consulting.
What data the form should collect
The general principles in Article 4 of Law No. 6698 require data to be processed in a way that is relevant, limited and proportionate to the purpose. In form design, this comes down to a single question: Can we respond to the request without this information?
When you scan a typical B2B quote form with this question, this is usually the result:
| Field | Is it needed? | Note |
|---|---|---|
| Full name | Yes | Needed for a reply |
| Business email | Yes | A single contact channel may be enough |
| Phone | Often optional | A preference can be asked instead of making it mandatory |
| Company and job title | Yes, for a quote | Not needed for general enquiries |
| Turkish ID number, date of birth | No | No justification at the quote stage |
| Free-text message | Yes | Add a warning not to enter sensitive data |
The free-text field carries a separate risk. The visitor may write health information, identity details or third parties’ data in the message; this means special categories of personal data being collected unintentionally. Put a short warning under the field, such as “Please don’t share health, identity or payment information”. Open a file upload field only when it’s really needed. If it is, set up type, size and storage checks according to the principles in the secure file upload guide.
Hidden fields go into the inventory too. Many form plugins automatically add the IP address, browser information, referring page and UTM parameters to the entry. These can also be personal data. If there’s no need for them, turn them off in the plugin settings; if there is, mention them in the privacy notice.
Separating the privacy notice from explicit consent
The mistake we see most often in the field is combining the two in a single box: “I have read the KVKK privacy notice and consent to the processing of my personal data.” This sentence ties two separate legal concepts to the same click.
- Privacy notice (Law Art. 10): The obligation to inform the data subject of the data controller’s identity, the purpose of processing, the parties data is transferred to, the collection method and legal basis, and the data subject’s rights. It doesn’t depend on the visitor’s approval; it’s presented with a visible link near the form, before the submit button.
- Explicit consent (Law Arts. 3 and 5): Consent relating to a specific matter, based on information and given freely. It’s only required for purposes for which there is no other processing condition.
The Turkish Personal Data Protection Authority’s communiqué and guides on the obligation to inform emphasize that these two processes are carried out separately; the current texts are at kvkk.gov.tr. The technical setup should therefore be:
- Below the form, above the submit button, there’s the sentence “Your personal data is processed in accordance with the Privacy Notice” and a link to the text. There’s no checkbox.
- For purposes beyond the request, such as a newsletter, campaign emails or marketing calls, a separate, unticked checkbox is added. Leaving the box empty doesn’t prevent the form from being submitted.
- When the consent box is ticked, the consent text (or its version number), date and time and the form address are written to the entry. The burden of proving consent lies with the data controller.
If commercial electronic messages will be sent, the obligations of Law No. 6563 and the Message Management System (İYS) also come into play alongside KVKK. Be sure to test that the marketing consent box is correctly mapped to the messaging permission field in the CRM. If the mapping is broken, consent stays on paper.
Where form entries are stored
A retention and deletion policy can only be applied if all the copies are known. On a typical WordPress site, the inventory looks like this:
| You are here | Example | Deletion method |
|---|---|---|
| Plugin entry table | Gravity Forms, WPForms Pro, Elementor Pro Submissions, Flamingo | Scheduled job or plugin setting |
| Notification email | Sales mailbox, shared mailbox | Mail retention policy |
| CRM / helpdesk | Lead record, ticket record | CRM retention rule |
| Email sending service | SMTP service message logs | Log retention in the service panel |
| Database and file backups | Daily site backup | Backup rotation |
| Application and error logs | Debug log, WAF logs | Log rotation |
Plugins behave differently. Contact Form 7 doesn’t store submissions by default, it only sends an email; when Flamingo is added, entries start being written to the database. The free version of WPForms doesn’t store entries; the paid version does. Elementor Pro forms keep entries in their own tables with the “Submissions” feature. When reviewing the site, ask separately for each form: Where is this form’s data?
If the request is passed to a CRM or a request management system, the copy in WordPress is usually unnecessary. Deleting the local entry after the transfer has completed successfully, or not keeping it at all, reduces both the attack surface and the deletion burden. If entries need to be visible in the admin panel, give access only to the relevant roles. Not every editor needs to read form entries.
Retention period and automatic deletion
Article 7 of the Law requires data to be deleted, destroyed or anonymized when the reasons requiring its processing no longer exist. The Regulation on the Deletion, Destruction or Anonymization of Personal Data provides that the periodic destruction interval can’t exceed six months; verify the text on mevzuat.gov.tr. What the period should be is a legal decision. In practice, what matters is that the period is enforced automatically, not by hand. Manual cleanup is forgotten after a few months.
For example, a small must-use plugin that deletes contact form entries stored in Flamingo once they’re older than 180 days can be written like this (the period is an example; change it according to your policy):
<?php
// wp-content/mu-plugins/form-entry-cleanup.php
add_action( 'init', function () {
if ( ! wp_next_scheduled( 'ere_form_entry_cleanup' ) ) {
wp_schedule_event( time(), 'daily', 'ere_form_entry_cleanup' );
}
} );
add_action( 'ere_form_entry_cleanup', function () {
$ids = get_posts( array(
'post_type' => 'flamingo_inbound',
'post_status' => 'any',
'fields' => 'ids',
'posts_per_page' => 200,
'date_query' => array( array( 'before' => '180 days ago' ) ),
) );
foreach ( $ids as $id ) {
wp_delete_post( $id, true ); // permanent deletion, not to the trash
}
} );
Check four points before putting this code into service:
- Triggering: WP-Cron runs on visits. On low-traffic sites, define
DISABLE_WP_CRONand switch to the system cron; otherwise the job may not run for days. - Permanent deletion: The code bypasses the trash. Try it first in the test environment with a dry run that logs the number of entries to be deleted.
- Backups: A deleted entry lives on in the backup. If the backup retention period is longer than the form retention period, write this into the destruction policy; add re-deletion of old entries after a restore from backup to the procedure.
- Address book: Flamingo also keeps senders separately as the
flamingo_contacttype. Apply the same retention rule to these records too.
If statistics are needed, anonymization is an alternative to deletion: the request type, sector and date remain; the name, email, phone and message text are deleted. Merely converting the email address to a hash value doesn’t count as anonymization. The same address can be hashed again and matched.
Data in notification emails
The default notification template of form plugins usually dumps all fields into the email body. That email spreads to the sales team’s shared mailbox, from there to phones, the mail archive and backups. However good your retention policy is, copies in mailboxes are in practice never deleted.
A more controlled setup looks like this:
- The notification contains only the request type, the company name and a link to the entry; the personal data stays in the entry itself, in an access-controlled system.
- Sending is done through authenticated SMTP or an API-based service. Sending directly from the server with PHP
mail()is weak in terms of both delivery and logging. - If the sending service is hosted abroad, this is considered a cross-border transfer under Article 9 of the Law; it should be reflected in the privacy notice and the VERBİS (Data Controllers’ Registry) records. Check in the panel settings how long the service keeps message content.
- The automatic reply shouldn’t send the visitor’s message back verbatim. A mistyped address means the data goes to a third party.
The form itself must be protected too. Spam bots can use the form to make it send automatic replies to third parties’ addresses; the server-side checks in the form spam prevention article limit this abuse. To generate validation rules on the client and server from the same schema, see the form validation guide. Add to the list of technical measures that the form can’t be submitted outside HTTPS, that the admin panel is accessed with MFA and that access to form entries is logged; for the general framework, the KVKK technical measures article is complementary.
KVKK form checklist
Before putting a new form live, or when reviewing existing forms, fill in the list per form:
- The purpose of every field is in writing; required fields are limited to those really needed for a reply.
- Hidden fields (IP, user agent, UTM) are in the inventory; unnecessary ones are turned off.
- The privacy notice link is visible before the submit button; it isn’t tied to a checkbox.
- Marketing consent is separate, unticked and optional; the consent record is kept with the text version and a timestamp.
- All locations the data is copied to (plugin table, email, CRM, sending service, backup, logs) are listed.
- For each location, the retention period and automatic deletion method are defined and tested.
- The notification email contains a minimum of personal data.
- Access to form entries is role-based; admin accounts are protected with MFA.
- How to find the entry in all locations when a data subject’s deletion request arrives is in writing.
The last item turns up missing in almost every audit. When a request arrives, it should be possible to search the plugin table, the CRM and the mailboxes by email address, and the result should be recorded. If you can’t search, you can’t delete. For producing a form inventory and setting up retention automation, see our KVKK-focused web forms service; for connecting requests coming from forms to an approval and tracking flow, see our form, request and approval systems page. Cookies and tracking tags are a separate topic; we explained tying them to consent in the cookie consent and tag management article.
Frequently asked questions
Is an explicit consent checkbox always required on a contact form?
No. For data processed only to respond to the visitor’s request, a processing condition other than explicit consent is considered in most cases. Explicit consent is needed for purposes that go beyond the request and don’t rely on another condition, such as sending marketing messages. Decide with your legal counsel which condition applies.
Is it right to have the privacy notice accepted with a checkbox?
The privacy notice is the data controller’s obligation to inform; it doesn’t need to depend on the visitor’s approval. An “I have read and accept” box doesn’t turn the notice into consent; it confuses the two concepts. Give a clear link to the privacy notice near the form, and obtain consent with a separate, unticked box.
Is it mandatory to keep form entries in the WordPress database?
No. If the request is passed to a CRM or helpdesk system, the second copy in WordPress is often an unnecessary data store. If a copy is kept, set a short retention period and set up automatic deletion.
How can I reduce the personal data in notification emails?
Don’t put all form fields in the notification; write the request type and a link to the record. Let authorized users view the record in an access-controlled system. That way, personal data isn’t copied to shared mailboxes, mobile devices and mail backups.