ComplyNextHome

Legal

Privacy Policy

Last updated: October 2026

1. What we collect

  • Account data: your name, institutional email address and a bcrypt-hashed password. We never store plain-text passwords.
  • Company profile: the name of your NBFC or co-operative bank and basic profile details you provide.
  • Loan accounts: the portfolio records you upload (account IDs, borrower names, days-past-due, outstanding amounts and existing classifications) for NPA staging analysis.
  • Policy documents: the internal policy files (.txt/.pdf) you upload for gap detection, and the analysis findings generated from them.
  • Audit trail: a timestamped log of actions taken in your workspace (classifications, analyses, scrapes) so every decision stays traceable.

2. How we use it

  • Solely to operate the ComplyNext service for your institution: authentication, compliance analysis, monitoring and reporting.
  • We do not sell your data. We do not share it with advertisers or unrelated third parties.
  • Policy text you submit for gap analysis is processed by our language-model inference provider to produce the analysis; it is not used for advertising.

3. Data isolation

  • ComplyNext is multi-tenant. Every record belongs to exactly one company, and every request is scoped to the company in your signed-in session. One institution cannot see another institution's loan books, policies or audit logs.
  • RBI circulars in the shared regulatory corpus are public documents, not personal data, and are the same for every user.

4. Cookies and local storage

  • We store a signed authentication token in your browser's local storage to keep you signed in. We do not use third-party tracking cookies.
  • Clearing your browser storage signs you out; nothing else about the service changes.

5. Data retention and deletion

  • Your workspace data is kept while your account is active. You can delete loan accounts and policy documents from inside the app at any time.
  • To request complete deletion of your account and company data, write to us at the contact below and we will remove it.

6. Security

  • Passwords are hashed with bcrypt. API access requires a signed token on every request. That said, no internet service can promise perfect security, so avoid uploading anything you would not want processed by a cloud service.

7. Changes to this policy

  • If this policy changes materially, we will update the date below and highlight the change in the app.

8. Contact

  • For privacy questions or deletion requests: nevinbali10@gmail.com.