Privacy and tool data handling
How WEPLET and its local-first tools handle visitor information and submitted inputs.
Core principle
WEPLET does not require an account. Inputs that can be handled in the browser stay there whenever practical. Values entered in local-first tools such as Metadata Preview are used only in the current page state.
Image Audit sends a submitted URL to the WEPLET server so it can request the public page and images. Processing is limited to providing the feature, and the product does not offer persistent storage for submitted content.
Analytics and operational logs
Where Google Analytics is configured, the site may send limited usage events to understand navigation and improve features. Hosting systems may temporarily retain standard logs such as request address, time, device, and browser information for security, debugging, and reliability.
Retention and third-party processing follow the settings of the deployed hosting and analytics services. Builds without an analytics identifier do not load WEPLET’s analytics script.
Safe use of the tools
Do not submit login pages, private documents, or URLs containing tokens to public URL tools. WEPLET is designed to restrict local and private-network access, but users should submit only public pages they are authorized to inspect.
This notice will be revised when features change. Until a public contact channel is confirmed, there is no account-based deletion workflow, and WEPLET does not collect account profile data.