Last updated: 13 September 2026
2. What LocalAction currently uses
LocalAction currently uses only cookies that are necessary to provide core functions such as authentication and security. We do not use advertising, marketing, or analytics cookies. LocalAction does not use local storage or session storage.
| Name | Purpose | Type | Duration |
|---|---|---|---|
__session, __client, and related Clerk authentication cookies | Clerk uses these cookies to authenticate business users, refresh short-lived session tokens, protect sign-in state, and let LocalAction retrieve the matching protected account. | Strictly necessary | Session-token cookies are short-lived and refreshed while the Clerk session remains valid. Other authentication cookies can remain until their Clerk or browser expiry, logout, revocation, or deletion in browser settings. |
3. How authentication cookies are protected
Clerk signs and rotates authentication tokens, uses short-lived session tokens, and applies cookie controls including secure production delivery and SameSite protection. Clerk's long-lived production client cookie is HttpOnly on the Clerk authentication domain. Its short-lived session cookie must be available to Clerk's browser SDK on LocalAction's domain and is refreshed while the session remains valid.
4. Analytics and public Action Pages
Public Action Pages can record simple events such as a page view, call, WhatsApp open, review click, or quote request. Those events are sent directly to LocalAction and do not use cookies, browser storage, visitor IDs, advertising IDs, or device fingerprints. Visiting a public Action Page does not cause LocalAction to set an analytics cookie.
5. Your controls
You can delete or block cookies using your browser settings. Because Clerk authentication cookies are required to recognise a signed-in account. Blocking or deleting them will prevent protected business pages from working or will sign you out. Public marketing and Action Pages remain available without these login cookies.
There is no optional LocalAction cookie category to accept or reject, so LocalAction does not display a cookie-consent banner or preference panel.
6. Third-party destinations
Clerk provides LocalAction's authentication and sets the strictly necessary cookies described above. LocalAction pages can also contain links to Google, WhatsApp, a business's website, email software, or telephone services. If you follow one of those links, the third party may use cookies or similar technologies under its own policy. LocalAction does not control cookies set after you leave our service. The marketing homepage also requests font files from Google's font service; LocalAction does not use that request to set its own cookie.
7. Changes to this policy
If LocalAction's use of cookies or browser storage changes, we will update this page and its “Last updated” date. If we introduce a non-essential cookie that requires consent, we will add an appropriate choice before using it.
8. Contact
Questions about cookies or privacy can be sent to support@local-action.com. You can also read our Privacy Policy or use the contact form.
Questions about this document? Visit our contact page or email support@local-action.com.