DocxPacer Privacy Policy

DocxPacer (“the extension”) is a Chrome extension that types the contents of a .docx file you choose into a Google Docs document open in your browser. This policy describes exactly what data the extension touches, where it stays, and what it never does.

Your document never leaves your device

DocxPacer does not collect, transmit, sell, or share your document content, the names of the files you open, or the Google Docs you type into. Your .docx is parsed and typed entirely inside your browser. This is the core promise, and it has not changed. The only personal data we ever collect is the sign-in email of users who choose to subscribe to Pro (see “Pro accounts and sign-in” below); the free tier needs no account and no email.

Anonymous diagnostics (opt-out)

So we can find and fix crashes and understand which features get used, DocxPacer sends anonymous product-usage events and error reports. This is strictly limited:

• What is sent: a fixed, published list of event names (for example: panel opened, file loaded, typing started, typing completed, an error occurred) plus safe, non-identifying metadata — such as your chosen words-per-minute, whether Pro mode is on, a word count, and how long a session ran — tagged to a random identifier generated on your device that is not linked to your name or email.
• What is never sent: your document content, the file name, the Google Docs URL or id, your email, or your raw IP address. (An approximate country is derived at the network edge for coarse geography; the IP itself is not stored.)
• Where it goes: to our own endpoint at docxpacer.xyz, which forwards it to our diagnostics providers — see “Third parties” below.
• Turning it off: open the extension, click the account icon, and set “Share usage data” to Off. That immediately stops all telemetry and discards anything not yet sent. You can turn it back on the same way.

Pro accounts and sign-in

The free tier needs no account. If you choose to subscribe to Pro, you sign in with Google, and this is the only point at which personal data is collected:

• What we collect: your email address (via Google sign-in, using the “email” scope) and your Google account identifier, used solely to link your Pro subscription to you and to check your entitlement.
• Where it is stored: your email and entitlement (plan and expiry) are stored in our own database on Cloudflare so we can verify your Pro status. A signed token (JWT) and a cached copy of your email and plan are also kept in the extension’s local storage on your device.
• How it is used: the extension sends the signed token — never your document — to docxpacer.xyz to confirm your subscription.
• Payments: subscriptions are processed by Dodo Payments, our Merchant of Record. Card and billing details are handled by Dodo; DocxPacer never sees or stores your payment information.

If you never sign in, none of the above applies and no email is collected.

What stays on your device

The following data is created and stored only in your browser’s local extension storage (chrome.storage.local), under your own Chrome profile, and is never sent anywhere:

• The parsed contents of the most recent .docx file you opened in the extension, so you don’t have to re-pick it next session.
• Your pace settings (target words, edit minutes, break minutes), whether natural corrections are on, and whether resume is on.
• A resume checkpoint indicating roughly how far into a document the last typing session got.
• A random anonymous identifier and your “Share usage data” on/off choice (see “Anonymous diagnostics” above).
• If you sign in for Pro, a signed token and a cached copy of your email and plan (see “Pro accounts and sign-in” above).

You can clear this at any time by removing the extension or clearing site data for the extension in chrome://extensions.

What the extension reads from your computer

• A .docx file you explicitly pick using the file picker. The file is parsed entirely inside your browser (no upload). Only the parsed paragraph structure is kept (see above).

What the extension reads from the web

To support the “Resume where you left off” feature, the extension performs a single authenticated request to:

https://docs.google.com/document/d/<your-doc-id>/export?format=txt

…against the Google Docs tab you have open. This returns the current plain text of that document, which the extension compares against your source .docx to find where to continue from. The fetched text is used only in memory, only during the resume check, and is never written to disk or sent elsewhere.

This request uses your existing Google session cookie (the same one your browser already sends to Google Docs); the extension does not access, store, or transmit your Google account credentials.

Optional on-device AI (Gemini Nano)

If you enable Chrome’s built-in on-device AI (the Prompt API for Gemini Nano) in chrome://flags, DocxPacer may use it to generate paraphrased drafts as part of the natural-corrections rhythm. This model runs entirely on your computer; no text leaves your device. If the on-device model is unavailable, the extension silently falls back to a small rule-based reworder bundled with the extension. Either way, the network is never used for paraphrasing.

Permissions and why each is needed

• activeTab — to locate the Google Docs tab you intend to type into when the extension is opened.
• storage — to remember your settings and the last .docx you loaded.
• host_permissions for https://docs.google.com/* and optional_host_permissions for https://*.googleusercontent.com/* — required to type into, and (for resume) fetch the plain-text export of, the Google Docs document you have open. The googleusercontent.com origin is optional and requested at runtime only for resume. Typing itself uses standard keyboard events in the page, not the debugger API.

Third parties

Your document never leaves your device and is shared with no third party. Aside from your Pro sign-in email (handled as described in “Pro accounts and sign-in”), the only third parties that receive data are our diagnostics providers, and only the anonymous events described above:

• Sentry (sentry.io) — crash and error reports.
• PostHog (posthog.com) — anonymous product-usage events.
• Dodo Payments (dodopayments.com) — processes Pro subscription payments as Merchant of Record (only if you subscribe).

Sentry and PostHog receive data only via our own docxpacer.xyz endpoint (never directly from the extension), and neither receives your document, file names, email, or IP address. Aside from these, the only other outbound request is the docs.google.com export described above, made by your browser to Google as part of your own existing Google session.

Children’s privacy

DocxPacer is not directed at children under 13 and does not knowingly collect information from them. The free tier collects nothing; if you subscribed to Pro and want your email and account removed, email us (see “Contact”) and we will delete them.

Changes to this policy

If we ever change what the extension touches, this page will be updated and the extension’s version number will be bumped. The change history lives in the repository’s CHANGELOG.

Contact

For privacy questions, email kimindiehacker@gmail.com.