All Tools
Browse

How Toolistify Handles Tool Inputs and Files

See how Toolistify handles calculator inputs, CV details, uploaded files, browser storage, vendors, encryption, retention and security reports.

Answer-first introduction

Toolistify aims to collect only the information needed to provide a feature. This page explains which tools run locally, which data is transmitted, whether browser storage is used, which vendors process information and how long server-side data is retained. No online service can promise absolute security.

Tool-by-tool data table

Publish a table with these columns: Tool Input type Local processing Sent to server Browser storage Server retention Third parties GPA Calculator Grades and credits [Yes/No] [details] [details] [details] [details] CV Maker Personal CV content [Yes/No] [details] [details] [details] [details] Image to PDF Uploaded [Yes/No] [details] [details] [details] [details] images PDF Merger PDF files [Yes/No] [details] [details] [details] [details] Scholarship Checker Profile [Yes/No] [details] [details] [details] [details] categories Password Generator Generated [Yes/No] [details] [details] [details] [details] value

Local processing

For a genuinely local tool, explain:

  • Which browser APIs or libraries perform the task
  • Whether network access is required after the page loads
  • Whether input values are included in analytics or error logs
  • Whether autosave uses local storage or IndexedDB
  • How the user clears saved data

Server processing

For a server-side tool, explain:

  • Why upload is necessary
  • Transport encryption
  • Storage location
  • Access controls
  • Vendor or subprocessors
  • Automatic deletion period
  • Backup treatment
  • File-name and content logging
  • How deletion failures are handled

Analytics and session replay

Exclude sensitive input fields and uploaded document content from analytics, advertising parameters and session-replay capture. Document the technical exclusion and test it.

Password generator

Confirm that generation uses an appropriate cryptographic random source, generated values are not transmitted, copy events do not include the password value in analytics and the value is not stored.

Security reporting

Send reports to [security email]. Provide a safe-harbor statement reviewed by counsel and a realistic acknowledgement target. Do not invite destructive testing.

Incident communication

Describe how Toolistify will evaluate incidents and notify affected users or authorities where applicable. Do not promise a universal deadline without understanding legal obligations and contact capability.

FAQs

Does every Toolistify tool run in the browser?

Only state this for tools confirmed through testing. The table above should provide the current answer for each feature.

Does HTTPS mean my data is never exposed?

No. HTTPS protects transport but does not address every storage, code, vendor or device risk.

Can Toolistify see my generated password?

The intended answer should be no after technical verification that the value is generated and remains locally processed.

How do I clear locally saved data?

Provide exact in-product controls and browser-specific guidance rather than telling users only to clear all site data.