Cookie Policy
This Cookie Policy explains how Jobzem uses cookies and similar technologies when you access, browse and interact with our websites and features. It describes the first-party cookies we use, the identifiers associated with third-party services that have been confirmed or may appear, their purposes, and the options available to control their use.
This Policy should be read together with our Privacy Policy and Terms of Use. The inventory below reflects Jobzem's known configuration as of the date of the last update. Cookies and identifiers associated with third parties may vary depending on region, consent, browser, campaign, enabled tags and changes made by the relevant providers.
1. What cookies and similar technologies are
Cookies are small files or records stored in a browser or device when a website is used. They may allow a service to recognize a session or browser, keep a user signed in, store preferences, remember choices, and support measurement, security, analytics and advertising.
Jobzem may also use similar technologies such as local storage, session storage, tokens, pixels, technical identifiers and consent signals. For ease of reading, this Policy may collectively refer to these technologies as “cookies,” although technically they do not all work in the same way.
A cookie may be created directly by Jobzem or result from the execution of technology supplied by a third party. Some identifiers associated with services such as Google or Meta may be stored under the domain visited by the user even though they are associated with those providers' technology and purposes. For this reason, this Policy distinguishes between Jobzem first-party cookies and cookies or identifiers associated with third-party services.
2. How Jobzem uses cookies
Jobzem uses cookies and similar technologies for purposes such as:
- maintaining user sessions and authentication;
- allowing automatic sign-in when the “Remember me” option is selected;
- recording the user's cookie consent preference;
- remembering certain interface preferences and interactions;
- storing recent mobile searches;
- avoiding excessive repetition of modals, prompts and onboarding;
- measuring use and performance of the platform when analytics is enabled;
- measuring traffic sources, campaigns, clicks and conversions;
- supporting attribution of Google and Meta advertising when those integrations are active;
- applying and transmitting consent choices and privacy signals within advertising ecosystems, where applicable.
Where applicable law requires prior consent for non-essential technologies, Jobzem should block or refrain from activating those technologies until the user makes the relevant choice through the banner or preference manager.
3. Cookie categories
3.1. Strictly necessary
These are used for essential functions requested by the user or required for the basic operation and security of the service, such as sessions, authentication and storage of the consent choice. Blocking these cookies may prevent sign-in or other essential functionality.
3.2. Functional and preference cookies
These remember choices or interface states, such as recent searches or whether onboarding or an app suggestion has already been shown. They make the experience more convenient, but not all are essential to the basic operation of the site.
3.3. Analytics and performance
These help us understand how the platform is used, including visits, interactions and performance. Where required by law, they are enabled only after the user makes the appropriate choice.
3.4. Advertising, measurement and attribution
These may be used to attribute visits and conversions to campaigns, measure advertising results, limit or personalize advertising, and associate interactions with campaigns from Google, Meta or other providers. They are subject to consent, opt-out or other requirements provided by the applicable jurisdiction.
3.5. Consent and privacy signals
These may record or transmit the user's choices within consent and privacy frameworks, including signals under the Transparency & Consent Framework (TCF) and Global Privacy Platform (GPP), where those technologies are present.
4. Jobzem first-party cookies
The following cookies and identifiers are set or used directly by Jobzem according to the features currently known:
| Name | Category | Purpose | Duration / condition |
|---|---|---|---|
jobzem_remember_me |
Authentication / user-requested preference | Records the user's choice to use the “Remember me” sign-in feature. | May remain associated with the “Remember me” feature for up to 6 months, unless removed or ended earlier. |
jobzem_remember_token |
Authentication / security | Stores the persistent token used to allow secure automatic sign-in on future visits when “Remember me” is enabled. | May remain valid for up to 6 months unless there is logout, revocation, credential change, cookie deletion or another security action. |
jobzem_consent |
Strictly necessary / consent | Records the user's cookie consent choice so the site can respect it on later visits. | Persistent; remains until the technically configured expiry, a change in choice or deletion by the user. The exact period may be adjusted by the platform. |
jobzem_app_prompt_seen |
Functional / preference | Indicates that the user has already seen the app suggestion modal, preventing repeated display over a short period. | Persistent for a period defined by the technical configuration; the duration may vary. |
jobzem_mobile_recent_searches_{country_code} |
Functional / preference | Stores recent searches made on mobile, segmented by country, such as br, us or another applicable country code. |
Persistent for a period defined by the technical configuration; may vary and may be deleted by the user. |
search_onboarding_seen |
Functional / preference | Records that the search onboarding has already been shown, preventing immediate repetition. | Persistent for a period defined by the technical configuration; the duration may vary. |
The periods above reflect the known behavior or technical purpose of each cookie. Where Jobzem has not yet defined or confirmed a fixed duration, we do not provide a numeric period in order to avoid inaccurate information.
5. Meta/Facebook — confirmed cookies
The following identifiers associated with Meta/Facebook technologies have been confirmed during use or inspection on Jobzem. They are used for advertising measurement and attribution when the corresponding integration is enabled and permitted by the user's choices:
| Name | Category | Purpose | Availability / duration |
|---|---|---|---|
_fbp |
Advertising / measurement / attribution | Browser-associated identifier used for Meta/Facebook advertising measurement and attribution. | Depends on Meta's configuration, consent, browser and region. The duration is defined by the provider's technology and may change. |
_fbc |
Advertising / attribution | Identifier related to a Meta ad click, typically associated with the presence of the fbclid parameter, used for conversion attribution. |
May appear only where there is a compatible click/campaign context. The duration is defined by the provider's technology and may change. |
6. Google and adtech — cookies that may appear
The cookies and identifiers below do not necessarily appear for every user or on every visit. Their presence depends on active tags, consent, region, Google products in use, advertising campaigns, browser and provider configuration.
| Name | Service / category | Main purpose | When it may appear |
|---|---|---|---|
_ga |
Google Analytics / Analytics | Helps identify or distinguish users/browsers for usage measurement. | When Google Analytics is enabled and permitted under the applicable consent configuration. |
_ga_<id> |
Google Analytics / Analytics | Cookie associated with a specific Google Analytics property or stream, used to maintain and measure session/use state. | May vary according to the configured property or stream identifier. |
_gid |
Google Analytics / Analytics | Helps identify or distinguish users within a shorter measurement window. | When the relevant product and configuration use this cookie. |
_gat |
Google Analytics / Performance | Historically used to help control analytics request rates. | May or may not appear depending on the Analytics version and configuration. |
_gcl_au |
Google Ads / Conversions | Supports campaign and conversion attribution associated with Google Ads and Conversion Linker products. | When the corresponding advertising/conversion tags are active and permitted. |
_gcl_aw |
Google Ads / Attribution | Stores information related to Google ad clicks for conversion attribution. | Typically associated with visits originating from Google Ads campaigns. |
_gcl_dc |
Google Marketing Platform / Attribution | Supports attribution for campaigns associated with DoubleClick/Google Marketing Platform integrations. | Only when the relevant integrations are used. |
IDE |
Google / DoubleClick / Advertising | Identifier used within Google's advertising ecosystem for ad delivery, measurement or personalization depending on the applicable configuration. | May be set or read in Google/DoubleClick advertising contexts and depending on consent/region. |
NID |
Google / Preferences and advertising | May be used by Google to store preferences and support personalization or advertising in Google services. | Depends on the Google services accessed or integrated and the user's choices. |
ANID |
Google / Advertising | May be used in advertising and personalization functionality within the Google ecosystem. | Depends on product, region, configuration and applicable consent. |
euconsent-v2 |
TCF / Consent | May store or represent the Transparency & Consent Framework (TCF) consent string for adtech vendors. | May appear when a TCF-compatible consent solution is active. |
addtl_consent |
Consent / Adtech | May record additional consent relating to vendors not covered by the standard TCF vendor list. | Only where the relevant consent solution uses this mechanism. |
gpp |
Global Privacy Platform / Privacy | May store or transmit global privacy and consent signals under the Global Privacy Platform. | May appear depending on the CMP, region and privacy configuration. |
gpp_sid |
Global Privacy Platform / Privacy | Indicates active GPP sections or states used to interpret privacy choices. | Depends on the implementation and applicable jurisdiction. |
The names, specific technical purposes and lifetimes of these identifiers may be changed by the providers themselves without Jobzem directly controlling those changes. The absence of a cookie during a particular visit does not mean the integration will never use it; likewise, inclusion in this table does not mean it will always be installed.
7. Consent and preference management
Where required by applicable law, non-essential analytics, advertising, attribution or personalization cookies and technologies should only be enabled after the user makes a valid choice.
Jobzem uses the jobzem_consent cookie to record the choice made through the consent mechanism. This choice may be used to allow, block or configure tags and technologies according to the categories accepted or rejected.
Users may change or withdraw consent choices through the cookie banner or preference manager provided by Jobzem, where that feature is available. Withdrawal should apply to future uses that rely on consent without affecting previous processing that was carried out lawfully.
Deleting cookies in the browser may remove the stored preference, causing Jobzem to ask for the user's choice again on a future visit.
In regions where the law requires prior consent for advertising cookies or similar technologies, simply continuing to browse, scrolling the page or using the site should not, by itself, be treated as valid consent for those technologies.
8. Advertising, measurement and attribution
Jobzem uses or may use measurement and advertising tools to understand traffic sources, assess campaigns and record conversion events.
This may include technologies from Meta and Google. Depending on the configuration, certain events — for example clicks, visits or conversion actions — may be associated with campaign or browser identifiers to assess advertising effectiveness.
Jobzem also uses Google Tag Manager as a tag-management tool. Google Tag Manager itself is used to manage the execution of tags; the cookies that are actually created depend on the tools and tags triggered through it.
Where required by law, non-essential advertising, analytics or attribution tags should respect the user's choice before they are triggered.
In certain U.S. jurisdictions, some uses of identifiers for behavioral or targeted advertising may receive specific legal classifications such as “sale,” “sharing” or “targeted advertising.” Where those rules apply to Jobzem, we will provide the transparency and opt-out mechanisms required by the relevant law.
9. Authentication cookies and “Remember me”
Session and authentication cookies are used to keep the user signed in and recognize the account state between requests.
When the user selects “Remember me”, Jobzem uses the identifiers jobzem_remember_me and jobzem_remember_token to maintain persistent sign-in functionality. This option may keep access recognized on that browser or device for up to 6 (six) months, unless ended earlier by logout, cookie deletion, password change, token revocation, a security risk or another need for re-authentication.
The persistent token should be used in a way that avoids storing the user's password directly in the cookie. Deleting these cookies may require a new sign-in.
10. Duration, expiration and deletion
Session cookies generally remain only while the session is valid. Persistent cookies remain until their expiry date, manual deletion by the user, revocation by the application or another technically defined event.
For first-party cookies where a specific duration has been confirmed, this Policy states that period. Where the duration has not yet been technically confirmed, we describe the purpose without inventing an expiry period.
Cookies and identifiers associated with third parties have durations defined by the relevant providers and may change depending on product, browser, region and configuration. Jobzem does not directly define those periods.
Users can delete cookies through browser settings. This may end the session, erase preferences, remove recent searches and require consent preferences to be configured again.
11. GPC, privacy signals and opt-out
Some browsers, extensions and systems may transmit privacy signals, including Global Privacy Control (GPC).
Where applicable law requires a particular signal to be recognized as a valid opt-out request, and Jobzem is subject to that requirement, we will seek to process the signal in accordance with the applicable legal and technical requirements.
In the United States, for example, certain state laws may require covered businesses to honor valid opt-out preference signals in relation to the sale or sharing of personal information or targeted advertising.
Do Not Track (DNT) does not have a uniform legal or technical interpretation across all jurisdictions. For that reason, choices expressly made through the cookie banner, preference manager and legally recognized privacy signals take priority according to the applicable law.
12. Third-party services and limits of control
Jobzem integrates third-party technologies, including, depending on the current configuration, services from Meta and Google. These providers may create, read, update or use cookies and identifiers associated with their services.
Jobzem may control the activation of certain tags integrated into the site where that activation is linked to its consent manager and the configuration of Google Tag Manager or equivalent technology. However, we do not fully control how third-party providers use their own identifiers, determine their duration, change their names or perform later processing under their own responsibility.
This distinction is important: the fact that Jobzem integrates a third-party technology does not mean that we can control all of the provider's later internal operations. Those activities are also governed by the relevant third party's policies, settings and legal obligations.
Authentication services such as Google or LinkedIn may also use their own cookies when the user is redirected to or interacts directly with their domains. Those cookies are not necessarily included in the Jobzem-domain inventory and are governed by the respective providers' policies.
13. International transfers
Analytics, advertising, authentication, consent or measurement technologies may involve providers with infrastructure located outside the user's country.
Where personal data associated with cookies or identifiers are transferred internationally, those transfers should comply with the mechanisms required by applicable data-protection law, as further described in our Privacy Policy.
The use of global providers may involve processing in different countries, subject to the safeguards, contractual protections and transfer mechanisms applicable to the relevant provider and its relationship with Jobzem.
14. Changes to this Policy
We may update this Cookie Policy when there are changes to the cookies used, providers, website functionality, advertising or analytics technologies, consent mechanisms or legal requirements.
The “Last updated” date identifies the current version. Where a change materially affects the purposes or categories of non-essential cookies, we may update the banner, request a new choice or take another appropriate measure where required by law.
Because third-party cookies may be changed by the providers themselves, we periodically review the inventory to keep this Policy aligned with the configuration observed on the site.
15. Contact
If you have questions about cookies, similar technologies or the choices available, please use our Contact Page.
For matters relating to personal-data processing, privacy rights, access, deletion, objection or other requests, please also refer to our Privacy Policy.
Because cookie preferences may be stored per browser or device, a change made on one device may not automatically be reflected on another.