Your personal data
Cookie Policy
Last updated: November 4, 2026
This explains the purposes for which cookies and similar browser records are used on the website.
This is a translation; the Turkish edition governs.
1. Session and security
If you are logged in, session cookies are used to maintain your session and provide secure access to your account. Security and abuse-prevention measures may also process technical records relating to requests. Features requiring login may not work if session cookies are disabled. A cookie named bd_izin is stored for 180 days to remember your cookie preference; this cookie does not contain an identity.
2. Preferences
Your preferences, such as theme, selected business, sidebar, and dashboard layout, may be stored in cookies or your browser's local storage. These records save you from having to select your preferences again; you can clear them in your browser settings.
3. Visit and usage statistics
We use PostHog to count how many people visit our promotional pages (such as the home page, pricing, and examples), which pages they visit, and where they come from; PostHog's servers are in the European Union. No cookie or similar record is written to your browser for this count. At PostHog, your IP address and browser information are converted into an irreversible hash using a key that changes every day and is deleted the next day; your IP address is not stored or used to identify you. Only campaign information (utm) is taken from the address. If Do Not Track or Global Privacy Control is enabled in your browser, you are not counted.
When you log in, information about which dashboard screens you use and the outcomes of actions such as generation and publication is sent to PostHog under an identifier linked to your account to improve the product; an identifier is stored in your browser's local storage for this purpose. Your name, email address, the content you write, and payment information are not sent.
3a. Advertising measurement (only if you give permission)
We use Meta Platforms' measurement tools to measure whether Buildary advertisements work. These tools run only if you give permission in the cookie banner or through the Cookie preferences link at the bottom of the page. If you do not give permission, Meta's script is not loaded, your browser sends no request to Meta, and our server sends Meta nothing about you.
There are two separate permissions. If the advertising tag (Meta Pixel) is enabled, the addresses of pages you open after arriving from an advertisement, your IP address, browser information and two cookies Meta writes to your browser are sent to Meta. If sharing registration and payment information is enabled, when you open an account or make a payment our server sends Meta the event type, amount paid, IP address, browser information and a SHA-256 hash of your email address. Meta may match this hash with its own accounts, so the hash is also personal data. Your telephone number, name, address, identity number or tax number and card information are not sent. The choice you make when opening an account applies to your new account. If you already have an account, your cookie-banner choice does not automatically become that account's permission: we ask separately for that account after you log in.
Meta processes this information on our behalf to measure and match advertising results. Under Meta's terms, it may also use it under its own responsibility for displaying advertisements and improving its products; it may retain event information for no more than two years. Transfers are made to the USA and are based on the Board's standard contract. Details are in the Advertising measurement section of the KVKK Information Notice. The legal basis is your explicit consent.
bd_izin: remembers your cookie preference. First-party cookie, 180 days. It is a necessary cookie and does not require permission._fbp: Meta's browser identifier. First-party cookie written by Meta's script. 90 days. Depends on advertising tag permission._fbc: links an advertising click to the browser. First-party cookie written by Meta's script. 90 days. Depends on advertising tag permission.
You can change your preference at any time: turn permissions off through the Cookie preferences link at the bottom of the page. Turning them off stops the Meta tag and deletes the _fbp and _fbc cookies. You must be logged in for sharing linked to your account: if you are logged in, new events from our server stop immediately; if you turn it off without logging in, sharing for your account is turned off when you next log in from this browser, or you can log in and turn the setting off again. Information previously sent to Meta remains at Meta; you can also apply to Meta concerning it. We remember your preference for 180 days, then ask again.
If your browser sends Do Not Track or Global Privacy Control, we do not show the cookie banner or run Meta tools; you may enable them yourself through the Cookie preferences link. You can also manage advertising preferences at aboutads.info/choices and youronlinechoices.eu.
4. Optional support and external services
Support is provided through WhatsApp; no third-party script is loaded or cookie written on our website for support. Advertising measurement is separate and runs only if you give permission (3a). When you open WhatsApp, WhatsApp's own terms apply. At payment, the provider's own cookie policy applies on iyzico's secure screen.
5. Control and contact
You can view, delete, or block cookies in your browser settings. If necessary session cookies are blocked, you may not be able to log in to your account. You can turn off advertising measurement permission at any time through the Cookie preferences link at the bottom of the page. Details of data processing and transfers abroad are in the KVKK Information Notice and Privacy Policy. You can send questions to buildarydev@gmail.com.















