Privacy Policy

Rivella is built and operated by Alexandr Ciumac, an independent developer. Contact: ciumac.dev@gmail.com, Telegram @spumony.

When a business connects Rivella, that business remains the owner of its clients’ data and decides why it is processed. Rivella acts as a processor on that business’s instructions.

Clients of a connected business who write to the bot: Telegram user id, username, name, phone number (if the client provides one), the full text of the conversation with the bot, and booking details — service, date and time, comment, status.

Staff of the business using the control panel: email address, password hash (bcrypt — the plaintext password is never stored), name and role.

Technical data: the service error log, which may contain fragments of the request that failed.

The public page at rivella.app runs no analytics, counters or advertising trackers. In the control panel the browser stores only an authentication token in localStorage, so that the password is not required on every page.

To answer a client’s question, find an open time slot, create or change a booking, send a reminder, and hand the request over to the business’s manager.

To show the business owner their own conversations, leads and statistics in the control panel.

To investigate service failures and keep the service secure.

Anthropic PBC (USA) — conversation text is sent to the Claude API to generate a reply. Anthropic does not use data submitted through the API to train its models.

Telegram Messenger Inc. — messages travel through the Telegram Bot API, which is an unavoidable part of the channel.

YClients — only for businesses that use YClients: name, phone and booking details are sent there to create the appointment.

Hetzner Online GmbH — server and database hosting.

Data is never sold, never shared with advertising networks, and never used for profiling beyond the purposes listed above.

All service data is stored in a PostgreSQL database on a dedicated Hetzner Cloud server in Helsinki, Finland (European Union). Traffic to the site and the API is protected with TLS.

Sending conversation text to Anthropic (USA) is a cross-border transfer, carried out under the provider’s standard contractual terms.

Client data is kept for as long as the agreement with the corresponding business is in force. Once the business stops using the service, its data is deleted on request.

A deletion request for an individual person is carried out within 30 days of receipt.

You may request access to your data, its correction, deletion or restriction of processing, receive it in a machine-readable format, and withdraw consent you previously gave.

If your data reached the service through a specific business’s bot, start with that business — it decides what happens to its clients’ data. If that is not possible, write directly to ciumac.dev@gmail.com.

If you are in the EU, you also have the right to lodge a complaint with your national data protection authority.

Each business’s data is isolated at the database level: every row is tied to a tenant id, and control panel queries are always scoped to it.

Passwords are stored only as bcrypt hashes. Control panel access is protected by a JWT token.

No system offers an absolute guarantee. If a breach affecting your data occurs, the affected businesses will be notified without undue delay.

When this document changes, the date at the top is updated. Material changes are additionally communicated to connected businesses.

Questions and data requests: ciumac.dev@gmail.com or Telegram @spumony.