Cookie policy

No cookies on the public website

Reading the home page, the portfolio, an article, the section on Puerto Rico or the contact form stores nothing on your device: no cookies, no local storage, no fingerprint, no identifier of any kind.

This is not an oversight we intend to correct later. It is a deliberate property of the site, and this page exists to record it.

No third-party requests either

Cookies are usually the visible part of a larger problem: pages that quietly ask a dozen outside companies for fonts, maps, videos and scripts, each of which sees your address as it answers.

This site asks none. The typefaces are served from our own domain rather than from Google’s servers. The map of Puerto Rico is a vector drawing generated from our own data, not an embedded map from a mapping provider. The videos are files on our own servers, not embedded players. There is no advertising network, no social media widget and no chat box.

Audience measurement without cookies

We do use two measurement tools from our hosting provider: Vercel Web Analytics, which counts page views, and Vercel Speed Insights, which measures how quickly pages load.

Neither sets a cookie and neither stores a persistent identifier, so neither can follow you between visits or between websites. What we see is an aggregate count of how many people read a given page and how fast it loaded for them. What we cannot see is who you are.

The one cookie that exists on this domain

The firm administers the site’s content through a private panel at /admin. Signing in to that panel sets a session cookie, without which it would be impossible to stay signed in from one page to the next.

It is set only after a successful sign-in by one of the partners. Visiting the website never sets it, and reaching the sign-in page without signing in never sets it either. Being strictly necessary for a service explicitly requested by the person using it, it is exempt from the consent requirement.

Name

sb-<project>-auth-token

Type

First party, set by Supabase authentication

Purpose

Keeps a partner signed in to the private administration panel

When it is set

Only on a successful sign-in at /admin

Duration

Until sign-out, or until the session expires

Why there is no cookie banner

Consent is required for cookies and similar technologies that are not strictly necessary. On this site there are none, so there is nothing to ask you about.

A banner would in fact make things worse: to remember that you had dismissed it, it would have to store something on your device, and it would become the only tracking-adjacent object on a site that has managed to do without one.

Controlling cookies yourself

Every browser lets you see, block and delete cookies from its settings, usually under Privacy. Blocking everything from this domain will not affect your reading of the public site in any way, since there is nothing to block. It will only prevent a partner from signing in to the administration panel.