Disclosure about messages, calls and service information

Last updated: June 27, 2026

1. What E2EE means here

E2EE means conversation content should be protected between participating devices. The service helps deliver, synchronize and connect activity, but it should not receive the private keys required to read that content.

2. Messages and groups

Text messages, private attachments and group activity travel as protected content or limited safety records. For group safety, NafqaX may receive events without the group name, without the full member list and without message text.

3. Audio, video and calls

Calls use connection information to reach participants. NafqaX may see events such as invite, accept, end, error, delay or connection state. Audio and video content should not be readable by NafqaX.

4. Notifications

Notifications are used to wake the app or indicate activity. Notification content should avoid sensitive content. The system may record delivery status to help diagnose problems.

5. Authorized assistants

External assistants should operate only when authorized by the user and by NafqaX. The service records access decisions, permissions and limited device/source references so access can be audited and blocked.

6. Moderation and reports

Reports and blocks are processed with the minimum information needed to act against abuse. When a user submits a report, they may provide context or related material. Without that, administrators generally work with limited service information and protected identifiers.

7. Important limits

Strong privacy does not remove every service record. To deliver messages, protect the network and fight abuse, NafqaX still needs limited information such as delivery status, device reference, app version, errors and safety decisions.