Privacy Policy

Effective Date: April 2026

1. Local Processing Only

4K Screenshot Studio operates on a strict "local-first" architectural principle. The core functionality of the extension—capturing your screen, rendering backgrounds, and applying canvas transformations—happens entirely within your local browser environment. We do not send your images, screenshots, or screen data to any external servers. Your sensitive visual data never leaves your device.

2. Data Collection

We prioritize your privacy by actively choosing not to collect data. Specifically:

  • We do not collect personal identification information.
  • We do not track your browsing history or interactions.
  • We do not employ any third-party telemetry, analytics, or behavioral tracking scripts within the extension.
  • We never access or log the contents of the web pages you capture.

3. Required Permissions

To function properly, the extension requests the following Google Chrome permissions:

  • activeTab: Allows the extension to capture the visible area of the specific, active tab you choose to execute it on. Our code cannot observe any background tabs.
  • scripting: Required exclusively to temporarily inject the full-page scrolling mechanism. This ensures long-form web pages scroll and stitch natively to maintain 4K fidelity.
  • debugger: Used strictly to attach the Chrome DevTools Protocol to the active tab to execute emulation overrides (applying high-density 2.0x scale factors for true 4K desktop captures) and capture composite GPU layers natively via DevTools commands. The debugger is only active during the brief capture process and is instantly detached afterward.
  • downloads: Needed to automatically save your compiled, high-definition product showcases directly to your device's Downloads directory.
  • storage & unlimitedStorage: Used to temporarily store the high-resolution capture buffer locally while transferring it to the Showcase Studio editor, and to save your custom 3D preset configurations.

These permissions are utilized strictly on-demand, triggering only when you explicitly interact with the extension.

4. Changes to this Policy

We may update our Privacy Policy occasionally to reflect changes in our practices or for other operational, legal, or regulatory reasons. Because we do not collect your email address, any significant updates will be reflected directly on this public page.

5. Contact Us

If you have any questions, concerns, or requests regarding this Privacy Policy, please open an issue on our GitHub repository or reach out via our associated social channels.