Privacy Policy
SnapMaster – Screenshot & Editor Chrome Extension
Last updated: October 22, 2026. This policy applies to all versions of the SnapMaster extension distributed via the Chrome Web Store (Extension ID: bllhjhfajpclmnlogplcfjjnlkmnlfmp).
1. Overview & summary
SnapMaster captures screenshots and lets you annotate them entirely on your device. We do not collect, transmit, or share any personal data, screenshots, or usage information with anyone — ever. Everything stays locally in your browser.
SnapMaster (“the Extension”, “we”, “our”) is a Chrome browser extension that allows users to capture visible-area screenshots, full-page scroll screenshots, and selected-area screenshots, then edit them with annotation tools (pen, arrows, text, blur, crop, etc.). The Extension is designed to operate entirely offline and locally within the user’s browser.
This Privacy Policy explains what information the Extension accesses, how it is used, and the rights you have regarding that information.
2. What data we collect
We do not collect, store remotely, or transmit: personal identifiers, browsing history, page content, form data, cookies, passwords, financial information, health information, location data, user communications, or any other personal or sensitive data.
The only data the Extension ever handles is:
- Screenshot images — the pixels of the page you choose to capture (visible area, a selected area, or the whole page), captured only when you trigger a capture. They are kept locally in your browser’s own database (IndexedDB) so the editor and the History page can open them. They are never transmitted anywhere.
- Page address and title — saved on your device next to each capture in your local History, and, only if you turn on “Add the page URL and date” in Settings, printed under the screenshot. They are never sent anywhere.
- Your settings — choices such as auto-copy, file format and name, self-timer, theme, default colours and tools, and optional watermark text — plus, if you choose one, a browser reference to your chosen save folder (SnapMaster only writes screenshots there). They are stored locally with
chrome.storage.localand are never synced or transmitted. - The clipboard — SnapMaster can write a screenshot to your clipboard when you press Copy or turn on automatic copying. It never reads your clipboard.
When you capture a screenshot, the image may contain sensitive information visible on your screen at the time of capture (e.g., banking pages, personal emails). This image data is stored only on your local device and is never transmitted to us or any third party. You are solely responsible for managing your captured screenshots.
3. Extension permissions explained
SnapMaster requests the following Chrome permissions. Each permission is used exclusively for core screenshot functionality and is not used to collect user data:
| Permission | Why it is required | Data sent externally? |
|---|---|---|
| activeTab | Capture a screenshot of the currently active browser tab when you click the extension icon or use a keyboard shortcut. Access is granted only for the duration of the capture action. | None |
| storage | Remember your settings (chrome.storage.local) and hand the editor the capture it should open. Data never leaves the device. | Local only |
| unlimitedStorage | Full-page captures and your History are many megabytes, more than the default storage quota. They stay in local browser storage (IndexedDB); nothing is transmitted. | Local only |
| clipboardWrite | Lets SnapMaster copy a screenshot to your clipboard when you press Copy or turn on “Copy to clipboard automatically”. It only ever writes; it never reads your clipboard. | Local only |
| downloads (optional) | Only if you turn on automatic saving or choose a download subfolder: saves the screenshot file to your Downloads folder. Requested at that moment and can be revoked at any time. | Local only |
| scripting | Run the selection overlay, the scrollbar picker and the scroll-and-capture logic in the tab you are capturing, and — when you copy without opening the editor — write the image to the clipboard from that tab. Scripts run locally and do not transmit page content. | None |
| host_permissions (<all_urls>) | Required by scripting and by screenshot capture so SnapMaster works on any website you choose. During a full-page capture it looks at which parts of the page scroll and briefly adjusts the page (hides scrollbars and fixed bars, pauses animations), then restores it. Page content is only turned into the image you asked for — nothing is read for any other purpose or transmitted. | None |
4. How data is stored
All data handled by SnapMaster is stored exclusively with the browser’s built-in local storage — chrome.storage.local for settings and IndexedDB for screenshots — which keep data on your device only. This storage:
- Is never synced to Google accounts or any remote server (we explicitly do not use
chrome.storage.sync). - Is never accessible by us, Google, or any third party.
- Can be cleared at any time by removing the extension or clearing browser data.
- Holds a History of recent screenshots whose size you choose in Settings (5 to 100 captures; 30 by default, or switched off). Older captures are removed automatically.
The SnapMaster extension makes zero network requests. It does not connect to any server, API, analytics service, cloud storage, or third-party service. You can verify this by inspecting the extension’s network activity in Chrome DevTools.
The optional “Boost SnapMaster” button in the extension simply opens this website’s boost page in a new browser tab. That page — not the extension — is where a tip is made, and only if you choose to send one. It asks for an amount and, optionally, a name and a message. Your payment is handled by Razorpay, and SnapMaster never sees your card or UPI details. The amount, the optional name and message you type, and the payment’s reference are stored on the developer’s server so a tip can be recorded and acknowledged; they are not shared or used for anything else. A boost is a voluntary tip and unlocks nothing.
5. Data sharing & third parties
We do not share, sell, rent, trade, or otherwise transfer any data to third parties. Specifically:
- No analytics or telemetry services are embedded in the Extension.
- No advertising networks or data brokers receive any information.
- No crash reporting services receive data about your usage.
- No cloud services receive your screenshots or any other data.
The Extension does not integrate with any third-party SDKs, libraries loaded from external CDNs, or remote scripts of any kind. All code runs locally from the installed extension package. (The only third party involved in anything SnapMaster-related is Razorpay, and only on the optional boost page described above.)
6. Data retention & deletion
Because all of the extension’s data is stored locally on your device, you have full control over it:
- Automatic cleanup: The extension keeps only as many captures as your History setting allows (default 30). Older entries are removed automatically when the limit is reached.
- Manual deletion: Delete one capture or everything from the History page, use Settings → Data & privacy → Clear history or Reset to defaults, or clear the extension’s data in chrome://settings/content/all.
- Uninstall: Removing the extension from Chrome automatically deletes all locally stored data, including screenshots.
We have no access to your screenshots, history or settings, so there is nothing for us to delete on your behalf. If you sent a boost and want the name or message you entered removed, email us (see below) and we will delete it.
7. Children’s privacy
SnapMaster does not knowingly collect any personal information from children under the age of 13 (or the applicable age of digital consent in your jurisdiction). Because the Extension collects no personal data whatsoever, it is inherently safe for all age groups. If you are a parent or guardian and have concerns, please contact us.
8. Changes to this policy
We may update this Privacy Policy from time to time. Any changes will be reflected by updating the “Last updated” date at the top of this page. We will not reduce your rights under this policy without your explicit consent. The most current version of this policy is always available at this URL.
Continued use of the Extension after any changes constitutes your acceptance of the updated policy. If you do not agree with the updated policy, please uninstall the Extension.
9. Contact us
If you have any questions, concerns, or feedback regarding this Privacy Policy or the Extension’s data practices, please reach out:
Developer contact
Email: arunbabuks03@gmail.com
We aim to respond to all privacy-related inquiries within 5 business days.
Chrome Web Store listing
Extension ID: bllhjhfajpclmnlogplcfjjnlkmnlfmp
This privacy policy was last updated on October 22, 2026.