# Dhanora Privacy Policy

**Effective date:** 17 October 2026  
**Last updated:** 19 October 2026  
**Operator:** Gurazala Kiran Kumar, owner of Dhanora  
**Website:** https://dhanoraledger.com  
**Privacy contact:** [kirannew40@gmail.com](mailto:kirannew40@gmail.com)

This policy explains how Dhanora handles information when you use its website and Android application to manage lending records, interest, Jama repayments and collections. It covers registered account holders and people whose information account holders enter into their ledgers.

## 1. Information we process

**Account and profile information.** Your account identifier, verified email address or phone number where supported, first name, display name, business name, sign-in provider, ledger names and account preferences. Authentication providers handle credentials and verification. Dhanora does not receive your ChatGPT password.

**Customer and financial records.** Information you enter, including customer names, father or mother names, mobile and WhatsApp numbers, email addresses, addresses, notes, lending dates, principal amounts, interest rates, compounding settings, repayment schedules, Jama entries, payment methods, balances and transaction history. Payment-method entries such as cash or UPI describe recorded transactions; they do not by themselves authorize Dhanora to debit an account.

**Files you choose to upload.** Customer photos, promissory notes, asset documents, agreements and other supported attachments. Such documents may contain personal or financial information about you or other people. Avoid uploading unnecessary identity numbers or unrelated sensitive information.

**Activity, communications and technical information.** Relevant account activity and correction history; reminder recipients and message content; delivery results and provider identifiers; notification preferences; device/session identifiers; browser or device descriptions; and security or error information. Network requests also expose technical information such as IP addresses to the hosting and service providers. Dhanora uses hashed identifiers for authentication and AI rate limits.

**AI questions.** Questions you submit to Ask Dhanora, recent question context, selected language and calculation date, as described below.

## 2. How we use information

We process information to authenticate users; maintain separate private accounts and ledgers; store and calculate balances; record repayments; provide reports and exports; deliver requested reminders and account communications; operate optional AI assistance; investigate faults or misuse; and process account deletion.

Customer details and financial records are not public profiles. Records are accessed through the authenticated account and authorized service operations. Administrative functions can display registered-user information for account administration and support.

Dhanora does not currently include advertising or functionality for selling personal data. If advertising, analytics or other materially different data uses are introduced, the policy and relevant disclosures must be updated before that processing begins.

## 3. Information about your customers

Account holders decide which customer information they enter and which communications they request. Only enter information you are entitled to use, explain its use to the people concerned, and obtain consent or another appropriate lawful basis where required. Dhanora does not obtain permission from a customer simply because an account holder uploads that customer's details.

If someone has recorded your information in Dhanora, contact that account holder to request correction or removal. You may also contact Dhanora using the privacy contact above. We may request proportionate information to verify your identity and locate the relevant record without revealing another person's private ledger.

## 4. Service providers and recipients

Dhanora uses providers to perform specific functions:

| Provider or recipient | Purpose and relevant information |
| --- | --- |
| OpenAI/ChatGPT Sites and Cloudflare infrastructure | Website/application hosting and storage of account, ledger and uploaded-document data; operational request information. |
| Supabase | Email/mobile authentication where enabled, verified contacts and authentication sessions. |
| Resend | Verification and notification emails, including recipient addresses, message content and delivery information. |
| OpenAI API | Interpretation of Ask Dhanora questions, as explained in Section 5. |
| SMS/WhatsApp providers such as Twilio, when enabled | Recipient phone numbers, verification or notification content and delivery information. Configuration does not mean every channel is currently available. |
| Browser push services, where supported and permitted | Push subscription endpoints and the alert payload sent to that device. |
| Recipients selected through notification settings | Relevant account, payment or reminder information sent to the account holder and/or the customer. |

Information may also be disclosed where required by applicable law or reasonably necessary to investigate security incidents or protect rights. Provider processing may occur outside India. This policy does not claim that all information remains in India; providers' applicable terms and safeguards also govern their processing.

## 5. Ask Dhanora and AI

Some questions can be handled by built-in application logic. Where external AI interpretation is used, Dhanora sends your question, up to six recent questions, language and calculation date to the OpenAI API. Names, amounts or other personal information you type in those questions are included.

The current integration does not automatically send the complete ledger database, uploaded documents or calculated answer balances to the model. It asks the model to identify the intended query, then calculates the answer using authorized ledger records in Dhanora. The assistant is read-only and cannot independently create accounts, change payments, delete records or send reminders.

Requests use `store: false`. This is not a promise of zero provider retention; provider security and abuse-monitoring practices may still apply. Avoid entering unnecessary sensitive information. You can use normal ledger features without asking AI questions. AI interpretations can be incorrect, so check the underlying records before relying on an answer.

## 6. Android permissions, fingerprint unlock and local storage

Optional fingerprint or biometric unlock uses Android's system authentication prompt. Dhanora receives the authentication result; it does not receive or store fingerprint images or biometric templates. Those remain managed by the device's operating system. The local preference that enables app locking is stored on the device.

The current standalone Android app requests internet and biometric/fingerprint permissions. It does not request contacts, call-log, SMS-reading or location permissions. File selection uses the system picker for files you choose. Current home-screen widgets provide navigation shortcuts and do not display customer names or balances.

The website and Android WebView use cookies and local/session storage for sign-in, session handling, language choices and application presentation. Downloaded exports and files you save remain on your device or wherever you share them. Signing out or deleting the account does not remotely erase independently downloaded copies.

## 7. Notifications and your choices

Email, in-app and supported push notifications may contain names, account details, amounts or account activity. Delivery depends on account preferences, recipient settings, permissions and enabled providers. Review recipients before enabling customer communications and review device lock-screen settings if alerts could reveal sensitive information.

You can change available notification preferences, revoke browser notification permission, disable biometric unlock in app settings, edit permitted profile/customer information and download supported reports or backups. Security and verification messages may be necessary to complete an action you request. Uninstalling the Android app does not delete the server-side account.

## 8. Retention and deletion

Account and ledger records remain in the live service while needed to provide the account, unless removed through an available deletion flow. Accounts moved to Trash remain stored and can be restored; this is different from permanent account deletion.

Use **Settings → Delete my account**, or follow https://dhanoraledger.com/delete-account. The flow requires a code sent to your verified account email, typed confirmation and an explicit slide-to-confirm action. Mobile-only users must first add and verify an email. Confirmed deletion blocks account access immediately and starts removal of all ledgers, customer records, accounts, payments, documents and related notification data. Cleanup failures remain queued for retry by the background job, currently scheduled every five minutes. A retry interval is not a guaranteed completion deadline.

For email/mobile accounts, the Dhanora authentication identity is removed. For ChatGPT sign-in, the Dhanora account and data are removed without deleting the separate ChatGPT account. Deleting records does not settle debts or waive obligations between lenders and borrowers.

A one-way account-identifier digest and deletion timestamps are retained to prevent old sessions from reopening a deleted account. Unconfirmed expired deletion challenges are eligible for removal after approximately 24 hours through scheduled cleanup. Minimal rate-limit information expires according to the relevant security limits and is cleaned up by application routines.

Provider logs, email-delivery records and infrastructure backups may follow separate provider retention schedules or applicable legal requirements. Account deletion does not claim to erase those independent records immediately. Specific provider and backup retention periods vary; contact us for information about retention relevant to your request.

## 9. Security

Dhanora uses HTTPS, server-side authentication checks, account-scoped data access and protected session cookies. Administrative/provider credentials are kept on the server. These measures reduce risk but cannot guarantee absolute security. Protect your email account and device, use device locking, and do not share passwords or verification codes. Contact the privacy contact if you suspect unauthorized access.

## 10. Children

Dhanora is intended for adults managing financial records and is not directed to children under 18. Do not create an account for a child or upload unnecessary information about children. Contact the privacy contact if you believe children's information has been provided improperly so the request can be reviewed.

## 11. Privacy requests and policy changes

Contact **[kirannew40@gmail.com](mailto:kirannew40@gmail.com)** with the subject “Dhanora Privacy Request” for questions, access/correction/deletion requests or concerns. Include only the information needed to locate the issue; do not send OTPs, passwords or complete sensitive documents. We may verify your identity and authority before acting, and will handle requests in accordance with applicable law.

We will update this policy when material practices change and revise its effective/updated date. Significant changes will be communicated through an appropriate in-app or account channel where required.
