TrueScreenshot privacy policy
TrueScreenshot captures the full page or a rectangular area you select in the tab you choose, automatically saves the result when automatic saving is enabled, and keeps a temporary preview you can open to inspect, copy, or save as PNG or JPEG. It does not automatically open a preview tab after capture. Area selection captures the visible page region you mark; it does not scroll the page. Very tall full-page captures may be saved as multiple image files. A page can contain personal or sensitive information, so capture only pages and areas you intend to save.
When TrueScreenshot reads page information
TrueScreenshot also provides an explicit Design capture action. It reads the chosen page's rendered HTML structure, element layout and styles, applicable CSS rules, font names and available asset addresses, and captures page or selected-element images. Form values and executable page scripts are omitted from the saved design markup. Design captures are local, encrypted temporary records with a separate session-only key, limited to the newest 20 records for one day; they are cleared after key loss or browser restart. Normal and incognito cases use separate contexts. A frozen snapshot does not reproduce a live server-backed application. Design content is transmitted through Jewell Made only when you enable a hosted TrueScreenshot MCP connection and approve a client to read it, as described below.
TrueScreenshot starts a capture after you use its toolbar button, keyboard shortcut, right-click menu or workbench action, or through a client with your explicit scoped approval. While a capture is active, it reads the page address to detect navigation and stop if the page changes. The active job's page address, title, and domain are kept in Chrome's session-only extension storage while the temporary capture exists; they are removed with the job, are not synced, and are not persisted as plaintext to disk. TrueScreenshot uses the page title in saved filenames. The site's domain is added to a filename only if you enable that setting.
Temporary capture storage and encryption
The temporary screenshot pixels and saved-part filenames, including the page title and optional domain when present, are encrypted in the extension's IndexedDB with AES-256-GCM. Each encrypted record uses a fresh 96-bit initialization vector (IV). The encryption key is stored only in chrome.storage.session, Chrome's session-only storage for trusted extension contexts; it is not written to disk or synced. The key is lost when Chrome restarts or the extension reloads or updates. TrueScreenshot clears temporary preview data when Chrome starts and before creating a new key, so an encrypted preview cannot be restored after the old key is lost.
A small set of job and retention fields, including job IDs, part numbers, timestamps, byte lengths, part counts, and incognito state, remains unencrypted so TrueScreenshot can build its retention index and clean up temporary records. The active job's page address, title, and domain are also held in session-only extension storage as described above. This encryption applies to temporary screenshot and saved-part records; it does not encrypt the whole Chrome profile, the device, backups, or files you export. It cannot protect a capture from someone or software that can access your active Chrome session.
Where captures go
When you explicitly start diagnostic recording, TrueScreenshot records the selected tab's request addresses, methods, status/timing, selected headers, console output and click locations. It starts at recording time; earlier page-load traffic may be missing. Network bodies are off by default. If you enable bodies, text/JSON payloads can include submitted form data; the default approved body origin is the page itself, and additional origins require your explicit list. Known authentication headers, cookies and credential fields are redacted. Automatic redaction cannot identify every kind of private content, so review the result before sharing. It does not log keystrokes or read field values for its action timeline. Supported socket messages are bounded and unsupported/binary data is labelled. Recording stops on your action, cancellation, time/data limits, incompatible navigation or loss of its debugger connection. These diagnostic records use the same separate protected temporary-case storage and retention as design captures. Recording data is transmitted through Jewell Made only for a hosted TrueScreenshot MCP request within your explicitly approved scope.
Captures are processed in Chrome on this computer. Ordinary capture and local exports do not upload page content to Jewell Made. An explicitly enabled hosted TrueScreenshot MCP connection relays only the content requested under your approved page/tool scope through the existing Jewell Made service to the connected client. Billing routes receive activation/recovery and subscription metadata, not page or capture content. There are no advertising or analytics calls. Nothing is written to Chrome sync storage.
TrueScreenshot MCP and AI clients
TrueScreenshot MCP lets an AI client request screenshots, rendered design, diagnostics, comparisons and artifacts only after you approve that client's exact page/origin, allowed tools, duration and optional body access. Connecting or linking an account alone does not authorize all tabs. Client display names are supplied by clients; the interface also shows their actual identity and return address. TrueScreenshot does not choose an AI model or call a model for you. Your connected client's provider receives the approved returned content and handles it under that provider's policies.
Local MCP clients can use the optional companion and Chrome native messaging; the companion reads only the completed exports within its explicitly approved roots when independently verifying files. The hosted MCP path uses OAuth and an extension-initiated outbound connection. It does not open an inbound port on your PC or require the local companion. Hosted access is available in regular Chrome windows while the connected workbench remains open. Revocation, expiry, incompatible navigation and disconnect stop further permitted browser work. A lost connection is detected through a bounded heartbeat rather than being represented as a successful empty capture.
For hosted MCP, Jewell Made processes the permitted screenshot/design/network artifact chunks to deliver your requested tools. Temporary relay payloads are encrypted in transit and encrypted at rest with context-bound AES-GCM. They become unreadable through the relay when their two-minute request expiry is reached; expired payloads are removed by request housekeeping or the service's maintenance schedule. Minimal request identity records are retained for at most one day to prevent unsafe duplicate work. OAuth access credentials last at most one hour; rotating refresh credentials last at most seven days and are stored only as hashes. Connection/client metadata supports account linking and revocation. No page content, tokens, link codes or merchant secrets are intentionally written to application logs. The separate temporary data on your PC follows the retention rules above; files saved to your chosen folder are ordinary user files.
New captures download to Chrome's Downloads folder by default, without opening another tab or requiring a Save click. A small confirmation on the source page reports saving or completion. Open preview or Last preview opens the preview only after you choose that action. In Settings you can turn automatic downloads off or choose a folder for future captures. With automatic downloads off, open the preview to save or copy manually. PNG/JPEG files and portable ZIP reports are ordinary files and are not encrypted by TrueScreenshot. The selected-folder report writer reads back its newly written file to verify its hash. The optional local companion can independently verify an explicitly requested, completed export inside an installer-approved output folder; it does not offer arbitrary file reads. Exports remain where you selected; TrueScreenshot does not later move or delete them. Copying a capture to the clipboard also requires an explicit action.
Portable reports contain local images, rendered-design JSON, redacted HAR, console/actions and explicit coverage/integrity metadata. Their offline viewer runs no captured scripts or recorded requests and does not fetch asset URLs. Comparisons include before/after/difference images and bounded structural/network changes; uncertain selector matches, incompatible dimensions and missing content remain labelled.
Optional AI clients and local companion
Other installed extensions may request pairing, which initially returns no page data. In the workbench you approve the verified client ID, one selected tab/origin, allowed tools, expiry and optional body origins. Only that grant's captures/jobs/artifacts are accessible. Expiry, revocation or incompatible navigation removes access. A client or model provider you choose can receive data you permit it to read; that workflow may send content to its provider. Review data before sharing and approve only clients you trust.
The optional Node companion is installed separately and uses authenticated local IPC and Chrome native messaging, without a public network listener. A fresh packaged connector lives in the explicitly opened workbench; closing that workbench or the final MCP client revokes native grants and stops their jobs. The companion is available in regular windows; native connections are unavailable in incognito. One installed companion configuration is a shared local principal, not an authenticated model/provider identity. Its private configuration and recovery backups should be kept private.
How long temporary captures are kept
A finished capture stays in the extension's temporary storage while its preview tab is open. Closing the preview deletes its capture. Captures without an open preview tab, including captures whose preview you have not opened, are deleted after one day and are limited to the three newest captures. Every remaining temporary capture is cleared when Chrome starts. Delete all captures on the preview or Options page removes all temporary captures. Pieces of an unfinished capture are removed when it finishes, fails, or is cancelled. Export any capture you want to keep.
Settings, billing and license state
Your settings, agreement record, installation credentials, private recovery code and signed license certificate are kept in Chrome's local extension storage on this device and are not synced. The selected folder's Chrome-granted directory handle is kept separately in a local IndexedDB preferences database; TrueScreenshot does not keep a general list of that folder's contents. If folder access is lost, saving reports the problem instead of silently changing destinations.
The billing service at truescreenshot.jewellmade.com uses Cloudflare Workers/D1 and Stripe. The active connection mode is shown in Plan & license. Development uses Stripe test connections; production uses separate real payment connections on the same service. The server stores encrypted connection configuration and an administrative change audit. Development and production license records use separate namespaces. Activation and recovery send installation identifiers, private credentials, bounded installation labels and selected billing actions over HTTPS; the server stores credential hashes, trial/paid term dates, active installation slots, Stripe customer/subscription identifiers and webhook-processing identifiers. It uses salted IP/time-bucket hashes to limit abuse; expired rate buckets are removed. Billing records exclude page/capture content. The separately approved MCP relay uses the same service for the transmission described above. There is no claim that reinstall abuse is impossible.
The evaluation lasts 14 days with no card or automatic conversion. You explicitly choose hosted Stripe Checkout for the USD59/year or USD9/month plan. Stripe handles any email, billing address and card information entered on its hosted page; the extension and license database do not store card details. Only test keys/prices are accepted while development is selected, so that mode makes no real charge. When production is explicitly enabled, checkout uses the displayed real recurring plan until canceled. A provider-verified purchase is distinct from the development-only local tier simulator. Developer preset states, including the simulated trial extension, are local fixtures and are not Stripe purchases.
A signed server certificate may permit access offline until its bounded expiry, at most 24 hours and never beyond its applicable trial/paid term. New captures stop when verified access is unavailable; exported files and local readers remain usable. A full refund revokes the applicable paid period; cancellation respects already-paid time. Recovery uses a private high-entropy code, not verification of a typed email, and is limited to three active browser installations per license. You can explicitly revoke old installations for transfer. A downloaded recovery backup is an unencrypted private file. License records are retained to operate the license and billing history; contact Jewell Made through its website for support or a data request. Production configuration disables local developer presets. A development license or purchase does not become a production entitlement.
Changes to this policy
If a later version adds network access or handles data in a new way, the privacy information and in-extension disclosure will be updated before that version captures anything.
Chrome Web Store User Data Policy
The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.