Cookie Policy: How Jobeezy Uses Cookies
Last updated: July 9, 2026 · Effective: July 9, 2026. This policy explains the cookies and similar technologies we use on our websites, organized by purpose, and how to manage your choices.
Last updated: July 21, 2026. Effective: July 21, 2026. This Cookie Policy is part of, and should be read together with, our Privacy Policy. It is published by Jobeezy, Inc. (“Jobeezy,” “we,” “us,” or “our”), a Delaware corporation with its principal place of business at 800 Brazos St., Suite 400, Austin, TX 78701.
The most important thing to know: We use a small number of cookies and similar technologies to run our websites and to understand how they are used so we can improve them. We do not sell or share your personal information, and we honor the Global Privacy Control (GPC) signal. We use no advertising or cross-site tracking cookies anywhere on our sites, with one disclosed exception: a single paid-ad landing page (jobeezy.com/get/) carries a Meta (Facebook) pixel, and it loads only if you choose “Accept.” You can change or withdraw your choices at any time using the “Cookie choices” control on every page.
Plain-language summary. Cookies are small files a website stores in your browser. We use a few that are needed to keep the site working (like remembering your cookie choice or keeping you signed in), and a few that measure how the site is used (Google Analytics and PostHog). Measurement cookies load only after you choose “Accept” — for every visitor, in every country. If you have not made a choice yet, they stay switched off, and no analytics event is sent. One page — our paid-ad landing page at jobeezy.com/get/ — also carries a Meta advertising pixel, which likewise loads only after you accept. Everywhere else we run no ad or cross-site tracking technology at all. To change your mind later, use the “Cookie choices” control on any page. We also automatically honor a browser Global Privacy Control signal. The full detail is below.
1. What this policy covers
This Cookie Policy applies to the two Jobeezy websites you can visit in a browser:
- Our marketing site at
jobeezy.com(the pages you are reading now). - Our web app at
app.jobeezy.com, where you sign in and use Jobeezy.
Our Android app (com.jobeezy.job) does not use browser cookies. Like most mobile apps, it uses software development kits (SDKs) and on-device storage instead. We explain that in the mobile app section below and in our Privacy Policy. iOS is not yet available; when it launches, it will follow the same approach.
For the full picture of what personal information we collect, why, who we work with, how long we keep it, and the rights you have, please read our Privacy Policy. California residents should also read our California Privacy Notice. Business customers and data-protection questions are covered in our Data Processing Addendum and on our Sub-processors page, which lists the third parties that process data for us. This Cookie Policy and the Privacy Policy are written to agree with each other; if you ever spot a difference, please tell us at privacy@jobeezy.com.
We aim to keep the tables below accurate, but the exact set of cookies present can vary by page, by device, and over time, so this is not a guarantee that every cookie you encounter is listed by name. If you find one that is not described here, let us know and we will explain it and update this page.
2. What cookies and similar technologies are
A cookie is a small text file that a website asks your browser to store. When you come back, the browser sends the cookie back, which lets the site remember things — for example, that you already chose your cookie settings, or that you are signed in.
“Similar technologies” means other ways a site or app can store or read information on your device that do the same kinds of jobs as cookies. We use two kinds:
- Local storage and session storage (
localStorage/sessionStorage): small pieces of data saved by your browser.localStoragestays until it is cleared;sessionStorageis erased when you close the browser tab. - Mobile SDKs and device identifiers: used inside our Android app instead of cookies (see the mobile app section below).
We treat all of these the same way the law does — by what they do, not just by the word “cookie.” We do not use tracking pixels, advertising tags, cross-site trackers, or device-fingerprinting for advertising on our sites.
A cookie is first-party when it is set by Jobeezy, and third-party when it is set by a company that provides a service to us (for example, Google Analytics or Clerk). We name the party for each entry in the tables below.
3. Legal basis and global privacy signals
Strictly-necessary cookies (the ones needed to run the site securely, keep you signed in, and remember your cookie choice) do not require your consent. Under EU and UK law they fall within the exemption for storage that is strictly necessary to deliver a service you asked for.
Non-essential cookies (our analytics technologies, plus the advertising pixel on our single paid-ad landing page) require your consent, and we ask for it the same way everywhere:
- Everyone, everywhere — consent first. We do not try to guess what country you are in, and we do not treat “we could not tell” as a yes. Until you choose “Accept” on our cookie banner, non-essential cookies stay switched off. This is stricter than United States law requires, and it is what we do for every visitor.
- EU, UK, Switzerland (and similar regimes): The law that governs placing a cookie is the ePrivacy Directive (Article 5(3)) and, in the UK, the Privacy and Electronic Communications Regulations (Regulation 6). These require your consent before a non-essential cookie is placed, which is the standard we apply worldwide. The later use of any personal data collected relies on the appropriate basis under the GDPR (usually consent or our legitimate interest in improving the Services).
- United States and other opt-out regions: You would be entitled to have non-essential cookies load on arrival with an opt-out. We do not do that — we wait for your “Accept” instead — and you can still withdraw at any time using the controls in the Your choices section.
Global Privacy Control (GPC). GPC is a signal your browser or a browser extension can send that says “do not sell or share my information.” We honor GPC on our websites and treat it as a valid opt-out of any sale or sharing of personal information — neither of which we do in the first place. Where we can, we will show you that the signal was recognized.
“Do Not Track” (DNT). There is no agreed industry standard for the older DNT browser setting, so we do not respond to DNT signals. We honor GPC instead.
Withdrawing consent does not make anything we did before you withdrew it unlawful; it just stops the processing going forward.
4. The categories of cookies we use
We group our cookies and similar technologies into four categories. The advertising category has exactly one member and appears on exactly one page; we would rather name it than keep a tidier-looking policy that is not accurate.
- Strictly necessary — needed to run the site securely and to remember your choices. This includes keeping you signed in (handled by our authentication provider, Clerk) and storing your cookie-consent choice. These cannot be switched off.
- Functional — remember preferences and help the site work smoothly (for example, not showing you the same pop-up twice). These are stored in your browser only, are not shared with anyone, and are treated as non-essential in the EU, UK, and Switzerland.
- Analytics — help us understand how the site is used so we can improve it. This is Google Analytics 4 and PostHog. Analytics cookies are non-essential and are loaded only after you choose “Accept.”
- Advertising — used on our paid-ad landing page (
jobeezy.com/get/) only, to measure whether an ad we paid for actually led to a sign-up. This is a Meta (Facebook) pixel. It is non-essential, it is the only advertising technology we run, it appears on no other page, and it loads only after you choose “Accept.”
5. Cookies and storage on our marketing site (jobeezy.com)
| Name | Type & party | Category | Purpose | Duration |
|---|---|---|---|---|
jb_consent_v1 |
localStorage · first-party | Strictly necessary | Stores your cookie-consent choice (accept / reject). Used to decide whether analytics may load. | Until you clear it |
jb_gdpr_consent |
Cookie (SameSite=Lax) · first-party | Strictly necessary | A cookie copy of your consent choice, so our servers and edge can read it. Records your consent for compliance. | 365 days |
jb_exit_intent_ts |
localStorage · first-party | Functional | Remembers when you last saw an exit pop-up, so we do not show it more than once about every 30 days. | Until you clear it |
jb_apply_assist_dismissed |
sessionStorage · first-party | Functional | Remembers that you dismissed the apply-assist prompt during this browser session. | Session (until tab closes) |
jb_sticky_dismissed |
sessionStorage · first-party | Functional | Remembers that you dismissed the sticky bottom call-to-action bar during this browser session. | Session (until tab closes) |
_ga |
Cookie · third-party (Google) | Analytics | Google Analytics 4 identifier that tells apart one browser from another for aggregate traffic measurement. IP address is anonymized. | 2 years |
_ga_TZH8NDVHZC |
Cookie · third-party (Google) | Analytics | Google Analytics 4 session-state cookie for our measurement stream G-TZH8NDVHZC. |
2 years |
_fbp (Meta pixel) |
Cookie · third-party (Meta Platforms) | Advertising | On our paid-ad landing page jobeezy.com/get/ only. Tells Meta that someone who saw one of our ads reached the page, so we can tell whether the ad money did anything. It is not present on any other page of our site. It loads only after you choose “Accept,” and never if you reject or have not chosen. |
Up to 90 days |
ph_*_posthog |
Cookie + localStorage · third-party (PostHog) | Analytics | PostHog product analytics: distinguishes visitors, counts feature usage, and powers funnels and A/B flags. On the marketing site, PostHog autocapture and session recording are enabled, so it may record how you move through and interact with pages. It also writes several localStorage keys for its session and feature-flag state. Loaded only after you choose “Accept.” |
Cookie ~365 days; local-storage keys vary |
6. Cookies and storage on our web app (app.jobeezy.com)
The web app is where you sign in and use Jobeezy in a browser. It uses these cookies and storage keys:
| Name | Type & party | Category | Purpose | Duration |
|---|---|---|---|---|
Clerk session cookies (__session, __client_uat, __clerk_*) |
Cookie · third-party (Clerk) | Strictly necessary | Keep you securely signed in. Set and managed by our authentication provider, Clerk. (These are the standard Clerk session cookies; their exact names and lifetimes are controlled by Clerk’s SDK.) | Session / short-lived |
access_token, refresh_token, id_token |
localStorage · first-party | Strictly necessary | Sign-in tokens (issued via Clerk) that let the app call our API on your behalf. Cleared when you sign out. | Until sign-out or session expiry |
jb_consent_v1, jb_gdpr_consent |
localStorage + Cookie · first-party | Strictly necessary | Stores and records your cookie-consent choice in the web app, the same way as on the marketing site. | localStorage until cleared; cookie 365 days |
jobeezy_onboarding_complete, jobeezy_guest_marketing_dismissed, jobeezy_auto_apply_disclosure_ack, jobeezy_intake_draft:<id> |
localStorage · first-party | Functional | Remember your place in the app: that you finished onboarding, dismissed a banner, acknowledged the Auto-Apply disclosure, and saved a draft of your intake form so you do not lose it on refresh. | Persistent until cleared |
ph_*_posthog |
Cookie + localStorage · third-party (PostHog) | Analytics | PostHog product analytics in the web app. Here it is configured without session recording and without autocapture, and personal information is stripped before events are sent. | Cookie ~365 days; local-storage keys vary |
| Sentry (no cookie) | Third-party (Sentry) | Strictly necessary | Error and crash monitoring so we can find and fix bugs. Sentry does not set a cookie for this; we list it here for transparency. Error reports are scrubbed of personal information before they are sent. | — |
Google, PostHog, Clerk and Sentry — the third parties that process data on our instructions — also appear in the Sub-processors section of our Privacy Policy and on our Sub-processors page, so those lists match across our documents. Meta is deliberately not on that list: for the advertising pixel described above, Meta decides its own purposes for the data, so it acts as an independent controller rather than as our processor. We name it here so it is disclosed to you either way.
Cookies we used to describe and no longer set. Earlier versions of this policy listed two first-party cookies, jb_variant (an A/B test assignment) and jb_city (an approximate, city-level location used to tailor headlines). Both were set by a content-delivery (edge) layer that we retired when we changed hosting providers. Nothing sets them any more, we no longer run A/B tests or geo-personalization on this site, and we have removed them from the table above rather than leave a description of something that does not happen.
7. Google Analytics and Consent Mode
Google Analytics 4 acts as our service provider (processor) for website measurement. We configure it in a privacy-protective way:
- IP anonymization is on.
- Advertising storage is always denied. We never turn on Google’s advertising or remarketing features, so Analytics is not used to build ad audiences or profiles.
- Google Consent Mode is used so that analytics storage is denied by default for every visitor, in every country, and is granted only after you choose “Accept.”
We deliberately do not try to detect your country to decide whether to ask you. If we cannot tell where a visitor is — which, since we retired our edge layer, is every visitor — we treat that as a “no,” not a “yes.” So _ga and PostHog are not set when you arrive; they are set after you accept, and you can withdraw at any time (see the Your choices section).
One thing we want to be precise about. Because the Google Analytics tag is present on the page before you decide, Consent Mode means Google may still receive a cookieless ping from that page load: a signal that a page was viewed, with advertising and analytics storage denied, no _ga identifier, and nothing written to your browser. We do not send any analytics event in that state — our tag drops them until you accept. We are spelling this out because “nothing at all reaches Google until you click Accept” would be a slightly stronger claim than what the technology actually does, and we would rather be accurate than flattering.
8. Your choices — how to manage or withdraw consent
You are always in control. You can change your mind as easily as you gave your choice.
- Change or withdraw your consent — one click, on any page. Every page on our sites carries a “Cookie choices” control — in the footer at the bottom of the page on our marketing site, and as a small button in the bottom-left corner in the web app and on the handful of pages that have no footer. Press it and the consent banner comes back, so you can switch from Accept to Reject (or the other way round) whenever you like. Withdrawing is exactly as easy as consenting, which is what the law requires and what we think is simply right.
- What withdrawing does. Choosing “Reject non-essential” stops analytics and the advertising pixel from loading on any page you visit afterwards, and tells Google Analytics that storage is denied. It does not reach back and delete data already collected — for that, use the deletion rights in our Privacy Policy. To clear identifiers already stored in your browser, you can also delete cookies and site data through your browser settings (below).
- Global Privacy Control. If your browser sends a GPC signal, we honor it automatically as an opt-out — you do not need to do anything else.
- Your browser settings. You can view, block, and delete cookies in your browser: Chrome, Firefox, Safari, and Edge. Blocking strictly-necessary cookies may stop parts of the site (like staying signed in) from working.
- Opt out of Google Analytics. You can install Google’s Analytics Opt-out Browser Add-on.
9. Region-specific rights
EU, UK, Switzerland, and similar regimes. Non-essential cookies are only placed with your consent. You can withdraw consent at any time, and it is as easy to withdraw as it was to give. The full detail of your data-protection rights (access, deletion, objection, and more) is in our Privacy Policy.
United States. We do not sell or share your personal information, and we honor the Global Privacy Control. California residents have specific rights described in our California Privacy Notice, including the right to opt out of sale or sharing (which we do not do) and to limit certain uses of sensitive information. Residents of other states with privacy laws have similar rights, described in our Privacy Policy.
10. International data transfers
Our analytics providers (Google and PostHog) are based in the United States, so when analytics cookies are used, some data about your visit is processed in the United States. Where you are in the EU, the UK, Switzerland, or Brazil, these transfers rely on the safeguards described in the International transfers section of our Privacy Policy (such as EU Standard Contractual Clauses or an approved adequacy framework). Having a valid transfer safeguard is separate from consent: we still ask for your consent before analytics cookies load.
11. The mobile app
Our Android app does not use browser cookies. Instead it uses SDKs and on-device storage — for example, PostHog for product analytics and Sentry for crash reporting. Because the app is a separate surface from our websites, its privacy choices are handled in the app, not by the website banner. You can also use your device’s controls: on Android you can reset or delete your Advertising ID (we do not use it for advertising). If we launch an iOS app, it will follow the same approach and use Apple’s App Tracking Transparency where required. For how the app handles data, see our Privacy Policy.
12. Changes to this Cookie Policy
We may update this Cookie Policy from time to time — for example, if we add or remove a tool, or if the law changes. When we do, we will change the “Last updated” date at the top. If the change is significant, we will give you a more prominent notice (for example, in the app or by re-showing the cookie banner). Please check back so you stay informed.
13. Contact us
If you have questions about this Cookie Policy or your cookie choices, contact us:
Jobeezy, Inc.
800 Brazos St., Suite 400
Austin, TX 78701, USA
Privacy & cookie questions: privacy@jobeezy.com
General: hello@jobeezy.com
We aim to acknowledge privacy requests within 10 business days and to respond within 45 days, and we will tell you if we need more time for a complex request. You can read more about your rights and how to exercise them in our Privacy Policy.