Privacy policy

Who is responsible

battlegent.com and its hosted hub are operated by Zentria OÜ, Estonia.

Company: Zentria OÜ
Reg. no.: 16130615
Address: Kivimäe, Ärina küla, Väike-Maarja vald, Lääne-Viru maakond, 46235, Estonia
VATIN: EE102404067
Contact: info@zentria.company

Zentria OÜ is responsible for personal data used to run accounts, billing and the service. If your organization uses battlegent to process somebody else’s personal data in a session, your organization is responsible for deciding why that data is processed; we handle it to provide the service on its behalf. This policy covers our website and hosted service. A hub operated by somebody else has its own operator and privacy arrangements.

What we handle

Account information. Your sign-in provider and account identifier, and the name, email address, email verification status and avatar it supplies.
Organizations and devices. Memberships, roles and invitations; device names, public keys, software versions and connection status.
Session content. Messages, agent responses, tool calls and results, questions, approvals and other session events. These can include source code, file contents, command output and personal data you or your agents put into a session.
Commands and usage. Messages and actions queued for your devices, their delivery status, and daily counts of commands, sessions and device activity associated with accounts and organizations.
Billing and support. Subscription and payment status, customer references, and information you send when contacting us. Stripe processes payment details; card details are entered into Stripe’s checkout rather than the battlegent hub.
Technical information. Sign-in sessions, browser user-agent information, request and error logs, and the network information needed to connect to the service.

Your machines and the hub

Your agents run on your machines, but the hosted hub handles session content. It relays messages, agent output and commands between your machines and connected clients. It also keeps a copy of session logs so you can read them while a machine is offline.

Model-provider credentials and device private keys stay on the machine running the daemon. Model requests go directly from that machine to the provider you use. That provider processes them under its own terms and privacy policy. The hub receives the resulting session events.

Connections to the hosted service are encrypted in transit. The hub must process session content to relay and store it; it is not end-to-end encrypted between your clients. People with access to your organization can access its shared devices and sessions.

Why we use it

We use account, device and session information to provide the service you request, authenticate you, connect your clients, synchronize sessions and deliver commands. We use billing information to manage subscriptions and payments. Where we have a contract with you, these uses are necessary to perform that contract.

We use technical information and usage statistics for our legitimate interests in securing, maintaining and improving the service, preventing abuse and understanding how it is used. We use records needed for accounting, tax and lawful requests to meet legal obligations. Where a use requires consent, we ask for it separately and you can withdraw it.

Session information is available to clients and people authorized in your organization. Service providers receive information needed for their role: your chosen identity provider handles authentication, Stripe handles payments, and infrastructure providers may handle data needed to host and deliver the service. We may also disclose information when required by law or necessary to protect the service and people using it.

Third-party providers may process information outside the European Economic Area. Where we transfer personal data to a provider outside the EEA, we must use an applicable legal transfer mechanism, such as an adequacy decision or standard contractual clauses. Contact us for details of the providers, processing locations and safeguards applicable to your use of the service.

How long we keep it

The hub’s automatic cleanup uses these periods:

Mirrored session logs: 90 days after the hub last synchronized new events for that session. Reading a session does not extend that period. A device that still has the original log can synchronize it again.
Finished commands: 30 days after delivery or final failure. Commands still waiting for delivery remain queued until resolved.
Daily usage and device activity records: 400 days. These contain counts and activity associated with accounts, organizations and devices, rather than transcript text.
Sign-in sessions: 30 days of validity. The hub removes their records seven days after expiry or revocation. Temporary sign-in flow records expire from storage after one hour.

Cleanup runs periodically, so these are expiry thresholds rather than a promise of deletion at an exact second. Account and organization records remain while needed to operate your account; you can request deletion by contacting us. Billing records may need to be kept longer to meet accounting and tax obligations.

These periods apply to the live hub database. They do not delete transcripts, files or logs on your own machines or records held by your model provider. Backup copies, where maintained, have a separate lifecycle and are not necessarily removed at the moment a live record expires.

Cookies and analytics

The hub uses an essential sign-in cookie to keep you authenticated. Clients also store local preferences, such as theme settings, in your browser. These serve the product’s functionality.

We use Plausible, hosted at plausible.zentria.ee, for aggregate website visits and selected product events, such as creating an organization or opening a session. The analytics script does not use cookies. Product events use the hub’s root address instead of URLs containing device identifiers, session identifiers or invitation codes, and do not include transcript content. Analytics can still process technical request information to produce those statistics.

Your rights

Subject to the GDPR’s conditions, you can ask to access, correct or delete your personal data, restrict its processing, or receive a portable copy. You can object to processing based on legitimate interests and withdraw consent where processing relies on it. We may need to verify your identity before acting on a request.

Write to info@zentria.company. If your request concerns data controlled by your organization, contact its administrator as well. You can complain to the Estonian Data Protection Inspectorate or the supervisory authority where you live or work.

Changes and contact

We update this policy when the service or its data handling changes. The date at the top identifies this version. We will bring material changes to your attention through the service or an appropriate account contact channel.

Questions about privacy or data processing? Contact Zentria OÜ at info@zentria.company.