HissabOne

Privacy Policy

Effective date
23 September 2026
Last updated
23 September 2026
Version
2026-09-23

This Privacy Policy explains what personal information HissabOne ("HissabOne", "we", "us") collects when you use the HissabOne website and application (the "Service"), why we collect it, who we share it with, and the choices and rights you have.

This policy describes our actual practices as implemented in the Service. It is not a claim of certification, approval or blanket compliance with every privacy law in every country. Section 13 explains which regional privacy laws we have assessed and how they apply to HissabOne today.

1. Who we are and how to contact us

HissabOne is currently operated on an individual basis and is not, as of the date above, registered as a separate company or other legal entity. This section will be updated with a registered business name and address if and when HissabOne is incorporated.

For any question about this policy, or to exercise a privacy right described below, contact us at support@hissabone.com or call +91 70302 42527. This mailbox and number are monitored by the person operating HissabOne.

2. Information we collect

We collect information in three ways: what you give us directly, what is created automatically as you use the Service, and what a third-party sign-in provider shares with us if you use it.

Information you provide directly

Depending on what you use, this can include:

  • Account and profile: full name, email address, mobile number, date of birth, postal address (address line 1/2, village, city, taluka, district, state, pincode, country), password (stored as a salted hash, never in plain text), and an optional profile picture.
  • Financial records you enter: ledger entries, account balances, categories, budgets, goals, recurring entries, calculator inputs, and similar records for the Personal, Business, Farm, Group and Investment Group workspaces you set up.
  • Contacts: names, and optionally an email/mobile number, of people you record money given to or taken from, or invite to a group — provided by you, about someone else.
  • Documents: files you upload to the Document Vault or attach as group receipts or investment evidence.
  • Support requests: anything you write in a support ticket, including the category you choose (for example "Data export" or "Account deletion").
  • Payment details you enter with Razorpay directly (see section 5) — HissabOne itself never receives or stores your card, UPI or bank account details.

Information created automatically

Account activity such as last-login time, and records the Service creates as a result of your actions — for example a payment order, a subscription record, or a notification.

Basic technical information any web request carries (such as IP address, as seen by our hosting providers) is not separately logged or profiled by HissabOne's own code as of this policy's effective date.

3. Why we collect and use this information

We use personal information for the following purposes:

  • To create and secure your account, sign you in, and let you reset a forgotten password.
  • To provide the Service itself: storing and showing you the financial records, documents, reports and calculations you create.
  • To operate shared features you choose to use: showing a group's members their shared expenses, or mirroring a lending/borrowing ledger to a contact who accepts your connection request.
  • To process subscription payments through Razorpay, apply the plan you purchased, and send you payment-related notices.
  • To send account, security, and service emails and SMS (verification codes, password resets, payment confirmations, reminders you set up) through our email and SMS providers.
  • To respond to support requests, including requests to export or delete your data.
  • To enforce our Terms and Conditions, and to detect and prevent fraud, abuse or unauthorised access.

4. Required versus optional information

Full name, email and password are required to create any account. Mobile number, date of birth and full postal address are also required by our current registration form; without them, registration cannot be completed. Address line 2, city and the profile picture are optional — leaving them blank does not prevent registration or affect how the Service works for you.

Within a workspace, the financial records, documents and contacts you enter are entirely your choice — the Service works with only the records you actually create.

5. Who your information is shared with

We do not sell personal information, and we do not use it for third-party advertising. Information is shared only in the following circumstances.

Service providers who process data on our behalf

Each of the following only receives the information needed to perform its function for us, under our instructions:

  • Razorpay (payment processing, India) — receives what is needed to process a subscription payment. Razorpay is currently used for INR (Indian Rupee) payments only.
  • MongoDB Atlas (database hosting) — stores the Service's data.
  • Render (application hosting) — runs the backend application.
  • Vercel (application hosting) — serves the frontend application.
  • Cloudflare R2 (file storage) — stores uploaded documents, receipts and exported data files in a private, non-public storage bucket.
  • Brevo (transactional email) — sends account, security and notification emails on our behalf. We do not send bulk or marketing email.
  • Twilio (SMS) — sends verification codes and, for the Document Vault, one-time unlock codes.

Other people you choose to share with

A group's members can see that group's shared expenses, splits, settlements and any receipts attached to them, within the group.

If a contact accepts a connection you send them, they see a read-only mirror of the lending/borrowing ledger between you — never edit access, and never any other workspace of yours.

A person you invite to an Investment Group sees the investment records that group's permission level allows them to see.

Legal and safety

We may disclose information if required by law, legal process, or to protect the rights, safety or property of HissabOne, our users or others.

6. The help assistant and automated processing

HissabOne's in-app help assistant is a locally built, rule-based feature. It answers using a fixed set of help content plus your own already-stored data (for example, your recent transactions or upcoming payments), read through the same API the rest of the app uses. As of this policy's effective date, the assistant does not call any third-party AI or language-model provider, and no personal information is sent to an external AI service for this feature.

HissabOne does not use personal information for automated decision-making that produces legal or similarly significant effects on you (for example, automatically approving or denying you a loan or service) without human involvement.

7. Cookies, analytics and browser storage

HissabOne does not set cookies, and does not use any analytics, advertising or tracking scripts (no Google Analytics, advertising pixels, or similar tools) as of this policy's effective date.

Signing in stores your session token in your browser's sessionStorage, not a cookie — it is cleared automatically when you close your browser. We also use your browser's localStorage for a small number of non-sensitive preferences: your chosen display language, which workspace you last had open, a few interface show/hide toggles, and which in-app notices you have dismissed. None of this is financial data, and none of it is sent to us automatically — it stays on your device.

8. How long we keep information

We keep your account and workspace information for as long as your account is active, so the Service continues to work as expected.

Account deletion is currently handled through a support request (see section 10). Once a deletion is scheduled, there is a 14-day window (configurable by us) in which it can still be cancelled; after that, associated workspace data — accounts, transactions, contacts, categories, goals, budgets and documents you own — is deleted, and your account record is removed. Some references inside other people's records that only involve your identifier are cleared or detached rather than deleted outright, so their own records stay intact.

Exported data download links expire 7 days after they are created.

Some information — particularly billing and payment records — may be kept for longer than the rest of your account where we are required to for tax, accounting or legal recordkeeping purposes, even after an account is otherwise deleted.

Routine backups of our database and file storage may retain copies of deleted information for a limited operational period after deletion, until those backups themselves are cycled out in the normal course of our providers' backup schedules.

9. Security

Passwords are stored as salted bcrypt hashes, never in plain text. Session tokens are signed and expire; they are never stored in a cookie. Uploaded documents are stored in a private Cloudflare R2 bucket with no public access. Sign-in is protected by a JSON Web Token issued only after a successful login, and sensitive account actions require re-authentication.

No method of storing or transmitting information is completely secure, and we cannot guarantee absolute security. We do not make, and this policy should not be read as, a guarantee against every possible security incident.

10. Where your information is processed

HissabOne's hosting providers are Render (application backend), Vercel (application frontend), MongoDB Atlas (database) and Cloudflare (file storage). These are all established international cloud providers; the specific data-centre region each is configured to use is an operational setting in each provider's dashboard rather than something fixed in our application code, and is not separately published here as of this policy's effective date. If you are located outside the country where a given provider processes data, your information may be processed in a different country than the one you are in.

We have not independently verified, and do not claim, that any particular cross-border transfer safeguard (such as Standard Contractual Clauses, an adequacy decision, or a specific transfer framework) is in place with a given provider beyond that provider's own standard terms. If this matters to you — for example because you are in the EEA, UK or another jurisdiction with transfer restrictions — please contact us before relying on the Service, and see section 13 for the regional assessment we have done so far.

11. Your rights and how to exercise them

Subject to the law that applies to you (see section 13 for jurisdiction-specific detail), you generally have the right to know what personal information we hold about you, to correct it, to ask us to delete it, and to ask questions about how it is used.

You can update most of your own profile information directly from Settings inside the app. To request a copy of your data, or to request deletion of your account, contact support@hissabone.com or raise a support ticket in-app under the "Data export" or "Account deletion" category — these are the mechanisms currently implemented for these requests; both are reviewed and actioned by us, rather than fully automatic and instant.

To protect your account, we will ask you to confirm your identity (for example, by verifying you can access the email or mobile number on the account) before acting on a request — we do not ask for government ID or other unnecessary identity documents to do this.

12. Children's privacy

HissabOne is a financial record-keeping application and is not directed at children. Our registration form asks for a date of birth but, as of this policy's effective date, does not technically block a date of birth that would indicate the person is a minor — this is a known gap we are tracking, not a claim that no minor could register.

Some features (for example, a savings goal you label "Education" or "Child's college fund") may let you record information that relates to a child as part of your own financial planning; this does not create a separate account or profile for that child, and we do not knowingly collect personal information directly from a child.

If you believe a child has provided us with personal information directly, contact support@hissabone.com and we will investigate and remove it as appropriate.

13. Changes to this policy

If we make a material change to how we collect or use personal information, we will update the "Last updated" date above and, where practical, post a notice in the app or email registered users ahead of the change taking effect. Continuing to use the Service after a change takes effect means you accept the updated policy; if you do not agree, you should stop using the Service and may request account deletion as described in section 11.

14. Regional privacy law supplement

This section explains, region by region, whether and how a particular privacy law currently applies to HissabOne. It is based on our actual operations (an individually operated service, primarily used in India, with some international sign-ups possible) and on our understanding of each law at the time of writing — it is not legal advice, and we recommend qualified legal review before treating any of it as a compliance guarantee.

India

HissabOne is operated in India and most of our users are in India, so Indian law is our primary reference point. India's Digital Personal Data Protection Act, 2023 ("DPDPA") has been enacted, and the Digital Personal Data Protection Rules, 2025 were notified on 14 November 2025, which also established the Data Protection Board of India. Based on the phased commencement schedule published alongside that notification, only the Board-related provisions were in force as of this policy's effective date; Consent Manager registration is scheduled to open around 13 November 2026, and the Act's core data-fiduciary obligations — the specific notice and consent requirements, security-safeguard and breach-intimation duties, and the associated penalties — are scheduled to take effect around 13 May 2027.

We have not treated the DPDPA's full data-fiduciary obligations as already legally binding on us before their scheduled commencement date, and we do not claim DPDPA compliance as a completed, certified status. In the meantime, and consistent with the DPDPA's general direction, we process personal information based on your consent (given by registering and using the Service) or as necessary to provide the Service you asked for, we let you access and correct your profile information directly in the app, and we handle deletion and other requests through the support channel described in section 11. We will update this section as the Act's remaining provisions come into force and as we complete a fuller compliance review ahead of that date.

HissabOne does not currently have a formally designated "Grievance Officer" or "Consent Manager" in the sense the DPDPA framework describes; support@hissabone.com is, for now, the single contact point for any such request. We have not registered with, or been assigned any statutory registration by, any Indian data protection authority.

European Economic Area and United Kingdom

We have not confirmed that HissabOne currently has users based in the EEA or UK, or that it is specifically marketed there. If you are in the EEA or UK and use HissabOne, the GDPR or UK GDPR may apply to our processing of your information; we have not conducted a full Article-by-Article GDPR assessment, appointed an EU/UK representative, or appointed a Data Protection Officer, because we have not established that those obligations are triggered for a service of HissabOne's current size and footprint. If you are an EEA/UK user, please contact support@hissabone.com so we can assess this properly, and be aware that, until that assessment is complete, we cannot confirm a lawful basis mapping, your right to lodge a complaint with a specific supervisory authority, or that appropriate cross-border transfer safeguards are documented for your data.

California and other US states

We have not assessed HissabOne against the CCPA/CPRA's statutory thresholds (which depend on factors like revenue and the volume of California residents' data processed) and do not currently claim CCPA/CPRA compliance either way. We do not sell personal information and do not use tracking that we are aware would count as a "sale" or "sharing" of personal information under these laws, but we have not implemented a Global Privacy Control response or a dedicated "Do Not Sell/Share" mechanism, because we have not established that we are a business these laws currently cover. If you are a California (or other US state) resident and want to raise a privacy request, contact support@hissabone.com and we will handle it consistently with the rights described in section 11 while we complete a fuller assessment.

Other countries

We have not assessed HissabOne against the privacy laws of Canada, Brazil, Australia or other countries beyond India, the EEA/UK and the US states discussed above. The Service being reachable from a given country does not by itself mean we have determined that country's law applies to us, or that we meet it. If you are located elsewhere and have a privacy question or request, contact support@hissabone.com.