Legal Center
Status: Draft v0.9 — 11 August 2026 — legal and operational review required before publication. Current provider: Heritage Timepieces AB, org. no. 559491-1157, VAT SE559491115701, Kungsgatan 2C, 223 50 Lund, Sweden. Entity notice: Klocktech AB is under registration and is not the current contracting party. Registration alone does not transfer an agreement. Contacts: legal@heritagetp.com (legal/privacy) · info@heritagetp.com (general).
The actual Klocktech production website and application must be scanned after deployment and after each material vendor or tag change. This draft must not be published as a factual cookie inventory until that scan is complete. Until consent management and the inventory are verified, the safest launch configuration is to deploy only technologies strictly necessary for a service the user requests.
Cookies are small files stored on or read from a browser or device. Similar technologies include local storage, pixels, SDKs and identifiers. They can support authentication, security, preferences, measurement and advertising.
Strictly necessary technologies may be used where they are required to transmit a communication or provide a service expressly requested by the user. Non-essential analytics, preference or advertising technologies are blocked until the user gives valid consent.
Consent must be freely given, specific, informed and active. The interface must offer “Accept” and “Reject” with equal prominence, allow choices by purpose, use no pre-ticked boxes, treat silence as refusal, and provide an always-available way to withdraw as easily as consent was given. Refusal of non-essential cookies must not block account login or another requested service.
| Category | Purpose | Default state |
|---|---|---|
| Strictly necessary | security, load balancing, authentication, requested session and consent storage | active where genuinely necessary |
| Preferences | remember optional display, locale or usability choices | blocked until consent unless strictly necessary for a requested setting |
| Analytics | understand use, performance and errors beyond what is strictly necessary | blocked until consent |
| Marketing | attribution, retargeting, profiling or advertising | blocked until consent |
Calling a technology “necessary” does not make it exempt; its operation must actually be essential to the requested service.
Before publication, replace this section with a table generated from the live deployment containing, for every technology:
| Required field | Description |
|---|---|
| Name | exact cookie or storage key |
| Provider and domain | first or third party that sets or reads it |
| Purpose | clear, specific explanation |
| Category | necessary, preference, analytics or marketing |
| Data | information collected or accessed |
| Duration | session or exact expiry period |
| Third-party transfer | recipient, country and relevant privacy link |
| Legal basis | necessity or consent |
At the date of this draft, no factual production inventory has been approved. The launch owner must attach the scanner output, verify each vendor contract, and test that rejected categories remain blocked.
The final website must provide a persistent “Cookie settings” link or icon on every page. Users can change choices there. Browser controls may also delete or block storage, but blocking necessary storage can prevent login or requested functions.
Withdrawing consent stops future non-essential use. It does not automatically delete information already processed lawfully, although associated cookies should be removed where technically possible and related personal data remains subject to the Privacy Notice.
The inventory and date must be updated when a tag, domain, purpose, vendor or duration changes. Questions or withdrawal problems may be reported to legal@heritagetp.com.