Privacy model

Privacy is an architectural choice.

Secure Tools is designed to process file contents locally in your browser. This page describes the current technical model, not a promise about unfinished features.

Local file processing

Supported tools read and transform files in browser memory. File contents are not sent to a Secure Tools server.

No accounts or analytics

The web hub has no user accounts, analytics, behavioral tracking, advertising, or tracking pixels.

Preference storage

localStorage is used only to remember your language and theme selections on this device.

External links

Following an external link, such as GitHub, leaves Secure Tools and is governed by that service's own policies.

Privacy metadata tools

Choose the tool that matches your file type. Image and PDF metadata have different supported scopes.

• Available→

  Image Metadata Inspector & Cleaner

  Inspect decoded and opaque metadata in JPEG, PNG, or WebP images, then save a verified Privacy Clean copy. Inspection may be partial and non-exhaustive.

• Available→

  PDF Metadata Inspector & Cleaner

  Inspect and remove supported PDF document-info fields. This does not cover every XMP packet, attachment, annotation, or hidden document structure.

These specialized tools process files locally and verify only their documented supported scope.