Agurel KVKK Compliance and Cookie Bar

No. The generated text is a starting point based on general KVKK requirements. It does not constitute professional legal advice. We strongly recommend that your KVKK privacy notice is reviewed or prepared by a qualified lawyer before publishing. This applies both to the auto-generated text and any custom text you write yourself.

No. The plugin is modular and the privacy notice generator is entirely optional. You can use:

• Only the cookie consent bar (default), or
• The cookie consent bar together with GA4 / Consent Mode v2, or
• The cookie consent bar with custom script blocking (Meta Pixel, Hotjar, etc.)

Go to Cookie Settings (Çerez Ayarları) in the plugin panel and enter the URL of your KVKK privacy notice page. The cookie bar will link to that page. We strongly recommend that this page contains a privacy notice prepared by a qualified lawyer.

No. Once you manually edit the privacy notice text, it is treated as your custom text and is no longer regenerated automatically. If you change your company information or data categories afterwards, go to the "KVKK Metni" page and click "Otomatik Oluştur" (Auto-Generate) again to refresh the text, or edit it manually.

The disclaimer acceptance is recorded per WordPress user. If a different user logs in, they have not yet accepted it, so it will be shown to them. Deactivating the plugin resets the acceptance records (the permanent file log is not affected), so reactivating the plugin will show the disclaimer again for all users.

Yes. As required by the KVKK Cookie Guidelines, analytics and marketing cookies are disabled by default. Only essential cookies are always active.

This is intentional. The KVK Board's guidelines prohibit manipulative design patterns (dark patterns) — for example, making the "Accept" button large and green while hiding the "Reject" button. All three buttons (Accept All, Reject All, Cookie Settings) are displayed in the same neutral color and size so that no option is visually prioritized over another.

All cookie categories (essential, analytics, marketing) are enabled. If GA4 integration is active, Consent Mode v2 signals (analytics_storage, ad_storage, etc.) are updated to "granted". Any custom blocked scripts are also loaded at this point.

Only essential cookies remain active; analytics and marketing cookies stay disabled. If GA4 integration is active, Consent Mode v2 signals remain "denied". Custom scripts are not loaded.

The site continues with only essential cookies — analytics and marketing remain off. The choice is saved as a cookie so the bar will not appear again on subsequent visits. This is not recorded as an explicit "Reject" but consent is not granted either.

Yes. Add the [kvkk_tercih_butonu] shortcode to your footer or any page. It displays a "Çerez Tercihlerimi Yönet" button — clicking it reopens the cookie bar so the visitor can update their preferences at any time.

The plugin offers three scenarios in the GA4/Script settings page:

• Cookie Bar only (default): If you do not use any analytics or advertising tools. Shows the consent bar for legal compliance only.
• GA4 / Consent Mode v2: If you use Google Analytics or Google Ads. GA4 Consent Mode v2 signals are updated according to the visitor's consent choice.
• Custom Script Blocking: If you use Meta Pixel, Hotjar, LinkedIn Insight, or other third-party tools. Paste the script code and it will only load after the visitor gives consent.

Consent Mode v2 loads the GA4/GTM script immediately but sends a "denied" signal — the script runs but collects no personal data. Custom Script Blocking is stricter: the script is not loaded at all until the user clicks "Accept". For the highest level of prior consent compliance, use Custom Script Blocking.

Default is 180 days (6 months), configurable from the admin panel.

Yes, partially. As of version 1.2.0, the following WooCommerce-specific data categories are available in the Data Categories panel and are automatically reflected in the privacy notice:

• Order information (order number, products, amount, date)
• Billing information (name, address, email, phone, tax ID or national ID)
• Shipping information (delivery address, recipient name, phone)
• Payment processing (handled by third-party payment providers such as iyzico, PayTR, Stripe — card data is not stored on your site)
• Date of birth (for loyalty programs or +18 age verification — includes a note about BTK regulations)