Cookie Policy

Version 1.0 — effective August 23, 2026. All humanizes policies.

In plain language

  • We use authentication cookies so you can sign in securely, and one seven-day preference cookie for the workspace sidebar.
  • We set no advertising, analytics, profiling or cross-site tracking cookies.
  • Affiliate referral attribution is the one non-essential thing we would store, so it is switched off until you can be asked to allow it.
  • Some drafts, interface settings and checkout state are kept in browser storage, which is not sent to us as a cookie.
  • Blocking authentication cookies means you cannot remain signed in or use the paid workspace.

Contents

  1. 1. Who this policy covers
  2. 2. Cookies and browser storage are different
  3. 3. Cookies we set
  4. 4. No advertising or analytics cookies
  5. 5. Local storage and session storage
  6. 6. Third-party requests and caching
  7. 7. How to control cookies and stored data
  8. 8. Global Privacy Control and Do Not Track
  9. 9. Changes to this policy
  10. 10. Questions and related information

1. Who this policy covers

This Cookie Policy explains how humanizes, the operator of humanizes.com uses cookies and other browser-side storage when you visit https://humanizes.com or use the humanizes service (the Service). It should be read with our Privacy Policy.

The inventory below reflects the Service as at the effective date at the top of this page. It distinguishes cookies from other technologies because they work differently and the legal rules applying to them are not always the same.

2. Cookies and browser storage are different

Cookie
A small text record associated with a website and stored by your browser. The browser ordinarily sends matching cookies with later requests to that site. Cookies can be session cookies, which end with the browser session, or persistent cookies, which remain until their expiry or deletion.
Local storage
A browser store available to scripts for the same website. Its values normally remain until the site or the user removes them. Unlike a cookie, a local-storage value is not automatically attached to HTTP requests.
Session storage
A browser store scoped to a tab or browsing session. Its values normally disappear when that tab or session closes and are not automatically attached to HTTP requests.
Cache
A local copy of a resource, such as application code or a font, kept so it can load faster or remain available offline. A cached resource is not a cookie.

4. No advertising or analytics cookies

WE DO NOT SET TRACKING COOKIES

WE SET NO ADVERTISING, ANALYTICS, PROFILING OR CROSS-SITE TRACKING COOKIES. WE DO NOT SELL OR SHARE PERSONAL INFORMATION FOR CROSS-CONTEXT BEHAVIOURAL ADVERTISING.

Under the EU and UK ePrivacy rules, storing or reading information on your device generally requires your consent unless it is strictly necessary to provide the service you asked for. Our authentication cookies, and the interface state described below, are used to deliver the Service you requested. There is no cookie consent banner today because nothing outside that necessary set is being stored.

One feature is deliberately switched off for this reason. Remembering which affiliate referred you is not necessary to run the Service, so it is not covered by that exemption. Referral attribution is therefore disabled in the application: it stores nothing on your device, and it will stay disabled until we ship a consent choice and you allow it. See the Affiliate & Paid Promotion Disclosure.

If we add any other non-essential cookie or storage, we will ask for consent before setting it wherever the law requires, and this policy will be updated with a new version and effective date first.

5. Local storage and session storage

The following values stay in your browser. They are not cookies and your browser never sends them to us as cookies. A value you choose to submit through the Service may separately be sent as part of that request.

Complete browser-storage inventory
KeyStoragePurposeTypical lifetime
humanizer.history.filterlocalStorageRemember the filter selected for humanization history.Until removed by you or the Service
humanizer.form.inputTextsessionStoragePreserve the current humanizer input within the browser session.Current tab or browser session
humanizer.form.modesessionStoragePreserve the selected humanizing mode within the browser session.Current tab or browser session
humanizer.prefill*sessionStorageCarry text into the humanizer or the AI detector within the browser session. Any suffix distinguishes the destination the text was sent to.Current tab or browser session
humanizer.rerun.*sessionStorageCarry the state needed to rerun a humanization request. The suffix distinguishes related values.Current tab or browser session
writer.form.*sessionStoragePreserve AI writer form state. The suffix distinguishes related values.Current tab or browser session
Pending-checkout keysBrowser storage on the pricing pagePreserve the selected checkout flow while sign-in or checkout is pending.Until the pending flow finishes, expires or is cleared
Insert Affiliate referral attribution — not currently activeBrowser storageWould remember which affiliate referred you, through sign-up, so the identifier pair can be included in Stripe Checkout metadata if a purchase follows. This is not strictly necessary to run the Service, so it is treated as requiring consent: nothing is stored today, and nothing will be stored until you are given a choice and allow it. Nothing is ever stored for an organic visit.Not applicable while inactive

6. Third-party requests and caching

The Service requests webfonts from Google Fonts at fonts.googleapis.com and fonts.gstatic.com. That HTTP request inherently reveals your IP address and user-agent to Google. We do not set a Google Fonts cookie and do not use that request for advertising or analytics.

A service worker may cache static application assets and font resources on your device for performance and offline availability. The cache is not a cookie, is not sent with every request, and can be removed using your browser’s site-data or developer settings. Providers involved in these requests are described in the Subprocessor list.

7. How to control cookies and stored data

Recent versions of Chrome, Edge, Firefox and Safari let you view, block and delete cookies and site data through their privacy or site settings. You can normally clear data for this site alone, block all cookies, or configure rules by site. Browser help pages give the exact steps for your version.

  • Deleting sidebar_state only resets the sidebar preference.
  • Deleting browser storage may remove an unfinished draft, selected filter, rerun state, referral attribution or pending-checkout state.
  • If you block or delete authentication cookies, you cannot stay signed in. Because an authenticated account and active paid plan are required to use the workspace, its protected features will not work until authentication cookies are allowed and you sign in again.
  • Private-browsing modes may clear cookies, storage and caches sooner than the lifetimes shown above.

8. Global Privacy Control and Do Not Track

Some browsers send Global Privacy Control (GPC) or Do Not Track (DNT) signals. We set no cross-context behavioural advertising cookies and do not sell or share personal information for that purpose, so there is no advertising cookie for either signal to stop. What the signal does do here is decide the optional categories for you: while it is on, every optional category — including referral attribution — is switched off, anything already stored under them is deleted, and the preference centre will not let them be switched back on until you turn the signal off in your browser.

Where an applicable US state law requires an opt-out preference signal to be treated as an opt-out request, we honour that signal as the request. DNT does not have one uniform legal or technical standard, but our no-tracking practice applies whether or not it is enabled. You can also make an opt-out or other privacy request through the privacy request form.

9. Changes to this policy

If our use of cookies or browser technologies changes, we will update the inventory, effective date and version history on this page. If a change introduces a cookie or device-storage use that requires prior consent, we will provide a choice before it begins where required by law.

10. Questions and related information

Questions about this policy can be sent to jakemorris@humanizes.com. For how we collect, use, disclose and retain personal data, read the Privacy Policy. For the providers involved in delivering the Service, read the Subprocessor list.

Version history

  • v1.0 — August 23, 2026: First version establishing a complete inventory of cookies and browser storage, the purposes and lifetimes of each, and the available controls.