Opt-out preferences

1. Introduction

Our website, https://stoneharborstaffing.com (the “website”), uses cookies and other related technologies (for convenience, all such technologies are referred to as “cookies”). Cookies are also placed by third parties we have engaged. In the document below we inform you about the use of cookies on our website.

2. Cookies

When you visit our website it can be necessary to store and/or read certain data from your device by using technologies such as cookies.

2.1 Technical or functional cookies

Some cookies ensure that certain parts of the website work properly and that your user preferences remain known. By placing functional cookies, we make it easier for you to visit our website. This way, you do not need to repeatedly enter the same information when visiting our website and, for example, the items remain in your shopping cart until you have paid. We may place these cookies without your consent.

2.2 Statistics cookies

We use statistics cookies to optimize the website experience for our users. With these statistics cookies we get insights in the usage of our website.

2.3 Marketing/Tracking cookies

Marketing/Tracking cookies are cookies or any other form of local storage, used to create user profiles to display advertising or to track the user on this website or across several websites for similar marketing purposes.

2.4 Social media

This website embeds no social media content. There are no like, share or follow buttons, no timeline or post embeds, and no code from LinkedIn, Facebook, X (formerly Twitter), WhatsApp, Instagram or Pinterest anywhere on it. None of those companies can place a cookie on your device through this website, and none of them is told that you were here.

Some pages do carry an ordinary link to a profile or a company page on one of those networks, such as a recruiter's LinkedIn page. A link is not an embed. It stores nothing and sends nothing until you choose to follow it, and once you do you are on that network's own website, under its own privacy statement, which this policy does not cover.

3. Placed cookies

Below is everything this website stores on your device, what each item does, and how long it lasts. Every entry was checked against this site's own code and against a live page, so this list describes the site you are reading rather than an earlier version of it.

Where a lifetime is a vendor's documented default rather than a period we set ourselves, the entry says so.

3.1 What a visit places before you choose

Stone Harbor Staffing Group itself writes two cookies and no others, and both are in 3.2. sh-consent records the answer you gave the banner and holds no identifier of any kind. astro-session does hold one — a random value pointing at a session on our servers — but it is written only when you sign in, it identifies that session rather than you as a visitor, and it is read for nothing but keeping you signed in. Neither is used to measure you or to advertise to you: we set no visitor identifier for those purposes and no advertising cookie of our own.

Everything else below is written by another company's script running in your browser, and each of those belongs to a category you control. Whether any of them has run before you answer the banner depends on where you are, and we would rather you read the uncomfortable half of that here than find it in section 4.

• In the European Economic Area, the United Kingdom and Switzerland, and anywhere we cannot identify, nothing in 3.4, 3.5 or 3.6 has run. Those scripts start switched off and stay off until you say yes, so a visit that has not answered has received none of the cookies they set.
• In the United States, they start switched on, which is what the law there provides for. So an American visitor who has not yet answered will already have the statistics cookies in 3.4, and on a campaign page the advertising cookies in 3.6. The banner is how you turn them off, and 4.1 is what happens when you do.

3.2 Strictly necessary

sh-consent, set by Stone Harbor Staffing Group as a first-party cookie.

• Function. It records the answer you gave the cookie banner. It holds which categories you allowed, which regime your answer was taken under, the two-letter country code that decided it, whether your browser was sending a privacy signal at the time, and when you answered. It holds no identifier and nothing that could pick you out.
• Purpose. Enforcing your choice. Without it we cannot tell whether you have answered, and every page would have to ask again. It is also what lets our servers leave an advertising tag out of a campaign page before it is sent to you, rather than sending it and hoping your browser blocks it.
• Expiration. One year from the day you answer.
• Category. Strictly necessary. We do not ask permission to remember your answer, because remembering it is the only way to honor it.

astro-session, set by Stone Harbor Staffing Group as a first-party cookie.

• Function. It holds a random identifier and nothing else. That identifier points at a candidate session kept on our servers, which is where the details you have given us, and the credentials used to reach our systems, stay. The cookie is marked HttpOnly, so no script running in a page can read it.
• Purpose. Keeping you signed in to a candidate account. There is no signed-in session without it, which is why we do not ask for consent to set it — but it is set at the moment you sign in, and never before.
• Expiration. None is set on it. It is a session cookie, so your browser discards it when you close the browser, and signing out deletes it immediately.
• Category. Strictly necessary.

These two are the only cookies this website writes itself. Everything below is written by another company's script running in your browser.

3.3 Form protection

Our forms, including the privacy request form on this page, are protected against automated abuse by Cloudflare Turnstile. The widget is loaded from challenges.cloudflare.com and runs there. On the pages we measured it set no cookie under this website's domain, and anything it needs to store belongs to Cloudflare's domain rather than to ours. It is there to tell a person apart from a script, and a form submission cannot be accepted without it, so it is strictly necessary.

3.4 Statistics

These load only if you allow the Analytics category.

We use Google Analytics 4, measurement ID G-3EN0K6627J, to count visits and to see which pages are read. Its script is loaded from Google and writes two cookies in your browser, both under this website's own domain.

_ga, set by Google Analytics.

• Function. Stores a randomly generated number that tells one browser from another, so that a second visit is counted as a return rather than as a new person.
• Expiration. Two years. That is Google's documented default, and our snippet does not change it.
• Category. Statistics.

_ga_3EN0K6627J, set by Google Analytics.

• Function. Holds the state of your current analytics session for the property named above. Its name carries that property's measurement ID with the leading letter and dash removed, which is why it reads the way it does.
• Expiration. Two years, again Google's documented default rather than a period we chose.
• Category. Statistics.

We also load Google Tag Manager, container ID GTM-T28FCTGX, under the same Analytics category. Tag Manager is a container rather than a tag of its own. It stores nothing on your device and sets no cookie. What it can do is load other companies' tags, and a tag loaded that way may set cookies of its own. Every tag we put in this container is described in this section, with the cookies it sets, alongside the entries above. So this section is the whole of what Tag Manager runs on your device, and where it names no tag, the container is loading none.

We also load Unbounce, from an address ending in ubembed.com, on marketing pages built with it. Unbounce serves variants of a page and measures which one led to an enquiry, and it sets visitor cookies of its own to attribute that enquiry to a visit. Measuring is what it is for, so it sits in this category and an Analytics refusal stops it loading. It is loaded only when it has been switched on in our own settings, so on any given day it may not be running at all; the way to tell is to view the source of a page and look for that address. We have not seen it write a cookie under this website's own domain — what it stores, it stores under its own — and if that changes, the cookie will be named here.

3.5 Functional

One vendor sits in this category. It is loaded only when it has been switched on in our own settings, and then only if you allow the Functional category, so on any given day it may not be running at all. The way to tell is to view the source of a page and look for the address below.

• UserWay, an accessibility widget loaded from cdn.userway.org. It remembers the display settings you choose in it, such as contrast and text size.

We have not seen it write a cookie under this website's own domain. Anything it stores, it stores under its own, which is why turning this category off stops the script being loaded rather than deleting a cookie of ours. If that ever changes, the cookie belongs in this section and this is where it will appear.

3.6 Advertising, on campaign pages only

These load only if you allow the Advertising category, and only on a campaign landing page that carries a pixel ID. They are not on the home page, the job board, an individual job page, the blog or this policy, and on those pages there is nothing in this category to allow.

A campaign landing page is one we build for a specific advertisement. Its address contains /lp/, and you will normally reach it by clicking an ad rather than by browsing the site.

_fbp, written by the Meta pixel under this website's own domain.

• Vendor. Meta Platforms, which operates Facebook and Instagram.
• Function. Holds a randomly generated browser identifier. Meta uses it to tell whether someone who saw one of our advertisements later reached the page it pointed at, and to show our advertisements to people who have visited that page.
• Expiration. 90 days, which is Meta's documented lifetime and not a period we set.
• Category. Advertising.

_fbc, written by the same pixel under this website's own domain, and only when you arrive from a Meta advertisement.

• Function. Holds the click identifier that Meta puts in the advertisement's link, so the click and the visit can be matched to each other.
• Expiration. 90 days.
• Category. Advertising.

fr, set by facebook.com rather than by us.

• Function. Meta's own advertising cookie, used to deliver and measure advertisements across its products.
• Expiration. Meta does not publish a lifetime for it in its cookies policy, so we do not state one here rather than guess.
• Category. Advertising. Because it belongs to facebook.com and not to us, we cannot delete it for you. Turning the category off stops us loading the pixel that causes it to be set, and your browser settings are where an existing one is removed.

_gcl_au, and the _gcl_aw, _gcl_dc and _gac_ entries beside it, written by the Google Ads tag under this website's own domain.

• Vendor. Google.
• Function. They hold information about an advertisement click, so that a lead submitted afterwards can be attributed to the advertisement that produced it. The name of a _gac_ entry ends with the identifier of the advertising property it belongs to.
• Expiration. 90 days, which is Google's documented lifetime for these cookies.
• Category. Advertising.

If you turn the Advertising category off, we delete the entries above that are under our own domain and reload the page, and no campaign page will load a pixel again while it stays off.

3.7 Storage that is not a cookie

A few things are kept in your browser's local storage instead of in a cookie. Local storage is never attached to a request, so none of it is sent to us.

• sh-consent is a copy of the consent cookie described in 3.2, kept so the preferences panel can still show your choices if you have blocked cookies for this site.
• sh_topbar_snapshot, and the sh_topbar_dismissed entries beside it, hold the last announcement bar you were shown and which announcements you have closed, so that a notice you dismissed stays dismissed and the bar does not jump into place on your next visit.
• sh-kaiya-session is written only if you use the chat assistant. It holds an identifier for the conversation, so the conversation survives moving between pages. It does not hold the conversation.

Clearing this website's data in your browser removes these along with the cookies above.

4. Browser and Device based Consent

This website asks you about cookies and acts on your answer. When you arrive without having answered, a card appears at the bottom of the screen offering Accept all, Essential only, and a settings button that opens the three categories one at a time. Your answer is stored in the sh-consent cookie described in 3.2, for one year, and it is what decides whether the scripts in 3.4, 3.5 and 3.6 are allowed to run.

Nothing in those sections is loaded before the check. The scripts are placed in the page in a form your browser will not execute, and only the categories you allowed are turned into running code. A category you refuse is never started, rather than started and then asked to stop. On a campaign page the advertising tag is left out by our servers before the page is sent to you, so there is nothing on the page to block.

4.1 Manage your opt-out preferences

Three things work, and they do different jobs. The first is the one that changes what runs on this device, and it takes effect at once.

• Cookie settings, in the footer of every page. It reopens the panel, where you can turn any category on or off at any time. Turning one off deletes the cookies we set for it under this website's domain and reloads the page, so nothing already loaded carries on running. Cookies set under another company's own domain, such as Meta's fr on facebook.com, are outside what any page here can remove; the next item is where those go.
• In your browser. Blocking or clearing this website's cookies removes everything named in section 3, including the record of your own choice, and blocking scripts from a vendor's domain stops that vendor loading whatever this site does. Section 5 below is about exactly this and covers where those settings live. Ordinary browsing is unaffected if you do it — the two cookies we need are in 3.2, and both are ours. One thing does stop, and it is the one exception: our forms are checked by Cloudflare Turnstile, described in 3.3, so while challenges.cloudflare.com is blocked no form on this site can be submitted, including the privacy request form on this page.
• By asking us, as a formal request. The form under How to submit a request includes "Do not sell or share my personal information" and "Object to, or restrict, how you process my information". That is a request about the information we already hold, made to our privacy team and answered by a person. It is not a setting on this device, which is why it is third here rather than first.

4.2 What we assume before you answer

It depends on where you are, because the law does. We use the country your connection resolves to at our network edge, and nothing more precise than that.

• In the European Economic Area, the United Kingdom and Switzerland, and anywhere we cannot identify, nothing non-essential runs until you say yes. Statistics, functional and advertising scripts all start switched off, and the card asks before any of them loads.
• In the United States, including California, statistics, functional and advertising start switched on and the card offers to turn them off. This is the opt-out model those laws are built on, and the Your Privacy Choices link in the footer is its front door.

4.3 Global Privacy Control

We honor the Global Privacy Control signal. If your browser or an extension sends it, the Analytics and Advertising categories are switched off and held off, whatever is stored against your device and wherever you are. The preferences panel shows both categories locked, with a line saying that your browser is what is setting them, so you are never looking at a switch that has been overruled without being told.

The Functional category is deliberately not affected. Global Privacy Control is an opt-out of the sale and sharing of personal information and of cross-context behavioral advertising. An accessibility widget that remembers the contrast setting you chose is none of those things, and switching it off in the name of the signal would take a control away from the person the signal exists to protect.

We treat the older Do Not Track header in exactly the same way. It is deprecated, it was never adopted as a standard and no regulator recognizes it, so honoring it is our choice rather than an obligation. Anyone who went and found that switch meant the same thing by it.

5. Enabling/disabling and deleting cookies

You can use your internet browser to automatically or manually delete cookies. You can also specify that certain cookies may not be placed. Another option is to change the settings of your internet browser so that you receive a message each time a cookie is placed. For more information about these options, please refer to the instructions in the Help section of your browser.

Please note that our website may not work properly if all cookies are disabled. If you do delete the cookies in your browser, they will be placed again after your consent when you visit our website again.

6. Your rights with respect to personal data

You have the following rights with respect to your personal data:

• you may submit a request for access to the data we process about you;
• you may object to the processing;
• you may request an overview, in a commonly used format, of the data we process about you;
• you may request correction or deletion of the data if it is incorrect or not or no longer relevant, or to ask to restrict the processing of the data.

To exercise these rights, please contact us. Please refer to the contact details at the bottom of this Cookie Policy. If you have a complaint about how we handle your data, we would like to hear from you.

For more information about your rights with respect to personal data, please refer to our Privacy Statement

7. Contact details

For questions and/or comments about our Cookie Policy and this statement, please contact us by using the following contact details:

Stone Harbor Staffing Group

2041 Rosecrans Ave, Suite 245,

El Segundo, CA 90245

United States

Website: https://stoneharborstaffing.com

Email: privacy@stoneharborstaffing.com

Phone number: 1 (800) 928-1124

How to submit a request