Privacy Policy: GoFullScreenshot Pro BETA
Last updated: 24 October 2026
GoFullScreenshot Pro BETA is the beta test version of the Chrome extension GoFullScreenshot, published by the same developer. It is free during the beta, and you'll never be charged automatically. It has no account, no sign-in and no payment screen. The production version is described in the GoFullScreenshot privacy policy.
This page describes what the Pro BETA extension handles, where and why, in line with the Chrome Web Store User Data Policy. The Chrome Web Store counts data as "handled" even when it never leaves your device, so this page lists everything the extension keeps on your device.
Summary
- Everything is processed and stored in this browser, on your device. No screenshot, page content, address, note or setting is sent to the developer or to anyone else.
- Pro code makes no network request. The shared capture engine can read the PDF you explicitly choose to capture, including an HTTP(S) document using your existing browser session. Other pages the extension loads are pages you open yourself, the addresses you list in Batch (and the redirects those sites make), and links you click.
- No accounts, analytics, advertising, tracking or sale of data. No human at the developer can see your data, because it never reaches the developer.
- Pro keeps more on your device than the production version: a Library of captures, Batch runs, evidence records with the page's HTML and text, presets, a brand kit, a default watermark and a default browser frame, and per-site capture settings. Each is described below, with when it starts and how to delete it.
- You choose. The Library starts only after you agree. Evidence snapshots are taken only when you choose "Capture as evidence". Optional permissions are asked only when a feature needs them, inside your click; Chrome shows a permission prompt when needed.
The capture engine is the same as GoFullScreenshot
GoFullScreenshot Pro BETA contains the complete GoFullScreenshot extension. Everything the GoFullScreenshot privacy policy says about capture, editing, export, Recent captures (local history), embedded pages, local files, the optional downloads permission for Save As, and the support diagnostics text applies to Pro BETA unchanged, with these differences:
- No website on install. After a fresh installation, Pro BETA opens its own welcome page, which is part of the extension. It does not open the gofullscreenshot.com welcome page. The welcome page links to this policy and to the support page; the website opens only if you click a link.
- Rate and Share. Pro BETA never asks for a review by itself. The Rate button (the star in the toolbar popup, and Rate the Pro BETA in Settings > Support) opens Pro BETA's own page in the Chrome Web Store, and only when you click it; a copy that was not installed from the Chrome Web Store opens the support page instead. To tell which, Pro asks Chrome how the extension was installed; this needs no permission and nothing is stored. Share works as in GoFullScreenshot: it shares the address of the public GoFullScreenshot listing through your system's share sheet, where you choose the recipient, or copies that address.
- Kept access to all sites. If you choose to keep access to all sites after an automatic Batch run (see Batch), Pro BETA can also capture a page embedded from another site without asking you first, until you switch that access off.
Complete PDF capture: Full PDF renders every saved page locally with bundled PDF.js. Local documents require Chrome's Allow access to file URLs switch. No PDF content or password is sent to the developer; passwords are held in memory only. Temporary render results are removed after transfer to the editor or cancellation. Unsaved changes in Chrome's PDF viewer are not included. Full PDF requires Chrome 125 or later in both Stable and Pro BETA. Both versions render at 144 dpi and accept up to 300 pages and 64 MiB of input. Each rendered page is limited to 20,000 pixels per side and 24 million pixels; the combined capture is limited to 250 million pixels and 200 MiB of PNG data. A document that exceeds a limit is rejected instead of saving a partial capture.
Moving from GoFullScreenshot
Chrome keeps each extension's data separate. Pro BETA cannot read the settings, Recent captures, keyboard shortcuts or site access of the regular GoFullScreenshot, and the regular GoFullScreenshot cannot read Pro BETA's. Two routes bring things over, and only when you use them:
- Copy settings from GoFullScreenshot. You paste the text that Copy diagnostic info makes in the regular GoFullScreenshot (it holds no page addresses, titles, file names or screenshots). Pro BETA reads its setting lines on your device, shows what would change, and changes only those settings, only after you confirm. The pasted text is not stored.
- Import images. Image files you choose (PNG, JPEG or WebP) are added to the Library, once you agree to the Library. Each gets its file name as title and the time from its file name or the file's date, plus the project and tags you give. Image files do not hold the page address, the page title or notes. An image is kept as the file you chose, including any details stored inside it, such as camera data or a location. Those details stay in it when you open it in the capture tab (Pro then copies it to Recent captures), download the original or back up the Library. Only images taller than 30,000 pixels or larger than 40 million pixels are saved again as PNG parts, without those details.
Removing the regular GoFullScreenshot deletes its Recent captures, so download the captures you want to keep first. If Pro BETA was installed as an update of the earlier Pro beta, that version's settings, presets, logo, watermark and file-name pattern are carried over on this device, and Settings shows once what moved. The earlier Pro beta's own copies stay on this device: its logo as the original file, and its watermark text and presets in the old settings. Reset to defaults in Settings deletes them; otherwise they stay until you uninstall Pro BETA.
Library
When it starts. Only after you choose Keep my captures in the Library (on the welcome page, in the toolbar popup, in the first-use setup, on the Library page, in Settings, or before your first Batch run). Until then, and whenever you switch the Library off, nothing is kept in it and captures follow your Recent captures setting. When you agree, the captures that Pro BETA already holds on this device at that moment (its Recent captures, or, with Recent captures off, the latest capture it keeps so the capture tab can show it) are copied into the Library once, and Pro asks Chrome to keep its storage safe when disk space runs low. Captures in the regular GoFullScreenshot stay there. Agreeing to the Library, or choosing Not now, never changes your Recent captures setting.
What it stores for each capture: the image at full resolution (all parts of a very tall capture), a small preview, the page address (URL) and title, the capture time, the pixel size, the device pixel ratio and the screen width, the capture type, editable annotations, a SHA-256 hash of each original image part, technical details derived from these (such as the file size and a simplified form of the address), and what you add: note, project, capture set, tags and pins. Captures from Batch also record the run, the address from your list and, after a redirect, the address it ended up at, the HTTP status code when the server answered with an error, the screen size asked for and the one it got, and short notes about the capture (for example that it was redirected, that lazy content was loaded first, or that an area was filled with the page background; no page content). Imported images have no page address.
Limits. By default the Library keeps up to 500 captures or 2 GB. You can change both in Settings. When the Library is full, the oldest captures are removed first; pinned captures and captures with an evidence record are never removed automatically.
Backup. "Back up the Library" makes a ZIP file with your captures, their details, runs and evidence records on your device and saves it as a normal download. "Restore from a backup…" reads a ZIP file you choose. Both happen only when you click them.
Deleting. Delete single captures or a selection on the Library page, or everything in Settings > Library > Delete Library… (captures, runs and evidence records). Switching the Library off stops adding captures and keeps the existing ones until you delete them.
Batch
What you give it. The list of web addresses you paste or import from a .txt, .csv or sitemap.xml file on your device, the screen sizes, a run name and a project. The file is read on your device; nothing is fetched to read it.
What it does. Batch opens one separate, visible Chrome window (the capture window), loads only the addresses in your list, follows the redirects those sites make, sets the window to each chosen size, captures each page and closes the window at the end. In an automatic run, at screen sizes 500 pixels wide or more, the capture window may already load the next two addresses of your list in muted tabs of the same window, so the next page is ready; when it does, the Batch page says so before you start, and these tabs are closed when the run pauses, stops or ends. Before Batch moves one of the tabs it opened in its capture window to the next address, or closes it, it temporarily switches off that page's "Leave site?" prompt, so a page cannot stop the run; it does this only in Batch's own capture window, never in your tabs from before the run, and it reads nothing from the page content. It changes the page's prompt handlers. If you drag a Batch tab out, Batch stops using it and tries to restore those handlers without reloading the page. If Chrome can no longer access that page, reload the tab to restore its normal behavior. You can choose to capture the full page or only the visible area of each page. You can pause, skip or stop a run at any time. Batch never reads, reloads, captures or closes your own tabs, and it closes only the tabs and windows it opened. In an automatic run, a tab you open in the capture window, or a link from another app that Chrome opens there, is moved to the window with the Batch page and shown there. A tab you drag out of the capture window stays where you put it.
What it stores. With the Library on, Batch keeps its captures in the Library, and you can also tick Also download each capture as it finishes. With the Library off, Batch asks first: Keep my captures in the Library, or Run without the Library. Without the Library, each capture is downloaded as it finishes and nothing is kept in the Library; the capture is kept only as GoFullScreenshot keeps any capture (your Recent captures setting), and Batch remembers this choice for your next runs. Both download options need Chrome's downloads permission: when you start the run, Batch explains it first, and Chrome may ask you to allow it. With the Library on, Batch also stores for each run the address list, the run name, project, mode, full page or visible area, screen sizes and how long the run took, and for each capture its status, any error, how long it took, the screen size it really got, the page title, the address it ended up at if it was redirected, the HTTP status code if the server answered with an error, and short notes about the capture. A run without the Library keeps no run record.
Access to sites. Chrome only lets an extension capture a page when you picked that page, or when it has access to all sites. Batch therefore has two modes:
- Automatic asks Chrome for access to all sites when you start a run, after an explanation on the Batch page. Chrome words it as "Read and change all your data on all websites". Batch uses this access only to load and capture the pages in your list, in the capture window. It switches the access off when the run ends, when you stop it, when it fails or when you close the Batch page, unless you tick Keep access for future batches (off by default). You can switch kept access off on the Batch page (Remove access), in Settings > Batch (Switch off access to all sites) or in Chrome's extension settings. When Chrome switches off access to all sites, it can also switch off sites you had allowed before; the Batch page and Settings > Batch then name those sites and offer Allow again.
- Guided does not ask for access to all sites. Batch asks Chrome only for the sites in your list, plus their usual https and www variants so a redirect does not stop the run, and Batch removes that access when the run ends. You confirm each capture with the capture shortcut or the toolbar icon in the capture window, once per site.
To clean up after a crash or a browser restart, Pro keeps a small local record of the access a run added (goFullScreenProBatchGrants) and schedules local clean-up retries with Chrome's alarms. It removes only access that Batch itself added. The same record keeps the sites Chrome switched off together with access to all sites (at most 50), with the time, so Batch can offer Allow again for 30 days. A site is removed when you allow it again or dismiss it, or the first time the Batch page or Settings > Batch opens after those 30 days.
Evidence captures (Proof)
When. A page snapshot is taken only when you choose Capture as evidence in the toolbar popup. The first time, the popup lists what will be saved and waits for Continue. In the capture tab, Seal this capture in the Proof panel seals an unedited capture that is still in Recent captures, without taking a page snapshot; a capture reopened from the Library cannot be sealed. If Seal evidence captures automatically is off in Settings > Proof, or sealing fails, an evidence capture waits with its page snapshot until you choose Seal now or Try again in the Proof panel, and that seal includes the snapshot.
What is saved on your device: a full-page screenshot and, unless you turn page snapshots off in Settings > Proof, the page's HTML (up to 20 MB) and visible text (up to 5 MB). Also the page address, title and referrer, its "last modified" date, language, character set and content type, the window size, pixel ratio, scroll size and scroll position, the time, your device's time zone and UTC offset, how long the snapshot took (kept only until the capture is sealed), and the browser, platform and extension version. The HTML is the page as it is at that moment and can contain anything in it, including personal data and hidden form values. Text you typed into input fields and text boxes is left out, unless the page itself copies it into the page, as some sites do; text in editable page areas is part of the page and is included. The values of password fields written into the page itself are blanked. Embedded page components (shadow DOM) are included only when the page marks them as serializable, and password values inside them are not blanked. Inline scripts and styles are part of the HTML; scripts, styles and images loaded from other files are not included.
Sealing. Pro records a SHA-256 hash of every file and signs that list with a key made in this browser. The private key is created so that it cannot be exported, not even by the extension, and it stays in this browser profile. Each evidence package contains the public key and its fingerprint, so others can check a package. A seal shows that the files have not changed since they were sealed on this device. It is not a trusted third-party timestamp.
Sharing. An evidence package (a ZIP with the files, the page snapshot, the signed manifest, the public key, a certificate PDF and a README) leaves your device only when you download it and share it yourself. The Verify page checks a package on your device.
Deleting. Settings > Proof > Delete all proof records… removes the sealed records, their copies of the files and every page snapshot, including the snapshots of evidence captures waiting to be sealed. Deleting the Library removes the sealed records too, but not the snapshots of evidence captures waiting to be sealed. The signing key stays so that fingerprints you shared keep matching; it is removed when you uninstall the extension.
Presets, brand kit, watermark and automatic export
Pro stores your export presets (formats, PDF layout, header and footer, file-name and folder patterns), the preset for the PRO button, your brand name and colour, logos you add, your default watermark (its text or logo, place, size and opacity, and whether it is on) and your pattern for the names of normal downloads. Logos are saved again as PNG, which removes photo metadata such as location. When the default watermark is on, it is drawn into what you download, copy or print as PDF, and into Batch downloads; Recent captures can still give you the untouched original. If you switch on automatic export for a preset, each new capture is exported with that preset without another click; it is off by default and applies to one preset at most. Delete presets and logos in Settings > Presets & brand kit; switch the watermark off with the Watermark button in the capture tab.
Pro also stores your default browser frame: whether it is on, the window style and theme, the colour of its window buttons, which address it shows (by default the domain only) and an address you type yourself under Custom… (at most 200 characters), whether it shows the page title, the site icon, the background (with your own colours), padding, shadow, corners, the image size and, for a fixed image size, which part of the page it shows. When the frame is on, it is drawn around what you download, copy or print as PDF, and around presets set to use it. A Batch run's PDF and overview image follow it too, unless you choose otherwise on the Batch page; any address shown comes from that page, never from a custom address; Hidden stays hidden. The capture you keep, the Library, evidence files and tickets never get it. A custom address is only drawn into the frame: it never replaces the page address that the Library, Batch, evidence records or tickets keep. Switch the frame off with the Frame button in the capture tab, or change it in Settings > Presets & brand kit > Default frame.
Capture helpers (per-site settings)
For the sites you set up, Pro stores the elements you chose to hide, whether to load lazy images first, and an optional extra wait. Each hidden element is stored as a CSS selector, which can contain an id, a class or an attribute value from the page (for example a cookie banner's label), with a short label that gives the element's tag, id or class and its size, never its text. The list shows which sites you configured. Hidden elements are hidden only while a capture runs and are shown again right after. Delete one site or all sites in Settings > Capture helpers.
Compare and ticket
Compare reads two captures from your Library and compares them on your device; it does not store the result. The change report PDF, the difference image and the copied summary are made only when you click them.
Copy for ticket and Save ticket bundle put, only when you click them, the image and these details on your clipboard or into a ZIP: the page address (with any user name or password removed; for a local file only its file name) and title, the capture time with its UTC offset and your time zone (for example Europe/Amsterdam), the capture type and pixel size, the screen size and pixel ratio, the browser and its version and the operating system, the extension name and version, and the capture's project, capture set, tags and note. The ZIP's environment.json also records when the ticket was made, the number of parts, the browser language, the operating system version and the full browser user-agent string, and the ZIP's README lists the SHA-256 hash of each image file.
Toolbar preference and local storage protection
The toolbar action (capture immediately or open the menu) is a local preference. The required contextMenus permission adds capture actions, Settings, Batch and Library to the extension icon's right-click menu; it adds no site access. Direct capture never turns Recent captures or the Library on without your choice.
The Library and Recent captures are not application-encrypted vaults. Their protection on the device depends on the browser profile and operating system; this beta provides no separate password for local storage. A Proof signature checks integrity and does not encrypt the capture or its evidence records.
Optional permissions
Pro asks for these only inside your click on a control that needs them. Chrome decides whether a permission prompt is needed; previously allowed access may be granted without another prompt.
- Local PDF access: Full PDF reads every saved page of the selected document locally. Chrome's file-access switch must allow access, and the capture action requests the optional file read permission. Chrome can remember it. Turn off Allow access to file URLs in extension settings to block file access. The extension never turns that switch on and never scans folders. A locally loaded development build can start with the switch enabled.
- Downloads: when an export saves several files at once, a split image or into a folder, when Batch downloads each capture as it finishes, and for the Save As setting of GoFullScreenshot. A single file saved straight to your Downloads folder works without it. File paths always stay inside your Downloads folder.
- Access to all sites: only for automatic Batch, as described above.
- Access to specific sites: for guided Batch, and, as in GoFullScreenshot, for a page embedded from another site that you choose to capture.
You can remove any permission in Chrome's extension settings.
Where the data is stored
All of it is in this Chrome profile, in the extension's own storage:
| Storage | What |
|---|---|
IndexedDB GoFullScreenProDB | Library captures (including imported images), evidence records, Batch runs, logos, the signing key, page snapshots waiting to be sealed, and small bookkeeping records (for example the time of the last backup, that you accepted the evidence notice, deletions you can still undo, which captures were already opened or downloaded automatically, the file names and folders of automatic exports, which can contain the page title or project depending on your name pattern, and the length of your Downloads folder path with your operating system type) |
chrome.storage.local goFullScreenProV2 | Pro settings, presets, brand kit, default watermark and default frame, the pattern for download names, the project and capture set for new captures, your Library, Batch and disclosure choices, how long your last Batch runs took per capture (only the times, for the time shown before a run), which Pro cards you closed and which Pro tips you saw, with the time, and the one-time note of what moved over from the earlier Pro beta |
chrome.storage.local goFullScreenProRecipes | Per-site capture settings |
chrome.storage.local goFullScreenProBatchGrants | The record of access a Batch run added, until it is cleaned up, and the sites Chrome switched off together with access to all sites (at most 50, offered for Allow again for 30 days) |
Web storage (localStorage) gfsp-batch-draft | A list of page addresses you typed on the Batch page but have not started yet, with your screen size and capture choices, so the page still has them when you open it again. Starting the run removes the addresses (the choices stay); deleting the Library removes all of it |
Web storage (localStorage) gfsp.popupRowSize | The height and top margin of the popup's Pro row, so its space can be reserved before it appears; no page content |
Web storage (localStorage) gfsp:popup-height:v1 | The height of the toolbar popup in pixels, so the next popup opens at that size; no page content |
Web storage (sessionStorage) gfsp:autodl:<capture> | The time a capture was downloaded automatically in this tab, so reloading the tab does not download it again; cleared with the tab's session |
Web storage (sessionStorage) gfsp-library-full-chip | Whether the Library capacity hint has appeared in this viewer tab; cleared with the tab's session |
chrome.storage.session goFullScreenProPending, goFullScreenProBatchSession, goFullScreenProNudgeSession | Short-lived capture intents (kept at most 10 minutes), a random marker for the current browser session, and which Pro tips you already saw or closed in this session; Chrome clears them when the browser closes |
IndexedDB GoFullScreenDB and chrome.storage.local settings | The GoFullScreenshot data described in its privacy policy (current capture, Recent captures, settings), kept separately for Pro BETA; Pro adds its own notes on the capture and, for Batch captures, the screen size used |
Nothing is stored in chrome.storage.sync, so nothing is copied to other devices by Chrome sync.
How long it is kept, and how to delete everything
Data stays on your device until you delete it, the Library limits remove older captures, or you uninstall the extension.
- Delete Library captures, runs and evidence records in Settings > Library, proof records in Settings > Proof, per-site settings in Settings > Capture helpers, and presets and logos in Settings > Presets & brand kit.
- Records of deletions you can still undo go once the deletion is final, or when you delete the Library. The other small bookkeeping records in the table stay until you uninstall the extension; the delete buttons above do not remove them. The earlier Pro beta's logo, watermark text and presets stay until you choose Reset to defaults in Settings or uninstall the extension.
- Uninstalling GoFullScreenshot Pro BETA deletes everything it stored in this browser, including the Library, presets, proof records and the signing key. Back up the Library first if you want to keep it.
- Files you downloaded (exports, backups, evidence packages) are ordinary files in your Downloads folder. The extension does not delete them, and once you share them, the recipients' own practices apply.
What Pro BETA never does
- Upload or send screenshots, page content, addresses, notes or settings anywhere.
- Browse or capture on its own: Batch opens only the addresses you listed, in its own capture window that you can see and stop; it may load the next two of them ahead in muted tabs of that window.
- Record keystrokes, clicks or scrolling.
- Use analytics, advertising, trackers or third-party services.
- Sell, rent or share data.
- Run remote code.
Preparing a page for capture
The capture engine temporarily stabilizes supported animations, fixed backgrounds and lazily rendered content, and waits for the page's existing visible images and fonts within bounded limits. This can cause the website's existing image or font resources to load from their original providers. Changes made by the extension are restored after capture or cancellation. Screenshots remain local; this adds no upload, telemetry or required permission.
Limited Use
The use of information received by GoFullScreenshot Pro BETA adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements:
- Data is used only to provide the extension's single purpose: capturing web pages you choose and turning those captures into deliverables on your device.
- No data is transferred to the developer or to any third party.
- No data is used for advertising, creditworthiness or any purpose unrelated to that single purpose.
- No human reads your data, because it never leaves your device.
Website visitors
Visits to gofullscreenshot.com, including this page, are described under "2. This website" in the GoFullScreenshot privacy policy. The extension does not send data to the website.
Changes to this policy
This is a beta, and features can still change. If Pro BETA starts handling data in a new way, this page and the Chrome Web Store listing are updated first, and the extension shows a notice explaining the change before the new practice starts.
Contact
For privacy questions, bug reports or support, use the GoFullScreenshot support page or the structured GitHub support request. Beta feedback goes to the same support page.
