The cookies and browser storage Logpagia sets, what each one does and how long it lasts. The marketing website sets cookies only after a visitor opens the chat.
Effective 14 October 2026Published by Logpagia Technologies LLC, 5900 Balcones Drive, Suite 100, Austin, Texas 78741, United States. Questions go to privacy@logpagia.com.
Last reviewed against the current source on .
This notice, published by Logpagia Technologies LLC, covers the Logpagia marketing website, the Logpagia workspace applications and the signing pages. Pagenia publishes its own cookie notice for the talent marketplace.
Every cookie listed here belongs to a Logpagia address and serves security, sign-in, a display preference or a chat the person opened. Logpagia sets no advertising or analytics cookies.
The marketing website sets no cookies and writes nothing to browser storage while a visitor reads it. Its content security policy allows scripts, styles, fonts and images from the website’s own address, plus the chat script and chat window from Logpagia’s support desk at support.logpagia.com, which load only when a visitor chooses Chat with us. The website loads no analytics or advertising, and its typeface is served from its own address.
Choosing Chat with us opens Logpagia’s self-hosted support desk in a chat window. Two cookies keep the chat working. cw_conversation, on the marketing website, holds a conversation token so the visitor can return to the same conversation; it lasts 365 days, and the token inside it expires after 180 days. Deleting it starts a new conversation. _chatwoot_session, on support.logpagia.com, secures the chat window and ends when the browser closes. The chat window also keeps two lists in support.logpagia.com’s own storage: the team members available to answer, refreshed after 24 hours, and the chat campaign list, which is always empty and is refreshed after an hour. Both stay until the chat window refreshes them or the visitor clears site data.
The server that answers each request records the requested page, network address and browser details in its logs, as described in the privacy policy.
The workspace applications and signing pages set the following cookies. The first two are strictly necessary; the service cannot keep a person signed in without them.
The workspace applications keep the short-lived access token in memory only; it is never written to a cookie or to browser storage.
Local and session storage hold interface state on the person’s own device: panel widths, collapsed sections, a dismissed setup guide, the batch a person is working on and similar view choices. The signing app stores a digest of each signing link, never the link itself, so reopening the same email resumes the session, and keeps at most 20 such entries. Help and support stores the signed-in person’s Logpagia user identifier under logpagia.support.identifier, so the chat starts fresh when someone else signs in on the same browser. The Help and support chat window keeps the same two lists, available team members and an empty campaign list, in support.logpagia.com’s own storage. Clearing site data resets these choices.
Paying for a subscription opens Stripe’s checkout page, which sets its own cookies under Stripe’s policy. When a deployment turns on the automated-submission check for public signing forms, Cloudflare Turnstile loads on that form under Cloudflare’s policy. A Health application such as RevMind 360 opens on its own address with its own cookie notice.
Logpagia uses no optional analytics or advertising tracking today, so it offers no cookie preference center. Continued browsing is never treated as consent.
If Logpagia adds optional tracking later, it first adds a working choice and withdrawal control and updates this notice with each cookie, vendor, purpose and duration.
Browser settings can block or delete cookies and site storage. Blocking the sign-in cookies prevents signing in to the workspace applications and the signing pages. Deleting the preference cookies returns the appearance to its default.
Logpagia updates this list whenever a cookie is added, changed or removed, and publishes each revision on this page with its effective date. Questions go to privacy@logpagia.com.