Guide
Browser privacy, Tools API, and commercial APIs: how the pieces differ
Clarifies what “runs locally” means on static tool pages, what Tools API v1 is for, and when paid product APIs replace free utilities.
What “runs in your browser” usually means here
Most salamyx.com tool pages are static: they load HTML and scripts, then process your input with Web APIs on your device. That is ideal for one-off checks where you do not want a backend copy of your paste.
You should still treat the page like any other website: keep your browser updated, watch for extensions, and avoid shoulder surfing. “Local processing” is not the same as “approved for classified data by default.”
Tools API v1: a catalog, not your data
Tools API v1 lists each tool’s title, route, and short hints so people—or integrations—can open the correct page. It does not accept your files or secrets to process them.
If an integration needs server-side execution, retention policies, or SLAs, that belongs to product APIs and contracts—not the free static utilities.
Commercial Salamyx APIs versus free tools
Product pages under /products/ and the paid API sections describe automation, access, and operational guarantees. They may involve server-side processing and billing.
Pick in-browser tools for quick personal workflows; pick commercial APIs when you need repeatable automation with vendor commitments.
A short checklist before pasting sensitive data
Confirm you are on the real salamyx.com site over HTTPS, read the privacy and limitations block, and decide whether an in-browser tool is appropriate for the sensitivity of your data.
When in doubt, use a dedicated enterprise workflow rather than any public web form.
Related pages
FAQ
If a tool runs in my browser, does nothing ever leave my device?
The tools are built so routine processing stays on your device, but you still download pages from the network and the site may use analytics. Read each page’s notes.
Can I use the Tools API to hash or encrypt user data for me?
No. Tools API v1 is for finding and linking to tool pages. Run hashing or encryption in your own trusted environment, or use a product API with a clear contract.
When should I choose a commercial API instead?
When you need audited processes, retention controls, batch throughput, authenticated access, or server-side execution that static pages cannot provide.
Are static pages safe for secrets?
They reduce exposure versus sending secrets to arbitrary servers, but they do not remove human risk, malware risk, or policy requirements. Follow your org’s data classification rules.
Where do I start if I am building an integration?
Skim /api/ for product direction, read Tools API docs to map tasks to the right tool URLs, then send people straight to that tool page.