← Blog

Guides

How to Export Attendee Data Safely in India

Abhinavtej ReddyNovember 21, 20266 min read

To export attendee data safely, take only the fields you need, store the file encrypted with access limited to named people, log who opens it, and delete it once the event purpose is over. India's Digital Personal Data Protection Act requires safeguards at every stage of processing, and the fiduciary stays responsible even when a third party handles the data [1]. The detailed minimum measures under Rule 6 and the breach duties under Rule 7 start on 13 May 2027 [5]. Penalties for weak security are large [2], so it makes sense to build the habit now.

What the law expects

The Act asks for safeguards that match the type of data and the risk it carries [1]. Attendee lists usually contain names, phone numbers, email addresses and payment details. Some events also collect ID uploads through custom registration questions. That puts an export well above a harmless spreadsheet.

As summarised by Lexology, Rule 6 sets out minimum measures: encrypting or tokenising personal data, access controls, logs of access, backups for continued processing, and equivalent safeguards written into contracts with processors [3]. A vendor summary lists much the same set, including masking and obfuscation [7]. We have not checked the primary rule text, so treat these as summaries.

DutyWhat it means for an exportSource
Security safeguardsEncrypt or tokenise the file, restrict who can open it, keep access logs[3]
Breach noticeNotify the Board within 72 hours, and affected people without delay, per one vendor summary[4]
ErasureErase data when consent is withdrawn or the specified purpose expires[8]
PenaltiesUp to Rs 250 crore for weak safeguards, up to Rs 200 crore for failing to notify a breach[2]

The Act also takes a stricter approach to children's data. If some attendees are minors and need guardian consent, the export needs extra care [3].

A safe export routine

  1. Write down the purpose first. Say why you need the file: check-in, a refund run or a sponsor report. If you cannot name a purpose, you probably should not export it.

  2. Cut the fields down. Most purposes need a name, a ticket type, a registration status and a check-in flag. Phone numbers and email addresses are for specific messages only. Leave out ID uploads and answers to sensitive questions unless a named person needs them.

  3. Start from the platform's own exports. Unifesto's CSV export covers per-event financials, with collected amounts, fees, refunds and net figures. Check inside the app what an attendee export contains before you build a process around it. Organisers can find the tools at /organisers.

  4. Store it encrypted, with named access. Keep the file in one restricted folder, protected with a password or encryption. Share the link only with people on the purpose list. Do not leave copies on personal laptops or phones longer than the task needs.

  5. Never send it to a broad group. A file posted in a large WhatsApp group reaches every member, including people who have left the club. Send it only to a named person. Use a fresh, time-limited link rather than an attachment that lives on in old chats.

  6. Keep a log. Note who exported the file, when, why and who received it. CERT-In's directions require enabling logs of ICT systems and keeping them for a rolling 180 days within Indian jurisdiction, if those directions apply to you [6]. If they do not, a simple log still makes later questions far easier to answer.

  7. Delete on time. When the event and its refund window close, delete the export and any copies. Erasure is a legal duty once the purpose expires [8].

Where the risk sits

Most leaks come from handling, not from the platform. The usual problems are a file left on a shared drive, an old volunteer who still has access, or a CSV emailed to a sponsor who did not need the phone numbers.

Handovers cause trouble too. When the team changes, export habits change with it. Keep records and logins with the club, not with one person, so no access is left orphaned. Our guide to handing a college club to next year's team covers the order of that move.

If the export goes to a foreign form, a ticketing tool or a cloud sheet hosted abroad, check the transfer rules. Rule 15 allows transfers of personal data outside India, which matters for those tools [9]. Read the tool's terms before you upload anything.

The check-in stage creates its own data. If you scan passes at several gates, the attendance records need the same care as the export. Our piece on checking in 2,000 people without long queues explains how to run several scan points without losing control of the list.

If something leaks: the reporting clocks

A personal data breach is any unauthorised or accidental compromise of confidentiality, integrity or availability. It needs prompt notice to the Board and the affected people [1].

CERT-In's directions of 28 April 2022 require covered entities to report listed incidents within 6 hours of noticing them or being told of them. Reports go by email to incident@cert-in.org.in, by phone or by fax [6]. The listed incidents include 'Data Breach' and 'Data Leak' as separate items [6]. Non-compliance can invite punitive action under section 70B(7) of the IT Act [6].

Whether a student society counts as a covered 'body corporate' is unclear. We found no source that settles it, so ask your college office or a lawyer before you assume either way. Meanwhile, a written leak plan with named people and phone numbers will save time once the clock starts.

Our view

Our view: a club should not download the full attendee list by default. Give the few people who need it a filtered view, and export only when a specific task requires the file.

The limits of this advice

We could not find platform-specific export steps for any form tool or ticketing system, so the routine above is general. The Rule 6 and Rule 7 points come from law-firm and vendor summaries, because we could not open the official rules directly. The sources also give different dates for some steps. Nothing here is legal advice. For the wider picture of how the Act applies to club registrations, read what the DPDP Act means for college event organisers.

FAQ

Do the DPDP security rules apply to my club's export today?

The detailed security safeguards under Rule 6 and the breach duties under Rule 7 start on 13 May 2027, according to one source [5]. The general duty to safeguard personal data already exists in the Act, so follow the routine now.

Can I send the attendee list to a sponsor?

Only if attendees agreed to that purpose and the sponsor needs the specific fields. Share a reduced list through a time-limited link, and record what you sent and why.

How long should I keep an attendee export?

Delete it once the purpose has expired, such as after the event and its refund window close. Erasure is required when consent is withdrawn or the purpose expires [8].

What do I do if a file goes to the wrong person?

Record what was sent, to whom and when, then follow your leak plan. If CERT-In's directions apply to you, the 6-hour reporting clock starts when you notice the incident [6].

Sources

  1. DPDP Act 2023 and DPDP Rules 2025: Compliance Guide: https://www.ey.com/en_in/insights/cybersecurity/decoding-the-digital-personal-data-protection-act-2023
  2. DPDP Rules, 2025 Notified A Citizen-Centric Framework for Privacy Protection: https://static.pib.gov.in/WriteReadData/specificdocs/documents/2025/nov/doc20251117695301.pdf
  3. India’s New Digital Privacy Law: The DPDP Act and Rules Explained - Lexology: https://www.lexology.com/library/detail.aspx?g=f4b2877e-a81b-4286-bdbf-77c4d9fd0807
  4. DPDP Rules 2025, Phased Rollout and Data Fiduciary Duties: https://veritect.ai/digital-data-ai-law/dpdp-rules-2025-phased-rollout
  5. DPDP Security Obligations: None In Force Until 2027 - BitScore: https://www.bitscore.in/resources/dpdp-act-security-obligations-for-data-fiduciaries
  6. Page 1 of 8 No. 20(3)/2022-CERT-In Government of India Ministry of Electronics: https://www.cert-in.org.in/PDF/CERT-In_Directions_70B_28.04.2022.pdf
  7. DPDP Rules 2025 Explained for Data Fiduciaries: https://www.progressive.in/blog/dpdp-rules-2025-explained/
  8. Understanding India’s New Data Protection Law: https://carnegieendowment.org/research/2023/10/understanding-indias-new-data-protection-law
  9. India’s Digital Personal Data Protection Act 2023 brought into force: https://www.hlc.com/en/publications/indias-digital-personal-data-protection-act-2023-brought-into-force-