Cookie and Local Storage Notice

1. What this notice covers

Cookies are small text files stored by a browser. Local storage is a browser feature that keeps a small amount of information on a device. This notice covers the WorkPulse website and Service. It should be read with our Privacy Notice.

2. Strictly necessary cookies

WorkPulse uses Laravel's session and security mechanisms to keep a user signed in, protect forms from cross-site request forgery and maintain a selected workspace. These technologies are necessary for the website and Service to work, so they cannot be disabled through a preference control.

Technology	Purpose	Typical duration
Application session cookie	Keeps the authenticated session and related server-side state available while a user uses the Service.	Configured by the deployed environment; the application default is 120 minutes of inactivity.
CSRF/session security token	Helps protect forms and state-changing requests against cross-site request forgery.	Session duration.
Remember-me cookie	Only used if a user actively selects a “Remember me” or equivalent sign-in option.	Configured by the application and browser.

The exact cookie names can vary with the application configuration. The application is configured to use HttpOnly and SameSite=Lax session-cookie controls by default; the secure-cookie setting depends on the production deployment.

3. Local storage used by the Service

The current web application uses browser local storage for functionality, rather than for advertising or cross-site tracking. Examples include:

• timeTrackerState, which remembers the state and position of the in-browser time-tracking panel; and
• workpulse_tour_step and workpulse_tour_completed, which remember product-tour progress.

Removing this local storage in your browser may reset those interface preferences. It does not delete your server-side account or work records.

4. No advertising or analytics cookies in the current application code

We have not identified Google Analytics, advertising, behavioural-profiling or session-replay cookies in the current WorkPulse application source. We do not use the cookie names previously described as platform_analytics, performance_metrics or feature_usage.

If WorkPulse adds a non-essential analytics, advertising or similar technology, we will update this notice and obtain consent where required before setting it.

5. Third-party services

Some actions use third-party services. For example, a Stripe-hosted checkout may use Stripe's own technologies to process a payment, and a browser or mobile notification service may use device-level identifiers or a push subscription. These are governed by the third party's own notice:

• Stripe Privacy Center for payment checkout and billing;
• Firebase privacy information for mobile push notifications when enabled; and
• the applicable browser or operating-system provider for browser push notifications.

The public site also requests fonts and icon resources from third-party content-delivery services. Those providers receive ordinary web-request information such as IP address and browser information when your browser requests the resource. Their use of cookies, if any, is governed by their own policies.

6. Controlling cookies and local storage

You can block or remove cookies and local storage through your browser settings. Doing so may prevent sign-in, form submission, workspace selection, push notifications or other Service features from working correctly. Browser settings usually allow you to delete site data, block third-party cookies and manage notifications separately.

For help with the Service, contact support@workpulse.solutions.

7. Changes

We will update this notice when our use of cookies, local storage or third-party technologies changes. The current version is available on this page.