This policy explains what Patrata does with information about merchants, and about the customers a merchant records. It is written to be read, not skipped. If anything is unclear, write to info@credsetu.in and we will explain it in plain language, in Marathi if you prefer.
1. Who we are
Patrata is a mobile application operated by CredSetu Technologies Private Limited (“Patrata”, “we”, “us”, “our”), a company incorporated under the Companies Act 2013, CIN U62090ME2026PTC475450, registered office C/o Renuka Khot, 143/8, Hirdao Road, Lonar, Buldhana – 443302, Maharashtra.
Patrata is the name of the product. CredSetu Technologies Private Limited is the company that operates it. Where this policy says “we”, it means that company.
2. Who is responsible for your information
Patrata involves two kinds of people, and responsibility is split between us and the merchant. This is the most important thing to understand in this policy.
| Information and activity | Who is legally responsible |
|---|---|
| A merchant’s record of his own customer — name, phone number, credit given, repayments | The merchant. It is his business record about his own customer, from a relationship that exists outside our app. Patrata holds and processes it on his instructions, as his Data Processor, under a written agreement — the Data Processing Agreement. |
| Payment reminders sent to that customer | Patrata. We send the reminder ourselves, on WhatsApp, on the permission you gave that shop. See Section 8. |
| Trust Score, Trust Band, cross-shop checks, payment timing alerts | Patrata. Here we decide the purpose and the method. These features run only where the customer has consented directly to us. |
| Identity verification of customers (DigiLocker) and GST verification of merchants | Patrata. We decide what is checked and why, and carry out the check through our verification provider. See Section 3.1 and Section 4.1. |
| A merchant’s import of his old book (Patrata Switch) | The merchant. It is his own business record, brought across on his instructions. See Section 3.4. |
| A merchant’s own account, billing, and Merchant Reliability Score | Patrata. |
3. Information we handle
3.1 About merchants
- Mobile phone number, used as the login identity.
- Name and, where given, business or shop name.
- Shop type, shop address and basic business details.
- Your UPI address, if you give one, so it can be printed on reminders for your customers to pay you.
- GST verification. When you sign up with your GSTIN, our verification provider DeepVue looks it up on the GST system. We keep the GSTIN, the registration details returned for it — legal and trade name, registered address, status — and the mobile number registered with GST, to which we send a one-time password to confirm the registration is yours.
- Subscription, payment and receipt records.
- A Merchant Reliability Score, calculated daily from how consistently the merchant’s records hold up — how often his entries are disputed, how they compare with other records, and whether any have been flagged as suspect.
3.2 About customers, recorded by a merchant
- Name and mobile phone number.
- Credit (udhaari) transaction records: amounts given on credit, dates, due dates, and whether an amount is paid, pending or partly paid.
- Repayment history and payment timing built from those transactions.
- Photos and files attached to a transaction: a photo of the bill added by the shop, and a payment proof (such as a UPI screenshot) added by the customer. Each is seen only by that shop and that customer.
- Whether the customer has confirmed or disputed each bill, when, and any note the shop added in reply to a dispute.
- The customer’s permission for WhatsApp messages from each shop: when it was given, where (on the consent slip, on the shop’s phone or in the Patrata app), and the exact wording and language shown.
- A record of the consent given: the exact text shown, the language, the version, and the time.
- Where the customer has consented: a Trust Score and Trust Band, and any voucher (community reference) or household links they choose to create.
- Where the customer has verified their identity: the details DigiLocker returns, the masked Aadhaar number and the date of the check. Never the full Aadhaar number — see Section 4.1.
Transaction records, repayment history and payment behaviour are financial information. We treat them as sensitive personal data under Rule 3 of the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules 2011.
3.3 Collected automatically
- A device identifier in the form of an anonymised code. We do not collect your device’s IMEI or hardware serial number.
- Basic app activity and technical log data — date and time of actions, app version, error logs — used to keep the service working and secure.
- Records of consents given or withdrawn, with the time and the version of the consent text shown.
3.4 When a merchant imports his old book (Patrata Switch)
A merchant moving from another bookkeeping app can upload the PDF customer report that app produces. It holds his customers’ names, phone numbers and outstanding balances. This feature is being introduced gradually and may not yet be available on every account.
- The file is checked for malware before anything opens it, and is read automatically on our own servers. No outside service reads it.
- The PDF is deleted straight away if the merchant cancels the import, and 30 days after he completes it. What remains is his list of customers and balances, as part of his own ledger.
- Imported customers are marked “not verified”. We do not message them, no repayment is recorded against them, and nothing about them reaches any Trust Score, until the customer has been added through the normal consent step and has confirmed the balance.
4. Information we do not collect, and identity verification
Patrata does not:
- read, upload or store your phone contacts list;
- read, upload or store your SMS messages or call logs;
- access your photos, media or files, except a photo or file you pick yourself, one at a time, through your phone’s own file picker — a bill photo, a payment proof, or an old-book report;
- track your precise GPS location;
- collect biometric data of any kind;
- collect bank account numbers, card numbers or UPI credentials;
- offer, arrange or disburse loans.
4.1 Aadhaar and identity verification
If you choose to verify your identity, you are sent to DigiLocker, the Government of India’s own service, and sign in there. You give DigiLocker permission to share your details with us; we never see your DigiLocker password and we never ask for an OTP. The exchange is carried out for us by DeepVue, our verification provider.
What comes back to us, and what we keep: your name, date of birth, gender, address, and the masked form of your Aadhaar number that DigiLocker returns — the last digits only. We also keep a one-way code derived from your DigiLocker account so the same person cannot be registered twice, and the date the check succeeded. We do not receive and do not store your full Aadhaar number. We do not keep your photograph or the underlying document.
The points below apply to this feature.
- You do not have to verify to be a Patrata customer. If you register yourself in the app, verification is part of signing up — it is how we confirm your name and date of birth, and how we make sure the same person is not registered twice. If you would rather not, your shopkeeper can add you to his ledger instead, and you are never asked for it. You keep the same rights either way, and no udhaar is refused because of it. Regulation 5(3) of the Aadhaar (Authentication and Offline Verification) Regulations 2021 and Section 8A(2)(c) of the Aadhaar Act require a viable alternative; being added by your shopkeeper is ours.
- Your consent is taken first, on a screen naming Patrata and saying what will be checked and why, before you are sent to DigiLocker. Regulation 6 and Section 8A(1)(a).
- Your full Aadhaar number is never collected, used or stored. Section 8A(3)(b) of the Aadhaar Act forbids it for any purpose. What we keep is set out above: the details DigiLocker returns, the masked number, and the date the check succeeded.
- No Virtual ID will be stored. Regulation 4A(4).
- You will never be subjected to Aadhaar authentication. We do not connect to UIDAI’s central database. Section 8A(3)(a).
- Verification servers will be in India. Regulation 22(1).
- Verification will be performed on our own account, never on anyone else’s, and no other entity will perform it on ours. Regulation 16A(2).
- You will be able to withdraw any permission to keep verified details, and we will delete them and confirm it. Regulations 16A(3) and 16A(4).
5. How information is used
| Purpose | What this means |
|---|---|
| Account and login | To create and secure merchant accounts and verify a login through a one-time password. |
| Credit ledger | To let a merchant record, view and manage the credit he has given to his own customers. |
| Payment reminders | To send you a reminder about an udhaar you owe that shop, on WhatsApp, from us, within the limits in Section 8. |
| Identity and GST verification | To confirm a customer’s name and date of birth through DigiLocker and stop the same person registering twice, and to confirm a merchant’s GST registration is his. See Section 4.1 and Section 3.1. |
| Bill confirmation | To let a customer confirm or dispute each bill a shop records, so that only bills the customer has had the chance to check count towards a Trust Score. See Section 9. |
| Trust Score | Where the customer has given permission, to calculate a Trust Score and Trust Band from repayments. See Section 9. |
| Showing a Trust Score to other shops | Only where the customer has separately turned on score sharing: a shop sees the score and band, nothing else, and every look is recorded. See Section 10.1. |
| Moving a merchant’s old book across | To read the customer report a merchant uploads from another app and add it to his ledger. See Section 3.4. |
| Payment timing alerts | Reserved — not active. When activated, to notify merchants who have live open credit with the same customer that a payment delay has been detected. Alerts will not reveal the shop, the amount or any other detail. We will obtain fresh consent before switching this on. |
| Merchant Reliability Score | To weigh how far a merchant’s records can be relied on when they feed a customer’s starting Trust Score. See Section 3.1. |
| Service quality and security | To keep the app reliable, fix errors, prevent misuse and fraud, and protect accounts. |
| Legal compliance | To meet our obligations under applicable law and respond to lawful requests. |
We do not use information collected for one of these purposes for a new, unrelated purpose without first asking for fresh consent.
6. Our legal basis
We rely on consent, and only on consent.
Today, Rule 5(1) of the SPDI Rules 2011 requires your consent in writing before we collect sensitive personal information, and Rule 5(5) limits us to using it for the purpose we collected it for. From 13 May 2027, Section 6 of the Digital Personal Data Protection Act 2023 requires consent that is free, specific, informed, unconditional and unambiguous, given by a clear affirmative action, and limited to the data necessary for the stated purpose. We have built to the 2027 standard from the start.
Indian data protection law gives a private company no “legitimate interest” basis and no “contract performance” basis. The “certain legitimate uses” in Section 7 of the DPDP Act are a closed list — State functions, medical emergencies, employment, and similar — and none of them covers recording a customer’s credit, calculating a behavioural score, or sharing one between shops. So consent is the ground for everything in this policy, apart from the limited retention the law itself requires.
Consent is asked for before information is collected, and separately for separate activities, so you can agree to some things and not others. Refusing one consent never costs you access to something unrelated.
7. Consent and your choices
| Activity | Who gives consent | How, and can it be withdrawn |
|---|---|---|
| Recording a customer in a merchant’s ledger | The customer, to the merchant | Using the consent step in the app, before the record is created. Withdrawable at any time — the record stops being processed, though money owed is not extinguished. |
| Receiving payment reminders | The customer, to the merchant | A separate permission, given per shop: on the printed consent slip, or on the shop’s phone when the shop adds you and confirmed with the one-time password sent to you, or by turning it on for that shop in the Patrata app. Every reminder carries a one-tap stop; using it ends reminders from every Patrata shop at once and no shopkeeper can undo it. |
| Identity verification (DigiLocker) | The customer, to Patrata | On a consent screen naming Patrata, before DigiLocker opens. Withdrawable as set out in Section 4.1. |
| GST verification | The merchant, to Patrata | By entering his GSTIN and confirming the one-time password sent to the GST-registered mobile number. |
| Trust Score generation | The customer, to Patrata | A switch shown when the customer signs up in the app. A customer added only by a shop has no Trust Score. To stop the score being calculated, write to us as set out in Section 14; we then delete the stored score. |
| Showing a Trust Score to other shops | The customer, to Patrata | Covered by the same sign-up switch. It can be turned off on its own, at any time, in the app’s Settings; from then on no shop can see the score. |
| Payment timing alerts | The customer, to Patrata | Not collected, because the feature is not active. Consent will be sought when it is switched on. |
| Voucher and household links | Each linked person, individually | Active in-app acceptance by each person from their own account. A notification is not consent. |
Withdrawing consent stops the related processing going forward. It does not undo what has already happened. We keep a record of consents given and withdrawn, including the exact text and version shown, as evidence that permission existed.
8. Messages sent to customers
Patrata sends payment reminders to you directly, on WhatsApp. Earlier versions of this policy said the shopkeeper sent them himself. That is no longer how it works, and this section has been rewritten to describe what the system actually does.
Because we are the sender, stopping the messages rests with us and not with your shopkeeper. Here is exactly what we do and what you can hold us to:
- We message you only if you agreed, shop by shop. Permission is taken on the printed consent slip, or on the shop’s phone when the shop adds you (you confirm it with the one-time password we send you), or when you turn it on for a shop in the Patrata app. It is recorded with the date, the exact wording you were shown, and the language it was shown in. The app lets you turn messages on; stopping them is done with the STOP button described below. Agreeing that one shop may remind you does not let any other shop message you — each is a separate permission, and so is each channel.
- How many messages, and when. At most eight for a single udhaar: three before the due date and five after, the last at thirty days. After that we stop permanently and leave the matter to your shopkeeper. Messages go out only between 9 am and 7 pm, never on listed public holidays, and never more than once a day in total — if you owe three shops, you still hear from us once.
- What a reminder says. The shop, the amount outstanding, the due date, and the shop’s own UPI address so you can pay if you want to. It is about your transaction with that one shop. It never mentions another shop, another debt, or anything about your overall record, and it is never an advertisement.
- What we will not send. We do not message your family, your employer or your neighbours about your udhaar. We do not describe you as a defaulter or use threatening, shaming or abusive language — that vocabulary is blocked by the system before a message can go out, including in text a shopkeeper has typed.
- Stopping, in one tap. Every reminder carries a “Stop messages” button; replying STOP works too. It stops reminders from every Patrata shop, not only the one that messaged you, and no shopkeeper can undo it. You can also tell us at info@credsetu.in or on +91 79959 53111. Stopping messages does not cancel money you owe.
- If the amount is wrong. Tapping “Amount is wrong” stops the reminders for that udhaar straight away and freezes any effect it could have on your record, until it is sorted out. Tapping “I will pay” stops them for two days.
- Your shopkeeper can hold them back. He can pause reminders for you for up to a fortnight — if you have already spoken to him, or there is illness or a death in the family — and he can send one himself, within strict daily limits.
9. The Trust Score
When a shop first records you, we work out a starting position from what that shopkeeper tells us about dealing with you — how long, how often, how you have repaid before, and the usual size of the udhaar. It is a starting point in the absence of information, not a judgement about you.
After that the score is recalculated from your repayments: how promptly amounts are repaid, how consistently, how much is outstanding against your history, how many independent shops have recorded you, how long the record has run, how quickly new credit is taken, and how partial payments behave. It is adjusted for seasonal income, so settling after a harvest does not count against you. If you withdraw permission for us to calculate it, we stop and delete the stored score; your udhaar records stay, because they are the shop’s own accounts.
Which bills count. A bill a shop records counts towards your score only once you have had the chance to check it: when you confirm it, or seven days after it was shown to you in the Patrata app or sent to you on WhatsApp, if you have not disputed it. A bill you dispute does not count while your dispute stands; the shop can cancel the entry, or stand by it with a note you will see, and you can withdraw a dispute at any time. Balances a shop brings across from another app count only after you have confirmed them. Bills recorded before 17 October 2026, when confirmation began, count as recorded.
Who can see it. Only if you have turned on score sharing (see Section 7). While it is on, a shop using Patrata can see your score and band — including a shop that looks you up by your phone number before it records you. Every time a shop looks at your score we record which shop, when, and what it was shown. A shop never sees the amounts you owe elsewhere, or which shops you owe — only the score itself. Turn sharing off in Settings and no shop can see it.
10. Who we share information with
10.1 With other merchants — only a Trust Score, and only with your permission
A merchant sees only his own ledger. He never sees another merchant’s customers, amounts, prices or records.
The one thing that can cross between shops is a customer’s Trust Score and Trust Band, and only while that customer has score sharing turned on. Each look is recorded, and the customer can turn sharing off in Settings at any time. See Section 9.
10.2 With service providers who work for us
We use a small number of third-party providers to run the service. Each processes information only on our instructions, only to provide their service, and under a written agreement.
| What they do for us | What they see |
|---|---|
| Cloud hosting, storage and database (AWS, Mumbai) | Merchant and customer records, bill photos, payment proofs and imported book files, encrypted in transit and at rest |
| One-time passwords by SMS, and WhatsApp messages to customers (MSG91) | The mobile number of the merchant or customer being messaged, and what the message says — for a reminder, the shop’s name, the amount, the due date and the shop’s UPI address |
| Identity and GST verification (DeepVue) | For a merchant, the GSTIN he enters and the registration details returned for it. For a customer, the details DigiLocker shares with us — see Section 4.1 |
| Website DNS (Cloudflare) | Website domain resolution only. No ledger data. |
| Payment processing for subscriptions | Not currently used — we do not yet process subscription payments through an integrated payment gateway. |
| Error and performance monitoring (Sentry) | Technical logs |
This list reflects the providers actually in use. If that ever changes, we will update this table before the change takes effect.
10.3 We do not share with banks, NBFCs or lenders
Patrata does not share any personal information with banks, non-banking financial companies or any other lender. Patrata is not a lending app and does not pass data to lenders. If that ever changes we will tell you first, obtain fresh consent, and hold the licences the law requires.
10.4 Legal disclosures
We may disclose information where we are required to by law, by a court, or by a competent authority, or where it is necessary to prevent fraud or serious harm.
10.5 Business transfers
If the business is acquired or merged, data may transfer to the acquiring entity. We will tell you at least 30 days beforehand and you may delete your data before the transfer.
10.6 We do not sell your data
We do not sell personal information. We may publish statistics that are irreversibly anonymised, from which no individual can be identified. That is not personal information and is not covered by this policy.
11. How long we keep information
| Type of information | Retention |
|---|---|
| Merchant account information | While the account is active, then deleted or anonymised within 90 days of closure, unless the law requires longer. |
| Credit ledger and transaction records | Three years after the last transaction on that record, or until the merchant deletes it, whichever is earlier. |
| Records where money is still owed | Kept until the amount is settled or written off. We call this a lawful retention exception, not anonymisation — the record still identifies the person, and calling it anonymised would be untrue. |
| Bill photos and payment proofs | For as long as the transaction they are attached to is kept (the two rows above). |
| Imported book files (PDF) | Deleted straight away if the import is cancelled, and 30 days after it is completed. |
| Trust Score | While the customer’s permission to calculate it stands. Deleted when that permission is withdrawn. |
| Identity and GST verification results | With the account they belong to: deleted or anonymised within 90 days of the account closing, or sooner where a customer withdraws permission to keep them, as Section 4.1 describes — unless the law requires longer. |
| Consent records | Three years after consent is withdrawn or the account closes, as evidence that permission existed. |
| Consent and opt-out records for reminders | Three years, as evidence that permission existed and that opt-outs were honoured. |
| One-time passwords | Five minutes. |
| Server and security logs | The CERT-In Directions of 28 April 2022 require 180 days, within Indian jurisdiction. We are configuring this and will state the confirmed period here once it is done — see Section 12. Until then logs are kept only as long as running the service requires. |
12. How we protect information
These are the measures we apply today. We have deliberately not listed anything we cannot currently evidence.
- All traffic between the app, the website and our servers is encrypted in transit using TLS.
- Our production database and storage volumes are encrypted at rest.
- Credentials and API keys are held in a managed secret store, not in code or plaintext configuration files.
- Access controls, so only authorised people can reach personal information.
- One-time-password login for merchants, instead of stored passwords.
- Multi-factor authentication on administrative accounts.
- Logging and monitoring of access to personal information; application errors are captured centrally.
- Written confidentiality obligations for everyone with access, including contractors and interns.
No system can be guaranteed completely secure. Our internal standards are set out in our Information Security Policy, reviewed every six months.
13. If something goes wrong
If we suffer a security incident affecting personal data, we will:
- contain it and revoke any compromised credentials within one hour;
- notify CERT-In within six hours of noticing the incident, for the categories listed in Annexure I of the Directions of 28 April 2022. This duty applies regardless of how many people are affected — there is no minimum threshold;
- tell affected people what happened, what data was involved and what they should do, in plain language, without delay;
- from 13 May 2027, when Section 8(6) of the DPDP Act commences, also notify the Data Protection Board of India without delay and file the detailed report within 72 hours of becoming aware;
- publish an internal post-incident review within seven days.
We do not conceal incidents. Hiding a breach from affected people or from the authorities is a serious breach of Indian law and of our own standards.
14. Your rights, and how to use them
Merchants and customers both have these rights. Some are available as a button in the app; others we carry out by hand when you ask. Either way the time limit is the same, and it is our obligation, not a courtesy.
| Right | What it means | We respond within |
|---|---|---|
| Access | Ask what personal information is held about you, and who it has been shared with. | 15 days |
| Correction | Ask us to correct, complete or update information that is wrong. | 15 days |
| Erasure | Ask us to delete your personal information, subject to records the law requires us to keep and to any amount still owed. | 30 days |
| Withdraw consent | Including consent to scoring, sharing, reminders or verification. Withdrawing is as easy as giving it was. | Immediately |
| Pause sharing | Customers can turn off sharing of their Trust Score in the app’s Settings. | Immediately |
| Raise a dispute | Challenge a transaction record you believe is wrong. Related processing and score impact are paused while we investigate. | Paused on receipt; resolved in 30 days |
| Nominate | Name someone to exercise these rights for you if you die or become unable to act. | 15 days |
| Grievance | Complain about how your information has been handled, to our Grievance Officer. | Acknowledged in 48 hours, resolved within one month |
There is no charge for a reasonable request. To make one, write to info@credsetu.in or use the in-app option where one is available. If you are not satisfied with our answer you may complain to the Data Protection Board of India.
Where you ask us to delete your record, the merchant continues to see only his own outstanding amount as his own business record; your profile and any Trust Score are removed.
15. Children’s information
Patrata is for adults aged 18 and over. A customer who signs up in the app has their date of birth confirmed through DigiLocker, and sign-up is refused for anyone under 18. When a shop adds a customer the app does not ask their age, so the shop is responsible for not adding a minor. We do not knowingly create a Trust Score or an independent profile for anyone under 18 without verifiable consent from a parent or guardian, and we do not carry out behavioural monitoring or targeted advertising directed at children. Merchants must not record a minor as an independent credit customer. If you believe a child’s information has been recorded without proper consent, contact our Grievance Officer and we will remove it.
From 13 May 2027, Section 9 of the DPDP Act makes these obligations statutory, with a penalty of up to ₹200 crore for breach.
16. Where information is stored
We require personal data to be stored and processed in India. We are completing verification of our hosting configuration and will name the provider and the specific Indian region in this section once that is confirmed. We are not going to state a location we have not verified.
Two rules push in the same direction and we intend to comply with both: the CERT-In Directions of 28 April 2022 require ICT logs to be maintained within Indian jurisdiction, and Regulation 22(1) of the Aadhaar Regulations would require verification servers to be in Indian data centres if we ever enable that feature.
If any information is ever processed outside India, we will do so only to countries permitted under Indian law and with appropriate safeguards, and we will say so here first.
17. Which laws apply, and from when
This matters because the Digital Personal Data Protection Act 2023 is enacted but not yet fully in force. We would rather tell you exactly where the line is than imply a protection that has not commenced.
| Law | Status today |
|---|---|
| Information Technology Act 2000, Section 43A, and the SPDI Rules 2011 | In force and binding on us now. Section 43A is due to be omitted on 13 May 2027. |
| CERT-In Directions, 28 April 2022 | In force now. Six-hour incident reporting; 180-day ICT log retention within India. |
| DPDP Act 2023 — Data Protection Board provisions (ss. 18–26, 38–43) | In force since 13 November 2025 (G.S.R. 843(E)). |
| DPDP Act 2023 — Consent Manager registration (s. 6(9)) | Commences 13 November 2026. |
| DPDP Act 2023 — notice, consent, fiduciary duties, children, your rights (ss. 3–5, 6(1)–(8) and (10), 7–17) and DPDP Rules 3, 5–16 | Commence 13 May 2027. |
| Aadhaar Act 2016 and the Authentication and Offline Verification Regulations 2021, as amended to 9 December 2025 | In force now, and binding on us for the verification feature. |
| Consumer Protection Act 2019 and the E-Commerce Rules 2020 | In force now. We sell our own service online, so these apply to us. |
| TCCCPR 2018, as amended 12 February 2025 | In force now for SMS and voice. |
18. Grievance Officer
We have appointed a Grievance Officer, as required by Rule 5(9) of the SPDI Rules 2011 and by Rule 4(5) of the Consumer Protection (E-Commerce) Rules 2020. Contact them with any question, request or complaint. We acknowledge within 48 hours and resolve within one month.
| Name and designation | Harsh Sakharam Khot, Director, CredSetu Technologies Private Limited |
| info@credsetu.in | |
| Telephone | +91 79959 53111 |
| Address | C/o Renuka Khot, 143/8, Hirdao Road, Lonar, Buldhana – 443302, Maharashtra |
| Nodal person of contact (resident in India) | Harsh Sakharam Khot, Director |
Full details, including how to escalate, are on our Grievance Redressal page. If you are not satisfied with our response you may complain to the Data Protection Board of India.
19. Changes to this policy
We may update this policy, for example when features or the law change. We will update the “Last updated” date, and for any material change we will give notice in the app at least 14 days before it takes effect. Where a change affects what you have consented to, we will ask for fresh consent rather than assume it.
20. How to contact us
| App | Patrata |
| Operated by | CredSetu Technologies Private Limited, CIN U62090ME2026PTC475450 |
| Support | info@credsetu.in |
| Grievance Officer | info@credsetu.in |
| Registered office | C/o Renuka Khot, 143/8, Hirdao Road, Lonar, Buldhana – 443302, Maharashtra |