Cookie Policy
Version 2026-10-06.2
1. Current approach
StudioTasker is designed to minimise tracking. The core customer workspace uses strictly necessary authentication/session technology so signed-in users can securely access the correct studio workspace.
2. Necessary session cookie
| Purpose | Type | Why needed |
|---|---|---|
| Authenticated StudioTasker session | HTTP-only, secure in production, SameSite=Lax session cookie | Keeps a signed-in user authenticated and helps prevent client-side scripts from reading the session token. |
3. Demo browser storage
The public interactive demo may use browser session storage to remember temporary demo choices, demo limits and visual customisation during the current browser session. This data is sample/demo state and is not intended for real personal information.
4. Analytics, advertising and Paddle
StudioTasker does not enable Google Analytics, Meta Pixel, behavioural advertising cookies or similar marketing trackers in the initial production configuration. If optional analytics or marketing technologies that require consent are introduced later, this policy and the consent interface will be updated before those technologies are enabled for affected users.
Paddle checkout technology is loaded when a signed-in studio owner deliberately starts subscription checkout. Paddle may use its own necessary checkout/security technologies as an independent controller for its transaction processing. StudioTasker does not load Paddle checkout merely for general page-view analytics.
5. Browser controls
You can delete or block browser storage through your browser settings. Blocking strictly necessary authentication storage may prevent the customer workspace from functioning.