Security & Trust
Last reviewed: 17 November 2026
Toolnexo is built around a simple rule: collect as little as possible, keep it for as short as possible, and be explicit when a tool needs a server. This page explains the controls behind that promise.
Data flow at a glance
| Area | Where data lives | Retention | How it is removed |
|---|---|---|---|
| Browser tools (116) | Your device only | Never uploaded | Closing the tab |
| Server tools (8) | Private app volume, random job ID | Deleted within 1 hour | Automatic sweeper + Delete now |
| Analytics (optional) | Google Analytics 4 | Only after opt-in; never tool inputs | Your consent choice |
| Contact email | Zoho Mail | Only what you send | Handled as email |
Browser-first by default
116 tools run with JavaScript in your tab. The file or text you provide is read locally and is not transmitted. You can verify this in your browser's network inspector: no request carries the tool input. These tools do not write your input to cookies, localStorage or IndexedDB.
Server tools: minimal, private, short-lived
Eight tools need server-side software: PDF OCR, PDF Password Protect, PDF Unlock, PDF to Word, Word to PDF, Excel to PDF, AVIF Converter and Bulk Document Converter. They follow the same rules:
- Only the file you explicitly choose is uploaded, over HTTPS.
- Storage uses a random job ID in a private volume; the original filename is never used as a path and files are not publicly served.
- Downloads require a short-lived HMAC-signed token, so a job ID alone is not enough to fetch an output.
- Files are deleted automatically within 1 hour.
- “Delete now” removes a finished job immediately.
- Files are never sold, shared for advertising, or used to train AI models.
- Passwords for protect/unlock are written to a private permission-restricted sidecar, used once, never stored in the database or logs, and deleted with the job.
Transport and infrastructure
- TLS/HTTPS is required for the public site and API.
- PostgreSQL and Redis are not published to the host; they live only on an internal Docker network.
- The API is rate-limited at the reverse proxy and again per client IP for uploads.
- Uploads are capped, validated by extension and magic bytes, and processed in isolated worker containers.
- Production API documentation is disabled; health endpoints are available only for monitoring.
- Dependencies and containers are updated deliberately; the public surface is kept small.
Analytics and advertising
Analytics is opt-in. Google Analytics 4 loads only after you accept, never receives tool inputs, and is disabled when you reject. No advertising cookies are set today. If ads are introduced, a Google-certified consent platform will request consent before any ad cookie is set in the EEA, UK or Switzerland.
No sale of data
We do not sell, rent or trade personal data. We do not build profiles for advertising. There is no account system and no data broker integration.
Responsible disclosure
If you find a security issue, please email contact@toolnexo.com with the subject “Security”. Include reproduction steps, affected URL and potential impact. Please do not test against other users' data, do not upload illegal content, and give us a reasonable window to fix the issue before public disclosure. We aim to acknowledge reports within 2 business days.
A machine-readable policy is published at /.well-known/security.txt.
What we do not claim
No service is perfectly secure. We do not claim “zero risk”, “military grade” or “unhackable”. What we can verify is the architecture above: minimal collection, short retention, private storage, signed downloads and no advertising sale of data.