Privacy Policy
Last updated: 8 September 2026
This policy describes what PrivaQuickTools actually does with data. It is written against the code that runs the site rather than against a template, and it is revised when the implementation changes. Where a third party is involved, that third party is named.
Who runs this site
PrivaQuickTools is an independently built and maintained project operated by one individual, not by a company. The source code is public at github.com/vishalanand1997/privaquicktools, so the claims below can be checked against the code that produces them. The site is built with Next.js and hosted on Vercel. Pages are mostly generated ahead of time and served as static files over HTTPS, with HTTP Strict Transport Security enabled.
The operator can be reached through the contact form. There is no published email address; the form is the only contact route.
What the tools do with your files and text
Nothing you put into a tool is collected, because nothing you put into a tool is sent anywhere. The PDFs, images, video, audio and text you work with are read into the browser tab, processed there by JavaScript and WebAssembly running on your own device, and written back out as a file you download. There is no upload step and no server-side copy, so there is nothing on the operator's side to store, read, retain or hand over.
This follows from the architecture rather than from a promise about conduct: the site has no upload endpoint for tool input, and you can confirm that yourself by opening your browser's Network tab while you use a tool. The How it works page explains how to do that, and is equally explicit about what this design does not protect against.
Three parts of the site do make network requests, and they are described under third-party downloads and the IP lookup below.
Analytics
The site can use Google Analytics 4. The script is injected only after you grant the analytics category in the consent banner. If you decline, or if you have made no choice yet, the script is never loaded and Google Analytics receives nothing at all — no page view, no identifier, no request.
Once loaded, Google Analytics records the ordinary measurement data it is designed to collect: which page was viewed and when, the referring page, approximate location derived from the IP address, device, browser and operating system details, and a randomly generated identifier stored in a Google cookie so that repeat visits within a session can be counted as one visitor. It is used to see which tools are worth maintaining. It never receives the contents of anything you process, because those contents never leave the page.
Google's handling of this data is described in how Google uses information from sites that use its services.
Advertising
The site is set up to display Google AdSense advertising, which is what pays its running costs. As with analytics, the AdSense script is injected only after you grant the advertising category in the consent banner. Advertising is configured through an environment variable, so depending on how the site is currently deployed, ads may not be displayed at all. When advertising is enabled and you have consented, the following applies.
- Third-party vendors, including Google, use cookies to serve ads based on your prior visits to this site and to other sites.
- Google's use of advertising cookies enables it and its partners to serve personalised ads to you based on those visits.
- The file at
/ads.txtauthorises the publisher accountpub-9161049309390906to sell advertising on this domain. It contains no information about visitors.
You can opt out of personalised advertising in Google Ads Settings, and read how Google uses data from partner sites at policies.google.com/technologies/partner-sites. Declining the advertising category in the banner prevents the script from loading here in the first place.
The contact form
The contact form is the one place on this site where you deliberately hand over personal data, and it is worth being precise about where it goes.
The form asks for a first name, a last name, a mobile number, a country and a message. When you submit it, those five values, plus the date and time of submission, are sent to this site's own server route and appended as a row to a Google Sheet owned by the site operator. The write is performed by a Google service account. This is a real transfer of your personal data to Google Workspace, and it is subject to Google's terms and its handling of data in that service.
- The data is used only to read your message and to reply to it if a reply is needed and possible.
- Rows remain in that sheet until the operator deletes them. There is no automatic expiry.
- The data is not used for marketing, is not sold, and is not shared with anyone beyond Google as the provider of the spreadsheet.
- Because the form is not encrypted end to end and the contents are stored in a spreadsheet, you should not put confidential file contents, credentials or sensitive personal details into the message field.
The IP address lookup
The Device Info tool shows you the public IP address your connection presents. To do that, the page calls this site's own /api/ip route, which reads the address from the x-forwarded-for or x-real-ip header of your request and returns it to you. The address is not written to any database or file by the application. It appears in the hosting platform's ordinary request logs in the same way that every other request to the site does.
No other tool on this site sends anything to a server for processing.
Storage in your browser
This site's own code sets no cookies. It uses exactly two keys in your browser's local storage:
theme— whether you chose the light or dark appearance.pqt-consent-v1— your consent decision for analytics and advertising, together with the time you made it, so the banner does not ask again on every page.
Both stay on your device and are never transmitted. If you consent to analytics or advertising, Google's own scripts then set their own cookies under Google's control; those are listed in the cookie policy.
Third-party downloads
Four tools need a processing engine that is too large to ship with every page, so they fetch it from a public CDN the first time you use them. Your file is not part of that request — only the engine is downloaded — but the request itself reveals your IP address, and normal request metadata such as your browser's user agent, to the CDN operator.
- Video Trimmer, Audio Converter and GIF Maker download the FFmpeg WebAssembly engine, roughly 30 MB, from unpkg.com on first use.
- OCR PDF downloads the Tesseract recognition engine and its English language data, roughly 15 MB, from the jsDelivr CDN on first use.
Two things that often are third-party requests are not, here. The face-detection models used by the privacy blur tool are served from this site's own domain. Fonts are self-hosted through Next.js, so no request is made to Google Fonts at runtime.
Server logs
The site is hosted on Vercel, which keeps ordinary request logs for the pages and routes it serves. Those logs contain the sort of information every web server records: the requested URL, a timestamp, the response status, the user agent and the originating IP address. They exist for operating the service — diagnosing errors, seeing that a deployment works, absorbing abuse — and are retained according to Vercel's own retention periods for its platform logs. The application does not copy them anywhere else and does not build profiles from them.
How long anything is kept
- Tool input: not retained, because it is never received. It exists in the tab while you work and is gone when you close or reload it.
- Contact form entries: kept in the operator's Google Sheet until deleted.
- Browser storage: kept on your device until you clear site data for this site.
- Analytics and advertising data: held by Google under Google's retention settings and policies, not by this site.
- Server logs: held by Vercel under its platform log retention.
Changing or withdrawing consent
Your decision is stored only in your browser, in the pqt-consent-v1 key. To change it, clear site data for this site in your browser settings. That removes the stored decision, and the consent banner appears again on your next visit so you can choose differently. Clearing site data also removes any cookies Google set while consent was granted, and your saved theme preference.
Withdrawing consent stops the scripts from loading on future page views. It does not retroactively remove data Google already collected while consent was in force; for that, use Google's own controls, including Google Ads Settings.
Children's privacy
This site is not directed at children under 13. It has no accounts, no profiles and no age-gated features, and it does not knowingly collect personal data from children. The only way to submit personal data here is the contact form. If you believe a child has submitted personal data through it, use the form to ask for the entry to be deleted and it will be removed from the sheet.
Access, correction and deletion
For most of the site there is nothing to exercise these rights against, because no personal data about you is held. The exception is the contact form. If you have submitted the form, you can ask for a copy of what was recorded, ask for it to be corrected, or ask for the row to be deleted. Send that request through the contact form, including enough detail — the name and approximate date you used — for the entry to be found.
Data held by Google as a result of analytics or advertising is handled under Google's own policies and controls, which are linked above.
Changes to this policy
This policy describes a specific implementation. If that implementation changes — a new tool that makes a network request, a different analytics or advertising provider, a change to how contact messages are stored — this page is updated at the same time and the date at the top changes with it. Continued use of the site after a change means the revised policy applies to that use.