Cookie Policy

This policy applies to the fidkeep.com website, the sign-in and sign-up screens at auth.fidkeep.com and the application running on fidkeep.com subdomains.

The data controller for personal data processed through cookies is FİDKEEP TEKNOLOJİ TİCARET LİMİTED ŞİRKETİ, Sarıgüllük Mah. Ali Nadi Ünler Bul. Milenyum Apt. No: 3A, Şehitkamil / Gaziantep, Türkiye. Contact: [email protected].

Cookies are small text files that are saved in your browser when you visit a website and sent back to the site with later requests. They are used for purposes such as keeping you signed in, ensuring security or measuring how a site is used.

Similar technologies include the browser's local storage (localStorage). Data in local storage is not sent to the server automatically; it is read only by scripts on the page. In this policy, "cookie" also covers these technologies unless stated otherwise.

Cookies are classified as follows:

• By provider: first-party cookies set by the domain you are visiting, and third-party cookies set by another domain.
• By duration: session cookies deleted when the browser is closed, and persistent cookies kept for a set period.
• By purpose: strictly necessary, functional, analytics and advertising/targeting cookies.

• Strictly necessary cookies: needed for the website and application to work securely, for signing in, for remembering your cookie preference and for protecting the site against abuse. The service cannot be provided without them.
• Analytics cookies: used only on the fidkeep.com website and only with your explicit consent, Google Analytics 4 cookies measure in aggregate how the site is used.

Fidkeep does not use advertising, targeting or retargeting cookies. No analytics or advertising cookies are used in the application.

Strictly necessary

• fidkeep_cookie_consent — Provider: Fidkeep; Purpose: to store the choice you made in the cookie banner and the date of that choice, and not to show the banner again while your choice is valid; Duration: 12 months; Type: first party, browser local storage (localStorage).
• __cf_bm — Provider: Cloudflare, Inc.; Purpose: when bot protection is active, to distinguish real visitors from automated traffic and protect the site against abuse; Duration: 30 minutes; Type: first-party cookie set by Cloudflare on the fidkeep.com domain.

Analytics (only with your explicit consent)

• _ga — Provider: Google LLC (Google Analytics 4); Purpose: to distinguish visitors by a randomly generated identifier in order to produce aggregate visit statistics; Duration: 2 years; Type: first-party cookie set by Google Analytics on the fidkeep.com domain; the collected data is sent to Google.
• _ga_XXXXXXXXXX — Provider: Google LLC (Google Analytics 4); Purpose: to maintain the state of a visit session and measure sessions; Duration: 2 years; Type: first-party cookie set by Google Analytics on the fidkeep.com domain; the collected data is sent to Google. In the cookie name, XXXXXXXXXX stands for the site's Google Analytics measurement ID.

Google Analytics 4 does not log or store IP addresses. Analytics data is kept for 14 months. Google Analytics 4 collects information such as page views, visit duration, traffic source, device and browser type and approximate location (country/city level).

On auth.fidkeep.com and the fidkeep.com subdomains where the application runs, only strictly necessary cookies and local storage for interface preferences are used:

• Session cookie — Provider: Fidkeep; Purpose: to recognise and maintain your session after you sign in; Duration: for the sign-in session, ending when you sign out or the session expires; Type: first party, HttpOnly and Secure cookie.
• Security (CSRF) cookie — Provider: Fidkeep; Purpose: to prevent forged requests being sent on your behalf (cross-site request forgery); Duration: for the sign-in session; Type: first party, HttpOnly and Secure cookie.
• Interface preferences — Provider: Fidkeep; Purpose: to remember interface preferences such as theme and last used sign-in method; Duration: until you clear your browser data or change the preference; Type: first party, browser local storage (localStorage).

HttpOnly cookies cannot be read by scripts on the page; Secure cookies are sent only over encrypted (HTTPS) connections. If you block these cookies, you cannot sign in to the application.

Subscription payments are taken through the secure payment form of İyzi Ödeme ve Elektronik Para Hizmetleri A.Ş. ("iyzico"). This form may set third-party cookies for iyzico's own purposes (such as payment security and fraud prevention). These cookies are governed by iyzico's own policies, and iyzico is an independent controller in this respect. Fidkeep does not control or access these cookies.

• Strictly necessary cookies: in the application, session and security cookies are necessary for the performance of the contract with you (Art. 5(2)(c) KVKK). On the website, storing your cookie preference and the Cloudflare security cookie rely on our legitimate interest in keeping the site secure and respecting your choice (Art. 5(2)(f) KVKK). Explicit consent is not requested for strictly necessary cookies.
• Analytics cookies: rely solely on your explicit consent (Art. 5(1) KVKK). Refusing consent does not restrict your use of the website in any way.

• On your first visit to the website a cookie banner is shown. The banner offers accepting and rejecting analytics cookies on the same layer and with equal ease.
• The Google Analytics 4 script is not loaded until you accept analytics cookies in the cookie banner; no analytics cookie is therefore set before your consent.
• Closing the banner without making a choice or continuing to use the site does not count as consent; in that case analytics cookies are not loaded.
• Your choice is stored in your browser under the key fidkeep_cookie_consent for 12 months. When this period expires, you are asked again.
• You can withdraw or change your consent at any time via the "Cookie preferences" link at the bottom of the website. When you withdraw consent, Google Analytics 4 is no longer loaded; you can delete analytics cookies already set through your browser settings.
• Your choice is specific to the browser and device. If you use a different browser or device, or clear your browser data, you are asked again.

You can view, delete or block cookies in your browser settings. Menu names may vary by browser version:

• Google Chrome: set cookie preferences under Settings > Privacy and security > Third-party cookies, and delete existing cookies via Settings > Privacy and security > Delete browsing data.
• Safari (macOS): block all cookies under Safari > Settings > Privacy, and delete data for specific sites with Manage Website Data. On iPhone and iPad, use Settings > Safari > Advanced > Website Data.
• Mozilla Firefox: clear or manage data under Settings > Privacy & Security > Cookies and Site Data.
• Microsoft Edge: set your preferences under Settings > Cookies and site permissions > Manage and delete cookies and site data.

To prevent Google Analytics from collecting data on all websites, you can also use Google's Google Analytics opt-out browser add-on.

If you block strictly necessary cookies, some security functions of the website may not work and you may not be able to sign in to the application.

Data collected through Google Analytics 4 is transferred to Google LLC if you have given explicit consent and may be processed in the United States or on Google's global infrastructure. Data associated with the Cloudflare security cookie is processed on Cloudflare's global network.

The United States is not a country covered by an adequacy decision under KVKK. These transfers rely on the standard contracts announced by the Personal Data Protection Board under Article 9 KVKK as amended by Law No. 7499 and notified to the Personal Data Protection Authority within five business days of signature; where that is not possible, they rely, on an occasional basis, on the exceptions in Article 9(6). The full list of our service providers is on the Subprocessors page.

You can exercise your rights under Article 11 KVKK regarding personal data processed through cookies through the Data Subject Request Form or by writing to [email protected]. Request methods and time limits are explained in the Privacy Policy.

We update this policy when the cookies we use change. The current version is published on this page with its effective date. If a new consent-based cookie category is added, those cookies are used only after your consent is obtained again.

For questions about cookies, write to [email protected]; formal notices can be sent to our KEP address [email protected].