Privacy policy
Last updated 21 November 2026
1. Who we are
WiseNutss Accounts is provided by WiseNutssX FZE LLC, Ajman, United Arab Emirates ("we", "us"). This policy explains how we handle personal data when you visit this website or use the application, in line with India's Digital Personal Data Protection Act, 2023 and the Digital Personal Data Protection Rules, 2025.
2. Your data and your clients' data
We handle personal data in two different roles:
- Your account. For the details you give us to sign up and use the service, such as your name, email and sign-in settings, we decide how the data is used. We are the data fiduciary.
- The books you keep. Bank statements, invoices, customer and supplier details, employee expense claims and similar records belong to the business whose books they are. That business (or the CA practice acting for it) decides what goes in and why; we process it only to provide the service, on its instructions. For this data the business is the data fiduciary and we act as its data processor.
If you are a customer, supplier or employee of a business that uses WiseNutss Accounts and want to ask about your data, please contact that business first. We will help them answer you.
3. What we collect
- Account details: name, email address, a password stored only in hashed form by our sign-in provider, two-step sign-in settings, and your role in each company or practice.
- Company details: legal name, type of entity, PAN, GSTIN, CIN, address and plan.
- Books content you add: bank statement lines, invoices and bills, parties with their PAN, GSTIN and contact details, journals, fixed assets, expense claims, and documents you upload.
- Personal tax computations, if an owner uses that module: income, deductions and capital gains they enter.
- Technical and security data: sign-in times, the device and browser used, IP address, and the actions recorded in each company's audit log.
- Messages and feedback you send us, and records of plan payments.
When you create an account you are shown this notice and asked to agree to it; we record which version you agreed to and when. If the notice changes in substance you will be asked again.
We do not collect your net banking credentials. Statement PDF passwords are used once to open the file and are not stored.
4. Why we use it
- To provide the service: keep your books, produce returns, files and statements, and let the people you invite work with you.
- To keep accounts and books secure: sign-in checks, two-step sign-in, access control, audit logs and fraud prevention.
- To support you and to improve the product from the feedback you send.
- To bill for plans and keep the records the law requires.
We do not sell personal data, use it for advertising, or share it with anyone for their own marketing.
5. AI document reading
AI reading of bills and bank statement PDFs is off for every company until its owner turns it on. When it is on and you upload a document for reading, that document (or the text taken from it) is sent to the AI service listed below to be read into a draft. Nothing is posted until a person checks the draft. Turning the feature off stops any further documents being sent.
6. Who processes it for us
We use these service providers, each bound to process data only to provide their service to us:
- Supabase: database, sign-in and file storage, in its Mumbai, India region.
- Vercel: application hosting, with the application running in Mumbai; pages and files may be delivered through its global network.
- Microsoft Azure OpenAI Service (and, during testing, Vercel AI Gateway): AI document reading, only for companies that turn it on.
- An email delivery provider for sign-in and notification emails, and Razorpay for payments, once these are connected.
We may also disclose data where the law requires it, for example to a tax authority or court with a valid order.
7. Where it is stored
Books, documents and backups are stored in Mumbai, India. Some processing can take place outside India, for example when pages are delivered through a global network or when AI reading is turned on and the AI service processes a document elsewhere. Where this happens we rely on providers with contractual and security commitments, and on the transfer rules under Indian law.
8. How we protect it
- Entries are final. A posted entry cannot be edited or deleted; a correction is a reversal with its own entry number.
- Every entry is chained. Each entry carries a fingerprint of its lines and of the entry before it, so a change made outside the application shows up when the chain is checked.
- Access is checked by the database. Every read and write is checked against your role in that company by the database itself, not only by the screens. Modules a company has not switched on are refused there too.
- Two-step sign-in with an authenticator app, required for practice staff and platform administrators, and available to everyone else.
- Roles and approvals: owner, admin, accountant, CA and viewer roles; a second person approves custom rules and, if chosen, journals; periods can be locked after filing.
- Audit log: rule approvals, licence and module changes, period locks, cancellations, exports and sign-in resets are recorded, including actions by our own support staff.
- Encryption: every connection is encrypted in transit, and the database, file storage and backups are encrypted at rest (AES-256). Personal tax computations are additionally encrypted by the application with a key held outside the database, so database access alone cannot read them.
- Activity logs: sign-ins, failed sign-ins, two-step checks, which companies each person opened (once a day) and downloads of books are logged and kept for 13 months. Company owners can see who opened their books.
- No anonymous access: nothing in the application's data interface can be called without signing in.
If a personal data breach occurs, we will inform the people affected without delay, through a notice in the application and by email, and report it to the Data Protection Board of India within 72 hours as the DPDP Rules require. We will also inform the businesses whose books are affected so they can meet their own duties.
9. How long we keep it
Activity logs are kept for 13 months and then deleted automatically. We keep account and books data while your account or the company is active. Businesses must keep their books of account for the periods set by law, so we do not delete books on our own while a plan is active. When a company owner asks us to close a company, we delete its data after giving the owner time to download a full copy, except records we must keep by law. [Exact retention periods to be confirmed.]
10. Your rights
Under the Digital Personal Data Protection Act, 2023 you can ask us to:
- tell you what personal data of yours we process and who we have shared it with;
- correct, complete, update or erase it, where the law allows;
- withdraw consent you have given, which stops further processing based on that consent;
- handle a grievance about how we have processed your data;
- nominate someone to exercise these rights if you die or become unable to.
The quickest way is your account page: signed in, open Your account → Your data and privacy to download your personal data, send a request (access, correction, erasure, withdrawal of consent or a grievance), follow its progress, and name a nominee. Withdrawing consent closes your account; books you kept for a business stay with that business. You can also write to our Grievance Officer at rk@wisenutssx.com [name to be confirmed]. If you are not satisfied with our answer, you can complain to the Data Protection Board of India.
The service is meant for businesses and their advisers. It is not intended for anyone under 18.
11. Cookies
We use only the cookies needed for the service to work: keeping you signed in and remembering whether you are working in a company's live books or its sandbox. We do not use advertising or tracking cookies.
12. Changes and contact
We will post changes here and, for significant ones, tell signed-in users in the application. Questions: rk@wisenutssx.com. See also our terms of use.