Privacy Policy
Toolslify is designed around a simple principle: inputs should be processed to deliver a result, not stored as a hidden product asset. This page explains how the current platform handles information, browser storage, and security behavior.
What we process
Toolslify processes the text, files, and transcript content that you submit to the tool you are actively using. The request is handled in memory for the purpose of generating the result you asked for.
What we do not store
Toolslify does not persist tool inputs or outputs on the server after the request is completed. The current platform is intentionally designed to avoid long-term request storage in the core workflow.
Local browser storage
Theme preference, language preference, and recent history are stored in your browser so the product can feel fast and familiar when you come back. That data stays on the device unless you clear browser storage.
File handling
Uploaded PDFs and audio files are processed only for the current conversion request. PDF extraction happens in the server runtime for the response you requested. Audio uploads can be routed through an external transcription provider only when a server API key is configured.
Security measures
Toolslify applies request sanitization, rate limiting, and common security headers including Content Security Policy, X-Frame-Options, X-Content-Type-Options, and Strict-Transport-Security.
Contact
If you operate Toolslify in production, you should replace this placeholder privacy contact section with your business email, address, and jurisdiction-specific compliance details.