Trust & Privacy

BigCap is a local-first desktop application for capturing full-page website screenshots. This document explains, in plain terms, what data the app touches, where it stays, and what it does not do. Our guiding principle is simple: BigCap runs on your machine, and your captures stay with you.

Summary (the short version)

• No account, no sign-up, no cloud. BigCap works entirely on your computer.
• No telemetry or analytics. We do not collect usage data, and BigCap does not "phone home" to CTRL Colab.
• We never receive your captures or the URLs you visit. Screenshots, PDFs, and the addresses you enter never leave your device except as part of the normal web request the app makes to the site you asked it to capture.
• You control where files are saved. Output is written only to the location you choose.
• Everything can be deleted by removing the app and its local data folder.

What data BigCap handles

1. Data you provide

• URLs / web addresses you enter or navigate to.
• Login credentials you may type into a site inside the "Browse & Capture" window (these are entered directly into the website, exactly as in a normal browser — BigCap does not read or store them separately).

2. Data stored on your device

• Preferences — your last-used options (width, scale, format, quality, Max Length, Break, Delay, and the various toggles) and your last save folder are stored in a local settings file in the application's user-data folder (on Windows, typically %APPDATA%\BigCap\settings.json).
• Browse & Capture session data — the in-app browser uses a persistent session so that logins and cookies stick between uses (convenient for capturing pages behind a sign-in). This session data (cookies, local storage) is stored locally in the app's user-data folder and is never transmitted to CTRL Colab. See "Managing your data" below to clear it.
• Captured files — saved only where you choose via Save As…. BigCap does not keep a hidden copy.

3. Data sent over the network

• To capture a page, BigCap loads it in a Chromium engine and requests that site's resources (HTML, images, fonts, scripts) directly from the site and its servers — the same requests any web browser makes. The site sees a normal request from your device/IP address.
• BigCap sends no data to CTRL Colab. There is no analytics endpoint, no license check, and no background update call in this version.

4. Data CTRL Colab receives

None. Because the app does not transmit usage data, captures, or URLs to us, CTRL Colab does not receive or store any personal information through your use of BigCap.

Optional privacy controls

• Block ad & tracker requests — when enabled, BigCap cancels requests to a curated list of known advertising, analytics, and consent-management domains before they load. This can reduce third-party tracking that the target site would otherwise trigger. It is off by default and is a domain-list heuristic, not a guarantee.
• Hide ads & cookie banners — a cosmetic option that hides ad slots and consent banners in the capture. It does not change what network requests are made (use the option above for that).

Security architecture

BigCap is built on Electron with a hardened configuration:

• contextIsolation: true, nodeIntegration: false, and sandbox: true on all renderer windows, so page content cannot reach Node.js or your file system directly.
• The user interface talks to the capture engine only through a small, explicit bridge (a fixed set of messages) — web pages you capture cannot invoke app functionality.
• Outbound links in the interface (e.g. the footer) open in your default browser rather than inside the app.

Third-party components

BigCap incorporates open-source components — notably Electron and Chromium — which render and capture web pages. These components are subject to their own licenses. When BigCap loads a website, that website's own terms and privacy policy govern your interaction with it.

Managing your data

• Change or clear preferences: delete settings.json in the app's user-data folder; BigCap will recreate defaults on next launch.
• Clear saved logins / session cookies: removing the app's user-data folder clears the persistent Browse & Capture session (on Windows, delete %APPDATA%\BigCap).
• Remove everything: uninstall BigCap and delete its user-data folder. Any capture files you saved yourself remain wherever you saved them until you delete them.

Children's privacy

BigCap is a general-purpose tool and is not directed to children under the age of 13 (or the minimum age required in your jurisdiction). We do not knowingly collect personal information from children — and, as noted above, we do not collect personal information from any user.

Changes to this document

We may update this Trust & Privacy document as the Software evolves (for example, if a future version adds an optional update check or other network feature). Material changes will be reflected in the version and effective date above and included with the corresponding release.

Contact

Questions about trust and privacy in BigCap:

CTRL Colab
Website: https://www.ctrlcolab.com
Email: support@ctrlcolab.com

© 2026 CTRL Colab. All rights reserved.

This document describes the behavior of BigCap version 1.0.0 and is provided for transparency. It is not legal advice; if you distribute BigCap publicly, consider having a qualified professional review your privacy disclosures.