Privacy Policy

In short

• We are Mannan Technologies Private Limited, operating as Agentive, in New Delhi. Our Grievance Officer is Rakesh Kumar, at hello@agentive.co.in.
• We have two roles. For your account, business verification, billing, website and marketing data, we are the responsible party. For the calls, recordings, contacts, conversations and leads in your workspace, you are the responsible party and we work on your instructions.
• You must tell the people you contact how you use their data and when a call is recorded or handled by an AI agent, and hold their consent where the law needs it (section 6).
• The licensed operators whose numbers you use, and the telecom rules they work under, require every business that takes a phone number to be verified. We verify the signatory's Aadhaar through our identity verification partner and keep the verification record securely, in encrypted form. We never see or store full card numbers.
• We do not sell personal data. Section 8 lists who receives it, such as telecom operators, Meta, Google, our payment gateway partner and the authorities.
• Your calls are routed in India and your call records are hosted in India (section 9). We do not use your calls, conversations or leads to train AI models shared with other customers.
• Recordings are deleted on your plan's schedule (30 to 180 days). Verification, call detail and billing records are kept for as long as telecom, tax and company law require, even after you delete your account. Section 11 gives every period.
• You can see, correct or delete your data, withdraw consent, nominate someone, or complain. We acknowledge within 24 hours and answer privacy requests within 30 days. You can block our analytics and advertising cookies in your browser (section 16) and stop our marketing at any time.

1. Who we are and how to reach us

This Privacy Policy explains how Mannan Technologies Private Limited, which operates as Agentive ("we", "us"), handles personal data.

• Registered office: 1st Floor, Plot No. 142, Street No. 5, Block-B, Balbir Vihar, New Delhi 110086, India
• CIN U62013DL2022PTC407210, GSTIN 07AAQCM3725R1ZN
• E-mail hello@agentive.co.in, phone 80056 80053
• Grievance Officer: Rakesh Kumar (section 20)

It covers the website agentive.co.in and its checkouts, Agentive Voice (voice.agentive.co.in), Agentive Chat (app.agentive.co.in), Agentive CRM (crm.agentive.co.in), our Android and iOS apps, our chat widgets and our APIs: together, "the services". The services are for businesses in India, not for personal or household use, and every user must be 18 or older.

This policy is published under the Information Technology Act, 2000 and its 2011 rules on sensitive personal data. It also follows the Digital Personal Data Protection Act, 2023 (the DPDP Act), which comes into force in stages. We describe what we do today, and will follow each part of that Act from the date it applies.

This policy is a notice, not a consent form. When you submit your business verification, you confirm your details and sign on screen. We then create a Customer Application Form that carries your details, your signature and your consent to the checks on the identifiers you gave. Ask us for a copy at any time.

2. Our two roles, in plain words

Role one: we are the responsible party. We decide why and how the data is used. The DPDP Act calls this a data fiduciary. It covers your account, business verification, billing, our website, our own marketing and our support conversations with you (section 3).

Role two: we work on your instructions. The calls, contacts, conversations, leads and AI agent content in your workspace (section 4) are mostly about your customers, leads and callers. You decide whom to contact and what to keep. We store and process this data only to run the services for you. Here the DPDP Act calls us a data processor and you the data fiduciary. Sections 6 and 7 say what this means for you and for the people you contact.

The section "Your data and our role" in our Terms of Service is the contract between us for role two. If you need a fuller signed data processing addendum, ask us. Where one is signed, it applies ahead of that section.

There are overlaps. Telecom rules, our operator agreements and tax law make us keep some records ourselves, such as call detail records and invoices (section 11). When we check a complaint, keep the WhatsApp opt-out record or run our do-not-disturb list (sections 5 and 7), we decide how that data is used, so we are the responsible party for it.

3. What we collect when we are the responsible party

• Account and team details. Name, work e-mail, mobile number, business name, role (owner, admin, manager or agent), your password (stored only in hashed form), login codes, trusted-device records, login history, a profile photo if you add one, and the team members you invite. If you choose Continue with Google or Continue with Apple on a sign-in page, Google or Apple sends us a signed token that carries the e-mail address on your Google or Apple account. A Google token may also carry your name and profile picture, which we ignore. We use that e-mail for one purpose: to find the Agentive account that already uses the same e-mail and sign you in. We never create an account from it, we never change your account e-mail to it, we send nothing back to Google or Apple, and we do not keep the token. We keep a sign-in record (the time, the provider, a masked e-mail and an anonymised provider identifier) for one year, as we do for every sign-in.
• Business verification records (Agentive Voice). The licensed operators whose numbers you use, and the telecom rules they work under, require us to verify the business behind every phone number. We collect the PAN of the business or its signatory, and your GSTIN, CIN or Udyam details with the name, address and contacts shown on those registers. We record a short video of the signatory reading out a code, and a drawn or typed signature. We keep your answers about what your business does and how you will use calling, any document you upload (such as a letter of authority), the Customer Application Form with your signature, and the IP address and time of signing.
• Aadhaar check of the signatory. We verify the signatory's Aadhaar through our identity verification partner and keep the verification record securely, in encrypted form. The check returns the signatory's name, date of birth, gender, father's or husband's name, address and photograph, which we keep with your verification record.
• Billing and payment details. Billing name and address, state, GSTIN if you give one, plan and term, orders, invoices and credit notes, wallet and pack balances, coupon use, and payment references from our payment gateway partner. If you switch on automatic renewal, we store the mandate reference, and your UPI ID if you pay by UPI. We never see or store full card numbers. For a saved card we keep only what is needed to show it and renew the plan, such as the last four digits and the card network. Card numbers, CVV, UPI PIN and net-banking passwords are entered on the payment gateway's pages, and we never receive them.
• Checkout and website data. What you type into a checkout or form, your IP address, device and browser type, pages viewed and the page you came from, campaign tags, advertising click identifiers from Google and Meta (such as gclid and fbclid), and cookies (section 16). A checkout you start is saved in your own browser for up to 24 hours. Once you press Pay, the details you entered are also saved on our servers. Section 16 says what our advertising tags receive before that. If you do not complete the payment, we may send you a reminder by e-mail or WhatsApp with a link to resume. If you use the "try the AI agent" demo, we verify your mobile number with a one-time code and our AI voice agent then calls it.
• Mobile app data. A push notification token and basic device details. The microphone only carries your voice during a call in the app. On Android, if your organisation has set you up to place business calls through your own SIM, the app reads your SIM number and the phone's call log, and sends new call entries (number, the contact name saved on your phone, time, duration and direction) to your organisation's workspace. Our servers store every entry the app sends, so use a phone or SIM kept for work. If your phone's own dialer records calls and you give the app access to that folder, the app also uploads recordings from it to your workspace, where they are kept like any other recording. You can withdraw any permission in your phone settings.
• Support and sales conversations. E-mails, WhatsApp chats, tickets, demo bookings, call notes, and calls with our team, which may be recorded.
• Marketing records. Whether you opened or clicked our e-mails, and your unsubscribe and opt-out choices.

Passwords, payment details and verification records are sensitive personal data. We collect them only for the purposes in this policy.

4. What we hold on your behalf

• Calls. Call records (numbers, date, time, duration, direction, who handled the call, call menu choices and outcome), call recordings and voicemail. Transcripts, AI summaries and conversation logs of AI voice agent calls, and the labels and answers your AI voice agent draws from a call, such as sentiment, intent, outcome and the fields you ask it to capture. Where call transcription is enabled on your account, the same for your team's calls, made when you ask for a transcript or, if caller memory is on, automatically. Where caller memory is on for an AI voice agent (it is on by default for some agents, and you control it in the agent's settings), the agent receives a short extract of a caller's calls from the past 90 days at the start of their next call.
• Contacts and campaigns. Contact lists you upload or build, do-not-call flags and blocked numbers, and dialer and voice broadcast lists with their results. For bulk SMS, which our team sets up for you with a messaging delivery partner: recipients, message content, sender registration details and delivery results.
• WhatsApp and chat. Conversations with your customers on your WhatsApp Business Account and your website chat widget, with names, numbers, messages, media and files; message templates and their status; broadcast audiences and results; opt-out and block records; and the identifiers and encrypted access tokens of the WhatsApp Business Account you connect.
• CRM. Leads and contacts (names, phone numbers, e-mail, address, business name, GSTIN, form answers, notes, deal values and payment references you record), the campaign tags and click identifiers that arrive with a lead, files you import, reminders, and the call and WhatsApp history linked to a lead. Leads arrive from imports, your website forms, our API and lead sources you connect, such as Meta lead ads. When you connect Meta lead ads, we also store the name and ID of the person who connected the Page, and an encrypted Page token.
• AI agent content. The knowledge base, website pages, FAQs, product lists, prompts and settings you give your AI agents.

We do not decide what goes into this data. Do not put card numbers, passwords, OTPs, Aadhaar numbers, health records or children's data into notes, custom fields, contact lists or AI agent content. The Terms of Service have the rule.

5. Why we use personal data

• To create and run your account, verify your business as operators and telecom rules require, give support and send service messages.
• To connect calls, deliver messages, run your AI agents, and record, transcribe, summarise and analyse calls as section 4 describes.
• To take payments, keep your wallet, renew your plan, and issue GST invoices and credit notes.
• To keep the services safe: to detect fraud, spam, caller-ID misuse and breaches of the Fair Use Policy. When we look into a complaint, signs of a breach or a lawful request, authorised staff may review the recordings, messages, templates, lists and lead sources involved.
• To check a refund claim under the Refund Policy, and to stop a business we removed under the Fair Use Policy from signing up again. To check a claim, we count the calls in your account's call history, and we match PAN, GSTIN, phone number and e-mail address against earlier accounts to apply the one-claim rule. To keep out a business we removed, we may also match the verified identity of its signatory.
• To answer lawful requests and keep the records the law requires.
• To measure our advertising and improve our website (section 16), and to send you marketing about our own products, which you can stop at any time (section 17).
• To improve the services, using statistics that identify no one.

We use personal data because you gave it to us for that purpose (for example to open an account or buy a plan), because the law or our agreements with licensed telecom operators require it (for example business verification, call records and tax records), because we need it to keep the services safe, stop fraud and protect our legal rights, or because you consented (section 14 covers withdrawal). Section 16 explains our cookies and how to block them in your browser.

We do not use your call audio, WhatsApp conversations, contacts or CRM leads for advertising, and we do not send marketing about our own products to your contacts, leads or callers.

6. When you are the responsible party

For the data in section 4, you are the responsible party. Whatever stage the DPDP Act has reached, our Terms require the following of you:

• Lawful reason. You need consent, or another ground the law accepts, for every person you call, message or store. The Fair Use Policy says whom you may contact and what proof to keep.
• Your own notice. Tell those people what you do with their data. If you place our chat widget or lead forms on your website, your privacy notice must cover them. The widget runs in a frame served from app.agentive.co.in. It saves a conversation ID, the contact details the visitor typed into the widget's form, and whether they rated the chat, in the visitor's browser storage, so that a returning visitor sees their conversation and is not asked twice. The chat widget on your website carries no Agentive advertising or analytics tags.
• Recording and AI disclosure. Call recording is on by default. If you want it off, write to us and we switch it off for your account. You must tell people that a call is recorded or handled by an AI agent, and get any consent the law needs.
• Retention and deletion. What you can remove yourself differs by product today. In Agentive Voice you can delete contacts. In Agentive Chat, a manager or admin can delete a conversation. In Agentive CRM you can delete a lead, unless it is marked as won. A deleted lead leaves every list, report and export at once, but we keep a hidden copy so that it can be restored. Contacts in Agentive Chat and Agentive CRM, and recordings, voicemail and call records in Agentive Voice, cannot be deleted one by one today. To have any of these erased for good, for example to answer a request from one of your contacts, write to us. We do it within 30 days, unless the law makes us keep the record (section 11). Recordings and voicemail go on your plan's schedule, or sooner if you ask us. While a complaint, a Fair Use review, a payment dispute or a lawful request is open, we may keep a copy of the data involved until it closes.
• Where your data goes. If you connect an integration, a webhook or an API key, data leaves our control when it reaches the destination you chose.
• Requests from your contacts. You answer them. Section 7 explains how we help.

On our side, we act on your instructions, except where the law, an operator or an authority requires otherwise, and for our misuse checks (section 5). We keep the data confidential, protect it (section 12), tell you about a breach (section 13), use other providers only under contract (section 8), and delete or return it at the end (sections 11 and 18).

7. If one of our customers called or messaged you

If a business that uses Agentive called or messaged you, that business decided to contact you and holds your data. Please ask it first. If you write to us instead:

• We ask which number or business contacted you, pass your request to that customer within 5 working days, and tell you that we have done so. We cannot hand over or change that data ourselves, because we hold it on the customer's behalf.
• For the few records we keep ourselves (section 2), such as call detail records and our do-not-disturb list, you can use the rights in section 14 with us directly. We may have to keep a record that the law requires.
• If you reply STOP to a WhatsApp marketing message, the platform records your refusal against your number and blocks further marketing messages from that business. The record is kept even if the business removes you from its lists, so that your refusal keeps being honoured.
• Our do-not-disturb list. If you tell us that you do not want calls from our platform, we check that the number is yours and add it to our platform-wide do-not-disturb list. We also add a number when its owner reports abuse to us, or when a telecom operator sends us a complaint made from it, as the Fair Use Policy explains.
• What listing does. No business can call a listed number through our platform. Calls from that number to any business that uses an Agentive number will not connect either, so ask us to remove it if you need to reach such a business. The number stays listed until you ask us to remove it. The list covers only calls carried by our platform, not WhatsApp, SMS or a call placed from a staff member's own mobile connection. It does not replace the national Do Not Disturb register, and you can also complain to your telecom operator on 1909.
• If you report spam, fraud or harassment, we look into it under the Fair Use Policy, which also explains how to report abuse. To look into it, we usually tell that business which number complained and when. If you do not want that, tell us, and we will look into it without naming your number where we can.

8. Who we share data with

We do not sell personal data. We share it only with:

• Your own organisation. Workspace content is visible to your admins and team according to their roles.
• The business you wrote to us about. If you send us a request or a complaint about one of our customers, we pass it to that customer, usually with the number involved and the date, so that it can answer or show its proof (section 7).
• Licensed telecom operators and messaging delivery partners. To connect calls and deliver SMS, they receive the calling and called numbers, call set-up details, message content and the call audio. An operator, or a telecom regulator acting through it, may also ask us for a business's verification records, a number's call records, and the proof of consent behind a call that drew a complaint. Where telecom rules require it, we tell the operator which numbers carry calls started by an app or an AI agent, and we may check a mobile number against operator or government records.
• Government, regulators, courts and law enforcement, when lawfully required. This can include business verification records, call detail records, recordings, and account and billing details. We give only what the request requires.
• Meta, for WhatsApp. If you connect a WhatsApp Business Account, your messages, templates, media and account details pass through Meta's WhatsApp Business Platform under Meta's terms, which you accept directly with Meta. Leads from Meta lead ads reach us from Meta.
• Google and Apple, for sign-in. If you sign in with Google or Apple, your browser or app talks to Google or Apple directly under their own terms, and they learn that you are signing in to Agentive. They send us the e-mail address on your account; we send them nothing.
• Our payment gateway partner. It receives your name, e-mail, mobile number, business name, state and GSTIN, the order details and amount, and the campaign and click identifiers attached to your checkout. It collects your payment details itself and holds any automatic-payment mandate.
• Our identity verification partner. It checks PAN, GSTIN, CIN or Udyam and Aadhaar details against official records.
• Cloud infrastructure, storage, e-mail and notification delivery providers, under contract, only to run the services.
• The messaging tool our team uses for internal alerts. When you sign up, pay or submit a verification, an alert with your name, business name, e-mail, mobile number and GSTIN reaches our staff through it.
• AI model providers for speech recognition, language and speech synthesis, under contracts that require them to protect your data (section 10).
• Meta and Google, for advertising and analytics. Our website and the Agentive Chat app load their tags (section 16). Each time you pay us, on the website, in the app, for a renewal or a wallet recharge, or in a sale our team records, our servers also send them a purchase event. Meta receives your e-mail, mobile number, name, state and country in hashed form, with your IP address, browser details, Meta click identifiers and the order value. Hashing hides the plain text, but Meta can still match the hashes to its own account holders. Google receives the order value, campaign tags and your Google click and analytics identifiers, or a hashed e-mail when that identifier is missing, and no other contact details from our servers. Both use the event to measure our advertising, under their own terms. We never send it about your contacts, leads or callers.
• Professional advisers and auditors, and a buyer of our business, under a duty of confidence and under this policy.

9. Where data is stored and processed

Your calls are routed in India and your call records are hosted in India. We use cloud infrastructure, e-mail, AI model and analytics providers under contracts that require them to protect your data.

10. AI processing

• Some features use AI: AI chat replies, AI voice agents, transcription, call summaries and call analysis. AI model providers process the relevant messages or call audio for us, under contracts that require them to protect it.
• We do not use your call audio, transcripts, conversations, contacts, leads or knowledge base to train AI models that are shared with other customers.
• We do not use WhatsApp conversations to train AI models.
• Caller memory stays inside your organisation.
• We do not use AI to make decisions about you that have a legal effect. A person reviews every business verification.

11. How long we keep data

• Account and team details: while your account is open. After it closes, we keep your registration details (name, e-mail, mobile number, business name, and sign-up and closure dates) for 180 days, as the IT intermediary rules require. We delete or anonymise the rest within 30 days of a verified deletion request, or with your workspace content when your account closes. The records below are kept longer.
• Business verification records (application form, video, signature, Aadhaar check results and consent record), call detail records (who called whom, when and for how long) and billing records (invoices, credit notes, payments and mandates): for as long as telecom, tax and company law require, even if you delete your account.
• Refund and enforcement records (business name, PAN, GSTIN, phone number, e-mail address, the signatory's name and verification reference, and what was refunded or why the account was closed): 3 years after the account closes, even if you delete your account.
• Call recordings and voicemail: by plan, for 30, 60, 90 or 180 days. Business Phone: 30 days, or 90 days on a yearly term. Phone + CRM: 60 days, or 180 days on a yearly term. Trials: 30 days, or 60 days on a Phone + CRM trial. An account that had a longer period before, for example after a yearly term or on an older plan, keeps it. Custom plans follow what we agreed. Ask us for the period on your account. After that, recordings are deleted automatically and cannot be recovered by you or by us in the normal course.
• Call transcripts, including AI voice agent calls: 90 days from the call. AI summaries, labels and captured answers stay with the call record while your account is open. Caller memory uses only the last 90 days.
• Contacts, WhatsApp and chat conversations, templates, campaign results and CRM leads: until you delete them, where the product lets you (section 6), or until they are deleted after your account closes (next item). The hidden copy of a lead you deleted in Agentive CRM is kept until your workspace closes or you ask us to erase it.
• When your account closes: the Terms of Service and the Refund Policy say how long you can still export. We delete your contacts, conversations, leads, recordings, transcripts and AI summaries within 90 days after that export window ends. The Terms let us refuse export after a termination for fraud or illegal use. If you delete your account yourself or ask us to delete it, there is no export window, and section 18 sets the timing.
• CRM lead limit: if we have set your CRM workspace to archive leads at the lead limit (the Plan page in your CRM says so), closed leads that were not won and are more than 30 days old are archived, and deleted for good 30 days later, after a warning in the app. Every other CRM workspace stops taking new leads at the limit and deletes nothing.
• Technical logs of incoming lead data and webhook deliveries: 30 days, or 120 days when the attempt failed. CRM inbox media files: 30 days.
• The WhatsApp opt-out record: kept even after the contact or the AI agent is deleted, until the business's whole workspace is deleted.
• The platform-wide do-not-disturb list and our marketing unsubscribe list: kept until the person asks to be removed.
• Checkout records: a paid checkout is kept with billing records. A checkout you started but did not pay for: 12 months.
• Security and access logs: 1 year.
• Analytics data and support conversations: 2 years.
• Backups: deleted data leaves our backups as the backup copies are overwritten.

When a period ends, we delete the data or make it anonymous. Where a law sets a longer minimum period for any data or logs, that period applies. The Terms of Service explain what happens to your numbers when a plan lapses or a workspace closes.

12. Security

• Traffic between your browser or app and our services is encrypted in transit. Calls over the public telephone network are carried by licensed telecom operators in the usual way and are not end-to-end encrypted.
• Passwords and API secret keys are stored only in hashed form. Integration access tokens are encrypted.
• Access inside your workspace follows roles. Where your plan includes number masking, admins can hide customer numbers from chosen agents.
• Recordings are played through links that expire within minutes.
• We use one-time login codes and trusted-device checks.
• Access to production systems is limited to staff who need it. When our support team opens your workspace to help you, the session is time-limited and logged.
• Webhooks carry a signature you can verify. For AI voice agent webhooks, set a signing secret to switch this on. APIs are rate-limited.

No system is fully secure. Please protect your logins and API keys, and remove people who leave your team. Report any weakness to hello@agentive.co.in.

13. If there is a data breach

If we learn of a breach that affects personal data, we contain it and investigate. Then:

• Where we are the responsible party, we tell each affected person we can reach, without delay: what happened, which data, the likely effect, what we have done and what the person can do.
• Where we hold data on your behalf, we tell your admins without delay, with the details you need to inform your own contacts.
• We report to CERT-In and, once the DPDP Act's breach duties apply, to the Data Protection Board of India, within the time the law sets. We keep a record of the breach and of what we did.

14. Your rights and how to use them

For the data in section 3, and the records we keep ourselves (section 2), you can:

• Access. Ask for a summary of the personal data we hold about you and what we do with it. Admins can export call records and contacts from Agentive Voice, and leads and contacts from Agentive CRM. Agentive Chat exports campaign results and wallet history today. For anything else, ask us and we will send it.
• Correction. Ask us to correct, complete or update it. You can change most account details yourself.
• Deletion. Ask us to erase data that we no longer need and that the law does not make us keep. Section 18 covers deleting an account.
• Withdraw consent. Where we rely on your consent, you can withdraw it as easily as you gave it. This does not undo what was done before, or remove records the law makes us keep. If you withdraw a consent we need, such as consent to business verification, the service that depends on it stops. That is your decision to end the service early, not ours. It is treated like closing your account (section 18), and money is returned only where the Refund Policy says so.
• Nominate. Name a person who may use these rights for you if you die or become unable to act. Write to us and we will note it on your account. We will follow the DPDP Act's nomination rules when they apply.
• Complain. Write to the Grievance Officer (section 20). Once the Data Protection Board of India accepts complaints under the DPDP Act, you may go to the Board after you have used our grievance process.

Signing in with Google or Apple changes none of these rights. We keep no link to your Google or Apple account, so there is nothing to unlink.

How. Write to hello@agentive.co.in with "Privacy request" in the subject line, or call 80056 80053. Write from your registered e-mail, or tell us the e-mail or phone number you gave us. We may ask for details to confirm who you are. There is no fee. We acknowledge within 24 hours and answer within 30 days. If we cannot do what you ask, for example because the law makes us keep a record, we tell you why.

For data that one of our customers holds about you, see section 7.

15. Children

The services are for businesses. Nobody under 18 may hold an account or use them. We do not knowingly collect personal data from children for our own purposes. If we learn that we have, we delete it. Customers must not use the services to collect children's data or to market to children.

16. Cookies and similar technologies

• Essential cookies keep you signed in, protect your account, remember your choices and make checkout work. They are always on. If you block all cookies, sign-in and checkout will not work.
• Analytics and advertising cookies. We use analytics and advertising cookies and similar tools on our own website and apps to measure visits and our advertising. They come from Google (Google Analytics and Google Ads) and Meta (the Meta Pixel), and from our own measurement tool. When you fill in a form or a checkout on our website, the Meta and Google tags also receive your e-mail, mobile number, name and state in hashed form, from the moment you move past the first step, so that Meta and Google can match a sign-up or purchase to an advertisement.
• How to block them. You can block these cookies and tags in your browser settings or with a content blocker, and you can switch off ad personalisation in your Google and Meta account settings. Our website still works without them.
• Similar technologies. Your browser's local storage saves an unfinished checkout, and our website reads advertising click identifiers in a link you followed. Our marketing e-mails may use a small image or tagged links that tell us whether you opened or clicked.
• Blocking cookies does not stop the purchase events our servers send to Meta and Google when you pay us (section 8).
• Product dashboards. The Agentive Voice and Agentive CRM dashboards load no analytics or advertising tags. After you sign in, the Agentive Voice and Agentive Chat dashboards load a feedback button from a separate service that we use to collect bug reports. When you connect a WhatsApp Business Account, Meta's own sign-up window loads and may set Meta's cookies. The sign-in pages of Agentive Voice, Agentive Chat and Agentive CRM load Google's and Apple's sign-in scripts, which may set their cookies; they are not advertising tags.
• Agentive Chat and the chat widget. The Agentive Chat app loads Google Analytics and the Meta Pixel. In that app, the Meta tag can also receive, in hashed form, contact details you type into a form. The chat widget on a customer's website carries no Agentive advertising or analytics tags.

17. Marketing messages from us

If you are a customer, a trial user or someone who asked about our products, we may send you news and offers by e-mail, and on WhatsApp if you opted in. The one exception today is the reminder about an unfinished checkout (section 3). Our team may call or message you about your enquiry, trial or account, within the limits TRAI's commercial communications regulations (TCCCPR) set. We send promotional SMS only as those regulations allow.

• Every marketing e-mail has an unsubscribe link. One unsubscribe covers all Agentive products, and it works at once.
• On WhatsApp, reply STOP. For calls and SMS, tell the caller or write to hello@agentive.co.in. We stop as soon as we record your request, and no later than 2 working days. We stop on the channel you used. Tell us if you want every channel stopped and we will do that too.
• Service messages are not marketing. We still send payment receipts, renewal reminders, verification reminders and updates, security alerts and policy changes, by e-mail, WhatsApp, SMS, push notification or in the app.

18. Deleting your account

Our data deletion page explains how to delete an account or a connected WhatsApp integration.

• Agentive Chat accounts can be deleted online. You sign in and confirm with a code sent to your e-mail, and your access ends at once. If you own the workspace, the whole workspace, including every team member's access, is erased 7 days later, unless the hold below applies. If you are a manager or an agent, only your own account is deleted and the workspace stays with your organisation. Registration details are kept for 180 days (section 11).
• Agentive Voice and Agentive CRM accounts are deleted by us on request. Write to hello@agentive.co.in from your registered e-mail and name the products to delete. If you bought Phone + CRM, one e-mail can cover both. We complete a verified request within 30 days. We delete only the products you name.
• If you signed in with Apple, also open Settings, choose your name, then Sign in with Apple, then Agentive, then Delete, so that Apple stops sharing your e-mail with us.
• Export anything you need first. We cannot recover data after deletion.
• When deletion waits. If a complaint, a Fair Use review, a payment dispute, an unpaid amount or a lawful request is open on your account, we may keep the data involved, or a copy of it, until it closes, and delete it then (section 6). Your access still ends on the date above.
• The records the law makes us keep, and the refund and enforcement records (section 11), stay with us after deletion. We do not use them to contact you or to market to you.
• Deleting an account is not a refund request and does not by itself bring a refund. It does not take away a refund you are already owed, so if the Refund Policy gives you one, claim it before you delete. Otherwise the rest of your paid term is not returned, and unused wallet balance, credits and packs are lost. Your phone numbers are released and cannot be recovered.

19. Changes to this policy

We may update this policy. We give 30 days' notice of a material change by e-mail and in the app, as the Terms of Service set out for all our policies. If a change needs your consent, we will ask for it. Earlier versions are available on request.

20. Contact and Grievance Officer

Privacy questions, requests and complaints go to our Grievance Officer, who covers this policy and every Agentive product:

• Rakesh Kumar, Grievance Officer, Mannan Technologies Private Limited (Agentive), CIN U62013DL2022PTC407210, at the registered office in section 1
• E-mail: hello@agentive.co.in, with "Grievance" or "Privacy request" in the subject line
• Phone: 80056 80053
• Hours: Monday to Saturday, except public holidays

Please give your name, your registered e-mail or phone number, and what went wrong. The Grievance Officer acknowledges every complaint within 24 hours. The Grievance Officer section of the Terms of Service says how fast each kind of complaint is resolved. Requests to see, correct or delete personal data are answered within 30 days (section 14).