Privacy Policy for WhatsSnap

Effective date: 3 October 2026 Contact: versedluke@gmail.com

Scope and purpose

WhatsSnap is a Chrome extension that helps a user find and save media they choose from WhatsApp Web into local folders. Its single purpose is to provide user-requested media discovery, scanning, organisation, and downloading for one chat or a selected set of chats.

WhatsSnap is independent software and is not affiliated with, endorsed by, or sponsored by WhatsApp or Meta.

No collection of WhatsApp data by the developer

WhatsSnap does not send your WhatsApp chats, contacts, media or downloaded files to its developer. There is no WhatsSnap analytics, advertising, profiling or media-upload service. Media is processed in your own browser and saved to your computer when you request a download.

Local processing and browser storage are explained below. They do not give the developer access to your WhatsApp account or files. Optional Pro payments are handled separately by the payment services described below.

Processing on your device

To provide its user-facing features, WhatsSnap processes the WhatsApp Web data needed for the action the user requests. This can include chat identifiers and titles, message identifiers and media metadata, sender labels, dates, media types, and the selected media bytes. WhatsSnap does not collect WhatsApp login credentials, authentication cookies, or session exports.

Your browser stores the following extension data to make the features work. These records are not uploaded to a developer-operated database:

• App preferences and default download/layout profiles. Chrome may synchronize the preferences stored with `chrome.storage.sync` between Chrome profiles where the user has enabled Chrome Sync. Unless stated otherwise below, other records remain in local or session extension storage.
• Saved chat identifiers/titles and remembered per-chat settings, the saved Multi-chat selection, folder suggestions, and a bounded duplicate-download ledger.
• The current local-day Starter usage count, short-lived download reservations and operation leases, and bounded completion records used to prevent a successful download from being counted twice.
• A paid-status cache containing only the entitlement state, plan, payment date, source, last-check time, and an error state when applicable.
• ExtensionPay's installation key, installation time, and a minimal paid/trial status cache. Its SDK stores these in synchronized extension storage, with local storage as a fallback. The key authenticates paid-status and checkout/restore requests to ExtensionPay; it is not a WhatsApp credential.
• Bounded compatibility diagnostics containing the WhatsSnap version, a sanitized WhatsApp build identifier, failed-check/error summaries, and a detection time. These diagnostics do not contain message text or media.
• Optional support diagnostics, enabled manually, store at most 80 predefined app-operation and payment/activation events with relative timings in this browser session, bounded to 60 KiB. Entries contain fixed outcome codes, durations, aggregate counts and the user-selected date/time and media filters used for each attempt, never WhatsApp message dates or message identities. A report includes the app/browser versions, available WhatsApp build, language, current operation, mode, non-sensitive preference choices and aggregate selection counts. The enablement preference stays on this device until turned off. These logs contain no emails, chat details, media, filenames, payment URLs or passwords. Nothing is sent automatically: you may copy the log or open the website report form. The form receives the log through a URL fragment, clears that fragment, and submits it to Netlify Forms only when you press Send log. You may add a description and an optional email, separately from the technical log. Reports are received by the developer for support; the email is used only to discuss the report and arrange a licence reward, never for mailing lists or marketing. Clear removes the local log; turning diagnostics off also removes it.
• A bounded session record of payment-page opening state and exact browser tab and window IDs prevents duplicate pages after delayed responses or background restarts. It contains no provider URL or payment credentials.
• An optional ZIP password encrypted in local extension storage with Web Crypto AES-GCM and a fresh random initialization vector whenever it is saved.

ExtensionPay may return additional account fields, including an email address, when WhatsSnap checks paid status. From version 1.1.5.0, WhatsSnap discards fields it does not need before returning or caching that response. This version does not store or display the purchaser's email address. Earlier versions may retain additional account fields in the SDK cache; the next SDK startup after updating removes them.

How data is used

WhatsSnap uses the data above only to perform the extension features the user requests, remember the user's choices, enforce the Starter allowance, confirm paid access, prevent duplicate downloads when enabled, diagnose local compatibility failures, and keep concurrent downloads consistent.

WhatsSnap does not operate an analytics or media-upload server. It does not sell user data, use it for advertising, use it for credit decisions, or permit the developer or other people to read a user's WhatsApp chats or downloaded media.

Separate services and network activity

WhatsSnap does not send WhatsApp chats, chat lists, message content, selected media, ZIP passwords, folder history, duplicate history, or compatibility diagnostics to the developer.

The following providers remain involved in the features the user chooses:

• WhatsApp provides WhatsApp Web and the media obtained from WhatsApp's services. WhatsSnap reads that data within the user's WhatsApp Web session.
• Chrome saves requested files and provides extension storage. Chrome may synchronize the preferences and ExtensionPay records described above under the user's Chrome Sync settings and Google's applicable policies.
• ExtensionPay receives paid-status requests and provides checkout and purchase restoration over HTTPS. ExtensionPay and its payment processor handle their own checkout data under their own privacy policies. Information you submit to those services is separate from WhatsSnap's local WhatsApp processing. WhatsSnap does not receive or store payment-card details.

WhatsSnap's use and transfer of user data adheres to the Chrome Web Store User Data Policy, including its Limited Use requirements.

Information you choose to send to support

If you email the developer, the developer receives your email address and whatever you choose to include, such as a description of a problem or a copied diagnostic report. That information is used to respond to your request. WhatsSnap does not automatically send support reports, chat contents or media.

Retention and deletion

Selection groups are stored only in this browser profile. They contain the name you choose and ordered chat identifiers, titles and group-chat flags, with revision and update dates. They contain no messages, media or profile pictures. Delete a selection group individually or clear the library with the confirmed whole-app reset. Ordinary mode resets preserve it. Date selections are transient.

Optional website feedback

An optional uninstall feedback page is available. Feedback you explicitly submit will be processed by Netlify Forms for the developer to read and improve WhatsSnap. The form asks for one comment, not an email address or sign-in. Technical metadata includes the extension version, Chrome/Edge distribution, the last locally confirmed WhatsApp Web build when available, and the browser/page language. A translation link is generated from your submitted comment; it is opened only when the developer chooses to use it. WhatsSnap does not attach chat, contact, media, licence, selection-group or device identifiers. The hosting provider handles the ordinary web request; this does not change local processing of WhatsApp data. Avoid including sensitive information in your comment. The form's successful receipt does not mean an email notification has been sent to the developer.

Local record retention

Preferences and remembered records remain until the user resets or clears them, clears the extension's storage, or uninstalls WhatsSnap. Duplicate history, diagnostics, completion records, and temporary reservations/leases are capped or expired by the extension. The current-day Starter counter rolls forward with the user's local calendar day.

Users can clear saved history and the optional ZIP password from Config and Info. The confirmed whole-app reset clears settings and locally remembered records but does not alter licence or payment-provider records. Uninstalling WhatsSnap or clearing its Chrome extension storage removes extension-held data. Files already downloaded remain in the location chosen through Chrome and must be deleted separately by the user.

Security

WhatsSnap limits its Chrome permissions to the features it provides, keeps page integration bounded, and uses HTTPS for ExtensionPay communication. The ZIP-password editor runs in an isolated extension-origin frame so WhatsApp page scripts cannot read the input; only the encrypted record is persisted. A ZIP archive is unencrypted unless the user configures a password.

No system can be guaranteed completely secure. Security or privacy concerns can be reported to the contact address above.

Changes

This policy will be updated when WhatsSnap's data practices materially change. The effective date at the top identifies the current version.

Contact

For privacy questions or requests, email versedluke@gmail.com.