Cookie Policy

How Barker uses cookies

This page explains cookies and browser storage Barker uses for authentication, security, product preferences, customer-link workflows, analytics, and performance monitoring.

Effective May 12, 2026

Current naming note

Some stored cookie or local-storage keys may temporarily retain legacy names while the Barker migration is completed. Those keys support the Barker product described here and do not change the privacy or security meaning of the storage.

Strictly necessary

Required for authentication, route protection, security checks, consent memory, and core Barker workspace operation.

Required for service operation

NameMechanismPurposeExpiryParty
barker_session / legacy session cookieCookieKeeps a signed-in company user or worker authenticated and protects app routes from anonymous access.7 days by default; cleared on logoutFirst-party
barker_cookie_consentCookieStores cookie consent choices so optional categories stay accepted or rejected across visits.365 days or until the consent version changesFirst-party
barker_mfa_pending / barker_mfa_verifiedCookieSupports multi-factor login checks and high-risk admin route gating.Session or until the MFA check is completeFirst-party
barker_user_type / barker_auth_role / barker_company_statusCookieStores route hints for owner, admin, sales, worker, and webmaster sessions so Barker can route requests without an extra database lookup on every page.7 days or cleared on logoutFirst-party

Functional

Remember product preferences and repeated workflow state such as table views, calendar selections, and local device settings.

Required for service operation

NameMechanismPurposeExpiryParty
barker-theme / barker-sidebar-densityLocal storageStores local display preferences such as theme, bold mode, and navigation density.Until browser storage is cleared or the preference is changedFirst-party
barker-table-*Local storageStores table sorting, filters, column visibility, and pagination for repeated operations workflows.Until browser storage is cleared or the view is resetFirst-party
barker_recent_jobs_*Local storageStores recently viewed jobs for faster navigation inside the signed-in workspace.Until browser storage is cleared or the list is overwrittenFirst-party
barker:calendar:*Local storageStores checked calendar selections and dispatch-view preferences for the signed-in user.Until browser storage is cleared or selections are changedFirst-party
barker_e2ee / barker_e2ee_device_idIndexedDB / local storageStores local device state for encrypted internal messaging where enabled. Clearing this storage may require device recovery.Until browser storage is cleared or the device is resetFirst-party

Analytics and performance

Help Barker understand public-site traffic, product usage, performance, attribution, and feature-test results. Barker does not use cross-site advertising cookies.

Optional where consent controls are available

NameMechanismPurposeExpiryParty
barker_utmCookieStores first-party marketing attribution parameters so Barker can understand which campaigns led to requests.30 daysFirst-party
barker:ab:distinct_idLocal storagePseudonymous browser identifier for feature tests and experiments when analytics is enabled.Until browser storage is clearedFirst-party
Vercel Analytics / Speed InsightsProvider scriptMeasures page views and performance so Barker can find slow pages and reliability regressions.Provider-controlled event storageThird-party
PostHogProvider scriptSupports product analytics, feature flags, and experimentation when analytics consent is present.Provider-controlled storage based on the configured project settingsThird-party

Choices and questions

Browser controls can delete cookies or block storage, but disabling strictly necessary storage may log you out or prevent Barker from loading protected pages. Product analytics controls are handled through Barker consent settings when enabled.

For privacy questions, email privacy@barkercrm.com.