Legal

Cookie Policy

Revision 4
Effective: October 20, 2026

Versions

Revision 4 · October 20, 2026 · Current
Clarifies optional analytics and advertising, regional defaults, first-party storage, and local file cleanup without treating every preference as strictly necessary.
Revision 3 · September 23, 2026 · Previous

This Policy explains cookies, local storage, tags, and similar technologies used by LW Agency Limited (Hushscript). Read it with our Privacy Policy and Sub-processor List.

Optional analytics and advertising

Analytics and advertising are optional. Use Cookie settings in the website footer to change them. Declining them does not prevent account transcription or purchases.

Where prior consent is required, these categories remain off until you choose. Elsewhere, both are enabled by default. Saved choices control later processing. We honor Global Privacy Control as an advertising opt-out; it does not disable analytics.

The marketing website can load Google Analytics and Google Ads through Google Tag Manager. Campaigns may also use Meta, LinkedIn, X, Microsoft Advertising, and LY Corporation. These technologies measure visits, conversions, and advertising, and may support remarketing using cookie or click identifiers.

The application does not load browser analytics or advertising scripts. Our API can send content-free action and transaction events to analytics and advertising providers, subject to the same choices and regional rules. These events exclude recordings, transcripts, filenames, titles, prompts, and form or clipboard contents. To stop optional server-side measurement too, use Cookie settings; blocking cookies in your browser alone may leave that saved choice unchanged.

Essential and functional technologies

Sign-in, security, payment processing, and consent storage support requested Service functions. Other functional records remember language/theme choices, referral attribution, and on-device file recovery. These functions are distinct from analytics and advertising; not every functional record is essential to every visit.

The Cookie settings controls apply to analytics and advertising. Functional records are managed through the relevant feature, account settings, or browser controls. You can block storage in your browser, but a feature may not work if the storage it needs is unavailable.

Stripe may use payment and fraud-prevention cookies when you use payment features. Cloudflare Turnstile processes requests on protected forms and tests to detect automated abuse and may use cookies. See Cloudflare’s Turnstile policy.

First-party cookies

These records are used on our own sites, with sharing between the website and application where applicable:

Cookie	Purpose	Set lifetime
`hs_consent`	Analytics and advertising choice	6 months
`hs_consent_required`	Whether prior consent is required for the visitor’s region	24 hours
`hs_geo`, `hs_region`	Approximate country/subdivision for consent defaults	24 hours
`hs_locale`	Language preference	6 months
`hs_theme`	Appearance preference	6 months
`hs_login_initiator`	Links an email sign-in request to its initiating browser	15 minutes

A record may be refreshed by later use or replaced when you change a setting. Browser controls can remove it earlier.

Browser storage and local files

Local storage is separate for each site and is not automatically attached to requests like a cookie.

hs_attr_v1: first-touch attribution on the marketing site, used for up to 90 days. It can contain campaign parameters, click IDs (gclid, gbraid, wbraid, fbclid, li_fat_id, twclid, msclkid, yclid), analytics/ad cookie IDs, and landing/referrer addresses with query strings removed. Analytics fields require the analytics choice; ad fields require the advertising choice. Withdrawing a choice removes the fields it covers. Attribution may pass to the application in a link.
hs_ref_v1: an optional referral link’s code, used for up to 90 days to attribute a new account. It is separate from advertising attribution.
Preferences and session state: hs-theme on the website; sign-in token, preferences, and cached views in the application. Clearing application storage signs you out locally.
Local file storage: where supported, the free recorder stores audio on your device for recovery. On a later visit, cleanup removes older interrupted recordings and those over 7 days old. Tools also write temporary output files and clear them when released or during later cleanup. These files are not uploaded by the local tools. Browser clearing or storage limits may remove them sooner.

The optional Chrome extension has separate local storage, described in the Privacy Policy.

Your controls

Change analytics and advertising through Cookie settings. You can also delete or block cookies, local storage, and local files in your browser. Clearing consent records may restore regional defaults on a later visit; make your choice again if needed. Your choice controls future processing. It does not automatically remove data a provider already lawfully received; the Privacy Policy explains how to request access or deletion where applicable.

Additional Google controls: Analytics opt-out and ad preferences.

Changes and contact

We publish updates with an effective date and retain the preceding version. If you need help with these settings, contact support@hushscript.com.