This page explains what cookies are, what our website sets when you visit it, and how you can control them. The short version is that we do not use advertising, analytics or tracking cookies, so there is very little to tell you. The rest of this page tells you the little there is, honestly.
1. What this policy covers
This Cookie Policy covers our website at https://blugency.co, which we call the Site, and our product application at https://app.blugency.co, which we call the Application.
It sits alongside our Privacy Policy, which covers everything else we do with personal information: what we collect, why, who we share it with, how long we keep it, and the rights you can use. If you want the full picture, read that page. If you want to know what is stored on your device, you are in the right place.
The Application has accounts, uploads and payments, and it runs on separate infrastructure from the Site. It does not have a separate set of legal pages. This page and the rest of our published legal set cover both, so what you read here is the answer for the Application as well as for the Site. Sections 4 to 7 describe what is set on the Site, because that is where you arrive without an account. A signed-in account area also has to set what it needs in order to keep you logged in and keep your session secure, and the commitment in section 7 applies there in exactly the same way: before anything that is not strictly necessary runs in the Application, it gets named on this page first.
This page describes what we do. It is not legal advice and it is not a substitute for advice from a professional you engage yourself. Our Legal Disclaimer sets out that position, and our Terms of Service covers your use of the Site and the Application.
2. Definitions
Blugency, we, us and our mean Blugency LLC, a New Mexico limited liability company.
Site means our website at https://blugency.co.
Application means our product application at https://app.blugency.co, which this policy also covers.
Personal Information means information that identifies you or that can reasonably be linked to you. Our Privacy Policy defines the term in full and uses it in the same sense.
Cookies means small files that a website asks your browser to store on your device. In this policy we use the word to cover similar technologies as well, including local storage, session storage, and small pieces of code embedded in a page, because from your point of view they all do the same kind of thing.
Strictly Necessary Cookies means Cookies that are needed for the Site to load, stay available and stay secure, and without which parts of the Site do not work.
Booking Widget means the Cal.com scheduling widget embedded on the Site, which you use to book a meeting with us.
3. What cookies and similar technologies are
A cookie is a small text file. When you visit a website, the site can ask your browser to store one, and your browser can send it back the next time you visit. Cookies are used for a wide range of things: keeping a website working across page loads, remembering a setting, protecting a form from automated abuse, counting visitors, and, on many websites, following people across the internet to advertise to them.
A few distinctions matter when you read any cookie page, including this one.
First party and third party. A first-party cookie is set by the website you are visiting. A third-party cookie is set by a different company whose content is embedded in the page. Third-party cookies are the ones most often used for advertising and cross-site tracking.
Session and persistent. A session cookie is deleted when you close your browser. A persistent cookie stays until it expires or you delete it.
Strictly necessary and everything else. Some Cookies are needed for a website to function at all. Everything else, including analytics and advertising, is optional, and asking permission before setting it is the standard we hold ourselves to.
Similar technologies. Local storage and session storage hold data in your browser in a similar way. Pixels are tiny images or scripts loaded from another company that report back that you visited a page. We treat all of these the same way we treat Cookies.
4. What we do not use
This section exists because most cookie policies describe tracking that is present, and ours has to describe tracking that is absent.
Today, on the Site:
- There is no analytics tool of any kind. No Google Analytics, no product analytics, no session recording, nothing that measures your behavior for statistics.
- There are no advertising or marketing trackers. No Meta pixel, no advertising network tags, no retargeting, no conversion pixels.
- We set no advertising cookies and no marketing cookies.
- Nothing we have installed on the Site tracks you across other websites.
- We do not build a profile of you from your visit, and we do not use Cookies to make decisions about you.
- We do not use Cookies or similar technologies to collect sensitive information such as government identification numbers or financial account numbers, and nothing collected on the Site is fed into an advertising, enrichment or profiling tool.
- We do not sell or share what Cookies collect on the Site, in the sense those words carry under state privacy law. Our Privacy Policy explains that in full.
The newsletter signup in the footer of the Site sets nothing on your device. It runs on Resend Audiences, which is part of the email service we already use to deliver your contact form messages to us, so it adds no new company to the list on our Subprocessors page. It uses a confirmed opt-in, meaning you click a link in an email before we send you anything, and this page, our Privacy Policy and our Subprocessors page are all updated before the signup is switched on rather than after.
One scoping point, because an accurate statement is worth more than an absolute one. The Booking Widget described in section 6 runs inside a frame that Cal.com controls. We put no advertising or analytics technology inside it and we receive no tracking data from it, but what it sets in its own frame is Cal.com's decision rather than ours.
5. What is set on our website today
What remains is a small set of strictly necessary technology from the providers that host, protect and power the Site, plus whatever Cal.com sets inside its own embedded frame. Each of these providers may set a Cookie or use similar browser storage in the course of doing that work. We describe them by category rather than by name, for the reason given in section 5.1.
| Category | Who sets it | What it is for | What happens if you block it |
|---|---|---|---|
| Hosting and content delivery | Vercel, our hosting and content delivery provider | Serving pages to you, routing requests correctly, and keeping the Site available and secure | Pages may fail to load or may load incorrectly. |
| Bot protection | Cloudflare, through the Turnstile check that runs invisibly on our contact form | Telling a real person apart from an automated script, so the form cannot be abused by bots | The contact form may refuse to submit. |
| The Booking Widget | Cal.com, inside its own embedded frame, under its own policies rather than ours | Running the scheduling widget so you can choose a time and book a meeting with us | The widget may not load or may not complete a booking. The rest of the Site is unaffected. |
5.1 Why this table has no cookie names or lifespans
The only honest way to publish a list of cookie names and expiry times is to read them out of a live browser session against the version of the Site that is actually deployed, and then keep that list current. We have not published names and lifespans here because that audit has to come first, and we would rather leave the detail out than print a list we cannot stand behind. When the audit is done, the names, the providers, the purposes and the lifespans go into this table.
5.2 Two things on our contact form that are not cookies
Our contact form uses a hidden field that a real person never sees, and a signed timestamp. Both are there to catch automated submissions, alongside the Cloudflare Turnstile check. Neither is advertising technology and neither is used to identify you or to follow you anywhere.
6. The booking widget on our website
When you book a meeting with us, you do it through a scheduling widget provided by Cal.com and embedded in a page on the Site. The widget runs inside its own frame.
Cal.com collects your name, your email address, and any answers you give to its booking questions. It can set its own Cookies and storage inside that frame. Making a booking also creates a Zoom meeting and a Google Calendar event, so that you and we both have the invitation.
What Cal.com sets, and how long it keeps it, is governed by Cal.com's own terms and privacy policy rather than by this page. Those documents are published by Cal.com on its own website, and we recommend reading them before you book if this matters to you. Our Privacy Policy explains what we do with a booking once it reaches us, and our Subprocessors page lists Cal.com, Zoom and Google alongside every other provider we use.
7. Why you do not see a cookie banner
We do not show a cookie banner, a consent pop-up or a preference center, and the reason is simple. A consent banner exists to ask your permission for technology that is not strictly necessary. We set none, so there is nothing to ask you about, and a banner would be theater.
The one thing that is not ours to answer for is the Booking Widget, which runs inside Cal.com's frame under Cal.com's policies. We are checking whether it loads only when you open the booking page or use it, and whether anything it sets goes beyond running the widget. If the answer is that it does, we will put a consent step in front of it rather than leave it running.
This is also a commitment, not only a description of today. Before we switch on any analytics tool, any advertising or marketing technology, any conversion pixel, or anything else that is not strictly necessary, we will do all of the following first:
- Update this page to name the technology, say what it collects, and say what it is for.
- Add the provider to our Subprocessors page.
- Put a consent mechanism in place so that you can accept or refuse the non-essential technology before it runs, rather than after.
- Honor browser opt-out preference signals against it from the first day it is live, as described in our Privacy Policy.
The consent mechanism we will use is a proper consent management approach rather than a notice bar that changes nothing. Specifically, the technology stays blocked until you accept it, so nothing loads and nothing is set while you are deciding. You choose by category rather than all at once, so you can accept one thing and refuse another. Refusing is exactly as easy as accepting, on the same screen, in the same number of clicks. Your choice stays visible and changeable afterwards, from a control that does not move or disappear. And we honor Global Privacy Control and other browser opt-out preference signals against anything the signal covers, without asking you to identify yourself, as section 8 and our Privacy Policy describe.
8. How to control cookies in your browser
Every current browser lets you see what a site has stored, delete it, and block new Cookies, either for all sites or for one site at a time. The controls live in your browser settings, usually under privacy, security, or site data. Chrome, Safari, Firefox and Edge each publish step-by-step instructions and keep them up to date, which is why we point you to their own help pages instead of reprinting steps here that would go stale.
You can also browse in a private or incognito window, which clears site data when you close it.
One warning, because it is the honest thing to say. If you block Strictly Necessary Cookies for this Site, parts of it will stop working. The contact form may fail the bot protection check and refuse to submit, and the Booking Widget may fail to load or fail to complete a booking. If that happens, email us at support@blugency.co and we will take it from there by email instead.
Some browsers and extensions send an opt-out preference signal, such as Global Privacy Control. We treat that signal as a valid opt-out request from the browser that sends it, and we honor it without asking you to identify yourself and without changing anything else about how the Site behaves for you. Because we do not sell or share Personal Information, there is nothing on the Site for the signal to switch off today, and we honor it anyway so that the protection is already working if that ever changes. Our Privacy Policy sets this out in full and explains how to make an access, correction or deletion request, which is a separate thing from a browser setting.
9. Changes to this policy
We will update this page whenever what we set on the Site changes, and we will update it before the change goes live rather than afterward.
Every version carries a version number and a date at the top. If a change is significant, for example the introduction of any non-essential technology, we will say so clearly on the page and we will pair it with the consent mechanism described in section 7.
We keep an archived copy of every version of this page that has ever been published, and of every other page in our legal set. If you want to see the version that applied on a particular date, or the version you accepted, email support@blugency.co and we will send it to you.
Contact
Questions about cookies, or about anything on this page:
Email: support@blugency.co
Post: Blugency LLC, 1209 Mountain Road Pl NE, Ste N, Albuquerque, NM 87110, United States
For a privacy request, including access, correction or deletion, follow the process in our Privacy Policy, which tells you what to include and how long we take to respond.