Trust

Compliance pack

Architecture notes and privacy receipts for agencies, freelancers, and security-minded teams who need to explain how client files are handled.

Processing model

OneDevToolkit tools run in the browser using JavaScript and standard browser APIs, including pdf-lib, Canvas, and Web Crypto. The file bytes a tool works on are not uploaded to OneDevToolkit for processing. You can confirm this yourself: open your browser's developer tools, watch the Network tab while a tool such as Compress PDF runs, and check that no request carries the file.

Privacy receipts

For supported tools, users can download a Processing Receipt in JSON format. It records the tool identity, timestamps, and SHA-256 hashes computed in the browser when the tool has access to the input and output files. Receipts can be checked with the Receipt Verifier, and the guide on how privacy receipts work explains each field.

A receipt is generated by the same page that does the processing, so treat it as a record of the job rather than independent proof. Pair it with your own network checks if a client needs stronger assurance.

What servers may store

  • Account credentials (hashed), if you create an account
  • Favorite and recent tool slugs for signed-in users
  • Messages you send through the contact form
  • Site analytics, as described in the privacy policy

In the local-first model, servers do not receive vault file contents or recipe file payloads.

Suggested contract language

The wording below is a starting point, not legal advice. Have your own counsel review it against your contract and the laws that apply to you.

“Vendor processes Customer files in the Customer’s browser. Vendor does not receive Customer file contents for tool execution. Customer may export a processing receipt with cryptographic hashes generated client-side.”

Privacy policy · Recipes · Vault