Last updated 13 October 2026.

Cookie policy

This policy explains the cookies and browser storage used by Blurwrite, what they do and how long they last. It also explains what happens if you delete or block them. We are a software company based in the United Arab Emirates. For details about how we handle other data, read our privacy policy.

What cookies are

Cookies are small pieces of data that a site places in your browser. They let the site recognise information between requests, such as whether you are signed in or which browser is using a free tool.

Browser storage also holds information in your browser, but it is separate from cookies. We use it for the editor's scroll position, saved detector reports and support chat. Some storage lasts only while a tab is open; other storage stays for the period described below or until you clear it.

Cookies we set

For visitors without an account, anon_id gives the browser an identifier so we can count free tool uses. It is used for free limits, not advertising.

The cookies __Host-sb-access-token and __Host-sb-refresh-token keep you signed in. Their purpose is to maintain your sign-in, rather than make you sign in again as you move around the site.

The cookie __Host-signed_in tells the page header that you are signed in. It holds no secret. This header cookie has a different purpose from the cookies that keep your account signed in.

The cookie details displayed in this section list their names, purposes and lifetimes. Browser storage is described separately below because it includes information that is not held in cookies.

Name	What for	How long
anon_id	Counts free uses for a visitor without an account.	1 year
__Host-sb-access-token, __Host-sb-refresh-token	Keeps you signed in.	30 days
__Host-signed_in	Tells the page header you are signed in. It holds no secret.	30 days
editor-offset (tab storage)	Keeps the editor's scroll position while the tab is open.	Until the tab closes
Detector reports (browser storage)	Your saved detector reports.	24 hours
Support chat (browser storage)	Keeps your chat conversation open across pages.	Until you clear it
_ga, _ga_<ID>	Our analytics service: tells visits apart, so each is counted once.	2 years

Browser storage

The editor uses editor-offset in tab storage to keep its scroll position while the tab is open. This storage lasts until the tab closes. Its purpose is to remember where you are in the editor.

Saved detector reports are kept in your browser, not on our servers. They are kept for 24 hours. A report older than 24 hours is not shown again and is deleted the next time you open any page of the site.

Support chat uses browser storage to keep your conversation open as you move between pages. This storage remains until you clear it. Closing a tab is therefore not the same as clearing the support chat storage.

These storage uses have separate lifetimes. The editor position ends with the tab, detector reports have a time limit, and support chat storage stays until you clear it.

How we count free use

To enforce free limits, we keep a keyed hash of your IP address and your browser's cookie id, per tool and UTC day. Daily limits reset at midnight UTC. We keep today's and yesterday's counts; older days are deleted at the next count.

These counts are pseudonymised, not anonymous. The browser identifier is part of the counting system, but it is not the only part: the keyed IP address hash also counts.

Per-minute limits work the same way. We keep the current minute's and the previous minute's entries, and older entries are deleted at the next request.

Clearing anon_id does not reset your free limits. Deleting that cookie removes the browser identifier, but it does not remove the IP hash used to count use.

No advertising or tracking cookies

We use no advertising or tracking cookies. The cookies used for free limits and sign-in serve those functions, not advertising.

When analytics is switched on, its cookies are used only to count visits and improve the site, never for advertising. The analytics information shown on this page explains that use separately.

Managing cookies and browser storage

You can delete or block cookies through your browser's settings. Use its cookie or site data controls to remove cookies for this site or block them. You can also clear the browser storage described above through the browser's site data controls.

Blocking the sign-in cookies signs you out. If you want to stay signed in, those cookies are needed for that function.

Clearing browser storage removes the information held there, such as saved detector reports or the stored support chat conversation. Clearing anon_id does not give you a new free allowance, because the IP hash also counts.

Deleting browser cookies or storage is separate from deleting your account. To have your account deleted, write to support@blurwrite.com.

Changes to this policy

When this policy changes, we publish the new version here, with its date at the top of the page.

Contact

If you have questions about cookies, browser storage or anything in this policy, write to support@blurwrite.com. A person answers within 24 hours.

Analytics while it is switched on

While analytics is switched on, we set _ga and _ga_<ID> for every visitor, with no consent step. They help tell visits apart so each is counted once.

The analytics service sees the page address, your browser and device, and an approximate location from your IP address. We use analytics only to count visits and improve the site, never for advertising.