Updated

Privacy policy

This policy explains data processing in the Rivela Android app (com.rivela.app), on rivela.ru and when contacting support. The service is intended for users in Russia. The Russian and English versions describe the same practices; both are publicly accessible without registration or geographical restrictions.

Diary entries stay on your deviceService data supports functionality and usage statisticsNo sale of data

Privacy contact: developer@rivela.ru

Delete local entries or request deletion of server-side data

1. Who is responsible for your data

The developer of Rivela and data controller is Vitaliy Vladimirovich Ivanov (Иванов Виталий Владимирович), a self-employed individual in Russia, taxpayer identification number (INN) 781415365949. For privacy enquiries, access, correction or deletion requests, contact developer@rivela.ru. Telephone: +7 981 100-45-77.

Rivela does not require registration of an online user account. Trial and paid PRO access use a technical installation record rather than a username-and-password account.

2. Diary and information on your device

You enter cycle and period dates, flow intensity, symptoms, sleep, energy, temperature, test results, discharge and personal notes yourself. Depending on the features used and saved history, age, height, weight, goals and preferences may also be stored. Older records or restored backups may retain previously entered profile and mood fields. A historical field does not mean that current screens offer it for entry.

This information, including sensitive wellbeing and reproductive health information, is stored and processed locally for the calendar, estimates, personal patterns, charts and reminders. Rivela does not upload diary or profile contents to its server for storage or analysis, or send them to advertising networks or external AI/LLM services. Sending a file to another recipient or including this information in a support request is a separate action you choose, as explained below.

3. Information received by the Rivela server

During network requests, the app sends the following service information:

  • Identifiers: a random installation identifier (install ID) and, when available, a key derived from the system Android ID. The original Android ID is not sent; the server stores a hashed representation of the key. These identifiers link an installation to trial and PRO history, including after reinstallation. They are pseudonymous, not necessarily anonymous.
  • Technical information: platform, device manufacturer and model, app version and version code, distribution channel, onboarding completion and notification permission status.
  • App usage: request times, last activity and app launch events (app_open). These support our own statistics about active installations and app versions, including usage after trial or paid access ends.
  • Access and payments: selected plan, order and invoice identifiers, amount and currency, payment status and time, trial/PRO dates and status, payment provider confirmation history, and access transfer codes and outcomes.

These requests do not include diary contents. Network infrastructure also processes IP addresses and HTTP headers for connectivity and security; error logs may contain them. Rivela does not use IP addresses to infer your location. Routine access logging is disabled on the current Rivela web server.

4. Purposes and grounds for processing

Local data supports the features you choose. Service information is used to provide and verify PRO, preserve trial dates, process payments, transfer paid access, prevent repeated trials and abuse, produce our own usage statistics, maintain security and provide support.

Depending on the operation, processing is based on consent where legally required, steps requested by you, performance of the agreement and paid access, or the controller’s legal obligations. Entering observations, exporting a file, contacting support and proceeding to payment are separate actions you choose. This page does not replace any separate consent that may be required.

Rivela does not sell data, use diary contents for advertising or make automated decisions with legal effects based on your diary. The app contains no advertising networks or external AI analysis of personal entries.

5. Recipients, payments and third-party services

  • Rivela infrastructure: the controller and authorised technical administrators have restricted access to service information; HOSTKEY provides infrastructure hosting. At the date of this revision, the service APIs, database and operational database backups are hosted on a server in Russia. These systems do not provide cloud diary storage.
  • Robokassa and banks: payment requests include the amount, plan description, order number and confirmation parameters. The provider returns confirmations, identifiers, payment status and related service parameters, which may be retained in the transaction history. Card details are entered with the provider or bank; Rivela does not receive or store a full card number or CVC. Additional information you enter for a payment or receipt is processed by the provider under its privacy policy.
  • App stores: stores process their own download and update information under their own terms. The RuStore version uses the RuStore SDK to check for and install updates; Rivela does not send diary entries to that SDK. See the RuStore privacy policy.
  • Support and email: the controller and email service providers process the sender’s address, subject, text and attachments voluntarily sent to support. Health information you choose to include is processed to respond to that request. Send only what is necessary; do not send your PIN, backup password, CVC, full card number or unsolicited identity documents.

Information may also be disclosed in response to a lawful request from competent authorities or an action you specifically choose. Independent services apply their own terms and retention practices. Contact support for information about recipients and the processing of a specific request.

6. Android permissions and app access protection

Internet and network state access support service requests and payments. Notification permission is requested through Android and can be revoked in system settings. System permissions for background work, wake locks and restoring scheduled work after a reboot support the reminder scheduler.

Android performs biometric verification. Rivela receives the outcome, not a fingerprint, face image or biometric template. The app does not request location, contacts, SMS, calls, microphone, camera or Health Connect access. You select files through the system file picker.

A PIN and biometrics protect entry to the app. They do not automatically protect PDF/CSV reports or other files you have saved outside it.

7. Backups, exports and notifications

Diary backups are encrypted with a separate password you choose. PDF and CSV exports may contain sensitive information and are not password-protected by Rivela. You choose where a file is saved and who receives it. If you select cloud storage, email or another app, that recipient’s practices apply. Rivela does not upload these files to its server. Deleting your diary or uninstalling the app does not delete files and copies previously saved elsewhere.

Reminders are generated on the device and may display information on the lock screen. You can hide details and manage Android notification channels. Separate notifications remind you when the trial is ending and offer PRO access; these can also be managed in Android notification settings. To check the current PRO status, the app contacts the server using service identifiers without diary entries.

8. Data retention

  • Local diary and profile: retained until you delete entries, clear app data or uninstall the app. External backups and exports remain until you or the service you selected deletes them.
  • Installation, licence and trial history: retained to provide and restore access, support users and prevent repeat trials, including after access ends or the app is uninstalled. Automatic deletion of these records after a fixed calendar period is not currently configured. Deletion requests are reviewed separately, subject to legitimate grounds for necessary retention.
  • Activity events: retained for our own usage statistics and app version monitoring. There is currently no configured automatic expiry for these events. You can request deletion of information associated with your installation.
  • Payment confirmations and support correspondence: retained for fulfilment of obligations, handling enquiries and disputed transactions, and applicable tax or other legal requirements. You can ask about the basis and period for any part that must be retained.
  • Technical backups and logs: operational encrypted service backups leave the rotation after 14 days. The current web server error log rotates daily and keeps 14 archived rotations. This is not the retention period for diary entries or records in the operational database. Separate one-off archives are outside the 14-day rotation and remain until removed by the controller; they are also considered when handling a verified deletion request.

After information is removed from the operational database, residual data may remain in previously created restricted backups until their rotation ends. If a backup is used for restoration, a previously confirmed deletion request must be taken into account again. Records that must lawfully be retained may be kept longer and are not used for new, incompatible purposes.

9. Delete data or submit a request

On your device: edit or delete individual entries, or use Settings → Delete my data to clear the diary and profile. The installation identifier, trial information and confirmed PRO entitlement may remain to preserve access and prevent a repeated trial. This action does not delete the server-side record. Separately delete your backups, PDFs and CSV files from the locations where you saved them.

On Rivela’s server: email developer@rivela.ru with the subject “Rivela data deletion request”. Specify whether you want service identifiers, activity history, a support conversation or all eligible information associated with you deleted. You can submit a request after uninstalling the app; reinstalling it is not required to send the request.

To identify the correct record and avoid deleting someone else’s data, include an available order number or other information you already have that can link the request to the installation. If you have no identifier, explain the situation; support will clarify the minimum information and suitable verification needed. Your password, full card number, CVC, health diary and identity document scans are not needed for the initial request.

After verifying a request, the controller deletes associated information that has no lawful retention requirement and communicates the outcome. If some information must remain, the reply explains why and gives the applicable retention period or criterion. Requests are handled within the time limits imposed by applicable law. Removing service information may prevent restoration or transfer of PRO; relevant consequences are clarified when handling the request. Rivela has no separate online user account that must first be closed.

The same address accepts requests for access to service information, correction, restriction of processing or withdrawal of consent where consent is the basis. You may also contact Roskomnadzor or a court to protect your rights.

10. Security and data transfers

Connections to the Rivela API and payment service use HTTPS. Safeguards include Android app data isolation, restricted administrative access, signed PRO entitlement confirmations and encrypted service backups. Device security, system locking and protection of files you save also depend on your settings and actions. Absolute security cannot be guaranteed.

The primary service infrastructure is hosted in Russia. Independent payment, email and app store services may use their own infrastructure. Changes to recipients or processing that trigger consent or transfer requirements must fulfil those requirements and be reflected in this policy.

11. Website and external links

The Rivela website and these policy pages are available without signing in. Current pages do not use advertising trackers, diary entry forms or cookies for behavioural advertising. Technical HTTP connection information is processed to deliver the site and maintain security. External payment pages, app stores and other recipients apply their own terms, including their cookie practices.

12. Purpose of the app

Rivela supports personal cycle and wellbeing tracking. It is not a medical device. Its features do not provide diagnosis, treatment, cures or prevention of disease. Estimates are approximate and must not be used as contraception. Consult a qualified healthcare professional for medical advice, diagnosis and treatment.

13. Policy changes and language versions

The current revision is published at rivela.ru/privacy.html and rivela.ru/privacy-en.html. The app links to the full document. The policy is updated when purposes, data categories or recipients change materially; separate renewed consent is requested when required. Store disclosures and declarations must match the actual distributed app version.