Privacy Policy — QuickReply

Last updated: April 19, 2026

Summary

QuickReply does not collect, transmit, sell, or share any user data. The extension ships with a 40-template starter library, supports smart variables ({{firstname}}, {{date+3d}}, conditionals, cursor placement), and exposes a sidepanel workbench — all running entirely inside your browser.

Data Collection

QuickReply makes zero network requests. The extension ships as a single static bundle; it does not load code, analytics, fonts, or any other resource at runtime. Nothing you type, paste, or insert is ever sent to us or to any third party.

Local Storage

QuickReply stores a small amount of data locally on your device via the Chrome storage.local API:

• Your templates — name, body, category, favorite flag, and per-template usage timestamps used solely to power the "Recent" sort inside the popup.
• Your settings — theme preference (system / dark / light) and the IDs of the two templates bound to your Alt+Shift+1 and Alt+Shift+2 quick-insert shortcuts.

This data never leaves your device. You can export every template as a JSON file at any time from Settings → Backup & restore, and you can delete everything by uninstalling the extension — Chrome clears the storage automatically.

Email Content

When you click Insert, QuickReply sends the expanded template text to the focused compose field on the active tab. It does not read any existing email content, recipient information, draft text, attachments, or email metadata. The content script only writes; it never reads page content.

Permissions

• activeTab — Used only at the moment you click Insert. The expanded template text is delivered to the focused compose field on the current tab via chrome.tabs.sendMessage.
• storage — Persists templates and settings on your device using chrome.storage.local.
• contextMenus — Adds a single right-click entry, "Insert Template…", that appears only when you right-click an editable element.
• sidePanel — Registers the QuickReply Workbench in Chrome's side panel surface (Chrome 114+), anchored to the right edge of your browser.

QuickReply requests no host_permissions. It cannot read the URLs you visit, attach observers to pages, or initiate background network requests.

Remote Code

QuickReply uses no remote code. All JavaScript, HTML, and CSS are bundled inside the extension package and shipped to Chrome unchanged. There is no eval, no Function() constructor, no scripts loaded from the network at runtime, and no WebAssembly fetched from a remote source.

Analytics and Tracking

QuickReply contains no analytics SDK, telemetry, crash reporter, tracking pixel, or third-party script. We have no visibility into how often you use the extension, which templates you favor, or whether you're using it at all.

Third-Party Services

None. QuickReply uses no payment processor, no font CDN, no error reporting service, no advertising network, and no cloud sync provider.

Children

QuickReply does not knowingly collect any information from anyone, including children under 13 — it collects no information from anyone at all.

Changes

If this policy changes, the updated version will be posted here with a new date. Material changes will be noted in the extension changelog and require a fresh review on the Chrome Web Store.

Contact

Questions? Email dev.abinovarghese@gmail.com