Last updated: 23 October 2026
1. Scope and contact
This policy explains how data is collected, used and retained when you use RONAX chats, calls, groups, statuses and ronaxapp.com.
RONAX is the service name. The individual responsible for operating the service and processing personal data is Afat Jafal Ateeq Alanazi
For support, privacy questions and requests:
ronaxapp@gmail.com
2. Data we process
Account data: telephone number, display name, registration and verification information, profile photo and chosen privacy settings.
Content you share: text messages, photos, videos, documents, voice messages, statuses, locations and contact cards.
Service data: group membership and member roles, message timestamps and delivery/read status, call metadata and state, status views, and block and mute settings.
Technical data: account and session identifiers, device notification tokens, IP addresses, and operational and error logs needed to provide and protect the service.
3. Address book
When you grant contact permission, the app reads telephone numbers and sends them to RONAX servers to identify service users, apply status audiences and check eligibility for broadcast delivery.
Uploaded numbers may include people who do not have a RONAX account. Names saved on your device are used to display contacts in a familiar way.
You can refuse or revoke permission in device settings. Contact-based features may be affected. Revoking permission stops subsequent access but does not automatically delete previously uploaded data. You may request deletion through our privacy email.
4. Permissions and location
We request camera access for capture and video calls, microphone access for calls and voice messages, photo/file access for selecting or saving media, and notification permission for message and call alerts.
We use precise location when you choose to share your location, and its coordinates are sent to the message recipients. Device-reported accuracy is an estimate, not a guarantee. Sharing a fixed location does not require continuous background location tracking.
You can manage permissions in your operating system settings. Refusing a permission may prevent you from using the related feature without necessarily preventing use of the rest of the service.
5. Purposes of processing
We use data to create and verify accounts, provide conversations, calls and statuses, deliver notifications, apply privacy settings, handle reports and support/deletion requests, prevent abuse and protect the service.
Applicable legal bases depend on your location, the data involved and the purpose of processing. They may include providing the requested service, consent for optional processing, legal obligations, and legitimate interests in operating and protecting the service where applicable.
6. Sharing and notifications
Messages and content are delivered to your selected recipients. Group members see the content and membership information available to them. People you communicate with may see your telephone number, while your profile photo follows its privacy settings.
Recipients may save content, take screenshots or share it further. We cannot control copies that others retain outside the service.
We use hosting and notification providers, including DigitalOcean, Google Firebase Cloud Messaging and Apple Push Notification service. Notification services may process notification identifiers, delivery information and a sender name, number or message preview, depending on the notification type.
Calls use WebRTC and connectivity services such as STUN. Network addresses may be disclosed to the other participant and connectivity providers needed to establish a call.
Data may be processed outside your country of residence depending on hosting and provider locations. Data protection laws may differ between countries. You may contact us to ask about processing locations and data protection arrangements relating to the service.
We may also disclose specific data when required by applicable law or when necessary to protect rights and security, limited to what is needed.
7. Data security
We use HTTPS connections and session/access controls to help protect data. RONAX servers process messages and media to provide the service. This policy does not claim that messages are end-to-end encrypted.
No technical measure guarantees absolute security. Do not share your password or verification codes with anyone, including when contacting support.
8. Reports and support
When you submit a report and confirm submission of evidence, a specific message or up to five relevant messages may be submitted, depending on the report type and selected option, together with conversation information and the report reason. Authorized administrators review this information. The reporting screen explains the scope of information being submitted.
Contacting support by email does not automatically submit your conversations. Send only information needed to resolve your request. Avoid sending unnecessary sensitive information, passwords or verification codes.
9. Data retention and deletion
Account data
We retain account data and settings to provide the service while the account exists. Upon successful completion of an account deletion request, account data is removed from the active system under our deletion procedures. Associated file removal is processed in the background. Files used by independent copies belonging to other users may remain.
Messages and chat media
Messages are stored to provide conversation history, subject to the available deletion options. We currently do not apply an automatic expiry period to existing message media.
Selecting “Delete for me” hides the message from the user who selected that option while leaving it available to other participants.
Selecting “Delete for everyone” removes the message content and media references. Associated files are then placed in a periodically processed cleanup queue. A file may remain if another message, profile photo, chat wallpaper or previously submitted report evidence uses it. Technical errors may delay cleanup. Some message-record metadata remains to enforce deletion.
Deletion does not remove copies that recipients previously saved outside the service.
Statuses
Statuses are intended to remain visible for 24 hours. After expiry, periodic cleanup tasks process the removal of status data and media. We do not guarantee immediate removal of every stored copy when a status stops being visible.
Call records
The current retention period for call records in the active system is 20 days from the call start time. Periodic cleanup tasks delete older records and their associated signaling data. Removal may be delayed until the task runs or because of a technical error.
Reports
Reports and evidence are retained for review and abuse handling. Reports currently have no fixed automatic expiry period. Closing a report or changing its status does not automatically delete it. Account deletion procedures include removing reports linked to the account or containing evidence from its messages.
Backups
Backups are separate from the active system and may contain data that predates a deletion. A periodic cleanup task deletes automatic backups that are at least 30 days old.
Manual backups do not expire automatically and may remain until manually deleted. Deleting data from the active system does not immediately remove it from every backup.
Operational logs and support records
Operational logs, error logs and support correspondence are used to diagnose problems, protect the service and handle requests. The call-record retention period above does not apply to these records. Backup retention periods also do not determine how long data remains in the active system. You may contact us to ask about retention of these records or request their deletion.
10. Deletion and your rights
You can change your profile photo and privacy settings, revoke device permissions, block users and delete messages using the available options.
You can request account deletion through:
Chat settings → Delete RONAX account.
You must transfer ownership of your groups or delete them before proceeding with account deletion. Uninstalling the app does not delete your account.
Removal from the active system differs from removal of shared files and backups, as explained in the data retention section. Copies that recipients previously saved outside the service may remain.
Contact us to request access, correction, deletion, objection to processing or withdrawal of consent where those rights apply. Withdrawing consent does not affect the lawfulness of processing carried out before withdrawal.
We may verify your identity only as needed to prevent unauthorized access. If a request cannot be fulfilled or an applicable legal exception applies, we explain the reason in accordance with applicable requirements.
11. Policy updates
We may update this policy when the service or our data practices change. We publish the revised policy and its date on the website and provide appropriate notice of material changes as required.
For support and privacy requests:
ronaxapp@gmail.com