VARUARemote ControlSetup SecuritySupport
Trust & transparency

Privacy Policy

How VARUA handles account, device, billing, operational, and Remote Control machine data.

Last updated October 11, 2026
Français
On this page
Scope and roles Information VARUA retains Machine data and remote execution How a remote request moves data User choices and data responsibilities Website, authentication, and cookies Purposes for processing Service providers Retention Account controls and user rights International processing Security Children Legal requests and safety Privacy governance and complaints Changes to this policy Contact

This Privacy Policy explains how Logiciels VARUA, operating under the VARUA brand ("VARUA"), handles personal information when you use the VARUA website, VARUA Remote Control, its hosted dashboard and control plane, and related support services.

Scope and roles

Logiciels VARUA operates the Remote Control account, dashboard, authentication integration, device-routing control plane, usage metering, security controls, and support channels from Quebec, Canada. Remote Control connects AI clients to computers that the user has explicitly paired and is authorized to control.

An AI client such as ChatGPT is a separate service. Information that you choose to send to that AI service is also governed by that provider's terms and privacy practices. VARUA does not control how a third-party AI provider processes the conversation or other information you submit directly to it.

Information VARUA retains

Depending on the features you use, VARUA may retain:

  • Account identity: stable OAuth issuer and subject identifiers and, when provided by the identity provider, email address and display name.
  • Device metadata: device id, user-assigned name, platform, architecture, public key, connection status, capabilities, and pairing history.
  • Subscription and billing state: plan, entitlement, Stripe customer/subscription references, and metered usage. VARUA does not store full payment-card numbers.
  • Usage metadata: tool name, metered units, timestamps, and bounded operational outcome/duration information.
  • Privacy-safe operational trace summaries: opaque correlation id, fixed tool/outcome, duration, fixed dispatch stage, and gateway/agent build identifiers. These summaries contain no account or device identifiers, command/path/environment values, request payloads, machine output, or result content.
  • Free-tier anti-abuse state: provider name, a one-way digest of OpenAI's anonymized openai/subject, and the shared monthly call count. VARUA does not store the raw OpenAI subject.
  • Security settings: custom blocked-path patterns, exact exceptions to built-in protected-path rules, and the security profile selected for the separate private MCP endpoint.
  • Pairing and browser-session metadata needed to complete or maintain authenticated sessions. Sensitive short-lived credentials are stored only as hashes where the protocol permits.
  • Support communications and information you choose to provide when contacting VARUA.
  • Standard security and operational logs needed to protect, troubleshoot, and operate the service. These logs are not intended to contain machine file contents, terminal output, or command output.

OAuth access tokens, agent private keys, browser-session plaintext tokens, headless pairing-code plaintext, and native pairing poll-token plaintext are not persisted by the control-plane application.

Machine data and remote execution

Remote Control is designed so machine work executes on the paired computer. Filesystem, process, search, and terminal operations are performed by the local agent under the operating-system permissions of the account running that agent.

When a remote AI client requests machine data, the requested result must transit the authenticated Remote Control connection so it can be returned to that client. Machine file contents, terminal output, and command output are not retained as control-plane user content by default.

Public MCP operations apply a local secret firewall before machine data can leave the paired computer, with a second gateway-side check before an MCP result is returned. When authentication material is detected, the content is withheld rather than intentionally persisted or returned. Process inspection excludes command-line arguments and environment variables.

Tool results can include opaque managed-process, batch, search, and terminal handles when those handles are necessary to continue, replay, wait for, cancel, or stop the same user-requested workflow. These operation handles are lifecycle identifiers, not authentication credentials or advertising identifiers.

Built-in protected paths and user-defined blocked paths further limit direct filesystem operations. Exact path exceptions can permit access to a built-in-protected path, but they do not disable the public MCP credential firewall. The public /mcp endpoint always uses the enforced security profile. A separately addressed /private-mcp endpoint can use the account's Standard or Developer profile; Developer mode is an explicit private-use choice and does not weaken the public endpoint.

How a remote request moves data

  • On your paired computer: The local agent performs the requested filesystem, search, process, or terminal operation. Output from managed jobs may be held temporarily in bounded local buffers to support follow-up reads or reconnection.
  • Across VARUA: A result requested by your connected AI/MCP client travels through the authenticated, encrypted connection and VARUA gateway to reach that client. VARUA must handle that result in transit; secret checks may withhold it, but cannot guarantee detection of every sensitive value.
  • At your AI provider: Results delivered to the connected client may appear in its conversation history or other records under that provider's practices. Deleting your VARUA account does not delete copies held independently there.
  • In VARUA service records: Account, device, billing, metering, and limited security/operational metadata may be retained as described below. The gateway is not intended to be a durable archive of your machine files or command output.
  • At separate providers: Auth0 handles identity services and Stripe handles billing; their data and retention practices are separate from the contents of a remote command result.

This summary distinguishes local execution, transient result transmission, third-party processing, and the service metadata VARUA keeps. It does not mean that data returned to an AI client remains only on your computer.

User choices and data responsibilities

You decide which devices, authorized folders, permissions, and third-party AI clients to connect, and whether to request operations that involve personal or confidential information belonging to you or others. You are responsible for obtaining necessary authorization before exposing third-party information to an AI client or carrying out work on someone else's systems.

Data returned to an AI/MCP client may become part of that provider's conversation history or other records under its own privacy practices, even though VARUA does not retain machine content as control-plane user content by default. Review the third-party service's settings and policies before sharing sensitive data.

These user choices do not remove VARUA's responsibilities to protect and lawfully handle the personal information under VARUA's control. Details about the respective technical protections and limitations are available at https://varua.ca/security.

Website, authentication, and cookies

The public VARUA website can be viewed without creating a Remote Control account. VARUA infrastructure may process ordinary web-request information such as IP address, user agent, requested URL, timestamp, and security events as part of normal service operation.

The authenticated dashboard uses session mechanisms necessary to sign users in, maintain account security, and provide the requested service. VARUA does not sell personal information and does not use machine file contents, terminal output, or command output for targeted advertising.

Purposes for processing

VARUA processes information as necessary to:

  • authenticate users and paired devices;
  • route and return user-requested MCP operations;
  • enforce capability, security, abuse-prevention, and rate-limit policies;
  • maintain reconnect-safe managed work;
  • provide dashboards, account exports, and device controls;
  • meter usage and operate subscriptions;
  • prevent multiplication of a Free allowance across linked accounts;
  • secure, monitor, troubleshoot, and improve service reliability;
  • provide support and respond to user requests; and
  • comply with applicable legal obligations.

VARUA does not train AI models on machine file contents, terminal output, command output, or user-requested MCP results.

Service providers

VARUA currently relies on service providers to operate parts of the service:

  • Auth0 for user authentication.
  • Stripe for subscription billing, payments, invoicing, tax-related billing features, and the Customer Portal when paid billing is enabled.
  • OVHcloud-hosted infrastructure operated by VARUA for the Remote Control service and PostgreSQL control-plane data.
  • Other infrastructure and network providers necessary to securely host and deliver the service.

Providers process information under their own legal, security, fraud-prevention, and compliance obligations. VARUA does not use Auth0 or Stripe as permanent storage for machine file contents, terminal output, or command output.

Retention

VARUA applies the following retention schedule to Remote Control data:

  • Account, device, subscription, security-setting, approved pairing metadata, and compact daily usage/audit aggregates are retained while the account exists and are deleted from the live control-plane database when the account is deleted.
  • Raw per-call usage_events and raw audit_events are retained for a maximum of 90 days. Before expired raw rows are deleted, bounded daily aggregates preserve the minimum information needed for historical usage and operational reporting.
  • A Free account's OpenAI anti-abuse binding is deleted with the account. Its pseudonymous shared monthly counter can remain through the current quota month so deletion and recreation cannot reset the allowance. Prior-month shared counters are removed on a recurring maintenance cycle.
  • Account deletion can retain a separate privacy-minimized anti-abuse entitlement tombstone through the end of the account's current Free-plan usage cycle. It contains only server-keyed pseudonymous identity digests, the usage-cycle anchor, current-cycle start/usage, and deletion time. It does not retain the raw email, OAuth issuer/subject, name, Stripe identifiers, device records, file/command activity, or historical usage/audit events. The tombstone is used only to prevent deletion and re-enrollment from resetting the current Free allowance, and it is removed after that preserved cycle expires.
  • Headless and native pairing sessions are short-lived. Approved pairing metadata remains with the account until deletion; expired unapproved sessions become cleanup-eligible shortly after expiry.
  • Browser OAuth state is short-lived and removed after use or expiry cleanup. Dashboard sessions use a 24-hour idle lifetime with sliding renewal and a seven-day absolute lifetime. OAuth access tokens are validated during login and are not stored; the hashed PostgreSQL session row is authoritative until idle expiry, explicit logout, account deletion, or the absolute lifetime is reached.
  • Production operational logs are configured for a maximum 30-day retention period.
  • Privacy-safe central operational_traces summaries are retained for a maximum of 30 days and are not keyed to an account or device, so account deletion does not need a separate per-account trace purge.
  • Production database backups are configured to expire within 30 days. Deleted account data already present in an encrypted backup can persist until that backup expires.

Provider records held by Auth0, Stripe, or infrastructure providers can be retained longer when required for security, fraud prevention, accounting, tax, legal compliance, or dispute resolution.

Account controls and user rights

Authenticated users can review account information, revoke paired devices, download a historical account export, and request permanent account deletion through the available account controls.

When an account has a linked Stripe Customer, Remote Control first attempts the required Stripe customer/subscription cleanup and only then deletes the local account data if the provider operation succeeds. Local deletion cascades through the account's devices, subscriptions, per-account usage metadata, audit metadata, approved pairing records, browser sessions, admin push registrations, security settings, and Free-quota binding, subject to the limited retention exceptions described above. The dashboard also clears the local session and initiates the configured identity-provider logout flow after successful deletion so an existing single-sign-on session does not silently recreate the account.

Deleting a Remote Control account does not itself delete the user's separate Auth0 identity. The same authenticated identity can later sign in and create a new Remote Control account. If that happens before the preserved Free-plan usage cycle ends, VARUA uses the pseudonymous entitlement tombstone described above to restore the prior cycle anchor and current-cycle usage rather than granting a new Free allowance.

Depending on where you live, privacy law can provide rights to access, correct, delete, or obtain a copy of personal information, withdraw consent where consent is the applicable basis, or raise a concern about processing. Requests can be sent to privacy@varua.ca. VARUA may need to verify identity before acting on a request and may retain information when applicable law requires or permits it.

International processing

VARUA is operated from Quebec, Canada. Service providers and infrastructure can process information in Canada, the United States, or other jurisdictions where they or their subprocessors operate. Those jurisdictions can have privacy laws different from those where you live.

Security

Remote Control uses TLS in production, OAuth for users, per-device Ed25519 identity, scoped capabilities, allowed filesystem roots, and separate local opt-ins for filesystem mutation and command execution. Public MCP operations also use value-aware local credential detection, protected-path rules, a gateway-side secret backstop, and metadata-only security-block audit events.

No internet-connected service can guarantee absolute security. Users should keep their account, AI-client account, local computer, and pairing credentials secure and should revoke a device or credential promptly if compromise is suspected.

Children

VARUA Remote Control is intended for users who can lawfully enter into the applicable Terms of Service. It is not designed as a service directed to children, and VARUA does not knowingly collect personal information from children for targeted advertising or similar purposes.

Legal requests and safety

VARUA may preserve or disclose information when reasonably necessary to comply with applicable law, legal process, or valid governmental requests; enforce agreements; protect the rights, safety, and security of users or the service; or investigate fraud, abuse, or security incidents.

Privacy governance and complaints

The Privacy Officer and person responsible for the protection of personal information for Logiciels VARUA can be reached at privacy@varua.ca.

VARUA maintains privacy governance practices proportionate to the service, including rules for retention and destruction, access controls, incident handling, and responsibilities for personal-information processing. Privacy complaints, access requests, correction requests, and questions about these practices can be submitted to privacy@varua.ca. VARUA may verify identity before responding and handles requests within the periods required by applicable law. For requests governed by Quebec private-sector privacy law, access and rectification requests are handled within the applicable 30-day statutory response period.

Changes to this policy

VARUA may update this policy as the service, providers, or legal requirements change. Material changes will be reflected by updating the date below and, where required, by providing additional notice.

Contact

Privacy questions and requests: privacy@varua.ca

Security reports: security@varua.ca

Support: support@varua.ca

Operator: Logiciels VARUA, operating under the VARUA brand

Privacy Officer / person responsible for the protection of personal information (role and contact): privacy@varua.ca

Business location: Montreal, Quebec, Canada

Public contact email: support@varua.ca

Operator jurisdiction: Quebec, Canada

Public privacy page: https://varua.ca/privacy

Privacy PolicyTerms of Service SecuritySupport