Tatheer product and methodology policy

Version: 1.0
Prepared: 6 September 2026
Status: Operating policy for publication; no independent religious or legal approval claimed
Operator: Sheriax Solutions, through Kizu

1. What Tatheer does

Tatheer helps you keep a separate record of possible bank-interest income, review the amount yourself, and record a payment you make directly to a recipient. It supports your own decisions; it does not decide whether income is religiously permissible or whether a religious obligation has been fulfilled.

Kizu is not acting as a bank, payment wallet, charity, investment adviser, or religious authority through this feature. Tatheer does not receive, hold, pool, transfer, or automatically dispose of your money. A recorded disposal is not a payment instruction, tax receipt, or certification.

2. Availability and your choices

Tatheer is available to everyone using Kizu, with tracking enabled by the user. Opening Tatheer does not enroll you. To start tracking, read this policy, select its acknowledgement and tap Enable tracking. Availability does not itself mean that a user has accepted a policy, requested a scan, confirmed an amount, or made a payment.

Tracking starts in manual-only mode. Scanning requires a separate Scan existing Kizu transactions action and confirmation each time. There are no automatic or background enrollment scans. You decide whether to use the feature and review each candidate. Kizu does not infer your religion from account activity. Policy acceptance is recorded only when you explicitly enable tracking, against the version shown to you.

3. Source data and detection

This release supports an INR ledger. Manual entries use the INR amount, date, and optional description you provide. On-request detection examines eligible recorded incoming transactions already held in Kizu. It does not log into your bank, ask for banking credentials, or retrieve a live balance.

The current detection rules support positive incoming INR transactions. They normalize narration and match phrases associated with possible bank interest, including “INTEREST CREDIT,” “SB INT,” and “INT PD.” Refund, reversal, correction, cashback, dividend, and reward phrases suppress a match. Unsupported currencies and unrecognized wording may not be detected.

A match creates a potential item with a reason code. A confidence indicator describes the strength of a text match, not religious certainty. Rules can produce false positives and miss real interest. Check the original transaction or bank statement before deciding. No candidate is automatically confirmed because a phrase matches.

4. Review and correction

You may leave a potential item unconfirmed, confirm the amount after review, or exclude it. Check the currency and amount, and correct the confirmed amount where the review form permits it. A manual entry or confirmation does not rewrite the original Kizu transaction.

Unconfirmed items must not be treated as confirmed obligations. When unsure about the nature of a receipt or its appropriate treatment, obtain advice from a qualified person you choose. Kizu does not present a match or a disposal record as a fatwa, Sharia certification, or legal conclusion.

5. Recipient listings and direct payments

A recipient can be offered for recorded disposal only after Kizu's recipient review has established the organization's identity, relevant program, acceptance of the funds, and ownership of its payment channel. A listing is not a guarantee of every activity of the organization or a substitute for your own checks.

Where no eligible recipient is listed, Kizu must explain that a disposal cannot currently be recorded through that flow. It must not invent a recipient or present an unreviewed recipient as approved.

You make any payment directly, using a payment service outside Tatheer. Verify the payee and amount before paying. Kizu does not make the payment, deduct funds, guarantee delivery, issue a donation receipt, or promise a tax benefit. The recipient or payment provider handles payment disputes and payment evidence.

6. Disposal records and claims

After paying, you may record the amount, date, recipient, and optional reference. The recorded allocation must match the disposal amount, use the same currency, and not exceed the remaining confirmed balance.

A user-entered record is labeled self-reported. It must not be described as recipient-verified unless separate recipient confirmation has actually been obtained. Recording a payment reduces the tracked outstanding amount; it does not certify religious completion or establish that the recipient received the money.

Public impact figures, if introduced, must distinguish self-reported records from recipient-confirmed outcomes. Estimates must be labeled as estimates. No religious or tax benefit is promised.

7. Privacy and access

Tatheer records are associated with your signed-in Kizu account. They can contain transaction links, amounts, currencies, dates, descriptions, review decisions, allocations, recipient selections, and payment references. Kizu processes this information to provide the feature and its ledger. Cloud processing and operational storage follow Kizu's published privacy policy; Tatheer is not described as local-only or as guaranteeing storage in India.

Do not enter passwords, card security codes, full account numbers, or unrelated sensitive information into descriptions or references. Ordinary product analytics must not contain Tatheer amounts, narration, recipient choices, payment references, or policy acceptance as a proxy for religion. Tatheer records must not be included in general AI chat context without a separate, clear product decision and disclosure.

8. Export and deletion

You can export the Tatheer records available to the app and choose whether to share the exported file. Once shared, a copy is controlled by the destination you select.

The Delete Tatheer data action asks for confirmation, removes Tatheer records from the active account data, and disables Tatheer for that account. It does not delete your general Kizu accounts or transactions, reverse a payment, or remove copies you exported or shared. This policy does not promise immediate erasure of backups or provider security logs; those follow Kizu's privacy policy and applicable retention processes.

9. Policy changes and support

The published policy must identify its version and publication date. Material changes to data use, detection, recipient handling, or enrollment must be explained before they apply. An acceptance record must identify the actual policy version accepted.

Use Help in Kizu to report incorrect detection, recipient information, privacy concerns, or ledger problems. Include only the information needed to explain the problem. Kizu may suspend unavailable or defective functionality while preserving access to existing records where practical.

10. Approval status

This is an operating policy written against the current implementation. It is not evidence of independent religious or legal review. Publication must not change that status to “approved,” “certified,” or “review completed” unless documented review supports the claim.

The operator has chosen universal availability with explicit user-enabled tracking. Publication enables that bookkeeping scope; it does not establish independent religious or legal approval. No recipient is listed without documented review. Recipient payments, certification claims and impact claims remain subject to their separate gates. Broader app privacy/store review and Google Play release remain separate release work. Tracking can be suspended operationally without removing read/export access to existing records. This policy makes no fixed backup-erasure or India-residency promise.