Active development is paused. The audit tool, credit purchases, and existing balances stay operational — no plans to take it down. Credits remain valid until used.
How the Avoid AI Writing browser extension handles your data.
The pattern scan runs locally in your browser. It does not transmit, log, or store the scanned text on any server. No account is required to use the pattern scan.
Your text only leaves your browser when you explicitly click the deep-audit or rewrite button. That sends the text to avoidaiwriting.com for a Claude-powered audit, which costs credits. To hold a credit balance and view your audit history, you can optionally sign in with an email magic link or a Solana wallet. Pattern scanning works fully without signing in.
The extension uses two storage areas, both scoped to your local browser profile. Nothing is synced across Chrome profiles, and the extension does not use any third-party storage.
chrome.storage.local persists:chrome.storage.session is used briefly when you click the deep-audit button on a page's floating panel (the in-page handoff to the web app — separate from the popup deep audit described below). The text is read by the web app immediately, the entry is removed within 60 seconds, and the entire session area is cleared when the browser session ends.Nothing else is stored. Scanned text itself is never persisted to disk by the extension. It lives in memory while the results panel is open and is discarded when the panel closes.
Retention. Options preferences persist until you change them or uninstall the extension. Session token, email, and cached credit balance persist locally until you click Sign Out (the server invalidates the token at the same time) or until 90 days of inactivity, whichever is sooner. Pending pair-handshake state is cleared within 10 minutes (sooner if the handshake completes or you cancel). Audit history saved on avoidaiwriting.com/history is retained until you delete individual entries or close your account; you can also disable history retention from that page.
The extension makes network calls only in the following situations, all of which require explicit user action:
There are two ways to start a deep audit, and they use different transports:
avoidaiwriting.com/api/audit containing your text and your session token. The result is rendered back inside the popup. One audit credit is consumed.chrome.storage.session and opens a new tab to avoidaiwriting.com/rewrite. The web app reads the stashed text via a same-origin postMessage, then clears the stash. Your text is not included in the URL. If chrome.storage.session is unavailable (rare), the extension falls back to a URL-fragment handoff (#text=...); URL fragments are not sent over the network and don't appear in access logs or Referer headers.In both paths your text is sent only to avoidaiwriting.com (which is Fernwillow Holdings LLC's server, the publisher of this extension). avoidaiwriting.com forwards the text to Anthropic's Claude API for the audit under Anthropic's data-processing terms. Anthropic does not use the text to train models. The audit input and result are saved to your account history at avoidaiwriting.com/history if you are signed in, so you can revisit past audits. You can delete individual entries or disable history retention from that page.
If you click Sign In, the extension calls avoidaiwriting.com/api/auth/extension/pair-init to start a pairing handshake, opens a tab to the avoidaiwriting.com sign-in page, and polls avoidaiwriting.com/api/auth/extension/pair-claim until you complete the magic-link or wallet flow on the web side. No scanned text is sent during sign-in — only the pairing tokens. On success the server returns a session token, which is saved to chrome.storage.local as described above.
When the popup opens for a signed-in user, the extension fetches your current credit balance from avoidaiwriting.com/api/credits with your session token. No text is included in this call.
Clicking Sign Out tells avoidaiwriting.com/api/auth/extension/revoke to invalidate the session token on the server, then removes the token and email from chrome.storage.local.
No other network calls are made by the extension. There is no telemetry, no analytics, no third-party SDKs.
Sign-in is fully optional. Pattern scanning works without it. You might choose to sign in to:
Sign-in methods are email magic link or Solana wallet signature. What we receive on sign-in is described in the site privacy policy.
manifest.json and grows over time.If you are in the EU, UK, California, or another jurisdiction with a formal data-protection framework, you have the right to:
To exercise any of these rights, email support@fernwillowholdings.com. We aim to respond within 30 days.
California residents: Fernwillow Holdings LLC does not sell or share your personal information for cross-context behavioral advertising, as defined by the CCPA/CPRA. We have not done so in the preceding 12 months.
If this policy changes, the updated version will be posted at this URL. Material changes that affect how user data is handled will be reflected in the extension's manifest.json as a version bump.
Last updated: May 16, 2026 (v1.2.0 — added disclosures for optional sign-in, popup-direct deep audit, credit balance fetch, and wallet payment; detection expanded from 36 to 43 categories with structural, social-template, stylometric, and AI-tool-fingerprint detectors).
The Avoid AI Writing browser extension is published by Fernwillow Holdings LLC, a Washington limited liability company. Fernwillow Holdings LLC is the data controller for personal data the extension collects, which is limited to: locally-stored preferences; for signed-in users, an email address and a session token; and audit inputs and results submitted on explicit user action.
Mailing address:
5729 Littlerock Rd SW Ste 107 PMB 252
Tumwater, WA 98512-7386
United States
Contact email: support@fernwillowholdings.com
Questions about the extension's data practices: email support@fernwillowholdings.com, reach out via @avoidaiwriting on X, or post in Telegram.