Privacy Policy

1. Introduction

Qannects treats personal information as a trust. Qannects policies are based on Islamic principles and values, including privacy, modesty, child protection, anti-exploitation, fair dealing, accountability, and community benefit.

Qannects does not treat user data as a commodity. Qannects does not sell personal information for money and does not use personal information for exploitation.

This Privacy Policy explains how Qannects handles information across Qannects websites, mobile applications, admin tools, workspaces, profiles, feeds, messaging, Watch, donations, payments, support, reporting, Legal Center pages, and related services.

Qannects aims to collect, use, share, protect, retain, and delete information only for legitimate product, safety, support, legal, community, payment, security, and operational reasons.

Store is currently treated as 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.

2. Information We May Collect

The information Qannects collects depends on the features used, account type, workspace role, device permissions, product settings, and request context.

• Account identifiers, name, email address, phone number, username, profile photo, bio, handle, authentication state, language, settings, notification preferences, local masjid/community selections, account status, lifecycle records, and legal acceptance records.
• Workspace identity, organization details, mosque/school/business/creator information, admin roles, invitations, access permissions, membership history, claim/review records, public page details, payment-device operator details, workspace authority records, audit logs, and security records tied to admin actions.
• Posts, comments, media, captions, reactions, follows, saved items, reports, moderation records, public profile activity, public page activity, events, janazah notices, announcements, donation appeals, reviews, volunteer requests, search activity, and other user-generated or workspace-generated content.
• Message content, attachments, conversation identifiers, delivery state, participants, reports, support evidence, device keys, metadata, notification records, and calling-related state depending on the conversation type.
• Watch uploads, live-session information, thumbnails, titles, descriptions, tags, comments, reports, copyright claims, counter-notices, watch history, progress, impressions, subscriptions, likes/dislikes, shares, analytics, device data, creator records, channel records, and studio records where Watch is enabled.
• Donation references, organization references, appeal/category details, donor selections, receipt records, recurring donation or subscription metadata, refund/support records, chargeback/dispute references, payment-device records, payment processor identifiers, and related audit data.
• Device type, app version, operating system, IP address, approximate location derived from network data, crash logs, diagnostics, session data, telemetry, security logs, push tokens, notification delivery records, rate-limit data, fraud-prevention data, cookies, local storage, analytics, logs, and session identifiers.

3. Device Permissions and Sensitive Inputs

If precise location, contacts, camera, microphone, photos, files, media library, Bluetooth, local network, notifications, or other sensitive device permissions are used, Qannects should describe the feature purpose in the app and request the required platform permission.

Users can usually manage device permissions through operating-system settings. Turning off a permission may limit the related feature.

4. Reports, Support, and Legal Requests

Qannects may collect information submitted in abuse reports, safety reports, privacy requests, copyright claims, Take It Down requests, account deletion requests, data-rights requests, support tickets, emails, screenshots, URLs, timestamps, content identifiers, contact details, verification tokens or verification status, public notes, internal review notes, and related evidence.

Sensitive legal request types may require contact-email verification before review continues. Legal request evidence may include links or uploaded files where enabled.

Public file evidence upload is available only if Qannects enables it for the relevant request type and environment.

5. How We Use Information

Qannects may use information to operate, secure, improve, and protect the service.

• Create, authenticate, secure, and maintain accounts.
• Provide profiles, feeds, pages, workspaces, donations, events, janazah notices, messaging, Watch, notifications, Legal Center pages, and support.
• Process donations, recurring donations, payment references, receipts, refunds, disputes, subscriptions, and payment-device activity.
• Provide admin/workspace tools, role-based access, auditability, workspace security, and authority review.
• Deliver, moderate, rank, personalize, recommend, and improve content and product surfaces.
• Operate search, discovery, notifications, saved items, history, analytics, and similar features.
• Investigate abuse, fraud, scams, harassment, exploitation, child-safety concerns, pornography, sexually explicit or immodest content, sexual exploitation, copyright issues, nonconsensual imagery, and other policy violations.
• Preserve evidence, respond to lawful requests, comply with legal obligations, and protect users and communities.
• Verify contact information or request ownership where needed for sensitive legal requests.
• Debug, analyze, test, improve, and secure the service.
• Communicate with users about accounts, policies, support, safety, payments, legal requests, product changes, and service updates.

6. Data Protection, Minimization, and Sharing

Qannects' default posture is to use information within the Qannects platform ecosystem and to share information outside that ecosystem only when needed to provide, secure, support, improve, or protect the service; process donations or payments; operate necessary third-party services; comply with law; protect safety; enforce policies; or follow the user's direction.

• With other users when product behavior makes content, profile details, messages, reactions, comments, follows, donations, workspace information, or public pages visible to them.
• With workspace owners, admins, editors, moderators, payment-device operators, or authorized representatives according to role, context, and product behavior.
• With payment processors and financial service providers for payment processing, fraud prevention, refunds, disputes, subscriptions, terminal/in-person payments, and related compliance.
• With vendors and service providers for hosting, storage, analytics, notifications, email, SMS, media processing, maps/geocoding where used, security, support, legal operations, and other operational services.
• With app stores and platform providers when required for distribution, billing, security, crash reporting, data-safety labels, app review, or policy compliance.
• With law enforcement, regulators, courts, child-safety organizations, copyright claimants, rights holders, or other parties when required by law, necessary for safety, or appropriate to enforce rights and policies.
• With successors, affiliates, or advisors if Qannects is involved in a reorganization, merger, acquisition, financing, diligence process, or asset transfer, subject to appropriate protections.

Qannects does not sell personal information for money and does not treat personal information as a product to trade. Some privacy laws define sale, sharing, targeted advertising, sensitive information, financial data, or cross-context behavioral advertising differently. Final published language must match Qannects' actual practices and applicable law.

When Qannects uses third-party service providers, Qannects should share only the information reasonably needed for the service, use reasonable contractual, technical, and operational safeguards where available, and avoid unnecessary external sharing.

As Qannects matures, Qannects intends to reduce unnecessary external service dependencies where practical so more user data can remain protected inside the Qannects ecosystem.

7. Public Content and Workspace Visibility

Some Qannects surfaces are public or semi-public. Public profiles, public pages, posts, comments, Watch content, events, organization information, donation appeals, janazah notices, announcements, reviews, and similar content may be visible to other users, visitors, search engines, recipients, or external viewers depending on product settings and routes.

Workspace and admin surfaces may make actions visible to authorized workspace operators. Users should not assume that every conversation with an organization, support team, payment operator, workspace representative, or admin is a private direct message.

Workspace authority and admin activity may be logged, reviewed, retained, and used for security, compliance, audit, support, safety, or policy reasons.

8. Messaging Privacy

Messaging privacy depends on conversation type. Private direct messages, workspace support messages, workspace-visible conversations, system messages, commerce/support contexts, and future conversation types may have different privacy and retention rules.

• Private direct messages may have stricter privacy and encryption behavior where enabled.
• Workspace-visible or support conversations may be visible to authorized workspace operators.
• Commerce, donation, support, moderation, safety, legal, and system messages may be retained or reviewed for operational, legal, security, or safety reasons.
• Reports may preserve message metadata, user-submitted evidence, and other records needed to investigate a concern.
• Deleting a message or conversation may remove it from one user's view without deleting copies held by other participants, reports, backups, legal/safety records, workspaces, or devices.

Qannects does not currently claim audited or universal end-to-end encryption for every messaging surface.

9. Donations and Payments

Qannects may collect donation/payment metadata and processor references needed to process donations and payments, issue receipts, support refunds or disputes, prevent fraud, provide organization/admin reporting, and maintain audit records.

Qannects does not intend to store full payment card numbers where payment processors handle card data. Payment processors and financial service providers may collect and process payment information under their own terms and privacy policies.

10. Retention and Deletion

Qannects keeps information for as long as needed to operate the service, maintain security, comply with law, resolve disputes, process payments, maintain audit records, investigate abuse, enforce policies, support users, and preserve safety/legal evidence.

The account lifecycle flow supports reversible deactivation and scheduled deletion where available. Deactivation hides or restricts the personal profile and signs out sessions, and a user may reactivate by signing in later.

The current in-app account deletion flow schedules deletion for 30 days. Logging back in before the scheduled deletion date may cancel deletion before finalization.

When deletion is scheduled, Qannects may hide or restrict the personal profile, revoke active sessions, reserve or tombstone public handles, and revoke non-owner workspace memberships automatically.

Full Qannects identity deletion may be held if the user owns a workspace, organization page, creator channel, donation surface, or other operated surface that must first be transferred, dissolved, suspended, or reviewed. Workspace dissolve support exists where enabled; ownership-transfer handling may require additional support or future tooling.

Users may request account deletion through available in-app flows, the Legal Center request form, or support. Legal Center account-deletion requests are support intake and verification paths; they do not automatically execute deletion by themselves.

• Deletion may not remove content copied, shared, exported, cached, backed up, screenshotted, or retained by other users.
• Deletion may not remove records needed for payments, refunds, chargebacks, tax/accounting, fraud prevention, security, legal compliance, child safety, copyright, takedown, audits, or disputes.
• Deletion may not remove workspace, organization, donation, Watch, messaging, moderation, support, or legal request records retained under a separate operational/legal reason.
• Deletion may not remove copies held by other participants, workspaces, devices, recipients, service providers, or external services.

Scheduled deletion finalization is focused on supported personal-account workflows. Qannects does not promise immediate deletion, automatic deletion from Legal Center intake, or complete deletion across every downstream product area.

11. Privacy Choices and Requests

Users may contact support@qannects.com or use the Legal Center request form to request access, correction, deletion, privacy review, or other privacy help.

• Depending on location and applicable law, users may have rights to access, correct, delete, export, object to, withdraw consent for, or limit certain uses of personal information.
• Qannects may verify contact email, account ownership, or identity before acting on sensitive requests.
• Users may control some privacy-related settings through account settings, notification settings, device permission settings, app-store platform controls, unsubscribe flows, or support flows where available.
• Region-specific rights, response timelines, appeal rights, authorized-agent processes, and data export tooling may vary based on applicable law and Qannects' available workflows.

12. Children and Minors

Personal account creation is intended for users who are at least 13 years old. Qannects is not currently intended for under-13 personal account creation unless a separate child privacy, parental consent, and safety workflow is approved.

Qannects may serve families, children, schools, mosques, organizations, events, TV/display contexts, and supervised community settings. Adults, parents, guardians, schools, mosques, and organizations should use care when posting, managing, or sharing information about children.

Qannects has zero tolerance for child sexual abuse material, grooming, sexual exploitation, sextortion, trafficking, and conduct that endangers minors. Qannects may preserve records, restrict accounts/content, and report suspected exploitation where required or appropriate.

13. Security

Qannects uses administrative, technical, and organizational safeguards intended to protect information. These may include access controls, authentication, audit records, monitoring, private storage controls, encryption where appropriate, security logging, and operational review.

No system can be guaranteed to be completely secure. Users should protect account credentials, devices, email accounts, phone numbers, and workspace access.

14. International Processing

Qannects may process information in the United States, Canada, and other locations where Qannects or its service providers operate.

Users who access Qannects from outside the United States or Canada understand that information may be processed in jurisdictions that may have different data protection laws than their location.

Bangladesh expansion will require local-law and operations review before Qannects expands public availability there.

15. App Store and Google Play Disclosures

Qannects app-store privacy disclosures and Google Play Data safety answers must match the actual data collection, use, sharing, retention, deletion, and third-party SDK behavior of the deployed apps.

Qannects aims to keep App Store privacy details, Google Play Data safety answers, account-deletion links, app permission explanations, and privacy-policy URLs accurate and up to date.

16. Changes to This Policy

Qannects may update this Privacy Policy. Material changes should be versioned and, where appropriate, presented through web/app notice or acceptance flows.

Qannects keeps versioned legal acceptance records for required Terms and Privacy updates. Older termsAcceptedAt timestamps may remain as compatibility records, but new material Terms or Privacy updates should use the current versioned bundle and acceptance flow.

17. Contact

For privacy questions or requests, contact support@qannects.com.

Qannects LLC

418 Broadway STE N, Albany, NY 12207 USA