Most privacy policies are long because the product collects a lot. This one is long because
it explains, line by line, why the product collects nothing. Frame Grabber has no servers,
no accounts and no analytics, and it never makes a network request.
Last updated 17 August 2026
Effective 17 August 2026
Applies to v1.2.0
Policy version 1.0
No account
Nothing to sign up for, nothing to log into, no identity attached to anything you capture.
No analytics
No event tracking, no usage counters sent anywhere, no crash reporting, no pixels.
No network calls
The extension has no server to talk to. It works with your machine offline once the video has loaded.
No remote code
Every line that runs ships inside the package you installed. Nothing is fetched or evaluated later.
01 Who this policy comes from
Frame Grabber is built and maintained by Rahul Gautam, an independent developer
working from India. There is no company behind it, no investor, no data team and no third party
with a commercial interest in what you capture. One person writes the code and one person answers
the email.
Product
Frame Grabber: Video Screenshot, a browser extension for Chrome, Edge, Brave,
Opera, Vivaldi and Firefox
This policy applies to the Frame Grabber browser extension in all of its builds, and to the
Frame Grabber pages hosted at rahulgautam.in/app/frame-grabber/. Where the two
differ, the difference is called out.
It does not cover the sites you visit while the extension is installed. YouTube, Vimeo, Twitch,
your university's lecture portal and every other page you watch video on have their own privacy
practices, and the extension has no influence over them. It also does not cover the Chrome Web
Store or Firefox Add-ons, which record install and update statistics under Google's and Mozilla's
own policies before the extension ever reaches your browser.
03 The short version
Frame Grabber does not collect, store, transmit, share, rent or sell any personal data. Every
action it performs happens on the machine in front of you. The developer never receives your
captures, your settings, your browsing history or any identifier that could be traced back to you,
because there is no channel through which any of it could arrive.
Specifically, none of the following is collected:
Name, email or identity Browsing or search history Location or IP address Keystrokes or clicks Passwords or form data Cookies or ad identifiers Payment information Page content beyond the video Your captured images
The Chrome Web Store listing declares every data category as not collected. That declaration and
this page describe the same code, and both are checked against the source before a release ships.
04 What the extension reads
A screenshot tool has to look at the page to do its job. Frame Grabber looks at as little as it
possibly can, and only at the instant you ask for a capture. Nothing is read while you are simply
watching.
The current frame of the video element. The pixels are copied from the video
into a canvas in your browser's memory and encoded as PNG, JPG or WebP. This is a true frame
grab at the video's decoded resolution, not a picture of your screen, so no other window,
notification or part of your desktop is ever in the image.
The video title, and on YouTube the channel name and video id. These fill in
the filename tokens, so the saved file is called something you can find again.
The page address and the current playback position. These build the timestamp
in the filename and the deep link back to that exact second, used in the embedded metadata and
in the optional sidecar text file.
That is the entire list. The extension does not read the comments, the recommendations sidebar,
the description, your subscriptions, form fields, cookies, local storage of the site, or anything
else the page happens to contain. None of the three items above leaves your computer.
05 Metadata inside your images
When Embed metadata into the image is on, which is the default, each capture
carries a record of where it came from, written into the file using standard fields: PNG text
chunks for PNG, and EXIF plus XMP for JPG and WebP.
Title
The video title
Author or Artist
The fixed credit line Frame Grabber by Rahul Gautam, recording which
tool produced the file, the way a camera records its model
Description
Where the frame came from, at which timestamp, at which resolution
Software
Frame Grabber plus the version number
Source
A link back to the exact second of the video
Creation date
When the capture was taken
No copyright field
No copyright or rights field is written in any format. The frame belongs to
whoever made the video, and claiming it inside the file would be wrong
This information stays inside the file, on your own disk. Nothing about it is reported anywhere.
It matters because a file you share carries it with you: post the image and the title and source
travel along. If you would rather they did not, turn off Embed metadata into the
image in Settings, and captures taken after that will be written clean.
Worth knowing before you publish: image metadata is readable by anyone who receives the file.
Some platforms strip it on upload and some do not. If a capture is sensitive, strip the metadata
or turn the setting off before you send it.
06 What is stored, and where
Frame Grabber uses your browser's extension storage to remember your own preferences between
sessions. All of it lives in your browser profile on your computer.
Your chosen export format and quality setting
Your filename template and download subfolder
Your in-page keyboard shortcut
The position, visibility and height of the capture button
Your toggles for the sidecar file, the clipboard copy, the rename step and metadata embedding
A running count of how many frames you have captured, which drives the {index} token
The title, channel, timestamp and resolution of your most recent capture, so the toolbar popup can
show it
If you are signed into your browser and have extension sync switched on, the browser may copy
these settings between your own devices using your own account, in the same way it syncs your
bookmarks. That transfer happens between you and your browser vendor. The developer has no part in
it and no access to it. Turn off extension sync in your browser settings if you would rather it
did not happen.
No history of your captures is kept. Only the most recent one is remembered, and it is overwritten
by the next capture.
07 What is transmitted
Nothing. Frame Grabber makes no network requests at all. There is no API to call, no telemetry
endpoint, no error reporter, no font or script pulled from a CDN at runtime and no third party
library loaded on the fly. Every asset it needs is inside the package you installed.
This is verifiable rather than merely asserted. Open your browser's developer tools, switch to
the Network tab, capture a few frames, and filter by the extension. You will see no requests
originating from it. You can also disconnect from the internet after a video has loaded and
capture as normal, because nothing in the capture path needs a connection.
08 Where your captures go
Captured images are written by your browser's own download mechanism into your Downloads folder,
using the filename and the optional subfolder you configured. If you turned on the save dialog,
they go wherever you point it. If you turned on the clipboard option, a copy is also placed on
your system clipboard so you can paste it straight into an editor or a document.
Both destinations are local to your computer. The developer never receives, sees, stores or backs
up a single capture. There is no cloud folder, no sync service and no gallery hosted anywhere.
What happens to a file after it lands on your disk is entirely up to you.
One consequence worth stating plainly: because captures are ordinary files in your Downloads
folder, anything else with access to that folder can read them. That is normal for any tool that
saves files, and it is the reason the extension does not hide them somewhere unexpected.
09 Permissions, one by one
An extension can only do what its permissions allow, so the permission list is the honest measure
of what a tool can reach. Here is every permission Frame Grabber requests and the exact feature
that needs it.
storage
Saves your own settings and the details of your last capture so the popup can
display them. Preferences only. No browsing data and no page content.
downloads
Writes the captured image, and the optional sidecar text file, into your
Downloads folder. The extension never starts a download you did not trigger, and it never
downloads anything from the network.
activeTab
Gives one off access to the single tab you are watching, at the moment you press
the shortcut or click the toolbar button. Access ends when you navigate away. This is what
lets the extension work on sites it has no standing permission for.
scripting
Injects the capture code into the specific frame holding the video, only once you
ask for a capture. Many players sit inside an iframe, so the extension first finds the right
frame, then injects into that one. All injected code ships in the package.
clipboardWrite
Places the captured image on your clipboard when the clipboard option is on. The
extension only ever writes to the clipboard, immediately after a capture you triggered. It
never reads the clipboard.
offscreen
Chrome only. A Manifest V3 service worker has no DOM and cannot write to the
clipboard, so a short lived hidden document performs that one write and closes. It renders
nothing and handles nothing beyond the image being copied.
youtube.com
The always-on YouTube integration: the button in the player control bar, your
capture key, and the title, channel and video id used to build the filename.
all other sites
Optional, and never requested at install time. It is asked for only if you turn
on Every other site with an HTML5 video in Settings, and only at that moment.
Revoke it in your browser and the extension notices and switches the setting back off by
itself.
If you never enable that last one, the toolbar button and the browser-wide shortcut still work
anywhere, because activeTab covers the tab you are actually looking at.
10 Third parties
The extension itself has no third parties. No processors, no sub-processors, no analytics vendor,
no advertising network, no crash reporting service, no A/B testing platform. Nobody is paid in
data, because no data is produced.
Two organisations sit between the developer and you regardless, and they are worth naming:
Google, through the Chrome Web Store, which distributes the Chrome build and
records anonymised install, uninstall and rating statistics under its own policies. The
developer sees only aggregate counts in the dashboard, never individual users.
Mozilla, through addons.mozilla.org, which plays the same role for the Firefox
build under Mozilla's own policies.
Neither relationship gives anyone access to your captures, your settings or your browsing. Your
data is never sold, rented, licensed or transferred to anyone, for any purpose, including to
determine creditworthiness or for lending. There is nothing to sell.
11 This website
The Frame Grabber pages on rahulgautam.in are static. They
set no advertising cookies, run no analytics scripts and build no profile of you. Two ordinary
things do happen when you load a page here, and both are worth stating:
Server logs. The web host records standard request data, which typically
includes your IP address, the page requested, the time and your browser's user agent. This is
how every web server on the internet works. It is used for security and to keep the site
running, and it is not combined with anything else or used to identify you.
Content delivery. Images on these pages are served from Cloudinary and the
Inter typeface is served by Google Fonts. Loading them means your browser makes a request to
those providers, which they log in the same standard way. No cookie from either is used to
track you across sites.
If you visit the donate page, any payment is handled entirely by the payment provider shown
there, under that provider's own terms and privacy policy. No card details ever reach this site
or the developer.
12 Security
The strongest security property here is structural rather than technical: there is no database to
breach, no server to compromise and no account to take over, because none of them exist. Data
that is never collected cannot leak.
What remains is the integrity of the code itself. Releases are built from a single source tree by
a zero-dependency build script, so no external package can slip something in. The extension
contains no remote code and evaluates nothing it downloads, because it downloads nothing. Every
update goes through the Chrome Web Store or Mozilla review process before it can reach you.
Your captured images sit in your Downloads folder under your operating system's own file
permissions. Protecting that folder, and the machine it is on, is the part that stays with you.
13 Retention and deletion
Nothing is retained by the developer, so there is nothing on any server to delete. The only
Frame Grabber data that exists anywhere is the settings block in your own browser profile, and
you control it completely.
Reset the settings. Open Settings and use the reset control to put every option
back to its default, including the capture counter and the last-capture record.
Remove everything. Uninstall the extension. Your browser deletes its stored
settings along with it. If extension sync was on, removing it also clears the synced copy from
your account.
Your images stay. Captures already saved to your Downloads folder are ordinary
files and are untouched by an uninstall. Delete them yourself if you want them gone.
14 Children
Frame Grabber is a general purpose utility with no social features, no messaging, no profile and
no content of its own. It does not knowingly collect information from anyone of any age,
including children under 13, because it does not collect information from anyone at all. There is
no age gate for the simple reason that there is nothing to gate.
If you are a parent or guardian and you believe some piece of information has somehow reached the
developer, write to ceo@rahulgautam.in and it will be
looked into and removed.
15 Your rights
Data protection law gives you rights over personal data that an organisation holds about you:
the right to access it, to correct it, to have it deleted, to restrict or object to its
processing, to take it elsewhere, and not to be subject to decisions made about you
automatically. Those rights exist under the EU and UK GDPR, under the California Consumer Privacy
Act as amended, and under India's Digital Personal Data Protection Act, 2023.
Frame Grabber holds no personal data about you, so in practice these rights are already satisfied
in full and by default:
Access
Everything the extension stores is already on your machine, readable in your
browser's extension storage. There is no copy anywhere else to request.
Correction
Every stored value is a setting you chose. Change it in Settings at any time.
Erasure
Reset the settings or uninstall the extension. Both are described in section 13.
Portability
Your captures are standard image files and your settings are a small block of
plain values. Nothing is locked into a proprietary format.
Objection
There is no processing to object to. Nothing is processed off your device.
Sale of data
No personal information is sold or shared as those terms are defined under the
CCPA. There is no opt out to offer because there is nothing to opt out of.
No international data transfer takes place, because no data leaves your device in the first
place. If you still want to exercise a right formally, or you disagree with anything on this
page, write to ceo@rahulgautam.in and you will get a
reply within 30 days. If you are in the EU, the UK or India, you also have the right to complain
to your national data protection authority.
16 Verifying all of this
A privacy policy is a promise, and promises are worth more when you can check them. Three ways to
check this one, in rising order of effort:
Watch the network. Open developer tools, go to the Network tab, capture a few
frames and look for anything originating from the extension. There will be nothing.
Pull the plug. Load a video, disconnect from the internet, then capture. It
works exactly as before, which is only possible if nothing is being sent.
Read the source. The extension is MIT licensed and its source is published.
Every file that runs in your browser can be read, and the store package is built from that same
tree by a build script with no dependencies.
17 Changes to this policy
If the extension's data practices ever change, this page is updated before the change ships, not
after. The date at the top always reflects the current text, and every revision is listed below
so you can see what moved and when. A change that materially affects your privacy will also be
noted in the release notes for the version that introduces it.
DatePolicyWhat changed
17 Aug 20261.0First published, covering Frame Grabber v1.2.0.
Continuing to use the extension after an update means you accept the revised policy. If you ever
disagree with a change, uninstalling removes everything the extension stored, immediately.
18 Contact
Questions about this policy, about what the extension does, or about anything you think it should
not do, go to one address and reach one person.
Replies come from a person, usually within a couple of days. If something in this policy is
unclear or reads as evasive, say so and it will be rewritten.
The whole policy, in four words
It stays on your computer. Take the frame, keep the file, tell nobody, including us.
Frame Grabber