WebdesizCookie Policy
Last updated: 25 September 2026 · Turkish version (binding)
This text describes what is stored in your browser on the webdesiz.com site and in the Webdesiz panel. The site and panel are operated by Birim Ajans Yazılım Limited Şirketi. For those who want the short answer: a few security cookies required for operation, a few browser records that remember your preferences, and Google Analytics to see visitor numbers. A Meta pixel whose fields we limit also runs, to see the results of our own ads (section 5).
1. What is a cookie, what is browser storage
A cookie is a small piece of text a site leaves in your browser and that is sent back with subsequent requests. Browser storage (localStorage) is a record area that stays on your device and is not sent to the server by itself. They are technically different, but because both take up space on your device we listed both item by item below.
2. Cookies we use
| Name | Type | Duration | What it does |
|---|---|---|---|
| oauth_state | Strictly necessary · cookie | 10 minutes | Verifies that the request in the Google or Facebook sign-in flow really came from you (CSRF protection). httpOnly; JavaScript cannot read it. |
| oauth_next | Strictly necessary · cookie | 10 minutes | Remembers which page to return to after sign-in, so you get back to what you were doing. |
| meta_oauth_state | Strictly necessary · cookie | For the duration of the connection flow | A signed security value used while connecting your Meta ad account. Prevents someone else from connecting an account on your behalf. |
| webdesiz-site-lang | Preference · cookie | 1 year | The site language preference (Turkish or English). Written when you click the language link in the header, so the home page no longer redirects based on your browser language. Carries no identity. |
| _ga and those starting with _ga_ | Measurement · third-party cookie (Google) | Period set by Google, 2 years by default | Used by Google Analytics to count visitors uniquely and see which pages are read. How to switch it off is explained in the section below. |
| _fbp | Ad measurement · first-party cookie (sent to Meta) | 90 days (renewed on each visit) | Tells your browser apart with a random number (fb.1.<time>.<random number>) to measure the results of our own Facebook and Instagram ads. It does not carry your name, email or account number. It goes to Meta with the Meta pixel request; details in section 5. |
| _fbc | Ad measurement · first-party cookie (sent to Meta) | 90 days | Written only if you arrived by clicking a Meta ad: it stores the fbclid click number from the address so we can measure which ad worked. It goes to Meta with the Meta pixel request. |
Without the first three, the sign-in and ad account connection flows do not work securely, which is why we call them strictly necessary. These three do not track you across sites.
3. What we keep in your browser
| Key | Duration | What it does |
|---|---|---|
| meta-saas-auth | Until you sign out | Your session. Your sign-in details and access token are kept here so you do not have to sign in again on every page. Deleted when you sign out. |
| webdesiz-lang | Until you change it | The panel language preference. Remembers whether you use Turkish or English. |
| webdesiz-ad-chats-v1 | Until a successful transfer or until you clear site data (legacy version only) | Ad assistant conversations left in the browser by the old version. Webdesiz does not show them automatically or upload them to your account. They are taken to the server only if you explicitly confirm the conversations are yours and choose to transfer them; after a successful transfer this old record is deleted. New conversations are not written to this key. |
| meta-saas-checklist-closed | Until you change it | So the setup steps list does not appear again if you closed it. |
| webdesiz-meta-satin-alma | Until you clear site data (at most the last 20 payments) | Keeps a short digest of the checkout session so the payment event sent to Meta after a payment is not sent a second time when you reload the page. The digest is not sent to Meta and contains no payment details. |
| pixelBannerDismissed | Until you change it | So the pixel warning strip does not open again if you closed it. |
These records stay only in the browser you signed in with. They do not carry over when you sign in from another device.
4. Measurement: Google Analytics
We use Google Analytics 4 (gtag.js) on the site, to see which pages are read, how many visitors come and where people get stuck. For this Google leaves the _ga cookies listed above in your browser, and device, browser and approximate location information is sent to Google during your visit.
If you do not want this, the easiest way is to press “Reject” on the notice at the bottom of the page or use Cookie preferences in the footer (6 October 2026): Google Analytics, Microsoft Clarity and the Meta pixel stop immediately, the cookies they set on our domain are deleted and they are not loaded on later pages; your choice is kept for 12 months in the km_cerez cookie. There are also two other ways: you can block third-party cookies in your browser’s cookie settings, or install Google’s Analytics opt-out add-on. Neither affects how the panel works.
5. Ad measurement: Meta pixel
To see whether our own Facebook and Instagram ads work we use the pixel of Meta Platforms Ireland Limited. We do not load Meta’s ready-made script (fbevents.js), because that script also collects the full page address, the page title and button texts. Instead your browser sends only the following to facebook.com/tr:
- The event name: page view (
PageView), completed registration (CompleteRegistration) or payment (Purchase) - The page address with its query part and the IDs in it removed (e.g.
/kampanyalar/[id]); the page you came from the same way, or only the site name if you came from another site - The time and a random number generated anew for each event
- The
_fbpcookie above and, if you arrived by clicking a Meta ad, the_fbccookie (the ad’s fbclid click number) - For the payment event, the amount paid and the currency
Your email address, name, phone number, the page title, screen information and your account, invoice or business numbers are not sent. By the nature of the request your browser also sends your IP address, browser information and, if you are signed in to Facebook, Meta’s own (facebook.com) cookies. The payment event is sent only after your payment has actually been collected by Stripe.
On pages whose address carries a secret value, such as password reset, the sign-in return and the data deletion status, the pixel does not run at all and no cookie is written. On the panel pages after sign-in no page view is sent; only the payment event is sent when a payment is completed. Meta may use this data to measure the results of our ads and to show our ads; the data may be processed on servers in Ireland and in other countries, including the USA.
If you do not want this: you can block cookies for this site in your browser or delete the _fbp/_fbc cookies, use an ad-blocking extension, or disconnect this activity in your Facebook or Instagram account settings under “Your activity off Meta technologies”. None of these affects how the site and the panel work.
6. What we do not use
- No ready-made ad scripts. Meta’s pixel script (fbq / fbevents.js), the Google Ads remarketing tag or similar ad tracking code is not loaded. The only thing that goes to Meta is the request described in section 5, whose fields we limit.
- No heat maps or session recording. We do not use any tool such as Hotjar or Clarity that records your screen.
- Fonts come from our own server. Site fonts are served with the application; your browser does not request a third-party site to get fonts.
- We do not sell cookies to anyone. We do not build advertising profiles with this data ourselves; the data goes only to Google and Meta, named on this page, within the scope described.
You may see a tag named facebook-domain-verification in the page source. This is not a tracking code; it is a one-line verification proving to Meta that the domain belongs to us. It leaves no cookie and collects no data.
7. The pixels you manage in the panel are a separate matter
Webdesiz lets you connect and control your Meta pixels. Those pixels run on your own site, measure the conversions of your ads and are not the subject of this policy. Responsibility for those pixels and the obligation to inform your visitors belong to you. The pixel in section 5, by contrast, measures only webdesiz.com’s own ads; it shares no data with your pixels or ad accounts.
8. You are in control
- You can delete cookies or block them for this site from your browser settings. If you block the strictly necessary cookies you may not be able to sign in.
- To clear browser storage you can use your browser’s “clear site data” option. This deletes the old browser chat record and your preferences; the current chat history in your account stays on the server and can be deleted from the Ad Assistant panel.
- When you sign out of the panel, your session record (
meta-saas-auth) is deleted from your browser.
9. Changes and contact
If we add a new tool we change this page and the update date at the top. You can send questions about cookies and personal data to destek@webdesiz.com. How personal data is processed is in the Privacy Policy and KVKK Notice.