The Privvert Blog
Long-form, no-fluff writing on file privacy, format internals, and how to do everyday file tasks without handing your data to a stranger. Read our editorial guidelines for how we research, source, and verify what we publish.
AI tools and your files: what ChatGPT, Claude, and Gemini actually keep when you upload
Drag a contract into ChatGPT, upload a spreadsheet to Claude, hand a folder of photos to Gemini - and the question that almost nobody answers in the marketing is what happens to the file after the model has finished answering. The short version: it lives a lot longer than the reply does, in more places than the consent screen suggests, and the rules are different between the free tier, the paid tier, and the enterprise tier of the same product. There are also live legal carve-outs - the New York Times v OpenAI preservation order has forced ChatGPT to keep deleted chats since mid-2025 - that the in-app help pages do not mention. Here is what each of the big AI tools actually does with a file you upload, what 'we don't train on your data' actually means in 2026, the incidents that show what goes wrong when the policy and the reality diverge, and the practical answer for handling anything sensitive.
Why an 'unguessable' Dropbox or Google Drive link is not private
Generating a share link feels like the privacy-respecting choice. The file does not get emailed around, the URL is long and random, and only people you send it to can open it. The reality is messier: search engines have been indexing shared cloud links since at least 2014, the Wayback Machine has snapshotted plenty of them, browsers and password managers sync the URLs across devices that may not all be yours, the Referer header leaks the link to every third-party script on whatever page you paste it into, and a single screenshot that includes the address bar is enough to make the link public forever. There is a long record of real incidents - Box.com exposing tens of thousands of corporate files via guessed and indexed share links, Microsoft Power Apps leaking 38 million records through default-public sharing, OneDrive 'private' links appearing in Bing - to make the point that 'anyone with the link' is not a niche-case warning. Here is what actually happens to a share link after you create it, where it leaks, and the share settings that are genuinely private.
Local Image Editors vs Cloud Editors: Privacy and Performance Tradeoffs
Compare local image editors versus cloud platforms. Learn how data flow choices affect privacy, metadata security, and processing speed for sensitive visual assets.
What is Local-First Processing and Why Browsers Should Stay Local
Local-first processing keeps your files on your device while your browser handles the compute. Stop uploading sensitive documents to servers you don't control.
How to Compare Text Differences Online Without Leaking Confidential Data
Text comparison tools often upload your sensitive drafts or code to private servers. Learn the risks of server-side diffs and how to compare text locally.
How to Unzip Files in Browser Safely Without Privacy-Violating Uploads
Stop uploading sensitive ZIP archives to remote servers. Learn how to extract files locally in your browser and why on-device processing is critical for privacy.
Local File Processing: Why Your Files Should Never Leave Your Device
Stop uploading sensitive documents to stranger's servers. Learn how local file processing via JavaScript and WebAssembly keeps your data and metadata private.
How to Convert HEIC Photos Locally Without Giving Data to Cloud Converters
Learn to convert HEIC to JPEG or PNG privately using on-device processing. Preserve image quality and metadata without exposing your photos to remote servers.
How to Redact PDF Files Locally Without Leaking Sensitive Data
Black boxes aren't enough. Learn how to redact PDFs locally to permanently remove text, OCR layers, and metadata without uploading files to third-party servers.
The 'Print to PDF' trap: what your exported PDF still contains - and what a screenshot leaves out
Print to PDF feels like flattening a document to a clean, sealed file. It is not. The PDF that comes out the other side typically still contains the full selectable text under every black box, the original author name and editing history in the metadata, hidden layers from the source application, comments and tracked changes you thought you removed, and - on macOS and Windows - a record of the printer driver and the machine that produced it. A screenshot of the same PDF, by contrast, is a flat bitmap with none of that. Here is what Print to PDF actually preserves, why a flattened screenshot leaks less in many real cases, when each is the right tool, and how to produce a PDF that is genuinely safe to send.
Do Browser Tools Store Files? The Difference Between In-Browser and On-Device
Understand how browser tools handle your files. Learn to distinguish between temporary RAM, persistent browser storage, and risky remote server uploads.
Online vs Offline File Converters: Why Local Processing is the Only Safe Default
Don't trade privacy for convenience. Learn why uploading files for conversion creates unnecessary risks and how local-first tools protect your data.
Why Local-First Browser File Tools Are the Only Safe Choice for Privacy
Stop uploading sensitive PDFs and photos to unknown servers. Learn why Privvert and on-device browser tools are the best way to process files without data leaks.
Verify No File Upload: Check If Your Privacy is Actual or Marketing
Stop trusting marketing claims. Use browser DevTools and offline testing to verify that your files stay local and are never uploaded to a remote server.
Do Online File Converters See Your Data? The Reality of Server-Side Uploads
If you upload files to free online converters, the service can see your data. Learn why server-side processing is a risk and how to use local-first tools instead.
What a Privacy-First File Converter Actually Does (and Doesn't) Do
Stop uploading sensitive documents to unknown servers. Learn why local, in-browser conversion is the only way to protect your PDFs, images, and data.
Browser PDF Tools vs Desktop Apps: Speed, Privacy, and Local Processing
Compare browser-based PDF tools with desktop applications. Learn why local, on-device processing is the only safe way to handle sensitive documents without uploads.
Your smart TV is the chattiest device on your home network - here is what it actually sends
A modern Samsung, LG, Sony, Roku, or Fire TV is a full Linux or Android device with a microphone, a camera-style frame grabber that snapshots whatever is on the screen several times per second, and a permanent connection to half a dozen ad and analytics endpoints. The technology is called ACR - automatic content recognition - and it runs whether you stream from the TV's built-in apps, plug in an Apple TV, or watch a Blu-ray. Here is what ACR captures, what your TV sends home over the network, which settings actually turn it off, and how to isolate the TV on a separate VLAN or guest network so the rest of the house is not on the same wire.
How to Compress Video in Browser Without Leaking Data to Servers
Don't upload private footage to unknown servers. Learn how to compress video in-browser using on-device processing to protect your privacy and reduce file size.
How to Protect PDF Files with Passwords without Sacrificing Privacy
Learn why most PDF protection tools fail, the difference between AES-256 and permissions, and why you should never upload sensitive files to add a password.
How to Extract PDF Pages Locally Without Compromising Private Documents
Learn to extract PDF pages locally on your device to ensure sensitive files never reach a remote server. Keep document data private with browser-based tools.
On-Device Image Resizing: How to Scale Photos Without Uploading Data
Stop uploading sensitive screenshots and photos to random servers. Learn how to resize images in the browser locally using high-performance, private tools.
Why You Should Convert WebP to PNG Locally Instead of Uploading
Stop uploading sensitive WebP files to random converters. Learn why local processing is the only way to protect confidential Mockups and avoid metadata leaks.
How to Base64 Encode Files Locally Without Uploading to a Server
Stop uploading sensitive binary data to random converters. Learn why local Base64 encoding is safer for protecting your documents, keys, and code.
On-Device Hash Generators: Why Local Verification Beats Uploading Sensitive Files
Sending files to a server for hashing defeats the purpose of verification. Learn why on-device SHA-256 generation is the baseline for security and privacy.
USB-C cables are computers: what a charging cable can actually do
The cable in your bag is not a passive wire. Modern USB-C cables contain a chip, negotiate power levels with the device, and - in the malicious version - can contain a full microcontroller with Wi-Fi that pretends to be a keyboard the moment you plug it in. Here is what a charging cable can actually do in 2026, why juice jacking is back in the headlines, how the O.MG cable works, how to spot a sketchy cable, and what USB Restricted Mode and the equivalents on Android actually protect against.
Offline JWT Decoders: Why Local Inspection Beats Sending Tokens to Strangers
Stop pasting production JWTs into random web decoders. Learn how offline JWT decoding protects sensitive claims and why no-upload tools are safer for debugging.
Why You Need a Local-First Browser Based JSON Formatter for Private Data
JSON often carries tokens and customer data. Learn why processing JSON in the browser is safer than uploading payloads to remote formatter servers.
How to Sign a PDF in Your Browser Without Sacrificing Privacy
Don't upload sensitive contracts to server-side converters. Learn how to sign PDFs in your browser locally and tell if your files are actually safe.
Why You Should Compress Images Without Uploading to Remote Servers
Stop handing private photos to unknown servers. Learn how to compress images locally to protect metadata, GPS coordinates, and sensitive content.
Merge PDF Files Locally Without Sharing Sensitive Data with Third Parties
Combine your PDF documents on-device. Avoid the risks of online file converters and maintain document privacy by merging files in your browser locally.
How to Remove Image Metadata Without Uploading Your Files
Stop leaking GPS, timestamps, and device details. Learn how to remove image metadata locally in your browser using Privvert for maximum privacy.
Choosing a Private PDF Redaction Tool: Why Uploading Files Is a Security Risk
True PDF redaction requires permanent data removal, not just black boxes. Learn why local-first processing is the only safe way to redact sensitive documents.
What 'delete' really does - on your phone, in the cloud, on an SSD
Tap delete and the file disappears from the screen. What actually happened underneath depends entirely on where the file lived. On a phone it usually goes to a 30-day bin and a thumbnail cache that outlives the bin. In iCloud or Google Photos it lingers in a recycle folder, in a shared-album cache, and in a machine-learning index for longer than that. On an SSD the bytes can stay readable for weeks because of wear-levelling, which is why 'secure erase' on a modern drive means something completely different than it did on a spinning disk. Here is what actually happens at each layer, and how to delete in a way that holds.
VPNs explained without the marketing bullshit: what they hide, what they don't, and when Tor is the right tool
Every 'do I need a VPN' search result is written by a VPN company, and the honest answer is more boring and less flattering. A VPN moves the entity that sees your traffic from your ISP to a private company whose entire pitch is that they will not look at what they can see - and the industry has a long, well-documented record of 'no-logs' providers producing logs the moment a subpoena arrives, from HideMyAss handing over LulzSec logs in 2011 to IPVanish and PureVPN doing the same despite identical marketing. Here is what a VPN actually does on the wire, what it does not do (anonymity, fingerprinting, the apps already phoning home over the same tunnel), why the free-VPN category is mostly the user-as-product business model, why we do not recommend one by default for ordinary users, the narrow cases where one is genuinely worth it, and when the right answer is Tor instead.
What 'end-to-end encrypted' actually means (and what it doesn't cover)
The phrase is on every messaging app's marketing page, but it covers a smaller surface than the headline suggests. End-to-end encryption protects the contents of a message from the network and the server in the middle. It does not protect the metadata around it, the backups on either end, the screenshot the other person takes, or the device that gets unlocked at a border crossing. Here is what E2EE actually does, how Signal, WhatsApp, iMessage, and Telegram differ in practice, and the gaps you should plan around.
Sign in with Google, Facebook, or X: what you actually trade for the convenience
One click and you're in - no new password, no verification email, no forgotten-password loop next year. The trade is real though: the social provider now knows every site you log into with the button, the site gets a different slice of your profile depending on which button you pressed, and losing the upstream account can lock you out of years of history. Here is what each big button actually sends, what breaks when the account goes away, and when email-and-password is the better privacy choice.
How long should a password actually be in 2026? The math, the myths, and why MFA is the real answer
Password length is the wrong question. A 16-character password and an 8-character password fall to the same phishing page, the same infostealer, and the same breached-database lookup. The thing that actually stops account takeover in 2026 is a second factor - and increasingly, no password at all. Here is the math behind the length debate, why 90-day rotation and complexity rules make passwords weaker, and what to set up instead.
Five things your browser sends to every website you visit (and how to stop them)
Before you type a single word, your browser has already told the site your IP, your operating system, your fonts, your screen, your time zone, and enough rendering quirks to identify you across sessions. Here is exactly what gets sent, why it works as a tracking signal, and what actually shrinks the surface.
PDF or image? How to choose the right format for sensitive documents
Should you send the contract as a PDF or a photo? Save the ID scan as JPEG or stick it in a PDF? Each format leaks different things, behaves differently when forwarded, and changes what the recipient can do with it. Here is a working guide to picking the format that fits what you are actually sending.
PDF redaction done right: why black rectangles in Word and Preview don't work
Drawing a black box over a name in Word, Preview or Acrobat's markup tools does not delete the text underneath - it sits on top of it, fully selectable and copyable. Here is what real PDF redaction looks like, the well-documented incidents that prove the point, and how to do it locally without uploading the file.
WebP vs JPEG vs AVIF in 2026: which image format to actually use
Three image formats, three sets of trade-offs, and a lot of confident-sounding advice on the internet that is out of date or wrong. Here is what each format actually does, where it wins, where it loses, what current browsers and platforms support, and how to pick without overthinking it.
How to remove metadata from photos before sharing
Your photos carry hidden data: GPS coordinates, device serial numbers, timestamps, and more. Here is exactly what is in there, why it matters, and how to strip it - on every platform, without uploading anything.
The hidden risks of online file converters (and how local processing fixes them)
Free online converters look harmless. Behind the scenes, your file is uploaded, processed on someone else's server, logged, often retained, and sometimes scanned or sold. Here is what actually happens - and what to use instead.