NeuralBytes Privacy Policy

Last updated: June 22, 2026

Overview

NeuralBytes provides a customer-controlled workflow bridge, downloadable agents, API access, monitoring, audit logs, and optional supervision. This policy explains what information may be collected when you request access, download software, connect an approved session, run a workflow, or use API access.

Information We May Collect

We may collect contact details you submit, device and operating-system information, workflow request details, session identifiers, connection timestamps, API events, diagnostic output, command history, customer instructions, review notes, agent action logs, screenshots or recordings created for review, and replay/audit records related to an approved session.

Monitoring, Audit Logs, and Replay

Approved sessions may be monitored in real time and recorded in an action timeline. These records help verify customer-authorized actions, review AI-assisted activity, troubleshoot mistakes, detect abuse, protect customers, and improve the platform. Do not enter or share passwords, payment details, private documents, health information, or other sensitive data unless specifically required and handled through an appropriate secure method.

How Information Is Used

Information is used to evaluate access requests, operate the workflow bridge, relay customer-authorized tasks, document activity, detect abuse, maintain security, improve tools, respond to follow-up questions, manage billing, and administer API access. Intake form details are reviewed by a human and are not automatically delivered to an agent or API workflow. NeuralBytes does not sell customer workflow records.

Security and Retention

NeuralBytes uses reasonable technical and operational safeguards, including monitored sessions and audit trails. Public website and relay traffic is encrypted in transit with HTTPS/TLS. Current relay credentials are stored server-side as hashes, and newer agents sign token-authenticated requests. No system is perfectly secure, and NeuralBytes does not claim that all server-side records are encrypted at rest unless a separate written agreement says so. We aim to keep records only as reasonably needed for service history, troubleshooting, security review, legal compliance, billing, and business operations.

Sanitized Training and Tool Improvement Data

NeuralBytes may use sanitized or de-identified workflow patterns to improve internal tools, routing, automation, evaluation, documentation, and training datasets. Raw customer records, screenshots, private documents, raw command transcripts, passwords, tokens, payment data, customer names, contact information, IP addresses, hostnames, full paths containing user names, and other unique identifiers should not be included in long-term training or knowledge records. Reusable records are reduced to generalized symptoms, environment categories, diagnostic categories, fix steps, verification steps, and risk notes where practical.

Third-Party Services

The website, support relay, downloads, email, hosting, and analytics or security services may involve third-party providers. Those providers may process limited information needed to deliver the service.

Your Responsibilities

You control what systems you connect, what workflows you request, and what information you submit through the bridge or API. You are responsible for backing up important files, reviewing requested actions, limiting unnecessary sensitive data, and confirming that you have authority over the systems and accounts involved. If private information was shared by mistake, contact NeuralBytes promptly.

Contact

For privacy questions, workflow records, or API access requests, contact NeuralBytes through the website contact form or email [email protected].