Privacy Policy

Effective November 4, 2026

Rillay is operated by liang li. This policy covers the Rillay iOS and Android apps, rillay.com, and live.rillay.com. Contact: domr@qq.com.

Information used to provide meetings

You choose a display name and language. A nickname is sufficient. We store these with a random participant identifier, a hashed device session identifier, meeting identifiers, meeting mode, and joining/leaving and expiry information to provide meetings, restore connections, and prevent abuse.

Your selected meeting language is remembered on this browser. Your name and call mode are kept in the current tab; saving them between visits is optional. The iOS app keeps its private session cookie in Keychain. The session cookie expires after 30 days. We do not use advertising identifiers, advertising SDKs, cross-app tracking, or sell personal data.

Camera, microphone and live translation

Camera and microphone access is optional. You can join with either or both off and revoke access in your device settings. When enabled, your live audio and video are transmitted through our meeting infrastructure to meeting participants. Connections use transport encryption; this service does not claim end-to-end encryption.

When live translation is on and your microphone is enabled, microphone audio is sent through our server to Soniox for speech recognition and translation. The resulting text is used to generate translated speech. Captions and translated speech are delivered to participants. Camera video is not sent to Soniox. Turn off your microphone to stop sending new audio for translation. You can also use original-audio meetings.

Rillay does not record or persist meeting audio, video, captions, or translated speech. Soniox states that its real-time API processes content transiently without retaining it or using it to train models. See Soniox’s Privacy Policy and security and privacy information. Information is processed on our hosting infrastructure and by Soniox, which may be outside your country.

Network and operational information

We keep daily access and application usage logs to understand application usage, operate the service, and prevent abuse. These logs include timestamps, IP addresses, client platform, language, original-audio or translated meeting mode, connection durations, translated-mode durations, and hashed meeting and participant references. Access logs also include the host, HTTP method, a normalized route, status code, request duration, and response size. Access logs omit invitation codes, query strings, cookies, and authorization headers. Application usage logs omit names, private device credentials, and meeting content. Logs are retained for up to 90 days. Translation operational logs contain timing, language, duration and random request references, not audio or transcripts. Aggregate daily translation usage is retained for up to 90 days to enforce service limits.

Browser storage and your choices

The public homepage does not create a meeting-session cookie or load third-party analytics, advertising, embedded videos, or external fonts. There is no automatic cookie or preferences popup. The meeting language you select is remembered by default, with a simple opt-out in Privacy settings. Your name and call mode stay in the current tab; saving those inputs between visits requires your affirmative choice. The meeting app uses a necessary host-only device-session cookie and temporary per-tab call settings. You can change or withdraw saved-setting choices at any time and still use the service. See Cookies & Storage for the full inventory and durations.

Purposes and legal bases

We process the meeting information and network connections needed to provide the service you request. Our operational and security logs support our legitimate interests in keeping the service secure, diagnosing faults, and understanding service reliability. We remember the language you explicitly select to provide the interface you request; you can turn this off in Privacy settings. We ask for permission before saving your name and call mode between visits. In translated meetings, microphone audio is processed to provide the translation feature. Turn off your microphone to stop sending new audio for translation, or use original-audio meetings. Browser storage choices do not turn off server-side access and service-quality logs.

Your data rights and international processing

Depending on your location, you may have rights to access, correct, delete, restrict or object to processing, request portability, withdraw consent, or complain to your local data protection authority. Contact the operator at domr@qq.com. We will respond as required by applicable law. Withdrawing consent does not affect processing already carried out. Our hosting infrastructure and Soniox may process information outside your country; contact us for information about processing locations and applicable transfer arrangements. We do not make automated decisions with legal or similarly significant effects about you.

Retention and your choices

Meeting and participant records are automatically deleted after the meeting expiry time is more than 30 days old, during regular cleanup. Live content exists only in transient processing and playback buffers. Other participants may independently capture what they see or hear; only share invitations with people you trust.

You can leave any meeting, disable devices, choose original-audio meetings instead of translation, change your display name, and clear local app data. For access, correction, deletion, or privacy questions, email domr@qq.com with the meeting date and relevant display name or meeting reference. Do not send private meeting audio or credentials. We may need limited information to verify a request.

Children and updates

Rillay is a general-purpose meeting service and is not designed specifically for children. If you believe a child’s information was provided improperly, contact us. We will publish policy changes on this page with an updated effective date.