Current cookie information
This page replaces the August 2022 PDF for the Snap Platform public website. For the related personal-data position, read privacy information.
About this website
This page concerns the Snap Recruitment website only. It does not make claims about cookies, analytics, advertising or storage used by third-party websites that you may visit through a link.
Managing your browser state
You can manage or clear cookies and site data in your browser settings. Clearing site data may affect preferences or in-progress activity on this website.
Use the Analytics preferences button at the bottom of any public page to review or change your analytics preference without clearing other site data.
For personal-data information, see privacy information.
Functional local storage
The keys snap.public-jobs, snap.my-work, snap.shift-fit.preferences and snap.employer-brief.draft are written only after you choose to save a job, remember a submission reference, save ShiftFit choices or save an employer brief draft. This functional state stays on the current device, is not sent to Snap merely by being stored, and can be removed from the relevant controls or by clearing site data.
My Work stores only public vacancy summaries and user-approved APP- or REQ- references. ShiftFit stores location, shift and licence/work-area choices for no more than 30 days. An employer brief draft stores only bounded workforce-planning fields for no more than 7 days. These stores must not contain email, phone, free-text notes, rates, purchase-order references, uploaded documents, consent choices or exact addresses.
Optional analytics consent and storage
The public site keeps non-essential analytics off until you choose to allow it. The snap_analytics_consent cookie stores the literal value granted or denied. The snap_analytics_consent_record cookie stores URL-encoded JSON containing consent, policyVersion (currently 2026-07-14) and an ISO updatedAt timestamp.
Both cookies use Max-Age=31536000, Path=/ and SameSite=Lax, with Secure on HTTPS. Missing, invalid, expired, mismatched or older-policy evidence is treated as no consent. A legacy plain granted value prompts for fresh consent; a record-less legacy denied value may be timestamped and retained as a denial.
Consented events are limited to jobs-board views, filtered searches and no-result searches, bounded ShiftFit checks, saved/compared/shared job actions, My Work view/action categories, brief-draft actions, status-lookup steps, job-alert journey steps, vacancy views, application starts and completions, and staffing-request starts and completions. Event records include the relevant page and allowlisted job, filter or flow categories plus the consent policy version and timestamp; they never include an IP hash, receipt reference, contact detail, free-text title, location, role or note. They are retained for 90 days, then removed by an hourly service-only database purge.
First-touch campaign and external-referrer attribution is held in sessionStorage for the current browser session only after consent is granted. Denial or revocation removes it immediately. An irreversible request hash is used only by an atomic 60-second rate-limit bucket, whose expired rows are purged at the minute boundary, and is never copied into an analytics event.