Privacy and data handling

Core browser and local tools

Files selected at deepbom.org and files read by the CLI or local MCP are analyzed on the user's device. The core audit does not upload model bytes, tensor values, inputs, outputs, or generated reports to the DEEPBOM service.

ChatGPT integration

A file attached to ChatGPT is already handled by ChatGPT under the user's OpenAI terms and settings. The DEEPBOM component obtains a temporary, plugin-authorized download URL and reads the attachment inside the ChatGPT browser sandbox. The DEEPBOM service does not fetch or retain the file. The component returns a bounded result to the conversation, which can contain the filename, file and evidence hashes, tensor or operator counts, encoding summaries, and findings.

Use the local CLI or local MCP instead when those result fields must not enter a ChatGPT conversation.

Optional services

Account, report-fingerprint registration, controlled research modules, and explicitly consented structural benchmark features are separate optional paths. Their screens identify what is sent before the user proceeds. Core artifact analysis does not require them.

Contact

Privacy or security questions can be reported through the repository contact path listed on the support page.