zapmetadata.com
Workbench
Zap Metadata
Zap Metadata
Zero-Server In-Browser Guarantee

Privacy Policy

We believe privacy is an inviolable human right. Zap Metadata was engineered with a zero-knowledge architecture: your files never leave your device.

📅 Effective Date: November 12, 2026🔄 Last Updated: November 12, 2026🛡️ Zero Data Collected
⚡

Executive Privacy Summary

Everything you need to know in 30 seconds

✓ Zero File Uploads

Files dropped into Zap Metadata are parsed entirely inside your browser's local RAM using TypedArrays and ArrayBuffers. No bytes ever leave your device.

✓ Zero Telemetry & Logging

We do not track file names, metadata tags, IP addresses, geolocation, camera models, device fingerprints, or AI prompt strings.

✓ Zero Tracking Cookies

We set zero advertising, profiling, or third-party marketing cookies. Only your local light/dark visual theme preference is saved in localStorage.

✓ 100% Offline Capability

Once loaded, you can disconnect your computer from Wi-Fi or enable Airplane Mode. The metadata scrubber continues to operate completely offline.

1. The Zero-Server Architecture

Unlike traditional online file converters or cloud-based metadata scrubbers (which require transmitting your private photos, legal briefs, medical records, or sensitive contracts across public networks to remote web servers), Zap Metadata executes 100% client-side.

When you select or drag a file into the Zap Metadata workbench:

  • The browser's native FileReader API reads the file directly from your local filesystem into sandboxed browser memory (RAM).
  • Our compiled JavaScript and WebAssembly binary parsers inspect and excise metadata markers (such as JPEG APP1 EXIF/XMP segments, PNG tEXt/iTXt chunks, WebP RIFF headers, PDF Info dictionaries, and Microsoft Office XML packages) at the byte level.
  • The cleaned file is reconstructed in memory as a binary Blob and served to your browser's download manager via an ephemeral blob: URL.
  • No remote server is ever contacted during the inspection or cleaning process. The data remains strictly isolated in your browser tab.

🔍 How You Can Independently Verify Our Zero-Server Claim

True privacy requires transparency, not blind trust. You can independently confirm our zero-server architecture at any time using your own browser:

  1. Open your browser's Developer Tools by pressing F12 (or Cmd + Option + I on macOS).
  2. Switch to the Network tab and check the Fetch/XHR filter.
  3. Drop any photo, PDF, or video into Zap Metadata and click Zap Metadata.
  4. Observe the Network activity: zero outbound HTTP POST/PUT network requests are initiated.

2. Information We Do NOT Collect

Because our architecture operates without remote processing servers, we do not possess the technical capability to harvest, store, or log your personal data:

✕ No File Contents or Metadata

We never see your photos, documents, videos, GPS coordinates, author names, camera serial numbers, or AI generation prompts.

✕ No IP Addresses or Geolocation

We do not log user IP addresses or geographical positions when you sanitize files on the platform.

✕ No User Accounts or Passwords

Zap Metadata requires no registration, no sign-in, and no personal profile creation. Use is completely anonymous.

✕ No Cross-Site Ad Trackers

We do not deploy Facebook Pixels, Google Tag Manager marketing trackers, retargeting scripts, or third-party fingerprinting.

3. Cookies & Client-Side Local Storage

Zap Metadata does not use cookies for tracking, behavioral profiling, or advertising purposes.

We utilize the standard browser localStorage API exclusively for strictly necessary, non-identifying user interface preferences:

  • theme: Stores your preference for Light or Dark mode ('dark' or 'light') so you don't experience a screen flash on subsequent visits.

You can clear or disable your browser's local storage at any time through your browser settings without impacting the core metadata stripping capability.

4. Global Privacy Compliance (GDPR & CCPA/CPRA)

Zap Metadata is architected in full alignment with the European Union General Data Protection Regulation (GDPR), the United Kingdom Data Protection Act, and the California Consumer Privacy Act as amended by the California Privacy Rights Act (CCPA/CPRA):

Privacy by Design & Default (GDPR Article 25)

Because our system is engineered to eliminate data transit and storage before processing ever begins, personal data protection is embedded directly into the software architecture. No personal data controllership or data processing agreements are triggered because no user data is handled by our servers.

Your Data Subject Rights (Access, Deletion, Rectification)

Under GDPR and CCPA, individuals possess the right to access, rectify, port, or erase their personal information. Because Zap Metadata stores zero records, customer identifiers, or uploaded files, we hold nothing to erase, export, or disclose. Your data remains in your exclusive possession at every microsecond of the process.

Sale and Sharing of Personal Information (CCPA/CPRA)

We do not sell, rent, license, or share personal information with any third party for monetary or other valuable consideration.

5. Children's Online Privacy Protection Act (COPPA)

Protecting the privacy of young children is especially critical. Zap Metadata does not knowingly collect, solicit, or maintain any personal data from individuals under 13 years of age (or under 16 in the European Union). In fact, because we collect zero data from any user regardless of age, children's privacy is rigorously protected by default.

6. Technical Security & Memory Lifecycle

When you scrub metadata with Zap Metadata, temporary object references created in browser memory are scoped to the active window lifecycle. As soon as you navigate away, refresh the tab, or close your browser, the temporary memory allocations are automatically garbage-collected and destroyed by your operating system.

All static web assets (HTML, CSS, JavaScript) for Zap Metadata are delivered exclusively over encrypted HTTPS with HTTP Strict Transport Security (HSTS) and modern TLS protocols, preventing man-in-the-middle attacks or code tampering.

7. Changes to This Privacy Policy

We may occasionally update this Privacy Policy to reflect enhancements to our tool, new format support, or changes in applicable privacy laws. Any modifications will be posted directly to this URL with an updated "Last Updated" revision timestamp. Our fundamental zero-server architecture and commitment to zero-data collection will never change.

✉️

Privacy Questions & Contact

If you have questions, feedback, or technical security inquiries regarding our privacy practices or zero-server architecture, please reach out to our privacy team:

📧 Email [email protected]💬 Contact Support Page

Clean Your Files with Zero-Server Privacy

Remove EXIF, GPS locations, author credentials, and AI prompts in seconds right from your browser.

Launch Zap Metadata Workbench