Privacy policy

Who and what this covers

This policy describes the AgenticNova public website, browser extension, local bridge, license service, and support communications provided by BytArch Labs. It explains the application’s data flows; independent AI providers, payment services, and MCP servers have their own policies.

For privacy questions and requests, contact bytarchbit@gmail.com. Do not send your full license key, passwords, or private project files in an initial request.

Website visits and support

The public pages use locally served styles, fonts, and images. The public application does not set its own tracking cookies or include analytics or advertising scripts. Server and hosting infrastructure may process standard request information such as IP address, requested URL, user agent, and request time for delivery, logging, and security. Infrastructure settings can affect cookies and logs.

Choosing a license opens WhatsApp with your selected plan, duration, and price in a draft message. You decide whether to send it. WhatsApp handles the opened link and any message under its own practices. Email and WhatsApp support communications may include your contact details, purchase request, and information you choose to share.

This website does not collect card details or process payment directly. Before using an agreed payment method, review that provider’s information and privacy terms. Support messages are used to respond to you, arrange licenses, and investigate issues.

License and device information

Activation and ongoing validation send your license key, product identifier, device identifiers, and a fresh verification challenge to the AgenticNova license service over HTTPS. License checks occur during use, including before tool operations. The license database stores:

• Your customer email, where supplied, license ID, plan, status, covered products, device allowance, and creation and expiry dates.
• A hash of the license key and its last four characters, not a recoverable full key in the license database. The full key is nevertheless transmitted when validating it and kept on your device for those checks.
• Device identifiers associated with activated machines, machine creation and last-seen times, and licensing events such as activation, renewal, replacement, or revocation.
• Payment-provider references when used to associate a purchase or subscription with a license.

Current Windows builds can send a Windows installation identifier; macOS builds can send a platform UUID. Linux builds hash available installation and hardware IDs, and the hostname-derived identifier is hashed. These are persistent device identifiers used to bind a license to a machine; they are not anonymous simply because some values are hashed.

This information supports issuing and validating licenses, enforcing device allowances, handling renewals and support, and investigating license misuse. The license-validation request does not include your chat transcript, project files, or tool output. Update checks send your platform choice and standard request metadata to retrieve release information.

AI chats and connected tools

The extension runs on supported AI chat websites. It reads relevant conversation content to recognize tool requests and can submit instructions and results into that chat. The local bridge routes tool calls to the MCP servers you enable.

Depending on the tool and task, results can include file contents, project paths, code, command output, images, or other workspace information. When these results are submitted to a chat, they are shared with that AI provider. Your provider’s retention, training, sharing, and account controls apply; AgenticNova cannot override them.

A third-party MCP server can also read, store, or transmit data according to its capabilities and configuration. Check its documentation and privacy practices before connecting it. Only approve workspaces and services whose information you are authorized to expose.

Local storage and diagnostic logs

AgenticNova stores working information on your device. This can include:

• Extension settings, custom instructions, remembered session references, server display information, and provider-specific settings in browser storage.
• Bridge configuration, MCP server commands and environment settings, saved license credentials and grants, and local validation or update state.
• Diagnostic logs at logs/bridge_debug.log, including errors, tool-call traces, and output from child MCP servers. Depending on the task, these may reveal paths, commands, or sensitive content.
• Before/after file snapshots in .agenticnova-history and optional workspace snapshots in .agenticnova-checkpoints. These can retain copies of project content after the working file changes or is removed.

These local records are not a promise of encrypted storage. Device access, browser profiles, backups, project sync, and other local software can expose them. Review and redact diagnostic material before sharing it with support. Checkpoint secret exclusions are name-based and not exhaustive.

Other services and disclosures

Data reaches AI providers, WhatsApp, email providers, payment services, and connected MCP servers when you use those services. Hosting infrastructure processes requests to deliver and protect the website and license service. These services may process information in countries other than your own.

Information supplied to support or stored for licensing may also need to be used or disclosed to address misuse, resolve a dispute, protect users or the service, or meet a legal obligation. Avoid sharing information that is unnecessary for your request.

Retention and your choices

Server-side license records do not automatically disappear when you uninstall the product or a license expires. Local logs and recovery snapshots can also remain until you manage them. This page does not promise a universal automatic deletion schedule; contact support about the records associated with your license.

You can stop an agent session, disable MCP servers, decline folder approvals, remove the extension, and stop the bridge. Stopping a session does not undo actions already completed. Manage local settings, logs, license files, and recovery folders separately, and keep any backups you need before removing recovery data. Removing local license data does not cancel a purchase.

Contact bytarchbit@gmail.com to request access, correction, or deletion of personal information, or raise an objection or other privacy request available under applicable law. We may need to verify that a request concerns your records. Legal, security, and recordkeeping obligations may limit deletion; request information about your situation rather than assuming immediate removal from all backups or third-party systems.

Changes and contact

We may revise this policy when the product or data practices change and update the date shown above. For questions, contact BytArch Labs at bytarchbit@gmail.com or +501 6332826 on WhatsApp.

Read the Security page for permissions and recovery limits, and the Terms of use for licensing conditions.