Legal
Privacy Policy
How we handle personal data on this website, and inside the Saaransh service.
Version 1.0 · Effective date: 16 November 2026 · Last updated: 16 November 2026
Who we are
Saaransh is a product of Enjay IT Solutions Ltd. (“Enjay”, “we”, “us”), incorporated in India, with its registered office at Enjay House, Bhanu Sangam, Sanjan Rd, near Shreeji Hospital, Bhilad, Daheli, Gujarat 396105.
This Policy covers the Saaransh website (saaransh.tech), the Saaransh web app, the Saaransh mobile app, and the Saaransh service (“the Service”). Saaransh is offered in India, and this Policy follows India’s Digital Personal Data Protection Act, 2023 and the DPDP Rules, 2025 (together, “DPDP”).
We act in two different roles:
- Data Fiduciary for data we collect for our own purposes: website enquiries, demo requests, customer accounts, billing and support.
- Data Processor for data inside the Service, such as call recordings, transcripts, contacts and reports. Here, our customer (the business using Saaransh) is the Data Fiduciary. We process this data only on the customer’s instructions, under our Terms and Conditions.
The personal data we collect
When you visit our website or contact us
Your name, work email, phone number, company name, industry type, team size, and anything you write to us. We also collect technical data such as IP address, browser and pages visited (see section 14).
When a business uses the Service
- Calls: call recordings, call date, time, duration and direction, and phone numbers.
- AI outputs: transcripts, summaries, sentiment, tasks, alerts and flags on important moments in a call, coaching reports, and minutes of meeting (MoM) ready to share over WhatsApp or email, all created from calls.
- Contacts and CRM data: contact names, phone numbers, notes and tasks, stored in Saaransh or in a CRM the customer connects (such as Sangam CRM).
- User data: names, login details and the device linked to each agent.
- Business context: information the customer gives us about its products, processes and sales stages, used to tailor the analysis.
On the mobile app
The app asks for these permissions, each for a specific reason:
- Phone: to know when a call starts and ends.
- Call history: to get the number, time, duration and direction of a call.
- Call recordings: to find the recording of a call and match it to the right call.
- Display over other apps: to show the “Log this call?” prompt right after a call ends.
- Notifications: to tell the user when a summary or task is ready.
- Battery optimisation exemption: so the phone does not stop the app in the background before a call is logged.
The app reads only what it needs to find the recordings of calls to be logged, as set by the user in the app. It does not read your contacts list, messages, photos or other files. You can refuse or withdraw these permissions at any time in your phone settings, but the app may then not be able to log calls.
How call data flows
- Recording is done by the phone, not by Saaransh. The agent’s phone records calls using its own built-in recorder. Saaransh does not switch recording on, and has no access to calls while they happen.
- Upload depends on the user’s setting. For each SIM on the phone, the user chooses one of three options in the app:
- Ask me every time: after each call, the app asks whether to log it. The recording is uploaded only if the user taps “Log Call”. Calls that are not logged never leave the phone through Saaransh.
- All calls: every call on that SIM is uploaded and analysed without asking.
- Saved customers only: only calls with numbers saved as contacts in Saaransh are uploaded and analysed. Calls with other numbers are not uploaded.
Users can also keep two lists of numbers in the app’s call settings:
- Business numbers: calls with these numbers are analysed by default.
- Personal numbers: calls with these numbers are never uploaded or analysed, whatever option is chosen for the SIM.
- Calls from a business phone system. Where a customer connects a call centre system or a cloud telephony provider, Saaransh fetches call recordings from that system for analysis, as authorised by the customer. The telephony provider is chosen by the customer and works under its own terms with the customer.
- Short calls are skipped. Calls under 20 seconds are not sent for AI analysis.
- The original stays on the phone. Deleting a recording from Saaransh does not delete the original file on the agent’s phone. That file is controlled by the customer and its employee.
How AI is used
Saaransh uses trusted third-party AI providers, through their enterprise services, to transcribe and analyse calls. Our current providers are listed in section 7. Our third-party AI providers do not use your data for training.
What is sent to the AI
The call recording, plus the details needed to understand it correctly: call direction, the agent’s name, and the business context described in section 2.
Where the AI runs
Recordings and results are stored in India. The AI analysis itself runs on our AI provider’s infrastructure and may take place outside India. The provider processes this data as our service provider under its enterprise terms.
What the AI provider does with it
- It does not use your data to train its AI models.
- It may hold data briefly in a temporary cache to make processing faster and cheaper, and may check requests for abuse under its terms. It does not use your data for any other purpose.
Learning stays with your account
When your authorised users give feedback, for example a team leader re-classifying a flagged call, Saaransh uses it to understand your business better. This learning is used only for your account. It is not shared with other customers or used to build a shared model.
AI can be wrong
AI outputs are generated automatically and may be incomplete or inaccurate. They are meant to help managers coach their teams. Customers should review them before acting, and must not use them as the only basis for decisions about an employee, such as hiring, firing or pay.
Why we use personal data
- To provide the Service: analysing calls and creating summaries, tasks, alerts, reports, and minutes of meeting (MoM) to share over WhatsApp or email.
- To set up and manage accounts, users and permissions.
- To provide support, fix problems and keep the Service secure.
- To bill customers and keep business records.
- To reply to enquiries and send product or service updates. You can opt out of marketing messages at any time.
- To meet legal obligations.
We do not sell personal data. We do not use customers’ call data to train AI models.
What our customers are responsible for
Customers decide how their call data is used (in law, they are the “Data Fiduciary”). So customers using Saaransh are responsible for:
- Telling callers. Informing the people their teams speak with that calls are recorded and analysed by AI, and getting any consent the law requires.
- Telling employees. Informing their agents in writing that business calls are recorded and analysed, including their voice and performance.
- Business calls only. Making sure only business calls are analysed. If its users choose “All calls”, allowing this only on company-provided phones or SIMs used for business, and telling agents in writing what that option does.
- Respecting objections. Not logging a call when a caller objects, and handling requests from callers to access or delete their data.
- Recordings on phones. Managing the original recordings kept on employees’ phones, including when an employee leaves.
- Personal calls analysed by mistake. If a personal call is analysed, the employee should contact the account owner at their company. The account owner can delete the summary and other outputs of that call.
Who we share data with
We share personal data only with service providers who help us run Saaransh, under contracts that require them to protect it and use it only for our instructions.
| Provider | What they do | Location |
|---|---|---|
| Google Cloud | Stores recordings and results | India |
| Google Cloud (Vertex AI, Gemini) | AI transcription and analysis | May be outside India |
| Data centre hosting provider | Hosts the servers that run the Saaransh application and store reports, transcripts and contacts | India |
| Google Analytics for Firebase | Helps us understand how the app is used so we can improve it. Receives anonymised usage data: app opens, updates and first launches, device information, region, number of sessions and users, operating system, session duration, usage data and an anonymised user ID. We do not share your name or email with this service. | May be outside India |
| Firebase Crashlytics | Tells us when the app crashes so we can fix it. Receives device details: manufacturer, model, Android version, Android SDK version and app version. | May be outside India |
| Firebase Cloud Messaging | Sends push notifications through the app. Receives device details: manufacturer, model, Android version, Android SDK version and app version. | May be outside India |
If this list changes, we will update this Policy and inform customers.
We may also disclose data where the law requires it, for example to a court or government authority, or as part of a merger or sale of our business, with the same protections in place.
Where data is kept
Saaransh stores transcripts, reports, alerts and contact data in India. Call recordings are not stored; they are deleted once analysis is complete.
AI analysis, and some app services listed in section 7, may take place outside India.
How long we keep data
| Data | How long |
|---|---|
| Call recording audio | Saaransh does not record calls. It only uses the recording made by the phone to create the summary and other outputs. Once the analysis is complete, Saaransh immediately deletes the audio from its servers. It is not kept. The original recording stays on the customer’s phone, as it was. |
| Transcripts, summaries, reports, alerts, contacts, tasks and call logs | Kept while the customer’s subscription is active. When the account is closed, we send the customer an option to download this data. It is deleted 7 days after the subscription ends. |
| Website enquiries and demo requests | Kept in our CRM so we can stay in touch about our products. Deleted when you ask us to. |
| Account, billing and security logs | As long as the law requires. DPDP requires certain logs to be kept for at least one year. |
Customers can ask us to delete their data earlier.
Security
We use reasonable safeguards to protect personal data. All data is sent over encrypted connections (HTTPS). Call recordings are held in encrypted cloud storage until analysis is complete. Each customer’s data is kept separate, so one customer cannot see another customer’s data.
No system is completely secure. Customers should protect their logins and devices, and remove users who leave.
Data breaches
If a personal data breach affects data we process for a customer, we will tell that customer without undue delay so it can meet its legal duties.
Your rights
Under DPDP, you have the right to:
- get a summary of your personal data and how it is used;
- ask for it to be corrected, completed or updated;
- ask for it to be deleted;
- withdraw consent, where we rely on consent;
- nominate someone to act for you in case of death or incapacity;
- raise a grievance with us, and then with the Data Protection Board of India.
If your data reached Saaransh through a business you spoke with, or your employer, please contact that business first. It controls the data. We will help it respond.
Children
Saaransh is a business service for adults. We do not knowingly collect data from children. If a customer’s use involves children’s data, the customer must get verifiable parental consent first.
Cookies
Our website uses cookies that are needed for it to work. You can block cookies in your browser settings.
Changes to this Policy
We may update this Policy when our product or the law changes. We will post the new version here with a new date, and tell customers about important changes.
Contact and grievances
For questions, rights requests or complaints, contact our Grievance Officer:
