← All news and guides
Data protection

AI Meeting Recorders and Note-Takers: Consent, Confidentiality and Data Retention

Can staff use AI note-takers under the DPDP Act? What to tell people on the call, which meetings to exclude, vendor checks and a retention schedule.

Mono Team ·

A small black audio recorder lying on a wooden meeting table beside a closed notebook and a glass of water, soft window light, shallow depth of field.

Short answer: you can use AI meeting recorders under the DPDP Act, but only if you choose the tool, sign a contract with its vendor, tell everyone on the call what is happening, and set rules for which meetings never get recorded and how long recordings live. A recording of someone's voice or face is personal data, so the Act applies to it. The Act and the Rules do not mention recordings, so how each duty applies depends on the facts. Those duties start on 13 May 2027. The bigger day-to-day risk is confidentiality: a note-taker that joins a client call on its own, or sends a summary to every invitee, can leak more than any breach.

This guide is for employers and the teams that run IT, security and legal. It covers Indian law only. It is engineering guidance, not legal advice. The legal reading for your business goes to counsel, and our partner law firm reviews the legal points we make in our DPDP work.

Is the audio and transcript from a meeting recorder personal data under DPDP?

Yes, in most cases. Section 2(t) of the DPDP Act defines personal data as "any data about an individual who is identifiable by or in relation to such data". A recording of a named colleague, a customer or a candidate, with their voice and often their face, meets that test. So does a transcript that carries their name, their opinions or their health, pay or family details.

A recorder produces more than one kind of data. Treat each as its own thing, because each is stored, shared and deleted differently:

What the tool createsWhy it matters
Audio or video fileWhy it matters: Holds voice and face. The hardest to redact and the largest to store
Full transcriptWhy it matters: Names every speaker and keeps their exact words. Searchable, so easy to copy elsewhere
AI summary and action itemsWhy it matters: A derived record. It can state things as fact that nobody said, and it is often e-mailed to people outside the company
Attendee list, calendar data and meeting titleWhy it matters: Shows who met whom and when. The tool often needs calendar access to join
Logs of who viewed, shared or exportedWhy it matters: These are processing logs. You need them as evidence

The Act does not define "sensitive personal data". It treats all digital personal data the same way. That does not make every meeting equal. A weekly stand-up and a disciplinary hearing carry very different risk, and your policy should say so.

Which DPDP duties apply when a note-taker joins a call?

Your company is the Data Fiduciary: it decides why the meeting is recorded and how (Section 2(i)). The recorder vendor is usually a Data Processor, because it handles the data on your behalf (Section 2(k)). The call participants are Data Principals. Five parts of the Act then matter:

  • A lawful ground. You need consent or one of the legitimate uses in the Act (Section 4). Legitimate uses include "the purposes of employment" (Section 7(i)). Whether that covers a given recording of your own staff is a question for counsel. It does not obviously stretch to a customer, a candidate or a supplier on the call, so assume they need a notice and, in most cases, consent.
  • Valid consent. Consent must be "free, specific, informed, unconditional and unambiguous with a clear affirmative action" and limited to the data needed for the purpose (Section 6(1)). A pre-ticked box or silence is not an affirmative action.
  • Easy withdrawal. Withdrawing consent must be as easy as giving it (Section 6(4)). If joining takes one click, stopping the recording cannot take an e-mail to the legal team.
  • Proof. You must be able to show that notice was given and consent was obtained (Section 6(10)). A spoken "is everyone fine with this?" that leaves no trace will not help you.
  • A contract with the vendor. A processor engaged for an activity related to offering goods or services needs a valid contract (Section 8(2)), and you stay responsible for what it does with the data (Section 8(1)).

The Act has an exemption for personal or domestic use (Section 3(c)(i)). A recording that staff make to do the company's work is not obviously personal use, so do not assume a staff member's own recorder falls outside the Act. Counsel should confirm the position for your cases. For a wider look at employees using AI tools, see our guide to using ChatGPT at work under the DPDP Act.

A quiet meeting room with a long wooden table, a single small black speakerphone in the centre, and empty chairs pushed in around it, soft morning light, nothing legible.

Do it in three places, so that nobody is surprised and you have a record.

  • In the calendar invite. Add a short line before the call: that an AI note-taker will record and transcribe, for which purpose, and who will see the output. This reaches people before they join. It is the best place to give the notice, because you can store the invite as evidence.
  • At the start of the call. The host says that the recording is on, states the purpose in one sentence, and asks anyone who objects to say so or to tell the host privately. Where the tool allows it, use the platform's own recording prompt, so each participant must press a button to stay. That is a clear affirmative action, which a nod on camera is not.
  • A link to the full notice. Rule 3 asks for a notice that stands alone, separate from any other terms. It must give an itemised description of the personal data, the specified purpose, and how the person can withdraw consent, exercise their rights and complain to the Data Protection Board. Link to one page that does this for recordings, and keep each version with its date.

The "specified purpose" is the purpose named in your notice (Section 2(za)). "Improve our products" is too wide. "Record the call so the host can produce minutes and action items, kept for 30 days" is specific. Say exactly what the recording is for, because every later use needs to fit within it. Training the vendor's models on the audio is a separate purpose, and you should switch it off unless you have a reason and a basis for it.

What if someone says no?

Plan for it, because it will happen. The simplest rule is that the host stops the recording, deletes any part already captured, and takes notes by hand. Do not make a person's job, a sale or an interview depend on agreeing to the recording unless that data is genuinely needed for the purpose. Consent that is a condition of something else will struggle to be "unconditional" under Section 6(1).

If a participant withdraws consent after the call, treat it like any other withdrawal request. Delete the audio, the transcript and the summary, and tell the vendor to delete its copies. Our rights request workflow shows how to log and track those requests, and our guide to DPDP erasure automation covers the deletion side.

Which meetings should never be recorded by an AI tool?

The consent question is only half of it. A recording is a permanent, searchable copy of a conversation that would otherwise vanish. Some conversations should not be copied, whatever anyone agrees to. Decide this by meeting type, not case by case in the moment.

Meeting typeSuggested ruleWhy
Calls with your lawyersSuggested rule: Do not record with an AI toolWhy: A transcript sent to a third-party vendor and shared widely can undermine confidentiality. Ask counsel how privilege is affected before any exception
HR, disciplinary and grievance meetingsSuggested rule: Do not record with an AI tool unless HR sets up a controlled processWhy: Holds sensitive personal detail. The summary may be wrong and used against someone
Board and investor discussionsSuggested rule: Company secretary or designated note-taker onlyWhy: Strategy, deals and unpublished results. A leaked summary is a major incident
Calls with clients under NDASuggested rule: Only with the client's written agreementWhy: Your contract may bar sharing their information with a third-party AI vendor
Health, financial or identity details discussedSuggested rule: Do not record, or pause the toolWhy: Aadhaar, PAN, account numbers and medical details are exactly what you do not want in a transcript
Internal stand-ups and project callsSuggested rule: Allowed with the standard noticeWhy: Low risk and the main use case

Write the table into your policy, and tell hosts to pause the tool when a call moves into a restricted topic.

What should you check in the AI recorder vendor?

Most of the risk sits here. A vendor that is a processor must work only on your instructions, and the contract must make that clear. Do this review before anyone gets a licence, not after a team has already signed up with a work e-mail.

CheckWhat you want to see
Contract and roleWhat you want to see: A signed agreement that names the vendor as your processor, limits its use of the data to providing the service, and sets security duties (Section 8(2))
Training on your dataWhat you want to see: Off by default for business accounts, stated in the contract, not only in marketing text
Sub-processorsWhat you want to see: A list of the cloud and AI model providers that handle your audio and text, with notice of changes
Where data is storedWhat you want to see: A named region. The DPDP Act does not require data to stay in India, but the government can restrict transfers to notified countries under Section 16, and none are notified as of 20 November 2026. Sector rules may add their own limits
Retention and deletionWhat you want to see: A setting for how long files are kept, true deletion on request, and a stated period for removal from backups
Access and sharingWhat you want to see: Single sign-on, role-based access, no public share links, and control over who gets the summary
Logs and exportWhat you want to see: An audit log of who viewed, shared, downloaded or deleted a recording, which you can export

Our guide to the data processor contract under DPDP lists the clauses to ask for, and a vendor evidence pack shows what good evidence from a vendor looks like. Add that vendors must tell you of a breach without delay, so you can meet your own duty under Rule 7, and that you can export and delete everything at exit.

How do you stop uninvited AI note-takers joining your calls?

A row of identical empty chairs along one side of a long boardroom table, one chair pulled slightly back, late afternoon light through blinds, shallow depth of field, nothing legible.

This is shadow AI. A person on your side, or the other side, links a free note-taker to their calendar, and the bot then joins every meeting they are invited to. It may record you without anyone on your team having signed anything. Three groups of controls deal with it.

  • Block and allow at the meeting platform. Set the meeting platform to hold unknown participants in the lobby, to require sign-in for internal meetings, and to restrict third-party recording apps to an approved list. Make the host the person who admits bots.
  • Control the calendar and OAuth permissions. In your identity provider, review the third-party apps that have been granted access to calendars, mail and files. Remove unapproved note-takers, and limit who can approve new apps without admin review.
  • Discover what is already running. Search sign-in logs, expense claims and browser extensions for AI note-taker names, and ask staff which tools they use with a short survey. Our shadow AI audit does this discovery, and the guide to AI tools under DPDP explains the legal side.

Give staff an approved option, because people turn to free tools when the approved process is slow or missing.

A host who finds an unknown bot on a call should ask who it belongs to, remove it, and pause any sensitive discussion until the owner is known.

How long should you keep meeting recordings and transcripts?

Keep them for the shortest time that fits the purpose. Section 8(7) says that unless a law requires retention, you must erase personal data when the person withdraws consent or when the specified purpose is no longer served, whichever is earlier. You must also make your processor erase the data it holds for you. The purpose of a recording is usually to produce minutes and action items. Once that is done, the recording has served its purpose.

ItemSuggested defaultNotes
Audio or video fileSuggested default: Delete once the summary is checked, within 30 days at the latestNotes: Largest and most sensitive. Keep longer only for a named purpose, such as a training session you will replay. Check the one-year rules below with counsel before you set this
Full transcriptSuggested default: 30 to 90 days, depending on the useNotes: Pick one period per meeting type and write it down
Summary and action itemsSuggested default: Keep with the project record, and apply that record's retention ruleNotes: Edit out personal data that the action list does not need
Recorder access and deletion logsSuggested default: At least one yearNotes: See below
Backups and vendor copiesSuggested default: Fixed expiry, written in the contractNotes: The Rules do not spell out erasure from backups. Document your backup expiry and apply it to the vendor too

The 30 to 90 day figures are our suggested defaults for you to adjust, not periods set by the Act. Two rules point the other way. Rule 8(3) requires fiduciaries to keep personal data, traffic data and processing logs for at least one year for the purposes in the Seventh Schedule, and Rule 6(1)(e) asks for logs and personal data to be kept for one year so that unauthorised access can be investigated. Whether either reaches a given recording, and so whether a 30-day deletion works for you, is a question for counsel. In any case, keep the logs of who recorded, who viewed and when it was deleted for one year, in line with Rule 6(1)(e).

Make deletion automatic. Set the vendor's retention setting to your period, and test it. Pick a recording older than your limit and confirm that it is gone. Summaries already e-mailed to inboxes need covering in your policy too, because deleting the vendor's copy does nothing to a copy in a mailbox. Our data map guide shows how to record where each kind of data lives.

What should an AI meeting recorder policy say?

One page is enough. It should be easy to follow on a Monday morning:

  • Approved tool. Name the one or two tools staff may use, with a link to the notice and settings. Say that personal accounts and free note-takers are not allowed for company meetings.
  • What to tell people. The invite line, the opening statement and the link to the notice.
  • Never-record list. The table above, with a named person to ask in doubt.
  • If someone objects. Stop, delete, and take manual notes.
  • Incidents. Report a wrongly recorded meeting or a leaked summary to the security or privacy contact at once, so the company can assess whether it is a personal data breach under Section 2(u).

Review the policy every six months, because default settings and sub-processors change. If you want help to map where recorders, copilots and other AI tools touch personal data, start with a DPDP gap assessment, which includes this kind of tool inventory.

The duties of the Act apply from 13 May 2027, but the confidentiality risks already exist. Fixing the settings and the policy is a small piece of work by comparison, and it protects you from the more likely problem: a transcript in the wrong inbox.

Sources: Digital Personal Data Protection Act, 2023 (MeitY), Sections 2(i), 2(k), 2(t), 2(u), 2(za), 3(c)(i), 4, 6, 7(i), 8 and 16. Digital Personal Data Protection Rules, 2025 (G.S.R. 846(E)), Rules 3, 6, 7 and 8. Last reviewed 20 November 2026.

FAQ

Is it legal to use an AI note-taker in a meeting in India?

Yes, if you meet the DPDP Act's duties for the personal data it records. That means a lawful ground (consent or a legitimate use such as employment), a clear notice, a contract with the vendor, and deletion when the purpose is served. The Act does not mention recordings by name, so the application depends on the facts and should be reviewed by counsel. The core duties start on 13 May 2027.

Do I need everyone's consent to record a meeting with an AI tool?

Not always, but plan for it. The Act allows processing on consent or on a legitimate use, and "the purposes of employment" is one of those uses (Section 7(i)). That may cover some recordings of your own staff, but it does not obviously cover customers, candidates or suppliers. For them, give a notice and get a clear affirmative action, such as pressing a button to stay on a recorded call. Counsel should confirm the ground for each case.

Is the AI recorder vendor a Data Processor under DPDP?

Usually yes. A Data Processor is anyone who processes personal data on behalf of a Data Fiduciary (Section 2(k)). If the vendor records and stores meetings only on your instructions, it is your processor. You need a valid contract with it (Section 8(2)), and you remain responsible for what it does with the data (Section 8(1)). Check that training on your data is off and that its sub-processors are listed.

How long can I keep AI meeting recordings and transcripts?

Only as long as the specified purpose needs. Under Section 8(7), unless a law requires retention, you must erase personal data when consent is withdrawn or the purpose is no longer served, whichever comes first, and make your processor do the same. The Act sets no fixed period for recordings. A starting point we suggest is to delete the audio within 30 days and keep logs of access and deletion for one year, but Rules 6(1)(e) and 8(3) contain one-year retention duties, so confirm the audio period with counsel.

Which meetings should not be recorded by an AI tool?

At least calls with your lawyers, HR and disciplinary meetings, board and investor discussions, client calls under an NDA that bars third-party tools, and any call where Aadhaar, PAN, bank or health details are discussed. Decide this by meeting type in a written policy, and give hosts a quick way to pause or stop the recorder.

How do I stop unknown AI note-taker bots joining my calls?

Hold unknown participants in the meeting lobby, restrict third-party recording apps to an approved list on your meeting platform, and review which apps have OAuth access to calendars and mail in your identity provider. Remove unapproved note-takers, and give staff an approved tool so they have no reason to bring their own.

Find out where AI tools touch personal data in your company.