Draft privacy

Draft for review only - not approved for publication or legal acceptance. Operator identity, contact channels, commercial policies and retention periods still require approval.

Operator and contact

Operator: Awaiting approval

Address: Awaiting approval

Contact: Awaiting approval

Current product behavior

Tahseel stores account, company, customer, contact, invoice, payment, promise and activity records. Separate verification challenges serve signup and recovery, with hashed verifiers. Company data and team permissions are isolated on the server.

The application also maintains sessions, audit history, and email/message delivery metadata. External delivery depends on an approved integration; Simulation and the local inbox are not external delivery evidence.

Deletion and retention

Request account deletion through the public deletion page after email verification. Requests have visible status and can be cancelled before execution. Erasure requires reviewed data policy and ownership handling; a sole owner must transfer ownership or explicitly arrange company closure. Execution removes profile information, credentials, sessions, memberships, personal payment proofs and local account-mail data. Company financial/audit records retain an anonymous identifier under the approved scope; no statutory retention period is assumed. Deactivation or trial expiry is not deletion.

Purposes and sharing

Data supports account operation, your company's collection work, permission checks, duplicate prevention and subscription review. Subscription proof is private to authorized platform review. Company roles cannot review other companies' subscriptions.

When you choose Open WhatsApp, your device shares the recipient number and reviewed draft with WhatsApp, potentially including name, amount, currency and date. You decide whether to send inside WhatsApp; its processing follows its own policies. Tahseel does not obtain WhatsApp passwords/session credentials or verify delivery. Your supplied contact number is not verified WhatsApp ownership.

Verification, recovery and invitation emails use the central transactional service when bound. The local test inbox is local evidence only. Device reminders are optional, require system permission and display no customer names or amounts. Secure local caches support some read screens with offline labels; Today requires an online read. Audit events track operations, not message-bearing WhatsApp URLs.

Your controls and data security

You can edit contact details, disable reminders, sign out and request deletion. Servers check tenant, role and session. Passwords/codes use hashed verifiers; completed deletion revokes sessions. An offline device cannot be remotely cleared instantly: cleanup occurs on its next failed online session validation, or you can clear app storage in system settings.

Operator identity, processing purposes and legal bases, user rights, processors/transfers and retention schedules require review and approval before publication.