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.
What we collect: nothing.
DocxPacer does not collect, transmit, sell, share, or transfer any personally identifiable information, document content, or usage analytics to any server operated by us or any third party. The extension does not run any analytics SDK, crash reporter, advertising network, or telemetry pipeline.
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
.docxfile 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.
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
.docxfile 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, tabs — to locate the Google Docs tab you intend to type into when the extension is opened as a standalone window.
- storage — to remember your settings and the last
.docxyou loaded. - debugger — Google Docs uses a canvas-based editor that does not respond
to standard DOM input events. The Chrome
debuggerAPI is the only reliable way to send keystrokes into Google Docs. The extension attaches the debugger to a singledocs.google.comtab only while you have actively started a typing session, and detaches as soon as the session stops or you click Stop. It is never used to read page content. - host_permissions for
https://docs.google.com/*andhttps://*.googleusercontent.com/*— required to send keystrokes into, and (for resume) fetch the plain-text export of, the Google Docs document you have open.
Third parties
None. DocxPacer talks to no servers operated by us. The only outbound network
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. Because the extension collects nothing, there is also nothing to delete.
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 kaizokagenou@gmail.com.