Privacy Policy & Local-Only Architecture

1. Zero Server Uploads

When you select, drop, or paste an image into ScreenshotEditor.in, the file is read entirely into your device’s local volatile RAM using the standard JavaScript FileReader and HTML5 <canvas> APIs.

We do not maintain any backend image storage bucket, API endpoints that receive image blobs, or cloud AI inference pipelines for your captures. If you disconnect your internet connection immediately after the web page finishes loading, the editor will continue to function without interruption.

2. Destructive vs. Overlay Redaction

Many online and desktop utilities apply blur through SVG filters or visual CSS overlays. In those systems, the original unblurred image remains embedded in the file layers, making it trivial for an adversary to remove the filter and read confidential text.

In ScreenshotEditor.in, blur and pixelation are implemented as destructive pixel array mutations via CanvasRenderingContext2D.getImageData() and putImageData(). Original RGB channel values in the redacted zone are permanently overwritten. The exported file contains only the post-mutation pixels.

3. Telemetry and Analytics

We do not use surveillance cookies, cross-site trackers, or invasive analytics that record your screen, mouse clicks, or canvas contents. We do not inspect clipboard data other than standard paste events directly initiated by the user.

4. Third-Party Integrations

This website does not share or sell user data to any advertising networks, brokers, or third parties. All styling and font assets are served directly through static production bundles.

5. How to Verify Local Processing

You can verify our privacy claims at any moment:

1. Open your browser Developer Tools (F12 or right-click → Inspect).
2. Switch to the Network tab.
3. Upload a screenshot and perform multiple blurs, annotations, and exports.
4. Observe that zero POST requests or image payloads are dispatched over the network.