Document Public Info Exposure with Screenshots
This guide walks you through creating a timestamped, visual record of your publicly exposed personal information using automated webpage screenshots. You’ll learn how to capture pages that display your data, organize the evidence, and store it securely. This is useful for personal audits, privacy complaints, or simply understanding your digital footprint.
What You’ll Need
- A computer with internet access.
- A web browser (Chrome, Firefox, Edge, or Safari).
- A list of URLs where your information may appear (e.g., social profiles, directory sites, data brokers).
- Basic familiarity with your operating system’s command line (optional but helpful).
Step-by-Step
- List your target URLs. Create a plain text file (e.g.,
urls.txt) with one URL per line. Include only pages you have permission to view and that are publicly accessible without logging in. - Choose a screenshot tool. For a simple, no-code approach, use a browser extension like “Full Page Screen Capture” (Chrome) or “FireShot” (Firefox/Chrome). For automation across many URLs, use a command-line tool like
puppeteer(Node.js) orplaywright(Python/Node.js). - Set up a project folder. Create a folder on your computer, e.g.,
exposure-docs. Inside, create subfolders:screenshotsandlogs. - Write a simple script (if using automation). Here’s a basic Puppeteer script that visits each URL, waits for the page to load, and takes a full-page screenshot:
const puppeteer = require('puppeteer'); const fs = require('fs'); const urls = fs.readFileSync('urls.txt', 'utf-8').split('\n').filter(u => u.trim()); (async () => { const browser = await puppeteer.launch(); for (let i = 0; i < urls.length; i++) { const url = urls[i].trim(); if (!url) continue; const page = await browser.newPage(); await page.goto(url, { waitUntil: 'networkidle2', timeout: 60000 }); await page.screenshot({ path: `screenshots/shot-${i+1}.png`, fullPage: true }); console.log(`Captured: ${url}`); await page.close(); } await browser.close(); })();Run it with
node script.js. - Add timestamps to each screenshot. Use a tool like
exiftoolto add the capture date to the image metadata, or rename the files to include the date and time. For example,2025-04-14_15-30-00_example.com.png. - Verify each screenshot. Open each image and confirm it shows the expected content and that the URL is visible in the address bar (if your tool captures it). If a page fails to load, note that in a log file.
- Create a log file. For each capture, record the URL, the date/time, and any errors. This log is your evidence chain.
- Store everything securely. Move the folder to an encrypted drive or a password-protected cloud folder. Do not share the screenshots unless you intend to file a complaint.
Common Mistakes
- Not waiting for dynamic content. Pages that load content via JavaScript may need extra time. Use
waitUntil: 'networkidle2'or a manual delay. - Capturing only the visible viewport. Your personal info might be below the fold. Always take full-page screenshots.
- Forgetting to log errors. If a page returns a 404 or a login wall, you need to know. Your log should capture that.
- Using a personal account to view pages. Logging in can change what you see and may violate the site’s terms. Use a private/incognito window or a separate browser profile.
- Storing screenshots in plain sight. These images contain sensitive data. Encrypt them.
Tips
- Use a headless browser for automation to avoid opening many windows. In Puppeteer, use
puppeteer.launch({ headless: true }). - Set a custom user agent if a site blocks default headless browsers. But be ethical—only use it for your own data.
- Run the script during off-peak hours to reduce the chance of rate-limiting.
- Keep a master spreadsheet with columns: URL, screenshot filename, date, status, and notes.
- If you need to prove the date, use a service like
timestamp.photoor include a clock in the screenshot (e.g., by opening a new tab with time.is).
Troubleshooting
- Screenshot is blank or partial. The page may not have finished loading. Increase the timeout, or add a delay:
await page.waitForTimeout(3000). - Site blocks automated access. Try a different user agent, or use a real browser extension that simulates a manual capture. If the site has a CAPTCHA, you may need to capture manually.
- Full-page screenshot cuts off. Some pages have infinite scroll. Use a tool that scrolls and stitches, or manually scroll and take multiple screenshots.
- Puppeteer not installing. Ensure Node.js is up to date. Run
npm init -ybefore installing puppeteer. - URLs with special characters. Encode them properly in the text file, e.g., use
%20for spaces.
Frequently Asked Questions
Is it legal to screenshot public web pages?
Generally yes, if the page is publicly accessible and you’re not bypassing login or access controls. However, using the screenshots for harassment or doxxing is illegal. This guide is for documenting your own exposure.
What if a page requires login to see my info?
That’s not public exposure. Logging in to capture it may violate the site’s terms. Focus only on pages that are openly accessible.
Can I use this for a data broker removal request?
Yes, many data brokers require evidence of the listing. Screenshots with timestamps can support your request.
How long should I keep the screenshots?
Until you’ve resolved the issue and are sure you no longer need them. Then delete them securely (e.g., using file shredding software).
What if the page changes after I capture it?
That’s why you have a timestamp. You can also use the Wayback Machine to show historical versions, but your own screenshot is more direct.
Do I need to redact other people’s info in the screenshots?
Yes, if you plan to share them. Use an image editor to blur names, addresses, or photos of third parties.
Related
Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.