Messaging Terms and Privacy Notice

1. Purpose and Scope

This Notice explains how Qannects messaging, support conversations, workspace conversations, attachments, notifications, reports, and call-related features are governed when those features are enabled.

Messaging privacy is a trust and responsibility. Qannects expects users, workspace operators, admins, moderators, support teams, and platform operators to use messaging truthfully, respectfully, privately, and only for lawful and permitted purposes.

Qannects messaging rules are based on Islamic principles and values, including trust, privacy, modesty, child protection, anti-exploitation, accountability, and fair dealing.

Not every messaging feature, conversation type, attachment type, or calling feature is available in every product, app, workspace, region, account state, or rollout stage.

2. Conversation Types and Visibility

Qannects may support different conversation types, including private direct messages, private or limited-audience group messages, workspace support conversations, workspace-visible conversations, admin or internal workspace conversations, commerce/payment/donation/event/janazah/service/support threads, and system, safety, moderation, legal, or support messages.

Different conversation types can have different privacy, visibility, retention, reporting, and access rules.

Private direct messages are intended for user-to-user communication and may use private encrypted messaging where that feature is enabled.

Workspace support, workspace-visible, commerce, payment, donation, event, janazah, service, admin, and operator conversations may be visible to authorized workspace owners, admins, support operators, finance users, moderators, staff, or other role holders depending on product context and permissions.

Users and workspace operators must not promise that every Qannects conversation has the same privacy model. A workspace-support conversation should not be described as equivalent to a private direct message.

3. Private Encrypted Messaging

Where private encrypted messaging is enabled for a conversation type, message text and supported attachments may be protected so Qannects is not the normal plaintext reader for that content.

Private encrypted messaging does not mean every Qannects message is end-to-end encrypted, that workspace/support/commerce/admin/system/legal/moderation/future message types use the same encryption model, or that Qannects cannot process metadata needed to operate messaging.

Reports, user-provided evidence, screenshots, device notifications, local backups, participant devices, and recipient actions may still expose message content outside Qannects' direct control.

Unless Qannects clearly states otherwise in the product and final policy, audio and video calls should not be described as end-to-end encrypted in the same way as private encrypted text messages.

Qannects may process metadata, device records, key-bundle records, encrypted message envelopes, delivery state, read state, typing state, replay cursors, session state, notification jobs, attachment metadata, report metadata, block/mute state, call state, support records, safety records, and legal records.

4. Metadata, Notifications, and Device Information

Messaging requires operational data even when message content is encrypted.

Qannects may process sender and recipient identifiers, conversation identifiers, participant state, timestamps, delivery and read receipts, typing indicators, unread counts, mute state, block state, device identifiers, notification tokens, route targets, attachment state, abuse-prevention data, rate-limit data, security events, and technical logs.

For private encrypted conversations, Qannects should avoid sending plaintext message content in push notifications unless a future feature explicitly supports and approves that behavior.

Device-level previews, operating-system settings, recipient actions, screenshots, and local backups may reveal message content outside Qannects' direct control.

5. Attachments, Files, and Voice Notes

Messaging attachments may include images, files, previews, voice notes, metadata, upload state, encryption envelope information, content type, file size, storage object references, scan state, and deletion state.

Where client-side encrypted attachments are enabled, Qannects should not receive plaintext file keys or rely on plaintext file content as the normal storage authority. Qannects may still process encrypted objects, envelope metadata, upload metadata, ownership records, delivery records, report records, and deletion state.

Private direct-message voice notes, where enabled, are treated as encrypted audio attachments rather than as proof that audio or video calling uses the same encryption model.

Attachment upload, delivery, preview, download, deletion, and reporting may be limited by file type, file size, account state, participant status, conversation type, workspace permissions, storage configuration, scan configuration, safety review, legal requirements, and product rollout status.

Qannects may use upload controls, malware scanning, access controls, deletion state, or safety review for attachments where those systems are enabled. Attachment controls can differ by conversation type and environment, and they may not apply to client-side encrypted attachments that Qannects cannot inspect.

6. Message Deletion, Editing, and Conversation Removal

Deleting a message or conversation may remove it from one user's view or redact supported active message fields in Qannects systems. It may not remove copies held by other participants, screenshots, exports, downloads, notifications, previews, local device copies, workspace-visible copies, reports, evidence, safety/legal/security/fraud/abuse-prevention/support records, payment/donation/commerce/event/janazah/admin context records, backups, audit logs, or retention records.

Where supported, sender deletion may redact active message bodies and attachment references. Deletion behavior can differ by conversation type, participant status, workspace context, legal hold, safety hold, technical state, product rollout, and applicable law.

Message editing, reactions, read/delivered state, mute controls, hide controls, leave controls, and participant restrictions may differ by conversation type and rollout stage.

7. Reporting, Blocking, Muting, and Safety Review

Users may report, block, mute, leave, or restrict conversations where those product controls are available.

Qannects may review reports, preserve relevant metadata or evidence, restrict users, remove participants, block accounts, disable attachments, disable conversations, suspend messaging access, preserve legal/safety records, or take other enforcement action consistent with Qannects policy and product capability.

For private encrypted messages, Qannects may need user-provided evidence to understand the content being reported. A report may include metadata only unless the reporting flow or reporting user provides decrypted message content, screenshots, attachments, or other evidence.

Do not use messaging for pornography, sexually explicit or immodest content, harassment, threats, bullying, grooming, sextortion, sexual exploitation, child exploitation, trafficking, fraud, scams, impersonation, spam, malware, illegal activity, doxxing, hate, targeted abuse, deceptive fundraising, payment abuse, copyright infringement, or other policy violations.

Serious violations can lead to message removal, conversation limits, account restrictions, suspension, termination, legal reporting, or other strict action. If there is immediate danger, contact local emergency services first.

8. Workspace, Support, and Admin Conversations

Workspace and support conversations may involve organizations, mosques, businesses, schools, creator channels, events, donation campaigns, finance users, moderators, or support operators.

Authorized workspace operators may access, review, manage, respond to, preserve, or escalate workspace-related conversations according to their role and permissions.

Qannects platform admins and support operators may access or preserve records where needed for support, security, safety, legal compliance, payment integrity, abuse prevention, debugging, migration, or enforcement.

Workspace operators must protect user, donor, family, child, payment, support, private, and safety information. They must not misuse workspace conversations for gossip, retaliation, unauthorized disclosure, harassment, deceptive fundraising, payment fraud, or personal misuse.

9. Calls and Live Communication

Where Qannects enables audio, video, ringing, or call-related features, Qannects may process call signaling, participant state, connection state, call identifiers, timestamps, device/network metadata, provider tokens, call-status events, quality data, and support logs.

Calls are separate from private message-content encryption unless Qannects clearly states otherwise in the product and final policy.

Users must not use calls for harassment, threats, sexual exploitation, child exploitation, grooming, impersonation, fraud, illegal conduct, hate, abuse, recording violations, or other prohibited conduct.

10. Retention, Legal Holds, and Account Deletion

Messaging data may be retained for different periods depending on conversation type, product state, account state, workspace context, deletion request, report status, legal hold, safety hold, backup lifecycle, audit need, payment context, support need, or applicable law.

Deleting an account may not delete every message or attachment from other participants, workspace records, reports, legal/safety records, backups, payment-related contexts, or devices.

Account deletion and data-rights requests are addressed in the Data Rights and Delete Account Policy.

11. Future Store and Delivery Services

Store is currently demo, preview, or pilot posture unless Qannects explicitly launches it as a public marketplace. Delivery services are not deployed as public services at this stage.

If Qannects later launches public marketplace, seller, buyer, driver, delivery, fulfillment, payout, order support, dispute, or related delivery services, related commerce and support conversations will need specific messaging privacy, retention, visibility, evidence, payment, refund, dispute, and safety rules before public launch.

12. Messaging Acceptance and Updates

Qannects may require users, workspace operators, admins, support operators, or other role holders to review and accept messaging-specific terms before using messaging features or before using particular messaging surfaces.

If Qannects materially changes messaging privacy, encryption, retention, visibility, reporting, attachment, call, or workspace-support rules, Qannects may require renewed acceptance before continued use of affected messaging features.

Messaging acceptance is a context-specific gate for messaging features, not a substitute for global Terms and Privacy acceptance.

13. Contact

Messaging questions, support requests, and policy concerns can be sent to support@qannects.com or submitted through available support and Legal Center flows.