Cookie policy

1. What is set

1.1 Nothing. No first-party cookie, no third-party cookie, no localStorage key, no sessionStorage key, no IndexedDB database.

1.2 This was measured, not assumed. Every route was loaded in a real browser, scrolled end to end, and inspected: document.cookie is the empty string, Object.keys(localStorage) and Object.keys(sessionStorage) are both empty arrays, and the list of origins the browser contacted contains only this site.

1.3 The site did once write one key, puente-theme, to remember a light or dark preference. The theme switch was removed and so was the key. Nothing replaced it.

2. How page views are counted

2.1 We use Vercel Web Analytics to count page views. We use it specifically because of how it identifies a visit: it does not.

2.2 In Vercel's own words, it works "without using any third-party cookies, instead end users are identified by a hash created from the incoming request", and "the lifespan of a visitor session is not stored permanently, it is automatically discarded after 24 hours". The hash is computed server-side and is never written to your device.

2.3 What is recorded with a page view: a timestamp, the URL and its route pattern, the referrer, filtered query parameters, an approximate location derived from the request at country, region and city level, your operating system, your browser, and your device type. None of it is tied to an identifier that persists, and none of it can be used to follow you to another site.

2.4 The script is served from this site's own origin, at /_vercel/insights/script.js. Loading a page of this site does not cause your browser to contact any other domain.

2.5 There is no advertising network, no tag manager, no pixel, no session recorder, no heatmap, no A/B testing tool, no chat widget and no embedded third-party content anywhere on this site.

3. The one thing held about you, briefly

3.1 When you submit the contact form, the server sees your IP address and holds it in memory, with the times you submitted, so it can enforce a limit of five submissions an hour. It is never written to disk, never sent anywhere, and is discarded within the hour or when the server instance recycles, whichever is sooner.

3.2 This is not a cookie and nothing is stored on your device. It is described here because it is the only thing about a visitor that is retained at all, and leaving it out of a page like this one would be misleading. The privacy policy covers it in full.

4. Why there is no consent banner

4.1 The consent requirement in Article 5(3) of the ePrivacy Directive, and in the national laws implementing it, is triggered by storing information on, or gaining access to information already stored on, a user's device. This site does neither.

4.2 Because nothing is stored on or read from your device, there is nothing for you to consent to, and a banner asking you to consent to nothing would be theatre. We would rather not put one in front of you.

4.3 This is a statement about a technical fact that we have measured. Whether it is sufficient in your jurisdiction is a legal question, and this page has not yet been reviewed by a lawyer.

5. What would change this

5.1 If we ever added a tool that stores an identifier on your device, this page would change before that tool shipped, not after. Concretely, that means anything in this category: Google Analytics or any product that writes a client identifier; an advertising or conversion pixel; a chat widget that keeps a session; a heatmap or session-recording tool; or an A/B testing tool that persists a variant assignment.

5.2 If we added any of those, we would need a consent mechanism that blocks the tool until you agree, records what you agreed to, and lets you withdraw it as easily as you gave it. We would list each cookie here with its name, purpose and lifetime.

5.3 We have no plan to add any of them. If that changes, the "last updated" date at the top of this page changes with it, and that date is generated from the change itself rather than typed in, so it cannot quietly stay the same.

6. Blocking it anyway

6.1 If you block scripts, the page-view count simply does not happen. Nothing else on the site depends on it, and the site works normally without it.

6.2 Browser-level Do Not Track and Global Privacy Control signals are not currently read, because there is no per-visitor tracking to switch off.

7. Questions

7.1 info@puenteglobal.com. If you think something on this page is wrong, tell us and we will check it and correct it. The privacy policy covers everything else we do with data, and the terms of use cover using the site.