Privacy Policy

1. Who is responsible

The responsible provider for the RIO Mentor beta is Casabuena Fernando Azarias. The public legal or commercial domicile is shown above as a placeholder until it is validated. Privacy requests can be sent to support@riomentor.com.

The applicable local authority, representative, or data-protection officer will be identified when required for a country or processing activity.

2. Data we may process

Account data may include your email address, authentication records, account identifiers, subscription or entitlement records, and security events.

When you use the assistant, we may process the text you submit, the generated response, conversation identifiers, and minimized DCS telemetry relevant to the request. Exact coordinates, pilot names, and world contacts are removed before the backend or language-model request when the current filtering rules apply.

The Windows client can create temporary audio while processing speech locally. Local transcript storage is disabled by default and is available only with an explicit opt-in and a configured short retention period.

Support messages, billing records, provider logs, and technical diagnostics may be processed when needed to provide the service, prevent abuse, comply with law, or resolve a dispute.

3. Purposes and legal bases

We use account and authentication data to create and secure your account and provide the requested service; this is generally necessary for the contract or requested pre-contract steps.

We use billing and entitlement data to provide paid access, prevent fraud, reconcile transactions, and comply with legal or accounting duties.

We use minimized telemetry and submitted text to answer the requested simulation question. Optional local transcripts require consent. Security and service reliability activities may rely on a legitimate interest or another lawful basis where applicable.

We do not use prompts, telemetry, or feedback to train models for a new purpose without appropriate notice and a valid legal basis.

4. Recipients and international transfers

Depending on the environment, recipients or processors may include Supabase for authentication and database services, Vercel for hosting and infrastructure, a configured language-model provider for inference, Paddle for billing, and support or security providers.

Vendor names, regions, sub-processors, retention settings, transfer mechanisms, and data-processing agreements must be confirmed for the production environment. We will not describe a transfer as approved until that evidence exists.

5. Retention and deletion

We retain data only for the purpose and period needed to provide the service, secure it, resolve disputes, meet legal or accounting obligations, and enforce valid rights. Specific periods depend on the category, provider, backups, and legal holds.

Local transcripts are disabled by default and, when explicitly enabled, use the configured 1–30 day retention range. Account and conversation deletion controls are described in the product; legal or security retention exceptions must be documented separately.

6. Your rights

You may request access, correction, updating, deletion, portability, restriction, objection, or withdrawal of consent where those rights apply. Send a free request to support@riomentor.com with enough information to locate the account; we may use proportionate identity verification.

For Argentina, requests must be handled within the applicable statutory periods, including the access and rectification, updating, or deletion periods described by the AAIP. You may also complain to the applicable supervisory authority, including the AAIP when applicable.

7. Children, AI transparency, and changes

The service is intended for people aged 18 or older and is not directed to children. We will review the service before knowingly processing a minor's data.

RIO Mentor uses artificial intelligence, can make mistakes, and is limited to DCS World simulation and training. It must not be relied on for real aviation, navigation, emergencies, military operations, or safety decisions.

We will publish a new version and effective date for material changes and retain an internal history of legal-document versions.