Cookies & storage
A clear distinction between this static website, account sign-in cookies, and storage used by the extension.
Last updated: September 22, 2026
On the public website
The website uses a webact_language cookie, kept for up to one year, and local storage to remember your language and sync it with the extension in the same Chrome profile. This preference contains only language settings and an update identifier. Fonts and assets are served with the site.
When you change language, contact form drafts and help searches are temporarily kept in this tab’s session storage so you do not lose your text. They are removed after being restored on the translated page or when the tab closes. Account passwords are not saved this way.
This website uses Google Analytics to measure visits and page views. The Google tag loads when a page opens and may set analytics cookies to distinguish visitors and sessions. You can use your browser settings to block or delete cookies.
On the account service
Signing in uses a first-party cookie so the account service can recognize your session. The extension reads the permitted WebAct session and verifies it with the service in the same Chrome profile.
| Cookie | Purpose | Lifetime |
|---|---|---|
__Host-webact-session | Production sign-in session; Secure, HttpOnly, SameSite=Lax. | Up to 30 days; revoked earlier on sign-out or credential reset. |
__Host-webact-oauth | Temporary Google sign-in state when Google is configured. | 10 minutes. |
webact-sessionwebact-oauth | Development equivalents, used in a local preview service. | Same intended durations as the corresponding production cookies. |
These cookies belong to the account service. They are not created merely by browsing this static website.
The account page shares the same language preference with the public website and the extension. Changing it in any of them updates the others in the same Chrome profile. This preference is separate from your sign-in session.
Inside the extension
Chrome extension storage keeps preferences, launcher position, active workflow state, and account-scoped local libraries. This is separate from cookies on the landing website.
Local saved tasks and optional text history remain until removed, pruned by storage limits, cleared with extension data, or removed by uninstalling. Signing out clears visible account state but allows the same account’s local library to be restored on a later sign-in.
Other services
ChatGPT, Google sign-in, Stripe checkout, and your connected workflow platforms have their own cookies and storage when you visit or use them. WebAct’s static website does not set those third-party cookies for them.
Refer to the service you use for its own cookie controls. Blocking sign-in cookies can prevent the related connection from working.
Your controls
Use browser settings to inspect or remove site cookies. Removing a session cookie can sign you out; it does not itself delete your account, provider conversations, saved service tasks, or billing records.
For those distinctions, see Data controls & deletion. For the wider data flow, read the privacy policy.