Codrenix Toolbox logoCodrenix Toolboxby Codrenix

Security

How your files are handled

No vague promises — here is the actual mechanism, tool by tool.

Client-side processing, by design

The tools that accept files on Codrenix Toolbox run entirely in your browser using client-side JavaScript. When you open a file, it is read into your browser's memory and processed by libraries downloaded with the page. There is no upload step because there is nothing to upload to.

No storage, no upload pipeline

We operate no file storage and no upload endpoint. Processed results are saved back to your device by your own browser when you click download. Close or refresh the tab and in-memory files are gone.

Tool by tool

  • PDF tools use in-browser PDF libraries; password protection uses local AES-256 encryption before the file is saved.
  • Image tools use the browser's canvas API to re-encode images locally.
  • Password generator uses your browser's Web Crypto random number generator.
  • QR code generator encodes data locally and draws the result in your browser.
  • Utility tools perform their calculations in browser code and do not upload the values you enter.

No accounts, no tracking of your work

There is no sign-up, login, or email required. We do not run analytics, use advertising cookies, or see, store, or process the contents of your files. See our privacy policy for details.

Honest limits

The current catalog contains 45 live tools. Most image tools enforce a 20 MB per-file input cap; the watermark image tool uses 20 MB for its main image and 10 MB for its optional logo. OCR, compression, and some conversion workflows use larger PDF caps, generally 30–50 MB. Multi-file workflows also enforce file-count caps, including 20 PDFs for Merge PDF and Rotate PDF, 20 PDFs for the PDF-to-JPG input, and 50 images for JPG-to-PDF.

These are input checks, not a promise of unlimited processing. PDFs, OCR, high-resolution images, multi-page batches, and conversions can require several times the input size in temporary browser memory. A file can pass the upload limit and still fail or slow down if the device runs out of memory, the tab is closed, or the file is unsupported or malformed. We have not established a minimum memory or processing-time guarantee for every device and file.

A malicious or compromised browser extension could in principle read page memory. That is a risk of browser-based processing, not something this page can eliminate. If a future tool ever needs server processing, that tool's page will state it clearly before you use it.

Report a security issue

If you believe you have found a vulnerability in this website, please email info@codrenix.in with the affected URL, what you observed, and reproduction steps if you have them. Do not include passwords, private documents, or sensitive personal data. This is the site's public contact address, not a dedicated security queue.

We will review reports and may ask for more information. We cannot promise a particular response time or guarantee that every report will result in a fix. Please avoid accessing data that is not yours, causing service disruption, or publicly disclosing an unverified issue before we have had a reasonable opportunity to review it.

Questions about anything here? Contact us.