Data processing notice

Every active tool is assigned a processing type from the registry so you can decide whether the content is appropriate to use.

• Local processing runs inside the browser for standard pasted text and selected files.
• Server processing sends defined input to Bacodev infrastructure only for a disclosed server feature.
• AI assisted processing sends defined input to a configured model provider only when the interface discloses that path.

JSON, CSV, YAML, text, and supported document operations run in the browser when practical. The page displays a local processing label based on the tool registry.

Local processing reduces network transfer, but your browser still uses device memory, optional browser storage, clipboard, and download features under your control.

Some conversions may require a server because the browser cannot reliably complete the operation. Before use, the tool will state what is sent, the purpose, retention behavior, and whether another processor is involved.

AI features are separated from deterministic formatters and converters. The interface will state when content is sent to an AI provider.

AI output can be incorrect or incomplete and must be reviewed before use.

Avoid submitting passwords, private keys, session cookies, authentication tokens, personal records, or confidential business data to server based tools unless the notice explicitly supports it.

Use redacted examples whenever the full value is not required.

Operational events may record that a tool was opened, an action succeeded or failed, or an input fell into a broad size range. Analytics events must exclude pasted content, selected file contents, filenames, generated output, tokens, and API keys.

You decide what content to paste, open, save locally, copy, or download. Review the processing label and clear optional browser storage when using a shared device.

When a signed-in visitor manually starts sync, the server stores selected workspace metadata such as favorite tool slugs, recent tool slugs, and interface preferences. Tool input and output are not part of this sync.

The installable application caches public application assets and selected local tool pages. This cache is stored by the browser and can be cleared by the visitor.