Cookie policy

Necessary technical cookies

This policy applies to the klynk.page website, the KLYNK Page private account area and pages published by users. The controller for the service's own cookies and measurements is KLYNK SRL, with registered office at Via Torquato Taramelli 60, 20124 Milano, partita IVA 14461420961. Questions can be sent to privacy@klynk.it.

A cookie is a small piece of information that a website stores in the browser and receives with later requests. KLYNK Page uses technical cookies to create, maintain and renew the session of users who access the private account area and to complete the authentication flow securely. These cookies are necessary to provide a function requested by the user and are not used for advertising or profiling; consent is therefore not required.

Authentication cookies have a technical name based on the Supabase project, in the format sb-<project-reference>-auth-token, and may be split by the browser into several parts. The sign-in flow may also use temporary cookies ending in code-verifier. The application settings use the / path, the SameSite=Lax attribute and a maximum technical lifetime of 400 days; cookies may be renewed while a session remains valid and are removed when the user signs out.

Simply visiting the website or a published page, without an account session or the external content described below, does not require KLYNK to set cookies in order to measure the visitor's behaviour.

Internal measurement of page events

KLYNK measures the operation and use of pages by recording events in its own systems, such as opening a page, clicking a link or booking action, starting and submitting a form, creating a contact request, and the outcome of the related notification. This measurement uses requests sent directly to KLYNK's systems and does not use analytics cookies, local storage or advertising identifiers.

The event log does not store the IP address, browser string or a device identifier. The server may read the IP address temporarily to limit excessive requests and protect the service, without writing it to the event log. Navigation events are not used to recognise the visitor or build a profile about them.

Operational events created after a form is submitted may be linked, through an internal identifier, to the contact request needed to verify its storage and delivery. This information is not used for advertising or profiling and follows the retention rules and roles described in the applicable privacy notices.

No profiling or third-party trackers

KLYNK does not integrate advertising or profiling tools such as Meta Pixel, Google Analytics, Google Ads, PostHog or similar services into its own website or published pages. References to possible pixels in product-planning documents do not correspond to features active in the code on the date of this policy.

A page may, however, include a calendar embedded by its owner and supplied by Calendly or Cal.com. In that case, the browser loads scripts and a frame directly from the external provider, which receives ordinary technical connection data. Tests carried out on 25 September 2026 on the current embeds, before any visitor interaction, found only third-party cookies used for security and bot protection, session continuity, CSRF protection and consent-preference management; no analytics, advertising or profiling cookies were set. KLYNK does not use this external content for its own advertising purposes or to profile visitors.

Map blocks use a first-party visual preview drawn by KLYNK Page. They do not load map tiles, iframes, scripts or cookies from a map provider. A map service receives the address only after a visitor chooses the external directions link.

Ordinary links to third-party websites, social networks or services do not load the external service until the visitor chooses to open them. From that point, the terms and notices of the relevant third party apply.

How to manage preferences

Because KLYNK does not use its own optional cookies, it does not currently display a preference panel for KLYNK cookies. Users can still view, delete or block cookies in their browser settings. Blocking technical authentication cookies prevents or interrupts access to the private account area, while those cookies are not needed to view an ordinary published page.

The current external embeds do not set optional analytics, advertising or profiling cookies before interaction, so KLYNK does not display a preference panel for them. They do use the technical third-party cookies described above. Blocking those cookies or the providers' scripts in the browser may prevent the embedded calendar from working; the external booking link remains available as an alternative.

If KLYNK introduces analytics or advertising cookies or other optional technologies, it will update this policy and, before activating them where required, provide a way to accept or reject them and change the choice. Preferences already expressed will not be treated as consent to new tools.