Data Processing Addendum

Yodhik CRM · yodhik.com · Operated by STOCK LEADS (Marketix Digital) ("Yodhik", "we") · Version 1.0 · Effective 3 October 2026 · Read with the Terms and Privacy Policy

1. Roles

Each company that signs up ("Customer") is the data fiduciary under the Digital Personal Data Protection Act, 2023 for the leads, customers, call recordings and employee data it loads into Yodhik. Yodhik is the data processor: we process that data only to run the service the Customer configured, on the Customer's documented instructions (the settings in the panel and the app are those instructions).

2. Multi-tenant isolation

Every record carries the Customer's company id and every query is scoped to it. Users see only their own company (and, inside it, only what their role and hierarchy allow). Platform staff (the Yodhik super-admin) can open a Customer's panel only through the console's "open as admin" action, which is logged in the audit trail with the staff identity and time. We never use one Customer's data to serve another.

3. What we process, for what

DataPurposeWhere it lives
Lead and customer records (name, phone, e-mail, notes, status, deal value)The CRM itself: dialing, follow-ups, reportsMySQL on the Yodhik server (India-hosted shared hosting, see §6)
Call metadata (number, direction, duration, time) and on-device call recordingsWork-call logging, playback for the Customer's managers, AI call review when the Customer switches it onRecordings as files on the Yodhik server, kept for the plan's retention period, then deleted nightly
Agent activity (status, app heartbeat, approximate location if the Customer enables it)Live floor view, performance and red-flag reports the Customer asked forMySQL, aggregated after 90 days
Payments recorded against leads (amount, mode, reference)Sales confirmation and results; Tally exportMySQL. Yodhik never holds the Customer's money; payment links settle on the Customer's own gateway account
WhatsApp messages sent / received through the Customer's WhatsApp Business numberLead timeline, campaign reports, opt-out handlingMySQL; message content stays on Meta's platform
Admin and user accounts (name, e-mail, phone, hashed password, sessions)Sign-in and permissionsMySQL; passwords are bcrypt-hashed, sessions are revocable

4. Sub-processors

We use the following third parties. Each one receives only what its row says, and only when the Customer turns the feature on. We will update this list on this page before adding a new sub-processor.

Sub-processorPurposeDataSwitched on by
Hosting provider (cPanel shared hosting, data centre in India)Servers, database, backupsEverything in §3, encrypted at rest by the hostAlways
Razorpay Software Pvt LtdYodhik's own subscription billing; and, for the Customer's payment links, the Customer's own Razorpay accountAdmin billing identity; for links: customer name, phone, amountBilling: always · Links: Customer
Google LLC (Gemini API)AI call review, summaries, gradingCall audio and transcript of the reviewed call, lead nameCustomer (AI Team Lead)
Groq Inc · OpenAI LLC · Sarvam AIAlternative AI providers the Customer may choose instead of GeminiSame as aboveCustomer (AI provider setting)
Meta Platforms (WhatsApp Business Cloud API, Lead Ads)WhatsApp messaging and campaigns; Facebook/Instagram lead formsPhone numbers, template parameters, lead form fieldsCustomer
Google LLC (Sign-in, Ads lead forms)"Continue with Google"; Google Ads lead-form deliveryE-mail and name from the Google account; lead form fieldsCustomer / user
IndiaMART InterMESH · Just Dial LtdLead delivery from those marketplacesEnquiry fields the marketplace sendsCustomer
E-mail delivery (the Customer's own SMTP, or the hosting provider's mail server)Digests, reports, support repliesRecipient address, report contentCustomer (SMTP) / always (platform mail)
QR image rendering (api.qrserver.com)Rendering the QR code shown in IntegrationsThe public landing-page URL onlyCustomer

5. Security measures

TLS on every connection; bcrypt password hashing; role- and hierarchy-scoped queries; one-year sessions that the user or admin can revoke from any device; rate limiting on sign-in and public hooks; strict Content-Security-Policy on the web panel; encrypted storage of third-party API keys; signed webhooks (Razorpay HMAC, WhatsApp verify token); audit log of administrative actions; nightly database backups kept off the web root; recordings purged on schedule. Agents' phones record only calls to numbers that are in the Customer's CRM, and the Customer can make recording mandatory or block the dialer when the microphone permission is revoked.

6. Location of processing

Primary processing and storage are in India. The AI providers and Meta process data in their own regions when the Customer enables those features; the Customer should pick a provider consistent with its own obligations (Sarvam AI is the India-resident option for transcription).

7. Retention and deletion

Lead data is kept for as long as the Customer's account is active. Call recordings follow the plan's retention (30/90/180 days, or 365 with the retention add-on) and are deleted nightly thereafter. When a Customer closes its account, we delete or anonymise its data within 30 days, except what Indian law requires us to keep (invoices, 8 years). Backups roll off within 35 days. A Customer can export leads, calls and payments at any time from Reports.

8. Data principal requests

Requests from a Customer's leads or employees (access, correction, erasure, grievance) are the Customer's to answer; the panel's DNC list, lead delete and user deactivation exist for that. If such a request reaches us directly we forward it to the Customer within 3 working days and act on the Customer's instruction.

9. Breach notification

If we become aware of a personal-data breach affecting a Customer we notify the Customer's admin e-mail without undue delay and within 72 hours, with what we know, what we have done and what we recommend, and we assist with any notification to the Data Protection Board of India.

10. Assistance, audits, changes

We answer reasonable security questionnaires and provide this page, the status page (/status.html) and the audit log as evidence. Material changes to this addendum are announced in the panel 30 days before they take effect. Questions: the support address shown in the panel (Help & support).