Privacy Policy · Screen Capture Tool
🛡️

Your Privacy,
Our Promise

This policy explains exactly what data Screen Capture Tool accesses, what it does with it, and — most importantly — what it never does. No legalese. Just honesty.

📵
No Data Collected
zero · ever
🌐
No Network Requests
100% offline
🔒
No Third Parties
no analytics · no ads
Privacy Policy
📋
1. Overview
Who we are and what this extension does

Screen Capture Tool ("the extension", "we", "our") is a Chrome browser extension developed by Bishnu Kartik Sah, an independent developer based in Nepal. The extension is published on the Chrome Web Store under the name "Screen Capture Tool — Full Page Screenshot".

The extension's sole purpose is to capture screenshots of web pages and save them to the user's local device. It supports four capture modes — visible viewport, full scrolling page, rectangular region, and circular region — and exports images as PNG, JPG, or PDF files.

We are committed to your privacy. This policy is a plain-language description of everything the extension does and does not do with your data. If something is unclear, please contact us using the details at the bottom of this page.

🚫
2. Data We Do Not Collect
An explicit list of what we never touch

Screen Capture Tool does not collect, store, transmit, or share any personal data whatsoever. Specifically, the extension never accesses or records:

  • Your name, email address, or any account information
  • Your browsing history or the URLs of pages you visit
  • The content of pages you capture (screenshots stay on your device)
  • Cookies, login sessions, or authentication tokens
  • Your IP address or geographic location
  • Device identifiers, hardware information, or OS details
  • Keystrokes, clipboard contents, or any form inputs
  • Usage statistics, analytics, or telemetry of any kind
  • Crash logs or error reports sent to any server
🔍
3. What the Extension Accesses — and Why
Transparent breakdown of every permission

The extension requests several Chrome permissions to perform its screenshot functions. Here is exactly what each one accesses and why it is strictly necessary:

Tab screenshot (activeTab + tabs)
When you click "Capture Screenshot", the extension uses chrome.tabs.captureVisibleTab() to take a screenshot of what is currently visible in your browser window. The tab's hostname and title are read only to suggest a default filename (e.g. github.com-2025-06-01) in the rename dialog. This information is never stored or transmitted.

Script injection (scripting + host permissions)
For full-page capture, scripts are injected to measure the page's total height, scroll it in sections, and temporarily hide sticky navbars. For rectangle and circle capture, a selection overlay is injected so you can draw a region on the page. These scripts run only when you actively initiate a capture, remove themselves immediately after, and do not read or transmit any page content.

Temporary session storage (storage)
After a region capture, the cropped screenshot (a base64 PNG string) is briefly stored in chrome.storage.session — a temporary, in-browser-only store that is cleared when the browser closes — so it can be passed from the background service worker to the popup. The data is deleted from storage immediately after the popup reads it. Nothing is written to chrome.storage.local or chrome.storage.sync.

File download (downloads)
The chrome.downloads.download() API is used solely to save your named screenshot file to your local Downloads folder. No file is uploaded to any server at any point.

✓ What we DO
  • Capture a screenshot of the current tab when you click the button
  • Temporarily store screenshot data in session memory to pass between components
  • Save the file to your Downloads folder with your chosen filename
  • Read the tab title/URL to pre-fill the filename suggestion
✗ What we DON'T
  • Send screenshots or any data to any server
  • Store anything beyond the current browser session
  • Run any code on pages you haven't chosen to capture
  • Access any tab other than the one you're actively capturing
💾
4. Local Storage & Session Data
What stays on your device and for how long

The extension uses chrome.storage.session exclusively. Session storage is:

  • Temporary: Automatically erased when you close the browser
  • Local only: Never synced to Google servers or any cloud
  • Minimal: Contains only the cropped screenshot PNG and your current tab's URL and title — used only to relay the result from the background worker to the popup
  • Self-clearing: Deleted from storage the moment the popup reads it

The extension does not use chrome.storage.local, chrome.storage.sync, localStorage, IndexedDB, or cookies.

🔗
5. Third-Party Services
External dependencies and what they do

The extension bundles one third-party JavaScript library:

jsPDF (bundled locally as libs/jspdf.umd.min.js) — used to generate PDF files from screenshots entirely within your browser. jsPDF runs 100% locally; it makes no network requests and has no telemetry. The library is included as a local file inside the extension package — it is not loaded from a CDN at runtime.

The welcome page and privacy policy page load Google Fonts (Plus Jakarta Sans, JetBrains Mono) from fonts.googleapis.com. This is a cosmetic font request made by your browser to Google's servers when those pages are opened. Google's standard privacy policy applies to font requests. No screenshot data, extension data, or personal information is included in font requests.

The extension does not integrate with any analytics platform (Google Analytics, Mixpanel, etc.), advertising network, crash reporting service, or any other third-party data processor.

🔑
6. Chrome Permissions Explained
Plain-language explanation of every manifest permission
  • 📸 activeTab — Allows capturing the visible area of the current tab when you click the extension button. Used only on-demand, never automatically.
  • ⚙️ scripting — Allows injecting temporary JavaScript into the current tab for full-page scroll capture, the selection overlay, and canvas-based image cropping. Scripts remove themselves after each capture.
  • 📥 downloads — Allows saving the finished screenshot file to your local Downloads folder. No upload, no remote storage.
  • 🗂️ tabs — Allows reading the active tab's URL and title for filename suggestions, and opening the welcome/goodbye pages on install/uninstall.
  • 🗃️ storage — Allows temporary session-only storage used as a relay channel between the background service worker and the popup. Not used for persistent data.
  • 🌐 host permissions (<all_urls>) — Required so that the scripting permission can inject code into whichever website the user is currently capturing. Without this, the extension would only work on a pre-approved list of domains. Access is exercised only when you click "Capture Screenshot" on a tab.
👶
7. Children's Privacy
COPPA compliance statement

Screen Capture Tool does not collect any personal information from any user, including children under the age of 13. The extension is a general-purpose tool with no user accounts, no sign-up flow, and no data collection of any kind. It is fully compliant with the Children's Online Privacy Protection Act (COPPA) by virtue of collecting no data whatsoever.

📝
8. Changes to This Policy
How we handle policy updates

If this privacy policy changes in a meaningful way — for example, if a future version of the extension introduces any form of data collection — we will update this page with a new effective date and increment the version number. The updated policy will be linked in the Chrome Web Store listing.

Given the nature of this extension (no accounts, no backend, no analytics), we do not anticipate any changes that would affect user privacy. Any future update that does involve data handling will be clearly disclosed before the update is published.

You can always find the most current version of this policy at the URL linked in the Chrome Web Store listing for Screen Capture Tool.

Contact
Questions about this policy?
If you have any questions, concerns, or requests regarding this privacy policy or the extension's data practices, please reach out directly. I'm a solo developer and I read every message.