Privacy guidance
Tool privacy and safe usage
Orlixio is built around fast browser-based tools. Many tools process pasted content directly in your browser, but safe handling still matters because copied developer data often contains secrets or private context.
What runs in the browser
Formatting JSON, validating syntax, decoding JWT sections, encoding Base64 text, converting timestamps, generating UUIDs, parsing raw headers, and creating hashes are designed as client-side workflows. The tool interface does not require login, a database, or a backend endpoint for pasted input.
Values you should avoid pasting
Production access tokens and refresh tokens
Private keys, passwords, and API keys
Customer records or confidential business data
Cookies and Authorization headers
Internal hostnames or infrastructure details
Payloads you are not allowed to share
Safer debugging pattern
- Create a small reproducible sample.
- Replace secrets with placeholders such as <token> or <account-id>.
- Use the relevant tool to inspect only the needed value.
- Copy results into tickets or docs only after a second privacy review.
Tool limitations
Orlixio tools help inspect and transform data, but they do not prove trust. A decoded JWT is not verified, a Base64 value is not encrypted, a hash is not password storage, and a valid JSON document may still fail API schema or business validation.