Overview
MTC PageShot is a Chrome extension for user-initiated full-page screenshot capture, local screenshot editing, and local PNG/PDF/PNG Parts/Copy output. It does not require an MTC account and does not upload screenshot pixels or captured webpage content to MTC or to a third-party screenshot-processing service.
How capture starts
Capture is always user-initiated. In MTC PageShot v0.5.2, clicking the MTC PageShot toolbar icon or invoking the configured Chrome extension shortcut (default Alt+Shift+P) starts the requested capture through a compact local progress panel. The progress panel can cancel or retry a capture. On a fresh installation, PageShot may open a packaged Welcome page; when an older version upgrades across the v0.5.2 release milestone, it may open a packaged What’s New page once. These informational extension pages do not capture webpage content.
Data MTC PageShot handles
During a user-requested capture, PageShot temporarily handles the visual contents of the active webpage and the screenshot segments created from it. A page chosen by the user may itself visually contain text, images, personal communications, personal information, or user-generated content.
To create and safely align the screenshot, PageShot also temporarily uses the page title and hostname, the current page address during the active capture, page and viewport dimensions, scroll position, and information about a detected scrolling area. The page title and hostname are used for result labeling and PNG/PDF filenames. The current page address is used during capture to detect navigation or route changes that could corrupt the result.
Purpose and local processing
This data is used only to provide and support the screenshot you explicitly requested, including capture alignment, reliability checks, temporary scroll/sticky/fixed-position and scrollbar coordination, restoration of the original page state, result display, optional local screenshot editing, and filename generation. Screenshot pixels and capture metadata are processed locally in your browser.
The extension does not use captured webpage data for advertising, profiling, analytics, lead generation, credit decisions, or unrelated product features.
Temporary local storage and retention
During capture, screenshot segments may be stored temporarily in Chrome's IndexedDB storage for the extension on your device so PageShot can assemble the local screenshot result. PageShot minimizes metadata saved with temporary session records. The raw page address is not retained in the stale-cleanup session record or completed result record.
Temporary capture data is deleted after successful result assembly and during handled error/cancellation cleanup where possible. Stale interrupted sessions become eligible for cleanup after approximately 60 minutes and are removed during a later extension startup or capture cleanup operation. Chrome or the extension may not be running at the exact 60-minute point, so deletion is not promised at an exact wall-clock time.
MTC PageShot does not maintain a screenshot history. For normal-size captures, the assembled screenshot and optional local edits remain only in the open result tab memory as needed for preview, editing, download, PDF generation, or copy. The editor keeps a bounded in-memory Undo/Redo history. For ultra-long captures that cannot safely become one browser canvas, PageShot creates memory-bounded PNG parts. One part is edited at a time, each part keeps separate local edit state, and PDF output can be rebuilt locally from the edited parts.
Local screenshot editing
The result page can select and adjust supported annotations, crop, highlight, draw a box or arrow, add Check/X marks, apply a visual Blur effect, or add a multiline Note callout. Supported annotations can be moved, resized, recolored/reweighted, or removed individually before export. These edits and note text are processed locally in the open result tab and are not uploaded by MTC PageShot. The Blur tool is a visual concealment effect and should not be treated as guaranteed secure redaction.
PNG, PDF, PNG Parts, and clipboard output
PNG, PDF, and PNG Parts output is generated locally. PDF conversion happens on the device and supports A4/Letter paper, orientation, and quality choices. Ultra-long PDF generation uses memory-aware settings and a 500-page software safety ceiling; actual completion still depends on available browser/device resources. If a result is too large for one safe browser image, single-image PNG/Copy/editing may be unavailable while PDF and sequential PNG Parts remain available. If you choose Copy Image, the image is written to the browser/system clipboard when that Chrome environment supports it. Files you download and clipboard data you create are then controlled by your browser, operating system, and your own storage choices outside PageShot.
Network transmission and sharing
The screenshot workflow does not transmit screenshot pixels, captured webpage content, capture history, page URLs, page titles, filenames, editor notes, or annotation content to MTC or third parties. Extension pages are configured to block network connections by extension code.
Optional support, feedback, review, website, and privacy links navigate to external pages only when you choose to click them. Clicking those links does not attach or transmit the screenshot. The result feedback buttons are navigation choices; PageShot does not send the button choice or screenshot content to MTC through the extension.
If you voluntarily send a screenshot or other information to MTC by email, Facebook, a support form, or another external service, that separately submitted information is handled as part of your support request and under the relevant external service's terms.
Permissions
MTC PageShot uses Chrome's activeTab and scripting permissions. These permissions support the user-requested capture of the active tab, packaged capture-controller injection, page measurement/scroll coordination, reliability checks, and restoration of the original page state. PageShot does not request persistent host access to all websites.
PageShot does not request host permissions or optional permissions.
Analytics, advertising, and tracking
The extension does not include advertising, extension analytics, tracking pixels, behavioral profiling, personalized advertising, or screenshot telemetry.
Chrome Web Store Limited Use
MTC PageShot's use of information received through Chrome extension APIs adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements. Information accessed for screenshot capture is used only to provide or support the user-requested screenshot feature and related reliability/operational functions. It is not sold, used for personalized advertising, or transferred for unrelated purposes.
External Chrome Web Store reviews
PageShot may provide a voluntary link to its Chrome Web Store listing so a user can choose to leave a review. PageShot does not create a rating or review automatically and does not provide rewards or features in exchange for a review. Reviews submitted on the Chrome Web Store are handled by Google under Google's applicable policies.
Changes
If MTC PageShot changes its data practices, this policy, applicable in-product disclosures, and Chrome Web Store privacy declarations will be updated before the changed practice is used where required.
Contact
Questions about MTC PageShot privacy can be sent to support@mtccore.com.