Skip to main content
DM

DiffMaster

Professional Code Comparison

100% Private

Privacy Policy

Last Updated: October 31, 2025

Our Commitment to Privacy

DiffMaster is built with privacy as a core principle. We designed this tool to operate entirely in your browser, ensuring your code and data never leave your device.

Data Collection & Storage

What We Collect

Nothing. We do not collect, store, or transmit any of your data to our servers.

Local Storage Only

  • Comparison History: Stored in your browser's IndexedDB
  • User Preferences: Stored in your browser's localStorage
  • Location: Browser only - never uploaded to servers
  • Retention: User-controlled - clear anytime via History panel
  • Access: Only you can access this data on your device

What We DON'T Collect

  • ❌ No user accounts or authentication
  • ❌ No cookies (except essential session cookies for the site to function)
  • ❌ No analytics or tracking scripts
  • ❌ No third-party trackers
  • ❌ No server-side logging of your code
  • ❌ No behavioral tracking
  • ❌ No personally identifiable information (PII)

How DiffMaster Works

100% Client-Side Processing

  1. You paste or upload code into the editor
  2. Your browser computes the diff using JavaScript
  3. Results are displayed instantly in your browser
  4. Nothing is sent to our servers

Shareable URLs

When you generate a shareable URL:

  • Your code is encoded in the URL hash (the part after #)
  • The hash is processed by your browser, not our servers
  • We never see or store the URL content
  • Security Warning: Anyone with the URL can read your code
  • Recommendation: Only share URLs with trusted recipients
  • Consider using private sharing methods (encrypted messaging, etc.)

File Uploads

When you upload files:

  • Files are read entirely in your browser using the FileReader API
  • No files are uploaded to servers
  • File content is processed locally in JavaScript
  • Your files never leave your device

Third-Party Services

No Third-Party APIs

  • DiffMaster does not integrate with third-party APIs for core functionality
  • All diff algorithms run locally in your browser
  • No external service dependencies

AI Features

  • DiffMaster does not currently use AI or LLM APIs
  • If AI features are added in the future, we will update this policy with:
    • Which AI provider is used
    • What data is sent (only with explicit user action)
    • How data is processed
    • Clear consent mechanisms

Your Rights & Controls

Data Control

  • View: All data is stored locally - inspect using browser DevTools
  • Export: Use browser tools to export your IndexedDB data
  • Delete: Clear history anytime using the "Clear All History" button
  • No Account Required: Use all features without registration

Browser Privacy Features

We recommend using:

  • Private/Incognito browsing for sensitive code
  • Browser extensions that enhance privacy
  • Clearing browser data regularly

Technical Details

Technologies Used

  • Diff Algorithm: diff npm package (runs in browser)
  • Syntax Highlighting: Prism.js (runs in browser)
  • Storage: IndexedDB (browser-native, local only)
  • Framework: Nuxt.js (static generation, no backend)

Data Flows

Your Code → Your Browser → Diff Algorithm (JS) → Display Results
     ↓
IndexedDB (local storage on your device only)

Server Interaction: Only for loading the initial HTML/CSS/JS files. After that, everything runs locally.

Compliance

GDPR Compliance

We are GDPR-compliant because we don't collect personal data. You have full control over all data stored in your browser.

CCPA Compliance

We comply with CCPA requirements. Since we don't collect personal information, there's nothing to sell or share with third parties.

Summary

DiffMaster's Privacy Promise:

100% client-side processing
No server uploads of your code
No tracking or analytics
No user accounts required
Full user control over data
Open and transparent

Your privacy is not just a policy - it's how we built the product.

Changes to This Policy

We will update this privacy policy if our data practices change. Updates will be posted at /privacy with a new "Last Updated" date.