On this page
- What cookies and similar technologies are
- The types of cookies, and which ones this site uses
- The cookies on this site
- Google Ads
- Google Analytics
- Calendly
- Turnstile, the check on our booking page
- Recruit CRM, on our job openings page
- Cloudflare
- Counting visits without cookies
- Global Privacy Control and Do Not Track
- Managing cookies
- Changes to this policy
- How to contact us
The short version
- Our own code sets no cookies. On the published site, Google’s tag sets cookies for Google Analytics, to measure visits and campaigns, and for Google Ads, to measure which of our ads bring inquiries and to show our ads to people who have visited the site — unless your browser sends a Global Privacy Control signal, in which case we do not load Google’s tag at all.
- Nothing from Calendly loads in your browser: when you book a call, our own server sends the booking to Calendly. Cloudflare’s Turnstile, which checks that a booking comes from a person, runs on the booking page once you pick a time and sets no cookie here; our host, Cloudflare, sets one only if a security check runs.
- We also count visits with Cloudflare Web Analytics, which uses no cookies and does not identify you.
- You can block or delete cookies in your browser at any time; the site keeps working without them.
1. What cookies and similar technologies are
Cookies are small text files that a website stores in your browser. They let a site remember something between one page and the next — that you are signed in, a setting you chose, or that you were here before. A cookie set by the site you are visiting is a first-party cookie; one set by another company whose content or code the site loads is a third-party cookie. A session cookie is deleted when you close your browser; a persistent cookie stays until its expiry date or until you delete it.
Similar technologies do the same kind of work by other means: tags and pixels are small pieces of code or invisible images that tell a service a page was viewed or an action happened; local storage and session storage are places in your browser where a site can keep information without a cookie; identifiers in the address of a page, such as the identifier of an ad you clicked, can also connect one visit with another.
This policy covers all of them. It is part of our Privacy Policy, which explains what personal information we collect and how we use it.
2. The types of cookies, and which ones this site uses
- Strictly necessary cookies make a site work — keeping a session open, protecting it from abuse. This site needs none of its own. Cloudflare may set one if it runs a security check; Turnstile, the check on our booking page, runs without one — see Turnstile.
- Functional cookies remember a choice you made. This site keeps one choice — “Pause motion,” in the footer — in your browser’s session storage, not in a cookie; it is never sent to us or to anyone.
- Analytics cookies count visits and measure how a site is used. On the published site, Google Analytics sets them to measure visits and campaigns — see Google Analytics. We also count visits with Cloudflare Web Analytics, which works without cookies or local storage and does not identify individual visitors.
- Advertising cookies connect an ad you saw or clicked with what you did afterwards. On the published site, Google Ads sets them to measure which of our ads lead to consultation requests — unless you opt out, as described in Global Privacy Control and Do Not Track.
3. The cookies on this site
These are the cookies and similar technologies that can be set when you use the site, who sets them, why, and how long they last. Durations are the ones their providers document; a browser may delete a cookie sooner.
| Name | Provider | What it does | Type | Party | Duration |
|---|---|---|---|---|---|
| _gcl_au | Google Ads | Connects a click on one of our ads with a later inquiry, so that the conversion can be measured | Advertising | Set on our domain by Google’s tag | 90 days |
| _gcl_aw, _gcl_gb, _gcl_gs | Google Ads | Store the identifier of the ad click that brought you to the site, when you arrived from a Google ad | Advertising | Set on our domain by Google’s tag | 90 days |
| IDE | Google (doubleclick.net) | Google’s advertising cookie, used to measure ads, to show them to people who have visited the site and to limit how often you see one | Advertising | Third party | 13 months in the EEA and the UK; 24 months elsewhere |
| test_cookie | Google (doubleclick.net) | Checks whether your browser accepts cookies | Functional | Third party | 15 minutes |
| NID | Google (google.com) | Google’s cookie for its own services, which may be set when its tag loads | Advertising, security | Third party | 6 months |
| _ga | Google Analytics | Tells one visitor from another, to measure visits and campaigns | Analytics | Set on our domain by Google’s tag | Up to 2 years; Chrome keeps it 400 days |
| _ga_* | Google Analytics | Keeps the state of a visit to this site; the name ends in our property’s identifier | Analytics | Set on our domain by Google’s tag | Up to 2 years; Chrome keeps it 400 days |
| Turnstile | Cloudflare | Tells a booking made by a person from one made by a program, on the booking page, once you pick a time. Cloudflare documents a Turnstile cookie only in its pre-clearance mode, which this site does not use; the check runs in a frame from challenges.cloudflare.com under Cloudflare’s own policy | Strictly necessary | Third party | None set on this site |
| __cf_bm, cf_clearance, _cfuvid | Cloudflare | Tell people apart from bots and remember that a security check was passed. Set only if such a check runs; none runs on this site today | Strictly necessary | Set on our domain by our host | 30 minutes of inactivity for __cf_bm; up to the check’s own limit for the others |
| tvc-ambient-motion | This site | Remembers that you pressed “Pause motion” in the footer. Session storage, not a cookie | Functional | First party | Until you close the tab |
Google’s cookies, for Analytics and for Ads, are set only on the published site and only if your browser does not send a Global Privacy Control signal. In our previews and while the site is being built, Google’s tag is not loaded at all.
4. Google Ads
We advertise on Google, and we want to know which of our ads bring consultation requests. To measure that, and to show our ads to people who have visited the site, the published site loads Google’s tag (gtag.js) after each page has finished loading. The tag sets the cookies in the table above and sends Google the address of the page you are on, your IP address, your browser type, the page that referred you and, if you arrived from one of our ads, the identifier of that click. When a call is booked and Calendly confirms it, or a consultation request is sent through our e-mail form and our form provider confirms it was received, the tag reports one conversion to Google, with a nominal value and currency — and nothing you typed into the form.
Google describes the cookies its advertising products use, and how it uses the data it receives from sites like ours, at Types of cookies used by Google and How Google uses information from sites or apps that use our services. You can manage how Google personalizes ads for you at Google’s ad settings.
Remarketing. Through Google Ads and Google Analytics, we can show our ads on Google and its partner sites to people who have visited this site. Google builds these audiences with its cookies; we never see who is in them, and we do not share the contents of any inquiry with Google.
We do not load the tag if your browser sends a Global Privacy Control signal, and you can block or delete its cookies at any time, as described in Managing cookies.
5. Google Analytics
The same tag loads Google Analytics, which we use to measure visits and campaigns: the pages viewed, how visitors reached the site, which campaign brought them and how they move through it, including when a form is started — the form’s address and the name of its first field, never what you type. It sets two cookies on our domain, _ga and _ga_*, which tell one visitor from another for up to two years; Chrome keeps them 400 days.
Google describes these cookies at Google Analytics cookie usage on websites and how it uses the data it receives at How Google uses information from sites or apps that use our services. You can opt out of Google Analytics on every site with Google’s opt-out add-on, and we do not load the tag if your browser sends a Global Privacy Control signal.
6. Calendly
Calendly schedules our calls, but nothing from Calendly loads in your browser. Our booking page shows the available times itself, and when you press “Schedule the call,” our own server sends the booking to Calendly through its interface for programs; Calendly then creates the appointment and e-mails you the invitation. No Calendly script, frame or cookie reaches this site, and your choice of time is kept on the page only until you leave it.
The one Calendly address the page can show is a link to our scheduling page on Calendly’s own site, offered only if our booking service cannot be reached. That page is Calendly’s, under Calendly’s privacy notice and its own cookie settings. Calendly processes every booking on our behalf under that notice.
7. Turnstile, the check on our booking page
Before our server sends a booking to Calendly, it checks that the booking comes from a person and not from an automated program. The check is Turnstile, a service of our host, Cloudflare. It loads on the booking page once you have picked a time — not before — and in most cases it decides without asking you anything; when it has to, it shows a small box to tick. It runs in a frame served from challenges.cloudflare.com and sends Cloudflare your IP address and the characteristics of your browser.
Turnstile sets no cookie on this site. Cloudflare documents a Turnstile cookie only in its “pre-clearance” mode, which we do not use. Cloudflare states that Turnstile processes only the data strictly necessary for this security function and does not access, store or transmit what you type into a form. Its data practices are described in Cloudflare’s privacy policy. If you prefer not to use it, the consultation form by e-mail on the same page does not load it.
8. Recruit CRM, on our job openings page
Our job openings page shows the roles we are recruiting for from Recruit CRM, the recruiting software we use, in a frame on the page. The frame loads from recruitcrm.io when you open that page — on no other page of this site — and what happens inside it is Recruit CRM’s: it may set its own cookies and use similar technologies there, under Recruit CRM’s privacy policy. Because Recruit CRM decides which cookies its frame sets, they are not in the table above. If you open the job board in a new tab, or apply for a role, you are on Recruit CRM’s own site, under the same policy.
9. Cloudflare
Cloudflare hosts this site and protects it from abuse. On a site like ours, Cloudflare sets no cookies by default. Its cookies — __cf_bm, cf_clearance and _cfuvid — belong to security features that run a check on a visitor’s browser to tell people apart from automated traffic, and they are set only if such a check runs. We have not enabled those features today; if we do, we will update the table above first. Cloudflare documents its cookies at Understanding Cloudflare cookies, and its privacy policy is at cloudflare.com/privacypolicy.
10. Counting visits without cookies
We also count visits with Cloudflare Web Analytics. It measures page views, the pages that are read, where visitors come from and how fast the site loads for them, and it does so without cookies, without local storage and without fingerprinting your browser: Cloudflare states that it “does not use any client-side state, such as cookies or localStorage, to collect usage metrics” and does not “fingerprint individuals via their IP address, User Agent string, or any other data.” It cannot tell one visit of yours from another, and it does not follow you across other sites. There is nothing to opt out of, because nothing identifies you.
Two other services this site uses set no cookies either: Fontshare, which serves one of the site’s typefaces and states that it receives only the referring domain and the number of font requests from it; and Web3Forms, which delivers the consultation form by e-mail with a single request when you press “Send” and stores nothing in your browser.
11. Global Privacy Control and Do Not Track
Global Privacy Control (GPC) is a setting in some browsers, and an extension for others, that tells every website you visit that you do not want your personal information sold or shared. We honor it: when your browser sends the signal, this site does not load Google’s tag, so no analytics or advertising cookie is set and nothing is sent to Google. The signal applies to the browser and device that send it. How to turn it on, and which browsers support it, is at globalprivacycontrol.org.
Do Not Track (DNT) is an older browser setting with no agreed standard for how a site should respond. This site does not respond to it. If you want to opt out of Google Analytics and of our advertising, use Global Privacy Control or the browser settings below.
12. Managing cookies
You can see, block and delete cookies in your browser’s settings, for all sites or for this one. Blocking cookies does not stop this site from working: its pages, its articles, its booking form and its consultation form by e-mail need none.
- Google Chrome: Delete, allow and manage cookies in Chrome
- Apple Safari: Manage cookies and website data in Safari on Mac — on iPhone and iPad, Settings › Safari › Privacy & Security
- Mozilla Firefox: Enhanced Tracking Protection in Firefox
- Microsoft Edge: Delete cookies in Microsoft Edge
To manage Google’s cookies specifically: turn on Global Privacy Control; opt out of Google Analytics on every site with Google’s opt-out add-on; adjust ad personalization at Google’s ad settings; or block third-party cookies in your browser, which stops Google’s own cookies while the site keeps working.
To clear the one thing the site itself keeps — the “Pause motion” choice — close the tab, or press “Play motion” in the footer.
13. Changes to this policy
When we add, remove or change a cookie or a similar technology, we update the table in this policy and the date at the top of the page before the change reaches the site. Our build process refuses to publish the site if it connects to a service that this policy and our Privacy Policy do not name.
14. How to contact us
Questions about cookies or about this policy: [email protected]. By mail: Baja Nearshore LLC, 1905 East Palomar Street, Unit 6, Chula Vista, CA 91913, United States.
Questions about cookies?
Write to [email protected], or by mail to Baja Nearshore LLC, 1905 East Palomar Street, Unit 6, Chula Vista, CA 91913, United States.