Cookie Policy

This page is informational and is not legal advice. It describes how Clox uses cookies and similar technologies and is read together with our Privacy Policy, which governs how personal data is handled.

1. What cookies and similar technologies are

A cookie is a small text file that a website stores in your browser. It lets the site remember information between pages and visits, such as whether you are signed in. Similar technologies, including browser local storage, let a site keep small amounts of data in your browser for the same kinds of purposes.

In this policy, references to cookies include these similar technologies. We describe below which of them Clox uses and why.

2. Strictly necessary cookies and storage

Some cookies and storage are needed for the Service to work, such as the ones that keep you signed in. Because they are essential, they do not need your consent and are always active.

• Sign-in: our authentication provider, Supabase, sets cookies that keep you signed in to the web app as you move between pages.
• QuickBooks connection: when a manager connects QuickBooks Online, a cookie named qbo_oauth_state protects the connection step. It expires after 10 minutes.
• Settings you choose: a cookie remembers for up to a year that you closed the getting-started panel, and your browser's local storage remembers your cookie choice, the last payroll export format you picked, the docs checklists you ticked, and whether a shared tablet has shown its kiosk tour.
• Offline punches: when the web app has no connection, it keeps your punches in your browser's storage until they reach Clox, and removes each one once it does.
• Rate limiting and other abuse protection run on our servers and set no cookie.

3. Analytics cookies

Clox uses two analytics tools in your browser. Both stay off until you accept analytics in the banner, and your choice applies to both.

• PostHog measures how people use our website at getclox.com and the web app, such as which pages they view. Once you accept, it keeps an identifier in a cookie and in local storage, both named after our PostHog project and starting with ph_.
• Google Analytics measures how visitors use getclox.com and whether they finish signing up. It loads on the website and on the sign-up steps. Once you accept, it sets its own cookies, such as _ga. When a visitor finishes signing up, it records the sign-up so that it can count as a conversion for our Google Ads. The sign-up record carries no company name, email address or account identifier.

4. Server records and what we do not use

Data from both tools is processed in the United States. Separately, our servers send PostHog a record of some account actions, such as starting or stopping a shift, exporting a timesheet or starting a subscription, so we can see how the product is used. These records set no cookie in your browser, and the banner does not turn them on or off. Our Privacy Policy describes them.

Clox does not set retargeting, social-media or other cross-site tracking cookies of its own, and does not sell your information. The only link between the website and advertising is the Google Ads sign-up conversion described above.

5. How to accept or decline

When you first visit, a banner asks whether you want to allow analytics. If you accept, PostHog and Google Analytics turn on in your browser. If you decline, they stay off and Clox works the same. The strictly necessary cookies and storage described above stay active either way, because the Service needs them.

We remember your choice in your browser's local storage, so you are not asked again on every visit. To change it, clear this site's data in your browser settings, and the banner appears again on your next visit. A different browser or device asks again too.

6. Managing cookies in your browser

You can manage or delete cookies through your browser settings. Most browsers let you block or remove cookies and clear local storage. Please note that blocking strictly necessary cookies may break sign-in and other core parts of the Service, so it may not work as expected if you do.

7. The mobile app

The Clox mobile app does not use cookies and runs no analytics tool. It keeps your session in encrypted storage on your device. Actions it sends to Clox can be among the server records described above.

8. Maps

The worksite map and the team map load their map tiles from MapTiler, or from OpenStreetMap's tile servers where MapTiler is not set up, directly from your browser. As with any request your browser makes, the tile server receives standard request information such as your IP address. Address lookups for worksite setup go from our servers to LocationIQ, with OpenStreetMap's Nominatim service as a fallback, so those services see our server's request, not your browser's.

9. Changes and contact

We may update this Cookie Policy from time to time. When we make a change, we will revise the effective date shown at the top of this page.

If you have questions about this Cookie Policy, email us at support@getclox.com. For more detail on how we handle personal data, see our Privacy Policy.