Privacy Policy
This Policy describes personal-data processing when the Rivrox website and its features are used, including the main data categories, purposes, legal bases, retention, safeguards and ways for Users to exercise their rights.
1. Processing Principles
Rivrox processes personal data lawfully and fairly, limits processing to specific purposes, does not combine incompatible purposes, and takes measures intended to maintain accuracy, security and timely deletion or anonymisation.
2. Data We May Process
- account data such as email, name or alias, user slug, settings and profile information;
- user content and related metadata;
- technical and security data such as IP address, user agent, session identifiers, login events and security or activity logs;
- support requests, reports and correspondence;
- records of consents and their versions;
- order, payment-status and receipt information; Rivrox does not store full bank-card details;
- data required for AI features, including prompt content and technical generation information where the User uses such a feature.
Rivrox does not request special-category or biometric data for ordinary use of the Service. Users should not publish such information unless necessary and legally permitted.
3. Purposes
Data may be processed for registration and login, providing Service functions, publishing and delivering content, preserving preferences, fulfilling orders and payments, recording consents and actions, security and abuse prevention, handling support and reports, legal compliance, service-performance analytics and development.
4. Legal Bases
Depending on the processing, the legal basis may include consent, steps necessary to enter into or perform a contract with the User, compliance with legal obligations, exercise of lawful rights and interests where the rights and freedoms of the individual are not overridden, and other bases provided by applicable law.
5. Processing Operations
Processing may include collection, recording, organisation, accumulation, storage, updating, retrieval, use, permitted disclosure, anonymisation, restriction, deletion and destruction, with or without automated means.
6. Data Localisation for Russian Citizens
When personal data of Russian citizens are collected through the Internet, Rivrox applies the requirements of Part 5 of Article 18 of Russian Federal Law No. 152-FZ to recording, systematisation, accumulation, storage, updating and retrieval using databases located in Russia, except where a statutory exception applies.
7. Providers and Recipients
Rivrox may use hosting and cloud providers, email delivery, authentication, payment, anti-fraud and security, analytics and AI technology providers. Only data needed for the relevant function or obligation is shared. Full card details are handled by the payment provider and are not stored by Rivrox.
8. Cross-Border Transfers
If a feature requires a transfer of personal data to a foreign recipient, the transfer is made only where the legal conditions are satisfied and required formalities have been completed, including notification to the competent authority where required. Availability of Rivrox in another country does not itself mean that data are transferred to that country.
9. Retention
Data are retained no longer than required by the processing purpose, contract, Service security or law. Active-account data are generally processed while the account is used. Financial, tax and other mandatory records are retained for legally required periods. When the purpose ends, data are deleted, destroyed or anonymised unless another lawful basis requires retention.
10. Security
Rivrox applies legal, organisational and technical measures appropriate to the nature and risks of processing, including access controls, credential protection, security logging, backups and measures against unauthorised access.
11. User Rights
Users may request information about personal-data processing, correction, restriction or deletion where provided by law, withdraw consent where processing relies on consent, and exercise other rights available under applicable law. Requests may be sent to info@rivrox.com. Rivrox may request reasonable identity verification to protect personal data.
12. Minors
Where applicable law requires consent from a legal representative for processing a minor's personal data, the relevant feature may be used only with that consent. If Rivrox identifies processing without a required legal basis, the account may be restricted and the relevant data may be removed in accordance with applicable requirements.
13. Cookies
Cookies and similar browser technologies are described separately in the Cookie Policy.
14. Data Sources and Service-Generated Data
Most data are provided directly by the User during registration, profile completion, publishing, support requests and use of Service features. Some technical information is generated automatically, including sign-in events, security logs, session information, technical identifiers and feature-operation statistics. Data from sign-in, payment or other integration providers are received only to the extent required for the relevant feature.
15. Requests and Processing Information
The personal-data controller is Evgenia Nikolaevna Tregubova, taxpayer identification number 503236138633. Requests concerning personal-data processing may be sent to info@rivrox.com. The Service is available at rivrox.com. A request should contain enough information to understand the issue and identify the relevant account without disclosing unnecessary personal data.
16. Records of Consents and Actions
Where processing relies on consent, Rivrox may retain a technical record of the consent event, including the User identifier, date and time, document version, confirmation method and related technical information. After account deletion, certain audit records may remain without a direct link to an active account where needed to evidence a prior action, maintain security or protect rights and where permitted by law.
17. Updates
The current version is available at /privacy-policy. Material changes are published as a new version with a new effective date.
The Russian version is authoritative. This English version is provided for convenience.
Version dated 3 September 2026.