Capture the post. Keep the context. Understand how SnapMyPost handles content, screenshots, and data on your device.
SnapMyPost is designed to process screenshots locally in your browser, without requiring an account or uploading captures to an external server.
SnapMyPost is a browser extension that helps users capture, edit, save, and organize screenshots of social media posts and visible webpage content.
SnapMyPost is designed to process screenshots locally in the browser without requiring users to create an account or upload their captures to an external server.
This Privacy Policy explains what information the extension accesses, how that information is used, and how users can manage locally stored data.
When you initiate a capture, SnapMyPost may access the visible structure and content of the selected webpage, including:
This information is used to identify content, generate screenshots, and provide available capture metadata.
If a post permalink is unavailable, the webpage URL may be recorded as a fallback and identified accordingly.
Video content is captured as still images.
Some capture operations may expand content or scroll webpages, which can cause the website to load additional information.
SnapMyPost does not bypass authentication, access restrictions, digital rights management, or website security controls.
Screenshot processing, image editing, metadata generation, and clipboard operations are performed locally within the browser.
Temporary capture data may be stored in browser session storage to support screenshot editing, copying, and exporting.
Temporary captures expire after approximately 30 minutes. Expired records are removed during subsequent cleanup operations, and some temporary status information may remain until browser storage is cleared.
The extension does not require cloud processing to generate screenshots.
Screenshot history is disabled by default.
When enabled, SnapMyPost can save captured images and associated information locally using the browser's IndexedDB storage.
Saved information may include:
Saved history remains available until the user deletes it.
Disabling history prevents new captures from being automatically archived but does not delete previously saved records.
Users can remove individual captures or clear their saved history through the extension's history management tools.
Uninstalling the extension generally removes its extension-managed local storage, subject to browser behavior.
SnapMyPost stores user preferences locally, including:
These settings are used to maintain the user's preferred experience across browser sessions.
SnapMyPost does not automatically transmit screenshots, extracted text, webpage URLs, or capture metadata to the publisher.
The screenshot capture workflow does not use a cloud screenshot-processing service, advertising SDK, analytics SDK, or developer telemetry.
Interface translations are provided through locally bundled language resources.
Websites may continue to load their own resources according to their respective privacy policies and normal browser behavior.
SnapMyPost does not control how third-party websites process information.
SnapMyPost includes an optional feedback function.
Users may generate a local JSON feedback report containing application information, the selected interface language, and a message entered by the user.
The report does not automatically include screenshots, browsing history, or visited webpage URLs.
No feedback is transmitted automatically.
If users open an externally configured HTTPS feedback form, the external provider may receive connection information and any information voluntarily submitted by the user.
Users can copy screenshots to the system clipboard or download them in supported formats.
Exported files may contain captured content and associated metadata depending on the selected export options.
Once content is copied, downloaded, or shared, its storage and handling may be governed by the operating system or receiving application.
SnapMyPost cannot automatically delete files or clipboard history maintained outside the extension.
Users decide when to:
Users can change their preferences through the extension's settings.
SnapMyPost processes captured content locally and does not require cloud transmission for screenshot functionality.
Locally stored information remains subject to the security controls of the browser, operating system, and device.
Users should avoid capturing or sharing sensitive personal information unless they have permission to do so.
The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
Information accessed by SnapMyPost is used only to provide its described screenshot capture, editing, export, and organization features.
This Privacy Policy may be updated to reflect changes in SnapMyPost's functionality, data handling, or applicable requirements.
The latest version will be available on the extension's official privacy policy webpage.
For privacy-related questions or support requests, contact: