Legal
Cookie Policy
This page explains what cookies and similar browser storage this website actually uses today — not a generic list of possibilities. It is based on a direct review of the website's own code, not assumptions about what a website like this typically uses.
2. What Copenhagen Bureau currently uses
Based on a direct review of this website's code, it does not set any cookies of its own. The only browser storage in use is described below: one first-party preference record, the technology that keeps you signed in to Core (Copenhagen Bureau's client workspace) once you log in, and the technology that comes with the Cal.com booking calendar once you choose to open it. Copenhagen Bureau does not use any analytics, advertising or tracking technology on the public website or within Core.
3. Necessary technologies
Necessary technologies are strictly required for the website to function, or for a service you have explicitly requested. They do not require consent and cannot be switched off.
| Name | Provider | Purpose | Type | Duration | Category |
|---|---|---|---|---|---|
| cbCookieConsent | Copenhagen Bureau (this website) | Remembers your cookie-preference choice so we don't ask again unnecessarily | localStorage | Until you clear your browser storage, or until your preference is updated | Necessary |
| Cal.com scheduling technology | Cal.com (app.cal.com) | Powers the embedded booking calendar you open when you choose to schedule a meeting | Cookies / browser storage set within Cal.com's own embedded page | Set and controlled by Cal.com, not by this website — [verify exact names/durations on the production domain] | Necessary — loads only after you actively request it |
| Supabase Auth session | Supabase (used by Core, Copenhagen Bureau's client workspace) | Authenticates you and keeps you signed in to Core once you log in, so you don't have to re-enter your password on every page | localStorage, or sessionStorage if you choose not to stay signed in (see "cb-keep-signed-in" below) | Until you sign out, clear your browser storage, or — if you chose not to stay signed in — close your browser | Necessary — only present once you sign in to Core; not required for the public website |
| cb-keep-signed-in | Copenhagen Bureau (this website) | Remembers whether you chose "Keep me signed in" at your last Core sign-in, so later visits use the same session behaviour | localStorage | Until you clear your browser storage, or until you sign in again with a different choice | Necessary — only present once you have signed in to Core at least once |
Cal.com's own script and calendar interface are never loaded until you actively click to schedule a meeting — nothing is loaded in advance "just in case." Because it only ever runs at your own request, it is treated as necessary rather than optional. The Supabase Auth session and "cb-keep-signed-in" are only ever present if you sign in to Core — they do not appear from browsing the public website alone, and neither requires your consent: both are technically necessary to provide the sign-in you've explicitly asked for.
4. Preference technologies
Copenhagen Bureau does not currently use any optional preference technology beyond the necessary technology described above. There is currently no language or display-preference selector on this website.
5. Analytics technologies
Copenhagen Bureau does not currently use any analytics or measurement technology on this website. If that changes in future, this page and the cookie-preferences panel will be updated before any such technology is activated.
6. Marketing technologies
Copenhagen Bureau does not currently use any advertising, retargeting or cross-site marketing technology on this website.
7. Third-party services
Formspree (form processing) and Google Workspace / Gmail (correspondence) do not set any cookies or browser storage on this website — form submissions are sent as a one-off request, not through cookie-based tracking. WhatsApp is only ever opened as an outbound link that you choose to follow; once opened, WhatsApp/Meta apply their own cookie and privacy practices outside this website, which we do not control.
Stripe, Resend and Supabase's own server-side infrastructure do not set any additional cookies or browser storage on this website beyond what is already listed in Necessary technologies above. If you pay an invoice through Core, you are sent to a payment page hosted directly by Stripe to complete it — that page is Stripe's own, governed by Stripe's own cookie practices, not this website's.
8. How to manage consent
You can review or change your cookie preferences at any time using "Cookie Preferences" in the footer of any page. This opens a panel showing every category described above, lets you accept all, reject non-essential technology, or save a specific choice.
9. How to withdraw consent
Because everything currently in use is necessary technology, there is nothing optional to withdraw consent from today. If an optional category is introduced in future, the same "Cookie Preferences" control will let you withdraw consent as easily as you gave it.
10. Changes to this policy
We will update this page whenever the technology described in it changes — for example, if analytics or marketing technology is ever introduced. The "Last updated" date at the top reflects the most recent revision.