Draft — Not for Publication
This document is an unpublished internal draft prepared for SKYSCRAPERS INFO LIMITED. It has not been verified against the live cookie inventory, installed scripts, third-party embeds, current Tilda configurations, or any active consent mechanism. Do not publish, link, or rely on this version until each "Pending verification" item below has been confirmed by the operator through DevTools inspection and the Tilda project dashboard.
This page explains how SKYSCRAPERS INFO LIMITED, the operator of skyscrapersinfo.ltd, uses cookies and similar storage and tracking technologies on the website https://skyscrapersinfo.ltd. It should be read together with our Privacy Policy, which governs the personal data we process and the lawful basis on which we rely.
This Cookie Policy (the "Policy") is published by SKYSCRAPERS INFO LIMITED ("the Company", "we", "us", "our"), a company incorporated in the Hong Kong Special Administrative Region, in its capacity as the data user and operator of the website at https://skyscrapersinfo.ltd (the "Website"), which presents international architectural media, skyscraper data and related commercial information.
This Policy explains what cookies and similar storage technologies are, how they are used on the Website, what categories they fall into, and the choices you have in relation to them. It is intended to operate alongside, and is to be read together with, our Privacy Policy, which addresses the personal-data processing operations, lawful bases, retention considerations and contact details that apply to information collected by or on behalf of the Company. Where the two documents address the same processing in different terms, the inconsistency will be reconciled by updating both documents; neither document should be read as automatically overriding the other on points where their wording differs while any such inconsistency remains unreconciled.
This version of the Policy is a working draft. It will be moved to an effective, published state only after the items marked Pending verification throughout this document have been confirmed by the operator.
A "cookie" is a small text file placed on your device (computer, phone, tablet) by a website. Cookies typically contain the name of the domain that set the cookie, a value, and an expiry period. They are used to distinguish you from other visitors, remember preferences, enable certain site features, and — in some cases — to deliver or measure content. Cookies may be set by the website you are visiting ("first-party cookies") or by a third party whose code, image, library, embed or pixel is present on the page ("third-party cookies").
In addition to cookies, this Policy also covers comparable storage and tracking technologies. These include:
Throughout this Policy, references to "cookies" should be read as covering all of the above technologies, unless a specific technology is named. Some of these technologies store data on your device; others never write data to your device but still allow a third party to observe that a request came from it. The Privacy Policy governs what happens to that information once it is sent.
On the Website, cookies and similar technologies are used for purposes that fall into the categories set out in Section 04. We will only deploy technologies within a category that is genuinely required for the corresponding purpose; broader, unconsented scope creep is not our practice.
Concretely, the purposes the Company intends to support include:
The specific tools, providers and cookie identifiers actually deployed on this Website have not yet been audited by an authorised reviewer and are recorded in the inventory table at Section 05, which remains unpopulated pending verification.
Until verification is complete, the Company does not claim to engage in any of the following on this Website, regardless of any feature a connected platform may technically support:
If, after verification, any such operation is found to be in place, the relevant consent mechanism must be activated or the operation must be disabled before this Policy is published.
Where applicable, the Company groups cookies and similar technologies into four categories. Once a verified consent layer is in place, the Analytics, Advertising / marketing and Functional / custom categories will be off by default and will only activate after a clear, affirmative opt-in from the visitor. Until that consent layer is installed and verified, the Company does not assert that any of those categories is currently blocked or gated.
Required for the Website to operate (load balancing, request routing, basic session state, fraud and abuse prevention). These cannot be switched off through the consent layer, because disabling them would prevent the site from functioning. Their exemption from prior consent is asserted only for genuinely required purposes.
Aggregated, statistical measurement of how the Website is used. Analytics cookies are treated as non-strictly-necessary in jurisdictions that require prior consent, and are off by default unless the exemption is established.
Cookies and pixels set by advertising networks, advertising partners or attribution services for audience reach, frequency capping, conversion measurement, retargeting or similar purposes. These are non-strictly-necessary and off by default.
Cookies that remember non-essential user preferences (for example, interface state, location units). These improve convenience but are not essential to core delivery. Off by default.
The Company does not classify a cookie as "strictly necessary" merely because the underlying platform or vendor supports it.
This section records the verified cookie inventory. Verification requires inspecting the live site with browser developer tools and the Tilda project dashboard (cookies, custom code, third-party integrations, HEAD/BODY code and active consent status). Until that audit is completed, this table is intentionally empty. No cookie name, provider, purpose, category, duration or retention claim is published here that has not been independently verified.
| Name | Provider | Purpose | Category | Duration |
|---|---|---|---|---|
| Awaiting verification — no rows populated yet. | ||||
A separate internal cookie inventory (with the extended columns above) should be maintained by the operator outside this public document and refreshed after each material change to the site, platform, vendor list, or jurisdictional footprint.
The Website is built and hosted on the Tilda publishing platform. Tilda provides built-in mechanisms that the operator can enable or disable inside the project settings.
Disabling optional analytics cookies via the visitor consent layer, or leaving the choice unsettled, does not on its own stop platform-level visitor counting at the Tilda level. Tilda's internal statistics may continue to register visits without setting an analytics cookie, using technical mechanisms that the platform treats separately from the visitor-side analytics category. Where simplified statistics mode is active, Tilda documents that page-view counting is performed through a cookieless method. The Company has not yet verified which mode is currently active on this Website. The Privacy Policy addresses the lawful basis for any resulting processing.
The Website may rely on infrastructure-layer services for traffic delivery, security and abuse prevention. Examples of services commonly used at this layer include content delivery networks (CDNs), reverse proxies, and bot-management vendors. Whether any such service is actually deployed on this Website, and the identity of that service, must be confirmed by inspecting DNS, the network panel and the relevant dashboard.
Some infrastructure cookies (such as those used for load balancing, DDoS mitigation or human verification challenges) may be asserted as strictly necessary because they are required for the service to function safely. That assertion is only made on a case-by-case basis where the underlying mechanism genuinely meets that threshold. Where any such cookie collects or is associated with personal data, the retention and transfer practices are described in the Privacy Policy, not here.
From time to time the Website may embed third-party content such as videos, maps, social-media posts or sharing widgets. Loading such content typically causes the third-party provider to receive information about your visit, including your IP address, the page you came from, and a unique identifier set by the provider.
A third-party cookie is, by definition, set by a provider other than the Company. Depending on what the provider actually does with the information it receives, it may act in one of several roles:
The role that applies to a given provider depends on that provider's actual arrangement with the Company. Until each provider has been reviewed, no party should be assumed to be a processor for the Company's purposes merely because its code is present on a page. Where the provider is an independent controller or a joint controller, its own privacy practices govern what it does with the information; that does not, however, release SKYSCRAPERS INFO LIMITED from its own data-protection obligations, including the duty to select and monitor the providers it works with and to be transparent to visitors about their involvement. A list of providers and the role the Company considers applicable to each is maintained in Section 05 once the inventory is verified.
Where the Company processes cookie-based or comparable tracking technologies on the basis of consent, the only authoritative source for what is permitted to run in a visitor's browser will be the consent mechanism once one is installed and verified. Until that mechanism is in place, the Company does not assert that any visitor's preferences are being recorded or honoured by a Website-side control.
Once implemented, the consent layer must meet the following requirements:
The Company does not assert that any of the behaviours listed above is presently working on this Website. They will only be claimed as a current fact once a consent mechanism is installed, configured and tested, and that testing has been independently verified by the operator.
In addition to any consent mechanism the Website provides, you can manage cookies and certain privacy signals through your browser. Common browsers offer several distinct controls, which work in different ways and have different legal effects:
Browser-level controls and signals may communicate preferences to websites to some extent (GPC, in particular, is intended to be transmitted to servers), but none of them is, on its own, a substitute for the Website's own consent mechanism where the law requires one. A browser setting that signals preference does not necessarily satisfy every applicable consent obligation; the legal effect of any signal depends on the visitor's location and on the applicable framework. The Company's Website-side consent mechanism, once installed and verified, will be the authoritative source for what runs in your browser under a consent-based regime.
Deleting cookies is helpful, but a number of the technologies described in Section 02 persist beyond a single cookie, including local storage, device fingerprinting, and server-side logs held by third parties. Clearing your browser does not, by itself, instruct third parties to delete server-side records.
The principles, lawful bases, retention considerations, security measures and cross-border transfer considerations that apply to personal data processed through or in connection with the Website are addressed in the Privacy Policy. The Privacy Policy is itself a working draft and should be treated as authoritative only to the extent that the items it describes have been verified by the operator. In particular, the Privacy Policy is intended to address:
The legal framework that applies to a given visitor depends on their location and on the processing in question. The Company is incorporated in Hong Kong SAR and processes personal data in accordance with the Personal Data (Privacy) Ordinance (Cap. 486) ("PDPO"). Where the Company offers goods or services to, or monitors the behaviour of, visitors located in the European Economic Area, the General Data Protection Regulation (Regulation (EU) 2016/679) and the ePrivacy Directive (Directive 2002/58/EC, as transposed) may also apply. Where the Company offers goods or services to, or monitors the behaviour of, visitors located in the United Kingdom, the UK General Data Protection Regulation and the Privacy and Electronic Communications (EC Directive) Regulations 2003 ("PECR"), as amended by the Data (Use and Access) Act 2025, may also apply. Worldwide accessibility of the Website does not, on its own, bring a visitor within the territorial scope of any particular framework. Rights, lawful bases, consent thresholds and the consent exemptions applicable to "strictly necessary" cookies vary by jurisdiction; the operative framework for any given situation is determined by the visitor's location and the processing in question, not by this document alone.
Visitors should note that the Privacy Policy, like this Cookie Policy, is a working document. Several of the items above are still under review and may be presented as placeholders until verified. Where the Privacy Policy and this Cookie Policy address overlapping processing, the two should be read together and any inconsistency reconciled through an update to both documents.
Cookie lifetimes and local-storage expiry are recorded in the inventory table at Section 05. Server-side retention, where it occurs, is addressed in the Privacy Policy. Cookies and any server-side records derived from them are tracked separately, so a short cookie expiry does not by itself shorten the retention of any corresponding server-side log, and vice versa.
The Company will update this Policy from time to time to reflect changes to the Website, the technologies used on it, the providers we work with, or the legal framework that applies to us. Each effective version will be identified by its effective date. Substantive changes will be flagged through the standard notice channels listed in the Privacy Policy.
Questions, requests or complaints relating to cookies, similar tracking technologies, or the personal data we process on the basis of consent, should be directed to the contact published in the Privacy Policy — under the heading used there for privacy enquiries — and not via forms or inboxes advertised for unrelated purposes (such as commercial enquiries or press requests).