Cookie & Similar Technologies Policy
This Policy explains when the Beyoğlu Professional website may store information on a user's device or read information already stored there, which technologies are necessary for the requested service, which technologies require a separate choice and how those choices must be respected.
Necessary technology and optional tracking are not placed in the same legal category.
A technology that is strictly necessary to provide a service requested by the user may operate without optional-cookie consent. Where consent is required for storage or access on a user's device, the technology should not be activated before that consent is obtained.
1 · Who operates this website?
Cookie decisions are part of the same controller framework described in our Privacy Policy.
Service brand: Beyoğlu Professional — PPWR-EPR Compliance Services.
Current website operator: THEMİR MEDYA İNŞAAT İTHALAT İHRACAT SANAYİ TİCARET ANONİM ŞİRKETİ , Tatlısu Mah. Aziz Blv. Çağrı Sitesi B Blok No:48, İç Kapı No:42, 34774 Ümraniye, İstanbul, Türkiye.
For wider personal-data processing information, see our Privacy Policy.
2 · What we mean by cookies
The rule applies to more than files literally called “cookies”.
This Policy uses “cookies and similar technologies” to include cookies, local storage, session storage, pixels, software development kit functionality and comparable technologies capable of storing information on or accessing information from a user's terminal equipment.
Strictly necessary
Security, session continuity, authentication, load delivery, consent-state storage and functions necessary to provide a service explicitly requested by the user.
Preferences
Optional choices such as interface or convenience settings that are not technically required for the requested service.
Analytics
Technologies used to measure traffic, interaction, performance and usage where those technologies are not strictly necessary.
Marketing / attribution
Advertising, remarketing, campaign measurement or cross-site attribution technologies, if such tools are ever enabled.
3 · Consent standard
Consent is not valid merely because a banner says “by continuing you agree”.
Where consent is required, the user must receive meaningful information about the purpose before the relevant optional technology is activated.
A user must be able to refuse non-essential technologies without being forced to accept them simply to read public PPWR information that does not technically require them.
Consent must be capable of being withdrawn or changed. Withdrawal must not affect the lawfulness of processing that occurred while valid consent was in force.
If an analytics, advertising or other consent-dependent script executes before consent, wording in this Policy does not cure that implementation. The production consent manager must enforce the actual choice.
4 · Current website infrastructure
The current public website uses Tilda infrastructure.
Tilda and infrastructure providers used through Tilda may process technical data required for delivery, security, project storage and backup.
Tilda's current published Data Processing Agreement identifies Hetzner Online GmbH, G-Core Labs SA and Google Cloud EMEA Limited among its processors.
A hosting or security technology does not become a “marketing cookie” simply because a third party provides it. Its actual purpose and technical necessity must be assessed.
Conversely, a third-party analytics tool does not become “strictly necessary” merely because it is useful to Beyoğlu.
5 · Live cookie inventory
We will not invent a static cookie list that no longer matches the live website.
The exact list of optional technologies can change as the production website and platform change.
The production consent-preference interface should therefore identify the actual technology or provider, category, purpose and relevant duration used at that time.
This Policy defines the legal and operational principles. The live consent interface is intended to provide the current granular inventory.
6 · Duration
Session technologies and persistent technologies are not retained for the same period.
Some technologies expire when the browser session ends. Others persist for a defined period so that authentication, consent status or an optional permitted function can continue across visits.
Where optional persistent technologies are enabled, their individual duration should be visible through the live consent inventory.
Consent should not be treated as perpetual merely because the underlying cookie has a long technical lifetime.
7 · How to change your choice
Withdrawal should be as real as acceptance.
Where optional technologies are in use, users should be able to reopen the cookie-preference interface and change the categories they previously accepted.
Users can also remove stored data using their browser controls. Blocking a strictly necessary technology can prevent authentication, account or security functions from operating.
8 · Do Not Track and browser signals
Browser signals do not replace the legal consent mechanism unless the applicable legal framework gives them that effect.
Browsers and devices can expose privacy preference signals. We evaluate such mechanisms against the technical implementation and law applicable to the service.
The website should not state that a signal is honoured unless it is actually implemented and technically enforced.
9 · Changes
New analytics or advertising tools require a new privacy assessment, not only a new script tag.
Material changes to cookie categories, providers or purposes will be reflected in the consent configuration and, where appropriate, this Policy.
Cookie or privacy question?
Contact Beyoğlu Professional if you need information about a particular technology or consent record.
Contact us