Privacy Policy
Last updated: 13 November 2026
The short version
- We collect what we need to run your account, bill you, keep the platform secure and meet the law.
- Details you send for a check are passed only to the source needed for that check. We do not store them, or the result, in our database once the result is returned to you.
- We do not sell personal data, show advertising, or use tracking or advertising cookies.
- Our servers are in Mumbai, India.
- You can ask to see, correct or erase your data, and complain to our Grievance Officer at support@grappi.ai.
1. Who this policy covers
This policy explains how Grappi (“Grappi”, “we”, “us”) handles personal data when you visit grappi.ai, use the dashboard, or call the Grappi APIs. It is written to meet the Digital Personal Data Protection Act, 2023 (“DPDP Act”), the rules made under it, and the Information Technology Act, 2000.
It covers three groups of people: customers (the businesses that hold a Grappi account and the people who use it), visitors to our website, and end customers (the individuals whose details our customers send to the APIs for a check).
2. Our role for each kind of data
- Your account data. For the details you give us about yourself and your organisation, Grappi is the data fiduciary: we decide why and how it is used, as set out in this policy.
- End-customer data. For the details a customer sends to an API about its own customers, the customer is the data fiduciary and Grappi is its data processor. We process that data only on the customer’s instructions, to carry out the check it asked for.
3. What we collect
Data you give us
- Account details: your name, work email address, phone number, organisation name and password. We store the password only as a salted one-way hash (scrypt); no one at Grappi can read it.
- Sign-in with Google or GitHub: if you choose it, the provider shares your name, email address and account identifier with us. We do not receive your password for that provider.
- Two-step sign-in: the secret for your authenticator app and your recovery codes, stored in protected form.
- Business and billing details: GSTIN, billing address and any documents you send to verify your business.
- API subscriptions: what you intend to use an API for and the volume you expect.
- Messages: what you write to us by email or through the website.
Data we collect when you use the Services
- Sign-in sessions: the IP address and browser of each sign-in, and when the session was last active.
- Usage records: for each call, which API was called, when, its request ID, whether it succeeded, how long it took and what it was charged. These records do not contain the details you sent for the check or the result.
- Wallet and payments: your balance, top-ups, charges and refunds, and the payment reference from the payment gateway. Card, UPI and net-banking details are entered on the payment gateway’s page; we never receive or store them.
- Security records: an audit log of security-relevant actions, such as sign-ins, API key changes, API activations and refused calls.
Data customers send us about end customers
The details needed for each check, for example a name, date of birth, PAN, bank account number and IFSC, GSTIN, vehicle registration number, or a document image. See section 5 for how we handle it.
4. Why we use it
- To provide the Services: create and run your account, carry out checks, activate APIs, and give support.
- To bill you: charge calls to your wallet, process top-ups and refunds, and issue tax invoices.
- To keep the platform secure: verify sign-ins, detect fraud, misuse and attacks, enforce rate limits, and investigate incidents.
- To meet our legal duties: tax, accounting, record-keeping, and requests from courts, regulators and law enforcement that the law obliges us to answer.
- To tell you things you need to know: one-time codes, billing notices, security alerts, changes to the Services or these policies, and replies to your questions.
We process your data either because you have given it to us for these purposes or consented to it, or for a legitimate use the DPDP Act allows, such as meeting a legal obligation. We do not sell personal data, do not use it for advertising, and do not send marketing email without your consent. You can withdraw consent at any time; this does not affect processing already done, and we may then be unable to provide some of the Services.
5. Data you send for a check
- We use the details you send only to carry out the check you asked for, and send to the data source only what that check needs.
- Once the result is returned to you, we do not keep the details you sent or the result in our database. Our usage record of the call holds no end-customer details.
- Some products must hold data to work, for example a consent record, a statement request, or the encrypted credentials for an account you connect. That data is encrypted where sensitive, kept separate for each customer, and deleted or anonymised at the end of its data-life (365 days by default) or earlier when the customer asks.
- We do not use end-customer data to build profiles, to train models, for marketing, or for any purpose of our own.
6. Cookies and similar technology
The website uses only the cookies it needs to work:
- Sign-in cookie: keeps you signed in to the dashboard. It cannot be read by scripts on the page and is sent only over HTTPS.
- Security cookie (
grappi_csrf): protects your account against forged requests from other websites.
We do not use analytics, advertising or tracking cookies, and we do not allow third parties to track you on our website. When you pay, the payment gateway’s page may set its own cookies under its own policy. Blocking our cookies will stop you signing in to the dashboard.
7. Who we share data with
We share personal data only with the following, and only what each needs for its job:
- Data sources: the official registries, government systems, regulated institutions and licensed data providers that carry out each check receive the details needed for that check.
- Hosting: the cloud provider whose servers in Mumbai, India run the Services.
- Payments: our payment gateway, Razorpay, processes wallet top-ups and refunds.
- Email and accounting: Zoho, for sending service email (such as one-time codes and billing notices) and for invoicing and accounts.
- SMS: an SMS delivery provider sends one-time codes to your phone.
- Sign-in providers: Google or GitHub, only if you choose to sign in with them.
- Professional advisers: lawyers, auditors and accountants, under a duty of confidentiality.
- Authorities: courts, regulators, tax authorities and law enforcement, when the law requires it or to protect the rights, property or safety of Grappi, our customers or others.
- A buyer or successor: if Grappi is merged, acquired or sells its business, subject to this policy.
Every service provider that processes personal data for us is bound by contract or its own terms to protect it and use it only to provide its service.
8. Where data is stored
The servers that run the Services and hold our database are in Mumbai, India. Some service providers, such as the sign-in providers, may process limited data outside India. Any transfer outside India follows section 16 of the DPDP Act and any restrictions the Government of India notifies under it.
9. How long we keep data
We keep personal data only as long as we need it for the purposes in this policy or as the law requires, and then delete or anonymise it. An automated job removes data whose data-life has ended.
| Data | How long we keep it |
|---|---|
| Account and organisation details | While your account is open. Deleted or anonymised after it closes, except what the law requires us to keep. |
| Wallet top-ups, charges, refunds and tax invoices | At least eight years, as company, tax and GST law require. |
| Usage records (which API, when, request ID, success, response time, charge) | While your account is open, then with the billing records above. |
| Sign-in sessions (IP address, browser) | A session ends at most 7 days after sign-in, or after 8 hours without activity. Session records are kept for security review. |
| One-time codes for email, phone and password reset | Stored only as a one-way hash and valid for minutes. |
| Details sent for a check, and the result | Not stored in our database once the result is returned to you. |
| Consent records, statement requests and connected-account data a product holds for you | Until the end of their data-life (365 days by default) or an earlier erasure request, then deleted or anonymised. |
| Security audit log | Kept as an append-only record for security and compliance. It holds no end-customer details. |
| Technical server logs | Size-capped and overwritten automatically. |
| Emails to support | As long as needed to resolve your request and handle any follow-up or dispute. |
10. How we protect data
We protect personal data with reasonable security practices, including:
- encryption in transit (HTTPS/TLS) for the website and every API call;
- AES-256-GCM encryption at rest for sensitive fields, with a separate key for each record, itself protected by a master key held outside the database;
- row-level separation in the database, so one customer’s data cannot be read with another customer’s access;
- passwords stored only as salted scrypt hashes, and one-time codes and recovery codes stored only as hashes;
- two-step sign-in, session time limits, and protection against forged requests;
- API keys that can be revoked at any time, per-key rate limits, and per-API activation;
- least-privilege access for our own staff and systems, and an append-only audit log.
No system is perfectly secure. Keep your password and API keys safe, and tell us at once at support@grappi.ai if you think they have been exposed or if you find a security weakness. More detail is on our Security page.
11. If something goes wrong
If a personal data breach occurs, we will contain it, investigate it, and notify the Data Protection Board of India, CERT-In and the people affected, in the form and within the time the law requires. Where the breach concerns data we process for a customer, we will tell the customer without undue delay so it can meet its own duties.
12. Your rights
Under the DPDP Act you have the right to:
- Access: get a summary of the personal data we hold about you and how we process it, and the names of those we have shared it with;
- Correction: have inaccurate or incomplete data corrected, completed or updated;
- Erasure: have your data erased when it is no longer needed, unless the law requires us to keep it;
- Withdraw consent: withdraw any consent you gave, as easily as you gave it;
- Grievance redressal: complain to us and have your complaint answered;
- Nominate: name a person to exercise these rights for you in the event of your death or incapacity.
To exercise a right, write to support@grappi.ai from the email address on your account. We may ask you to confirm your identity before acting. Much of your account data can also be viewed and changed directly in the dashboard. We will not charge you for a reasonable request.
13. If you are an end customer
If a business checked your details through Grappi, that business decided to run the check and is responsible for it. Please send requests to see, correct or erase your data to that business first. If you write to us, we will tell you which of our customers sent the request where we can identify it, and help that customer answer you. We do not keep the details sent for a check, or its result, after the result is returned, so in most cases we hold no record of them.
14. Children
Grappi accounts are only for people aged 18 or over acting for a business. We do not knowingly collect data about children for our own purposes. A customer that sends a child’s details for a check must first obtain verifiable consent from the child’s parent or lawful guardian, as section 9 of the DPDP Act requires.
15. Grievance officer
Grievance Officer, Grappi: support@grappi.ai. We acknowledge a grievance within 72 hours and aim to resolve it within 15 days. If you are not satisfied with our answer, you may complain to the Data Protection Board of India.
16. Changes to this policy
We may update this policy as the Services or the law change. We will tell customers about material changes by email or a notice in the dashboard before they take effect. The date at the top of this page shows when the policy last changed. See also our Terms of Service.
17. Contact
Questions about this policy or your data: support@grappi.ai. See Contact for all our contacts.