Baharlar Vadisi

Baharlar Vadisi

Cookie Policy

Browser technologies, external connections and ways to manage your choices.

Updated: 22 September 2026 · Version 2026-09-22.1

1. What are cookies?

Cookies are small text files a website may store in your browser. They can maintain sessions, remember preferences or support measurement. Not every network request involves a cookie; an external service may still receive an IP address even without cookies.

2. Use in this version

The public presentation pages do not contain Google Analytics, Google Ads or Meta Pixel measurement/advertising scripts. No optional advertising or analytics cookie feature has been activated for these pages, so this version does not display an accept/reject panel for those cookies.

Language selection uses the /tr and /en addresses. When Supabase authentication is configured and an authorised operator signs in, sb-…-auth-token cookies and, where needed, chunked versions may maintain the session. They are not advertising trackers for public visitors. The library’s default maximum storage period is 400 days; access-token expiry, renewal and sign-out are separate. This period does not mean access remains valid for that entire time.

3. Maps and external websites

The location map loads styles and tiles from OpenFreeMap. Opening the map establishes a direct connection; the provider may receive your IP address and technical request details. The map does not request your device’s location. Its displayed area is approximate, not a cadastral or title boundary.

Following THE BARK, map-attribution or other external links brings you under the destination’s own privacy and cookie terms. THE BARK’s UTM labels identify Baharlar Vadisi as the referring site; your enquiry name, email and message are not added to that link.

4. Managing your choices

Your browser’s privacy settings let you inspect, delete and block cookies. Blocking session cookies may prevent authorised-user login. Deleting browser cookies does not erase an enquiry already submitted; a separate data request is needed.

If consent-requiring analytics or advertising technologies are introduced, a separate choice mechanism must precede their operation, with equally accessible rejection and later preference changes. Continuing to browse is not consent.