Privacy Policy

Scope and contact

This policy explains how Vyvick processes information when providing Lira RDP Security, its website, portal, Windows agent and support. Questions and privacy requests may be sent to [email protected].

Information we process

We process only the information required to operate and secure the service.

• Account and organization details, including name, business email, role and language.
• Server metadata, agent health, configuration status and software version.
• RDP authentication events, including source IP address, account name, time, server and result.
• Administrative audit events, support correspondence and limited website analytics.

Credentials and sensitive data

Lira does not collect or store Windows or RDP passwords. Agent enrollment uses a short-lived installation key, and operational credentials are stored and transmitted using protected service mechanisms.

Purposes and legal bases

We use information to provide the contracted service, detect attacks, apply requested security controls, maintain auditability, support users and meet legal obligations. Depending on the context, processing is based on contract performance, legitimate security interests, legal obligations or consent for optional communications.

Retention and deletion

During the 30-day trial, event data is retained for up to 14 days unless an agreement states otherwise. Paid-plan retention follows the subscription terms. Account, audit, support and backup records are retained only as operationally or legally necessary. You may request export or deletion, subject to applicable retention duties.

Service providers and transfers

We may use carefully selected hosting, email delivery, monitoring and support providers. Optional AI-assisted review is used only when enabled for the relevant service. Providers receive only the access needed for their task and are bound by confidentiality and data-protection obligations. Where data crosses jurisdictions, appropriate contractual and legal safeguards are used.

Your rights and security

Subject to applicable law, you may request access, correction, deletion, restriction, portability or object to processing, and may complain to a competent supervisory authority. We use access controls, tenant isolation, encryption in transit, audit logging, signed releases and vulnerability management to protect information; no system can be guaranteed absolutely secure.

Changes

We may update this policy when the service or legal requirements change. The revision date above identifies the current version. Material changes will be communicated through an appropriate service channel.

AI data processing

The authenticated engineering assistant is a deterministic, tenant-scoped readiness tool and does not call an external model. The optional support product assistant calls an administrator-configured OpenAI-compatible endpoint only when a visitor submits a chat message.

The support request contains the submitted message, selected interface language and conversation history supplied in that chat. Lira does not automatically attach server records, IP addresses, usernames, hostnames, event data, passwords, MFA secrets, enrollment tokens, agent keys or platform secrets. Do not place secrets in a support message.

The assistant cannot change a server or account. Its response is not stored as a support ticket; a support analytics event retains up to the first 200 characters of the submitted message and is tenant-scoped when the visitor is signed in. The configured provider, model, processing region, provider retention and training terms are not asserted here because deployment settings can override the code defaults. To opt out, do not use chat and open a normal support ticket instead.