Creatives Data

Cookie Policy

1. About this policy

This Cookie Policy explains the cookies and similar technologies that store information in your browser (local storage, session storage, pixels and tags) used on the creativesdata.com website (the "Site"). It is prepared under the Turkish Law on the Protection of Personal Data No. 6698 ("KVKK") and, for visitors from the European Union, the General Data Protection Regulation ("GDPR"). For general information on how we process personal data, see our KVKK and GDPR texts.

2. Data controller

Data controller: Talha Çoruh, trading as Creatives Data

Address: Fikirtepe Mah. Rüzgar Sok. No:29/1K Dükkan:10, Kadıköy, İstanbul, 34720, Türkiye

You can submit requests about your rights through the channels described in the "Exercise of the Rights of the Relevant Person" section of our GDPR text.

3. What is a cookie?

A cookie is a small text file that a website stores in your browser. Local storage and session storage also keep information in the browser; session storage is deleted when the tab is closed. In this policy we call all of them "cookies". First-party cookies are stored under the Site's own domain, third-party cookies under another provider's domain.

4. Cookie categories

  • Necessary: needed for the Site to work, to keep it secure and to remember your cookie choice. Always on; they do not depend on your consent.
  • Analytics: help us measure and improve how the Site is used. Only with your consent.
  • Marketing: help us measure our advertising and show relevant ads. Only with your consent.
  • Notifications: let us send browser notifications. Only with your consent and your browser's own permission.

The cookie banner asks only about the categories that have a tool on the Site at the time. Today the Site has tools in the Analytics and Marketing categories; when the tool in the Notifications category is switched on, the banner will ask about it too and this policy will be updated. Until you turn a category on, its tools are not loaded and write no cookies.

5. How to change your choice

  • The "Cookie preferences" button at the bottom of the Site (footer) opens the cookie banner again with its settings. You can turn categories on or off, or choose "Reject all" or "Accept all".
  • When you withdraw consent for a category, its tools are stopped, their cookies and records under the Site's domain are deleted and the page reloads once.
  • Your choice is kept for 180 days; after that the banner asks again.
  • You can also delete or block cookies in your browser settings. If you block necessary cookies, your choice cannot be remembered and the banner may appear on every page.

6. The Site's own cookies

NameTypeCategoryPurposeDuration
cd_consentFirst-party cookieNecessaryYour cookie choice: consent ID, the categories asked, your choices and the time of the decision180 days
cd-consentLocal storageNecessaryA copy of the same choice; keeps open tabs in step180 days, with the decision
cd-first-touchSession storageAnalyticsThe first page you landed on, the referring site and campaign tags (UTM); added to the contact form if you send itUntil the tab is closed
cd-pushLocal storageNotificationsWhen to offer notifications: the number of sessions and page views in this browser, the time the page stayed visible and when the offer was last shownUntil you withdraw notification consent
cd-push-cleanupLocal storageNecessaryA temporary mark that completes the deletion of OneSignal's database in your browser after you withdraw notification consentUntil the deletion is complete, usually the next page

7. Tools we use

The tables below show the tools used on the Site today and the tools planned to be switched on. Planned tools load only after you consent to their category; this policy will be updated when they are switched on. Durations are those stated in each provider's own documentation.

7.1 Tools used today

ToolProvider and countryCategory and purposeCookies / storage and duration
PostHogPostHog Inc., USA. Data hosted in PostHog Cloud EU, Frankfurt (Germany).Analytics: page views, clicks and performance (Web Vitals).ph_[project key]_posthog cookie: 365 days. Local storage under the same name: until consent is withdrawn or it is deleted. ph_[project key]_* session storage keys: until the tab is closed.
SentryFunctional Software, Inc. (Sentry), USA. Data hosted in Sentry's EU region, Frankfurt (Germany).Necessary: detecting and fixing errors on the Site and keeping it secure.In the Site's configuration it writes no cookies and no persistent storage (session replay is off).
VercelVercel Inc., USA. The Site's server functions run in Frankfurt (fra1); account data in the USA.Necessary: hosting and serving the Site (processor).Writes no cookies on the live Site.
SupabaseSupabase Pte. Ltd., Singapore. The database and files are stored in the eu-central-1 region, Frankfurt (Germany).Necessary: storing contact form submissions and the Site's images (processor).No cookies in the browser; used on the server only.
ResendPlus Five Five, Inc. (Resend), USA. Account and email records in the USA.Necessary: sending the form notification and auto-reply emails (processor).No cookies in the browser; used on the server only.
UpstashUpstash, Inc., USA. Database in the selected region.Necessary: rate limiting form submissions to prevent abuse (processor). Only a hash of the IP address is used.No cookies in the browser; used on the server only.
Google Tag ManagerGoogle Ireland Limited (Ireland) and Google LLC (USA).Loaded with Analytics or Marketing consent; runs the measurement and advertising tools below according to consent. Collects no visitor data itself._dc_gtm_[id] cookie (in some configurations): 1 minute.
Google Analytics 4Google Ireland Limited (Ireland) and Google LLC (USA).Analytics: measuring visits and form conversions._ga and _ga_[id] cookies: 2 years (browser limits may be shorter).
Microsoft ClarityMicrosoft Ireland Operations Limited (Ireland) and Microsoft Corporation (USA); data in Microsoft Azure.Analytics: understanding page use through heatmaps and session recordings. Form fields are masked; what you type is not recorded._clck (1 year) and _clsk (1 day) first-party cookies. Third-party cookies of clarity.ms and bing.com: CLID, MUID, ANONCHK, SM, MR (Microsoft's official page states no duration).
Google AdsGoogle Ireland Limited (Ireland) and Google LLC (USA).Marketing: reaching visitors of the Site again in Google ads (remarketing) and keeping the ad click in a first-party cookie with the Conversion Linker; these run today. Measuring form conversions from ads (with SHA-256 hashes of email and phone for Enhanced Conversions) starts once the conversion label is set._gcl_au, _gcl_aw, _gcl_gs and similar first-party cookies: 90 days. IDE (doubleclick.net, third party): 13 months.
Meta Pixel + Conversions APIMeta Platforms Ireland Limited (Ireland) and Meta Platforms, Inc. (USA).Marketing: measuring page views and form conversions, ad targeting. Today the browser pixel runs; the Conversions API starts reporting the conversion from our server as well once its server key is set. Automatic advanced matching is on: the pixel may hash details such as email, phone, name and city from form fields with SHA-256 in the browser and send them to Meta (section 8)._fbp and _fbc first-party cookies: 90 days. The Conversions API writes nothing in the browser.
OpenAI PixelOpenAI OpCo, LLC (USA); the data of visitors in the European Economic Area and Switzerland is processed by OpenAI Ireland Ltd. (Ireland). For this data OpenAI and we are independent controllers.Marketing: measuring our ads in ChatGPT; page views and form conversions (with an event ID). Automatic advanced matching is on: the pixel may hash customer information on the page with SHA-256 in the browser and send it to OpenAI (section 8).__obref (365 days) and __oppref (30 days; only when you arrive from a ChatGPT ad) first-party cookies; __oaiq_domain_probe (at most 60 seconds, deleted at once); session storage oaiq_cs:… (until the tab is closed).
ToolLegal basisRetention at the providerInternational transfer (planned basis)
PostHogExplicit consent (KVKK art. 5(1); GDPR art. 6(1)(a)).7 years.KVKK art. 9: the Board's standard contract. GDPR: EU-U.S. Data Privacy Framework (DPF) certification and standard contractual clauses (SCCs).
SentryLegitimate interest (KVKK art. 5(2)(f); GDPR art. 6(1)(f)).Error events 30 or 90 days, by plan.KVKK art. 9: the Board's standard contract. GDPR: DPF and SCCs.
VercelEntering into and performing a contract, legitimate interest (KVKK art. 5(2)(c), (f); GDPR art. 6(1)(b), (f)).For the term of the contract; deleted within a reasonable time after it ends.KVKK art. 9: the Board's standard contract. GDPR: DPF and SCCs.
SupabaseSteps before entering into a contract, legitimate interest (KVKK art. 5(2)(c), (f); GDPR art. 6(1)(b), (f)).Form data for the periods in our privacy texts; deleted within 30 days after the contract ends.KVKK art. 9: the Board's standard contract. GDPR: SCCs.
ResendSteps before entering into a contract, legitimate interest (KVKK art. 5(2)(c), (f); GDPR art. 6(1)(b), (f)).Email records 30 days.KVKK art. 9: the Board's standard contract. GDPR: DPF and SCCs.
UpstashLegitimate interest (KVKK art. 5(2)(f); GDPR art. 6(1)(f)).The rate limit key expires with its 10-minute window.KVKK art. 9: the Board's standard contract. GDPR: DPF and SCCs.
Google Tag ManagerExplicit consent (KVKK art. 5(1); GDPR art. 6(1)(a)).Standard request logs deleted within 14 days.KVKK art. 9: the Board's standard contract (planned). GDPR: DPF and SCCs.
Google Analytics 4Explicit consent (KVKK art. 5(1); GDPR art. 6(1)(a)).User and event level data: 14 months (our setting).KVKK art. 9: the Board's standard contract (planned). GDPR: DPF and SCCs.
Microsoft ClarityExplicit consent (KVKK art. 5(1); GDPR art. 6(1)(a)).Recordings are available for up to 30 days.KVKK art. 9: the Board's standard contract (planned). GDPR: SCCs.
Google AdsExplicit consent (KVKK art. 5(1); GDPR art. 6(1)(a)).The periods in Google's advertising terms.KVKK art. 9: the Board's standard contract (planned). GDPR: DPF and SCCs.
Meta Pixel + Conversions APIExplicit consent (KVKK art. 5(1); GDPR art. 6(1)(a)).Hashed contact data deleted after matching; event data up to 2 years.KVKK art. 9: the Board's standard contract (planned). GDPR: DPF and SCCs.
OpenAI PixelExplicit consent (KVKK art. 5(1); GDPR art. 6(1)(a)).OpenAI's documentation states no period for pixel data.KVKK art. 9: the Board's standard contract (planned). GDPR: the data is processed by OpenAI Ireland Ltd., which uses a valid transfer mechanism for onward transfers.

7.2 Tools planned

ToolProvider and countryCategory and purposeCookies / storage and duration
TikTok Pixel + Events APITikTok Technology Limited (Ireland) and TikTok Information Technologies UK Limited (United Kingdom).Marketing: measuring page views and form conversions, ad targeting. The Events API reports the conversion from the server. Once switched on, automatic advanced matching will be on: the pixel may hash details such as email, phone, name and city from form fields with SHA-256 in the browser and send them to TikTok (section 8)._ttp, ttcsid, ttcsid_[pixel code] and ttclid first-party cookies and the tiktok.com _ttp third-party cookie: 13 months from last use. The Events API writes nothing in the browser.
LinkedIn InsightLinkedIn Ireland Unlimited Company (Ireland) and LinkedIn Corporation (USA).Marketing: measuring page views and form conversions, ad targeting.li_fat_id (30 days) and li_giant (7 days) first-party cookies. linkedin.com third-party cookies: bcookie (1 year), lidc (24 hours), li_gc (6 months), UserMatchHistory and AnalyticsSyncHistory (30 days).
OneSignalOneSignal, Inc., USA.Notifications: browser push notifications. Only with your consent and your browser's own permission.Sets no cookies. IndexedDB: ONE_SIGNAL_SDK_DB; local storage: os_pageViews, userConsent and, once you dismiss the notification offer, onesignal-notification-prompt (3, 7 or 30 days); session storage: onesignal-pageview-count; after your browser's permission, the service worker OneSignalSDKWorker.js and the push subscription. Until you withdraw notification consent or clear your browser data; when you withdraw consent, the Site ends the subscription and deletes them. Your browser's notification permission can only be removed in its settings.
ToolLegal basisRetention at the providerInternational transfer (planned basis)
TikTok Pixel + Events APIExplicit consent (KVKK art. 5(1); GDPR art. 6(1)(a)).TikTok's documentation states no period for pixel event data.KVKK art. 9: the Board's standard contract (planned). GDPR: SCCs.
LinkedIn InsightExplicit consent (KVKK art. 5(1); GDPR art. 6(1)(a)).Directly identifying data removed within 7 days; pseudonymised data deleted within 180 days.KVKK art. 9: the Board's standard contract (planned). GDPR: DPF (LinkedIn Corporation) and SCCs.
OneSignalExplicit consent (KVKK art. 5(1); GDPR art. 6(1)(a)).On the free plan, subscribers inactive for 18 months are deleted; on paid plans, until deleted. Messages sent through the API about 30 days.KVKK art. 9: the Board's standard contract (planned). GDPR: DPF and SCCs.

8. Server-side events (Meta Conversions API, TikTok Events API)

Once the server keys are set and you successfully send the contact form, this conversion is reported directly from our server to Meta (Conversions API) and TikTok (Events API), in addition to the pixel in your browser. Today this report is not made: only the browser pixel runs for Meta, and TikTok is not switched on yet. This report:

  • is made only if you consented to the Marketing category; without consent nothing is sent;
  • contains your email address and phone number only as SHA-256 hashes; never in plain form;
  • also contains an event ID, the event time, the address of the form page, your IP address, browser information and, if present, these platforms' cookie values on the Site (_fbp / _fbc for Meta, _ttp for TikTok) and the ad click ID;
  • carries the same event ID as the browser pixel, so the platform does not count the same conversion twice.

Automatic advanced matching in the browser. If you consented to the Marketing category, the Meta and OpenAI pixels (and the TikTok pixel once it is switched on) may hash identifying details from the form fields on the page with SHA-256 in your browser and send them to their providers. The plain values are not sent. According to each provider's own documentation:

  • Meta: details such as email, phone, first name, last name, city, state or province, country, postal code and gender; from form fields and also from other sources on the Site. The hashed details are discarded after matching.
  • OpenAI: its documentation refers to "supported customer information"; it does not list the fields it detects.
  • TikTok (once switched on): email, phone, first name, last name, address (city, state or province, postal code, country; street-level details are not collected) and external IDs such as a customer number; from input fields and also from text shown on the page and the Site's data layer.

Whether free-text fields, such as the message field, are read is not stated in the documentation of any of these three providers. Without marketing consent these pixels are not loaded at all.

Under Meta's and TikTok's own terms, for visitors whose data is subject to the GDPR or the UK GDPR, we are joint controllers with Meta and with TikTok for the collection of pixel and server event data and its transmission to these platforms.

9. Consent record

Every decision you make in the cookie banner is recorded as proof of consent: a random consent ID, the policy version, your choices per category, the type of decision (granted, updated, withdrawn), its time, the page where you made it, a hash of your IP address and browser information. Your IP address is not stored in plain form. The record is kept for 3 years and then deleted or anonymised.

10. Retention periods

  • Your cookie choice (cd_consent): 180 days.
  • Consent record: 3 years.
  • Event data in Google Analytics 4: 14 months.
  • Tools' cookies: the durations in the tables above.
  • Contact form and other personal data: the periods in our GDPR text.

11. International transfers

Most of the tools we use process data on servers outside Türkiye, which is a cross-border transfer under the KVKK.

  • Basis: under Article 9 of the KVKK as amended by Law No. 7499, a cross-border transfer is made to a country with an adequacy decision of the Personal Data Protection Board or with one of the appropriate safeguards. As the safeguard, the standard contract announced by the Board is signed with the providers and notified to the Personal Data Protection Authority within 5 business days of signature. For occasional, non-regular transfers, the exceptions listed in the Law (such as explicit consent) may be relied on.
  • Under the GDPR: for transfers outside the European Economic Area, the provider's certification under the EU-U.S. Data Privacy Framework or the European Commission's standard contractual clauses (SCCs) are used.
  • The basis planned for each tool is in the tables in section 7.

12. Your rights

Under Article 11 of the KVKK and the GDPR you have the right to learn whether your personal data are processed, to request information, rectification and erasure, to object to processing and to withdraw your consent at any time. Withdrawing consent does not affect the lawfulness of processing before the withdrawal. How to apply is described in our GDPR text. Visitors in the European Union also have the right to lodge a complaint with the data protection authority of their country.

13. Changes

We update this policy when the tools we use or the law change. The current version is always on this page; when the cookie categories change, the cookie banner asks for your choice again.

This policy in Turkish: Çerez Politikası.