FinalSnap

FinalSnap Privacy Policy

Last updated: May 10, 2026

FinalSnap is a Chrome extension for capturing full-page screenshots, restructuring screenshots, cleaning visual noise, and exporting images or PDFs. This policy explains what data FinalSnap processes, where that data is handled, and what choices users have.

Core Privacy Promise

FinalSnap is designed so screenshot editing happens locally in the user's browser.

Screenshot image data is not uploaded to FinalSnap servers by the extension.

Data Processed Locally

FinalSnap processes screenshot and editor data locally in the user's Chrome profile. This may include:

• Screenshot image data from the active tab after the user starts a capture.
• Local screenshot history, which may include the captured page URL, page title, capture time, image dimensions, and edited screenshot data.
• Editor actions, annotations, crop settings, cut-middle regions, erase areas, source-bar settings, date settings, PDF pagination settings, and export settings.
• Extension preferences such as language, default image format, JPEG/PDF quality, and PDF page settings.
• Trial status, limited local feature-use counters, and local license status used to decide whether Pro features are available.

This local data remains in the user's browser profile unless the user deletes it, clears extension data, or uninstalls FinalSnap.

Optional Data Sent to a License or Promotion Server

If Pro licensing, paid features, beta access, tester access, redemption codes, or promotion-based Pro rewards are enabled, FinalSnap may contact a license or promotion server to verify access. The extension may send:

• An installation ID generated for license, trial, tester, and abuse-prevention checks.
• An optional account/contact email address if the user provides one for license lookup, beta access, tester access, support, Pro code delivery, or promotion reward review.
• The extension version.
• Trial status, remaining Pro days, license status, and limited feature-use counters.
• Payment or subscription identifiers returned by the payment provider.
• Promotion claim details submitted by the user, such as the promotion platform, public post URL, requested reward days, account email, and claim notes.

This data is used only to verify Pro access, manage purchases or subscriptions, deliver codes to the registered account email, review promotion reward claims, provide beta or support access, and prevent abuse.

FinalSnap does not upload screenshot image data as part of license or promotion checks.

Optional Product Analytics

If FinalSnap's analytics endpoint is configured and the user keeps anonymous usage statistics enabled, FinalSnap may send low-frequency product events to help understand installation quality, version adoption, and feature reliability. These events may include:

• A generated installation ID.
• The extension version.
• Browser language, time zone, platform, and Chrome version.
• Key product events such as install, update, capture started, capture succeeded or failed, editor opened, Cut Middle confirmed, Smart Erase confirmed, export completed, upgrade prompt shown, checkout clicked, and uninstall feedback page opened.
• Basic event properties such as output dimensions, number of screenshot tiles, export format, warning codes, or whether a capture was partial.

FinalSnap does not upload screenshot image data, webpage content, captured page URLs, continuous browsing history, keystrokes, mouse movements, or raw clickstream data for analytics.

Server-side logs may derive coarse region information such as country, region, or city from hosting or CDN headers. FinalSnap does not need to store IP addresses for the analytics summary.

Users can disable anonymous usage statistics in FinalSnap Options.

Support and Feedback

If a user chooses to send a support, feedback, beta-request, or tester-request email from FinalSnap, the email may be prefilled with diagnostic context such as the extension version, installation ID, page title or URL related to the issue, basic extension settings, browser language, platform, and browser user agent.

The user can review and edit the email before sending it. FinalSnap does not automatically attach screenshots or upload screenshot image data.

Payments

Payments, if offered, are processed by Stripe Checkout or another disclosed payment provider. FinalSnap does not collect, process, or store credit card numbers.

FinalSnap may receive payment or subscription identifiers from the payment provider so that Pro access can be activated, refreshed, cancelled, or restored.

What FinalSnap Does Not Collect

FinalSnap does not intentionally collect:

• Passwords, credentials, security questions, or personal identification numbers.
• Credit card numbers or full payment card details.
• Health information as a separate data category.
• Personal communications such as emails, text messages, or chats as a separate data category.
• Continuous browsing history or background browsing activity.
• Keystroke logging, mouse tracking, or continuous clickstream tracking for analytics.
• Screenshot image data on FinalSnap servers.

A screenshot may contain whatever visible webpage content the user chooses to capture. That screenshot content is processed locally by the extension unless the user separately chooses to share or send it outside FinalSnap.

Chrome Permissions

FinalSnap requests Chrome permissions only to provide its screenshot, editing, export, source display, and local history features.

• activeTab: used only after the user starts a capture, so FinalSnap can access the currently active tab.
• scripting: used to inject the capture helper into the active tab after the user starts a capture, so the page can be measured, scrolled, captured, and restored.
• offscreen: used to combine captured screenshot tiles and prepare exports inside the extension context.
• downloads: used to save exported PDF or image files to the user's device.
• storage and unlimitedStorage: used to keep local settings, screenshot history, edited image data, export preferences, trial state, and license state.
• contextMenus: used to provide an optional right-click capture command.
• favicon: used to show the captured page's site icon in the optional browser-style source bar and local screenshot context.

Third-Party Services

FinalSnap may interact with these third-party services only when needed for the described product features:

• Chrome and Chrome extension APIs for capture, local storage, downloads, and extension UI.
• A payment provider such as Stripe if the user chooses to purchase paid features.
• An email provider if the user chooses to send support, feedback, beta, tester, or promotion emails.
• A license or promotion server if Pro access, redemption codes, tester access, beta access, or promotion rewards are enabled.
• An analytics endpoint if anonymous usage statistics are enabled.

Screenshot image data is not sold, transferred to advertising networks, or uploaded by the extension to FinalSnap servers.

Remote Code

FinalSnap does not load remote JavaScript or remote WebAssembly into the extension. Core screenshot capture, editing, restructuring, and export logic is packaged with the extension.

Communications with remote services, when enabled, are limited to feature access checks, payment/subscription status, promotion reward review, support, or beta/tester workflows described in this policy.

Data Sharing

FinalSnap does not sell personal data.

FinalSnap does not transfer user data to advertising platforms, data brokers, or information resellers.

FinalSnap does not use or transfer user data to determine creditworthiness or for lending purposes.

FinalSnap only shares or transfers data when needed to provide the extension's single purpose, manage Pro access, process payments, deliver support, prevent abuse, comply with law, or complete a user-requested action.

FinalSnap's use and transfer of information received from Google APIs follows the Chrome Web Store User Data Policy, including the Limited Use requirements.

User Controls and Deletion

Users can control local FinalSnap data by:

• Deleting local screenshot history in FinalSnap when the feature is available.
• Clearing Chrome extension data.
• Removing or uninstalling the extension.
• Avoiding optional support, beta, tester, license, or promotion submissions.
• Turning off anonymous usage statistics in FinalSnap Options.

Users can request deletion of support, beta, tester, license, promotion, or analytics records associated with an account/contact email address or installation ID by contacting FinalSnap at the address below.

Data Retention

Local screenshot history and extension settings remain in the user's Chrome profile until the user deletes them, clears browser extension data, or uninstalls FinalSnap.

License, payment-status, beta, tester, support, promotion, and analytics records may be retained as long as needed to provide access, resolve support requests, improve product reliability, prevent abuse, maintain business records, comply with legal obligations, or administer the relevant program.

Children's Privacy

FinalSnap is not directed to children under 13 and does not knowingly collect personal information from children.

Changes to This Policy

This privacy policy may be updated from time to time. The updated version will be posted on this page with a new "Last updated" date.

Contact

For privacy questions, contact: finalsnapapp@gmail.com