Google Docs Invoice Template: 6 Privacy Risks (and the Fix)
Every Google Docs invoice template carries 6 hidden privacy risks — from revision history that travels with shared docs to PDF metadata that exposes clients. A hardened build process below.
Redact PDFs, extract bank statements, strip metadata, and process sensitive files without sending them to a server. Every tool runs in your browser using client-side JavaScript. Your documents never leave your device.
Create professional invoices & receipts, download as PDF
Generate pay stubs with deductions, download as PDF
Create QR codes for URLs, Wi-Fi, email & more
Create payment receipts & proof of payment PDFs
Rent receipts for landlords & tenants, download as PDF
Draw or type your signature, download as transparent PNG
Permanently remove sensitive information from PDFs
Combine multiple PDF files into one document
Extract specific pages or split into individual files
Reduce PDF file size while preserving quality
Rotate PDF pages — individually or all at once
Convert PDF pages to high-quality JPG or PNG images
Convert JPG, PNG, or WebP images to a PDF document
Convert WebP images to PDF documents
Convert Markdown text into a styled PDF document
Paste or type formatted text and download as PDF
Convert Apple HEIC photos to JPG or PNG format
Convert Google WebP images to JPG or PNG format
Convert WebP images to lossless PNG with transparency
Rename .jpeg files to .jpg (or vice versa) instantly
Convert JPG images to lossless PNG with transparency
Convert PNG images to smaller JPG files
Convert AVIF images to universally compatible PNG
Convert AVIF images to smaller, compatible JPG files
Crop photos with preset ratios — 1:1, 16:9, 4:3 & more
Resize photos for social media, web, or print
Reduce JPG, PNG, WebP file sizes while keeping quality
Add text watermarks to protect your photos
Strip metadata, GPS location & camera info from photos
Convert Matroska video files to universal MP4
Convert WebM videos to MP4 format
Convert legacy AVI videos to modern MP4
Convert uncompressed WAV audio to compact MP3
Convert MP3 audio to uncompressed WAV for editing
Convert lossless FLAC audio to portable MP3
Format, beautify, validate & minify JSON
Format, beautify & view XML with tree view
Convert CSV data to JSON format instantly
Convert JSON arrays to CSV for spreadsheets
Convert XML data to JSON format instantly
Convert text to Base64 or decode Base64 to text
Pick colors from images & convert between HEX, RGB, HSL
Browse SQLite databases, run queries & export to CSV
When you use most online PDF tools — Smallpdf, iLovePDF, Adobe's web apps — your file is uploaded to a remote server, processed there, and sent back to you. For those few seconds (or minutes), your document sits on someone else's infrastructure, subject to their retention policies, their breach risk, and the jurisdiction their servers happen to be in. For a cat photo, that's fine. For a bank statement, medical record, legal filing, or anything with an SSN on it, it shouldn't be.
FilePulp takes the opposite approach: nothing leaves your browser. Every tool — redaction, extraction, conversion, compression — runs entirely via JavaScript and WebAssembly on the device you're already using. The file you "upload" is actually just handed to your own browser's memory. It's never sent across the network. There's no server to breach, no retention policy to trust, no audit trail to subpoena. When you close the tab, the file is gone.
FilePulp's tools rely on a small stack of open-source browser libraries: pdf.js (Mozilla's PDF parser) for reading documents, pdf-lib for writing them back out, the Canvas API for image conversion, and ffmpeg.wasm for audio and video. None of these libraries make network requests with your file's contents. You can verify this yourself by opening your browser's Network tab while using any tool — the file data never appears in an outbound request. The only server traffic is loading the page itself, which you've already done.
This architecture is why FilePulp works offline after the first page load, why there's no file size limit imposed by us (only by your device's memory), and why we don't need to ask you to create an account. We literally couldn't store your files if we wanted to — they never reach us.
Accountants redacting client SSNs before sharing returns. Lawyers stripping PII from discovery documents. Healthcare workers handling PHI that can't touch third-party servers. Anyone emailing a bank statement to their landlord, accountant, or lender and wanting to hide account numbers first. Journalists publishing screenshots without GPS coordinates embedded in them. Anyone who reads privacy policies and doesn't trust "bank-level encryption" to mean what it says.
You don't have to be a privacy absolutist to prefer a tool that can't leak your data. You just have to have documents that you'd rather not hand to a stranger.