Cookie and Local Storage Policy

The extension uses chrome.storage.local, rather than website cookies, for:

• authentication tokens, the signed-in email address, and user identifier;
• signed-out hide and restore actions that may later synchronize after sign-in;
• short-lived pending checkout information used to synchronize a subscription; and
• development controls that are not part of normal production use.

The current extension actively deletes the legacy database named DB. It does not use IndexedDB as an active store for resumes, job history, account data, or AI results. Authenticated product history is stored by the JobFitsMe backend as described in the Privacy Policy.

The website uses first-party local storage to remember whether you accepted or rejected optional analytics. The record includes a consent-policy version and decision time. A missing, malformed, or older-version record is treated as no decision, with analytics disabled until you choose again.

Only after acceptance, enabled analytics may use first-party local storage to remember the first landing page, referral and UTM campaign values, and first-visit time. Session storage may record whether a returning visit was already counted in the current browser session. These values do not contain account, resume, job, billing, or AI content.

Your browser may also cache static website files and fonts as part of normal web delivery.

Optional analytics is disabled by default. After you explicitly accept and JobFitsMe's separate analytics kill switch is enabled, the website may load Contentsquare to understand page visits, interactions, scrolling, device/browser context, approximate location, and session behavior. Contentsquare may use first-party cookies and similar identifiers under its own privacy terms.

Mixpanel and Google Analytics integrations exist behind the same consent gate but are not approved as active production processors in this revision. We will update this policy before activating either service in production. JobFitsMe does not use website analytics for personalized advertising or intentionally join it to your extension account.

The first-visit panel offers equally prominent Accept analytics and Reject analytics choices. The persistent Analytics preferences button lets you review or change the recorded choice later. Rejecting does not prevent use of the website.

When you withdraw a previous acceptance, the website records rejection, stops future provider loading and events, clears known first-party analytics storage, and invokes available provider controls. For Contentsquare, it sends the documented optout command, which removes other Contentsquare cookies and may leave a _cs_optout cookie recording the exclusion. For configured Google Analytics and Mixpanel integrations, it applies their disable or opt-out behavior and clears the current analytics identity or persistence where available.

You can also clear or block cookies, local storage, and session storage in your browser. Browser privacy controls and content blockers may provide additional controls, although their effect depends on the browser and provider.

We will update this policy when storage or analytics practices materially change. Questions can be sent to [email protected].