Local tools
Selected files and tool inputs are processed in your browser. The tools do not upload or execute your original files. Pasted strings from the text-hashing, encoding and IOC tools are not automatically collected for research.
Aggregate usage counts
Successful real file inspections, file hashes and nonempty text hashes report an operation type and a random retry-protection identifier. Those counting reports do not include filenames, file contents, calculated hashes, pasted text or persistent visitor identifiers. Examples and failed operations are excluded. Retry identifiers become eligible for cleanup after 48 hours; aggregate totals are retained. Counts describe browser-reported operations, not verified unique visitors or files.
Optional research contributions
You can prepare a contribution linked to a selected file’s SHA-256 fingerprint. Its core fields are SHA-256, size, detected format, tool used, submission time and consent version. Separate unchecked options let you include an editable submitted filename and a research note or pasted snippet of up to 10 KB. Folder paths are removed from the filename field. The text you choose to share is stored as reviewed; it may itself contain personal or confidential information, so review and remove details you do not want to contribute.
Preparing or previewing a contribution does not submit it. Records are sent only when you choose Share for research. Your original file is never uploaded. Filenames and text are unverified contributed context. Submitted text is displayed safely as plain text, never executed, and submitted links are not automatically fetched.
Access, retention and review
Research contributions are private to site administrators, who can view and export them. The contribution form and preview show the retention policy for that submission: a fixed 90-, 180- or 365-day period, or retention until manually removed with an annual review. Changing the site setting applies to future contributions and does not extend a previous record’s agreed expiry. Older version-1 contributions keep their original 90-day term.
Expired records are excluded from administrator views and exports and removed during scheduled cleanup. Under manual retention, the site owner reviews records annually and removes information no longer needed. WordPress scheduled cleanup depends on site traffic or configured hosting tasks.
Removing a contribution
While your current tab remains open, use Remove my shared records to remove contributions made from that tab. Closing the preparation option prevents further submissions and does not erase received records. After closing the tab, contact the site owner with the file’s SHA-256 to request removal. Administrators can remove individual records. Removing research records does not change aggregate operation totals.
Normal website requests and backups
WordPress and the hosting provider receive normal page and API requests and may keep operational or security logs. The tools plugin does not copy IP addresses or browser user-agent information into its counting or research tables. The theme loads fonts from Google Fonts. Login cookies, hosting backups and additional plugins have their own data handling. Copies in backups and exported CSV files follow separate retention; deleting a live record does not immediately remove existing backup copies.
Contact
For privacy enquiries, contact hello@quditlabs.co.uk.