Cookie notice draft
Cookies, session storage, and analytics
This draft describes the limited tracking posture for launch. It should be reviewed before production marketing analytics are enabled.
Required Product Storage
Yrka uses authentication cookies and session storage needed to sign users in, protect routes, sync browser and server sessions, remember display mode, and operate the hosted product.
Required storage also supports account-bound routing, protected admin and employee surfaces, CSRF-resistant session handling through the platform stack, and the basic preference state needed to keep the app usable across page loads.
Blocking required product storage can prevent sign-in, route protection, session refresh, theme preference, or authenticated workflows from functioning correctly.
Marketing Analytics
The public site may use Vercel Analytics in production for aggregate page and performance measurement. Google Analytics 4 runs only after the visitor accepts the marketing analytics cookie. Yrka should not use advertising pixels or cross-site behavioral advertising unless the privacy policy, cookie notice, and subprocessor list are updated first.
Marketing analytics are for public-site measurement, such as page visits, performance signals, referral posture, and campaign effectiveness. They are not intended to profile employee behavior inside the authenticated workforce product.
If a future marketing program adds new tracking categories, the cookie notice, privacy policy, subprocessor list, and consent behavior should be updated before that tracking is enabled.
Customer Choices
Browser settings may block nonessential tracking, but required authentication/session storage is necessary for signed-in product access.
Visitors can use browser controls or site-level consent controls to decline nonessential marketing analytics where those controls are available. Declining marketing analytics should not block access to public marketing, legal, trust, or documentation pages.
Customers deploying Yrka to employees remain responsible for communicating their own workplace notice, monitoring, device, and browser-policy obligations to their teams.
No Advertising Pixel Baseline
Yrka's launch baseline does not rely on advertising pixels, cross-site behavioral advertising, or employee-product tracking for marketing retargeting. Adding those categories would require a separate review because they change the privacy and consent posture materially.
The authenticated app should remain focused on operating the customer workforce account. Product telemetry, support diagnostics, and security logs should be handled under the privacy and security posture rather than treated as marketing cookies.