Updated 27 September 2026. This policy explains how ClockIN uses cookies and similar browser storage in the current beta product.
ClockIN uses session and authentication cookies so you can sign in, stay signed in, complete security checks, recover access and use protected account features. These cookies are necessary for the service to work and are not used to build advertising profiles.
ClockIN may use short-lived browser or cookie state for security, login continuity, trusted-device or multi-factor authentication flows, and other settings needed to complete a feature safely. Similar temporary state can also be stored in the browser for a specific workflow.
ClockIN currently measures product activity mainly from first-party account and product records, such as coarse daily-active markers and feature events already created by normal use. We do not currently use third-party advertising cookies or a general third-party behavioural analytics cookie stack such as Google Analytics, Meta Pixel, Mixpanel or PostHog on the main ClockIN product.
If you intentionally open a third-party checkout, meeting, form or other embedded/external service, that provider may set cookies or similar technologies under its own policy. Examples can include a supported payment provider, Jitsi Meet, Google Forms or another provider used for the feature you chose to open.
You can block or delete cookies in your browser settings. Blocking essential authentication cookies can prevent sign-in, security checks or protected ClockIN features from working. Where ClockIN later introduces non-essential cookies that require a choice, we will add the appropriate consent controls before using them.
We will update this page if ClockIN adds material new cookie-based analytics, advertising, personalization or other tracking. The policy should be reviewed whenever a new browser-side provider is added.
See the Privacy Notice for broader data handling and the service-provider page for providers used by ClockIN.