Local-first where practical
Prefer on-device processing when it meaningfully reduces unnecessary exposure.
Secure Tools
An ecosystem of independently maintained browser tools, desktop applications, local AI software, and reusable libraries designed to minimize unnecessary data exposure.
What Secure Tools is
Secure Tools brings independently released software into one understandable ecosystem. Projects favor local processing where it is practical and disclose when network access, storage, or other runtime behavior is required.
Each product owns its technical guarantees, version, and release cycle. The Hub provides discovery and high-level disclosure without forcing projects into one runtime, plugin system, or ecosystem version.
Core principles
Prefer on-device processing when it meaningfully reduces unnecessary exposure.
Request, transmit, and retain only what a product actually needs.
Explain when requests occur and what purpose they serve.
Favor lower-exposure behavior by default where it is technically appropriate.
Keep source and dependencies understandable where practical.
Make official web deployment provenance visible where practical.
Products
Each application is maintained and released independently.
Local browser workflows for supported PDF, image, metadata, and privacy tasks.
View productA local desktop companion developed outside the browser utilities runtime.
View productA planned category whose processing, model, and network boundaries are not finalized.
View productLibraries
Libraries support products without becoming end-user applications.
Deterministic, local metadata inspection, cleaning, and verification for supported image formats.
View libraryPrivacy disclosure
Browser tools, desktop applications, local AI runtimes, and libraries have different processing and network requirements. Product-specific disclosures take precedence over ecosystem-level principles.
Understand the ecosystem privacy model