Privacy Policy for Capture Página

Last Updated: October 26, 2026
Extension Name: Capture Página
Publisher / Developer: Daniel Felipe Zapata Martinez
Contact Email: danielzapatam93@gmail.com
Website / Repository: https://dfzm.github.io/

1. Introduction & Core Principle

Capture Página ("the Extension") is designed from the ground up with a strict local-first, privacy-by-design architecture.

The Extension's single purpose is to capture, annotate, and export webpage screenshots at your explicit request. All data processing, image stitching, freehand drawing, and file encoding occur exclusively on your local computer. The Extension does not operate external servers, does not transmit your data off your device, does not sell or share user data, and contains no analytics, advertising, or telemetry trackers.

2. Information Handled by the Extension

When you explicitly trigger a capture, the Extension handles the following categories of data locally on your device:

1. Webpage Visual Content (Screenshots):
   The Extension captures the visual pixel data of the active tab that you explicitly request to capture (either the visible viewport, the full scrolling document, or a selected rectangular area).
2. Page Title and URL:
   The Extension reads the title and URL of the active tab at the exact moment of capture. This information is used solely to display the page title and domain in the result preview header and to generate a clean, sanitized default filename for your downloaded image (e.g. PageTitle_YYYY-MM-DD_HH-mm-ss.png).
3. User Annotations (Brush Strokes):
   If you choose to use the "Draw" tool, the vector coordinates, colors, and brush widths of the strokes you draw are held strictly in the active result tab's temporary in-memory JavaScript/DOM state (AnnotationOverlayController). Strokes are not persisted in IndexedDB and are lost if the result tab is refreshed or closed.

Programmatic Data Extraction vs. Visual Content:

• The Extension does not programmatically inspect, scrape, extract, or transmit your personal identity, passwords, payment details, form inputs, cookie jars, or browsing history.
• Visual Information Notice: Because the Extension captures raw visual screenshot pixels of the tab you select, any personal, confidential, or sensitive information visibly displayed on that webpage at the moment of capture (such as your account username, email address, profile photo, or on-screen billing statements) will naturally be included as visual pixels within the screenshot image.
• All such visual pixels remain exclusively on your local computer within your browser's private storage until you explicitly export or delete them.

3. Storage and Data Transmission

• On-Device Storage (IndexedDB):
  Captured image segment bitmaps and page metadata (title, URL, dimensions) are stored locally on your device in the browser's origin-private IndexedDB database named capture-page (store captures).
• In-Memory Tab State:
  Freehand brush annotations reside solely in volatile tab memory and are not written to disk or database.
• Exported Files & Clipboard:
  When you download a PNG or PDF file, it is saved directly to your local file system via your browser's standard download manager. When you copy an image, it is written to your operating system clipboard. These exported files and clipboard copies exist independently on your computer outside the Extension's IndexedDB storage.
• Zero Remote Transmission:
  The Extension does not send or upload your screenshots, URLs, titles, or annotations to any remote server, third party, cloud service, or API. Everything remains strictly within your browser.

4. Data Retention and Deletion Policy

The Extension manages local storage according to the following real, automated lifecycle rules:

• No Immediate Deletion on Tab Close:
  Closing the capture result tab does not immediately delete the capture record from your local IndexedDB. This design ensures that you can safely reload the result tab (result.html?id=...) or recover your capture if you accidentally close the tab.
• Trigger-Based Automated Purge (Records Older than 1 Hour):
  The Extension automatically checks and purges expired records upon browser profile startup (chrome.runtime.onStartup) and immediately before each new capture operation (safePurge()). Any capture record with a timestamp older than 1 hour (3,600,000 milliseconds) is permanently deleted from IndexedDB.
• Not an Exact Timer:
  Deletions do not execute on an exact 60-minute background alarm; cleanup is evaluated and executed upon the next capture or browser restart once the 1-hour cutoff timestamp has passed.
• Scope of Purge:
  The automated 1-hour purge applies strictly to the Extension's internal IndexedDB database cache. Files previously downloaded to your local file system or images copied to your system clipboard remain under your direct operating system control and are not deleted by the Extension.
• Verified Manual Deletion:
  Users who wish to manually erase the Extension's stored data can do so using either of the following verified methods:
  1. Uninstalling the Extension: Right-click the Capture Página icon in your Chrome toolbar (or navigate to chrome://extensions) and select Remove from Chrome. This action immediately, completely, and permanently destroys the Extension's origin-private IndexedDB database and all associated cached images.
  2. Chrome Developer Tools Site Storage: On the extension result tab (result.html), open Chrome Developer Tools (F12) → go to the Application tab → select Storage in the sidebar → click Clear site data.
  (Note: Chrome's general "Clear browsing data" dialog targets web origins and does not reliably guarantee the purging of extension internal storage unless the extension is uninstalled or its site data is cleared directly).

5. Browser Permissions Used

The Extension requests only the minimum permissions necessary to deliver its core functionality:

• activeTab:
  Grants temporary access to the currently active tab only when you open the popup or initiate a capture. Used to take the screenshot via chrome.tabs.captureVisibleTab and inject the scrolling helper. It does not allow background monitoring or access to any un-interacted tabs.
• scripting:
  Allows the Extension to inject the in-page helper (page-agent.js, scroll-container.js and, for area selection, region-geometry.js) into the active tab to calculate scroll dimensions, perform progressive scrolling during full-page captures, and restore original page scroll and styles when capture completes. It also inserts and removes the overlay stylesheet (overlay.css), which draws the area-selection rectangle and backdrop; it is inserted only when area selection starts or a selection error notice is shown, and removed when they end.

Permissions Deliberately Omitted:
The Extension deliberately does not request <all_urls>, broad host permissions, webRequest, downloads, storage, or debugger.

6. Third-Party Services and Analytics

Capture Página contains:

• No third-party SDKs, analytics libraries, or telemetry trackers.
• No remote scripts or dynamically downloaded code (strict script-src 'self' Content Security Policy).
• No advertising networks or data brokers.
• No cookies or tracking pixels.

No user data is ever sold, leased, or transferred to third parties for any purpose.

7. Changes to this Policy

If this Privacy Policy is updated in the future (for instance, to reflect new features), the updated document will be published with a revised "Last Updated" date. Any change that expands data processing will be disclosed transparently in release notes and in the Chrome Web Store.

8. Contact Information

If you have questions, feedback, or concerns regarding this Privacy Policy or the data practices of Capture Página, please contact:

• Developer: Daniel Felipe Zapata Martinez
• Email: danielzapatam93@gmail.com
• Project URL: https://dfzm.github.io/