Who Owns Your Data When You Cancel? The Export Window Nobody Checks

What usually happens to your data when you cancel?

A typical clause provides that on termination the customer may retrieve its data for a stated period, after which the vendor may delete it. Thirty days is common, shorter periods appear, and some agreements say nothing at all beyond permitting deletion. Some go further and cut off access on the termination date itself, leaving an export window that exists only on request through support.

Prompt deletion is not usually a punitive act. Vendors have their own retention and data minimisation obligations, and holding a departed customer's data indefinitely creates risk for them. The problem is not that they delete; it is that customers do not plan for it.

Read the definitions too. Customer Data may be defined to cover only what you uploaded, leaving out reports, dashboards, workflows and configuration you built inside the product. Those can represent months of work and are often the hardest things to recreate elsewhere.

Why does the export format matter so much?

A contract promising export in a commonly used format sounds adequate until you receive it. A dump of raw tables without the schema, or a set of CSV files that cannot reconstruct the relationships between records, technically satisfies the clause and is close to useless if you are migrating.

The specific question worth asking during evaluation is what an export actually looks like for your data, including attachments, audit trails, historical versions and anything the product generated rather than you uploaded. Ask to see a sample export before you sign. It is a reasonable request and surprisingly revealing.

If the records may be needed as evidence, the format question extends further. Electronic records produced in court generally need a certificate under Section 63 of the Bharatiya Sakshya Adhiniyam, 2023, which replaced the Indian Evidence Act from 1 July 2024. Exports that keep metadata, timestamps and audit logs are much easier to support with such a certificate than a spreadsheet re-typed later.

Your own record-keeping duties do not end with the contract

Many SaaS tools hold records that Indian law requires you to keep. The vendor's thirty-day deletion right does not reduce your retention period, so the export is how you meet it. The table sets out common examples; check the specific periods with your chartered accountant or company secretary, and note that State rules under the Labour Codes vary.

The DPDP overlay

Where the data includes personal data, the Digital Personal Data Protection Act, 2023 expects the data fiduciary to erase personal data once consent is withdrawn or the purpose is no longer served, and under Section 8(7) to cause its data processor to erase it too, unless retention is required by law. So deletion and return on termination is a term the contract should address in any event as part of allocating processor obligations.

That gives you a second reason to raise it, and it aligns your commercial interest in getting your data out with a compliance reason the vendor will recognise. It also means silence is a gap rather than a neutral position. A contract that says nothing about what happens to personal data on termination has not allocated an obligation that the framework expects to be allocated. Most of these obligations are scheduled to apply from 13 May 2027 under the DPDP Rules, 2025.

The two duties fit together: export what you are legally required or entitled to keep, then require the vendor to delete its copies and certify that it has done so.

A worked example

A Mumbai distributor pays ₹2.4 lakh a year for a cloud billing and inventory tool and decides to move to a new ERP. The contract allows thirty days after termination to export, then deletion. It gives notice on 1 June; the term ends 30 June; the window closes 30 July.

On 10 July the team runs the export and finds that invoices come out as CSV rows without the PDF tax invoices, the e-way bill references are missing, and credit notes are not linked to the original invoices. Six years of records are involved, and the new ERP cannot import them as they are. The vendor offers a full export with attachments as a paid service at ₹1.5 lakh, delivered in three weeks, close to the deadline.

Had the distributor asked for a sample export at signature, and written 'complete export including all attachments, at no additional charge' into the contract, the cost and the scramble would have been avoided.

What to negotiate

• An export window of at least 30 days after termination, and 60 to 90 days for data-heavy systems such as accounting, ERP and HR.
• Export in a documented, machine-readable format, with the schema, attachments and audit trail.
• Read-only access during the export window, so you can verify completeness.
• Vendor assistance with migration, at a defined rate rather than at its discretion.
• Confirmation that export is available even where termination follows non-payment or a dispute.
• Notice before deletion, so the window cannot close silently.
• A deletion certificate after the window closes, covering backups within a stated period.

Sample clause wording

A buyer-friendly clause reads: 'For sixty days after termination or expiry for any reason, Vendor shall provide Customer with read-only access to the Services and, on request, a complete export of Customer Data, including attachments, metadata and audit logs, in [CSV/JSON] format with a schema description, at no additional charge. Vendor shall not delete Customer Data during this period. Within thirty days after this period ends, Vendor shall delete Customer Data, including copies held by sub-processors, except where retention is required by law, and certify deletion in writing.'

How do you leave a SaaS tool cleanly, step by step?

• Three months before the term ends, read the termination, export and deletion clauses again and note every deadline.
• Run a full test export and check it against your record-keeping needs, including attachments and audit trails.
• Give non-renewal or termination notice exactly as the notices clause requires.
• Set up the new system and import the test export, so gaps show up while the old tool is still live.
• Take the final export in the last week of service, and a second one during the post-termination window if records changed.
• Store exports securely, with access limited to the people who need them, and record what was exported and when.
• Request deletion and the deletion certificate once you have confirmed the export is complete.
• Remove the vendor's integrations, API keys and single sign-on access on your side.

What if the vendor shuts down?

Termination by you is the planned scenario. The unplanned one is a vendor that stops trading, is acquired and sunsets the product, or enters insolvency proceedings. In those cases the export window in the contract may be of little practical help.

Two protections work. The first is contractual: a commitment to give a stated notice period, such as ninety days, before discontinuing the service, with export rights during it. The second is operational: regular exports of critical data on your own schedule, so you are never fully dependent on the vendor at the moment it fails.

If a vendor enters insolvency proceedings, a moratorium and the control of an insolvency professional can slow down every request, including requests for your data, even though the data is yours. For business-critical systems, larger buyers sometimes negotiate a right to receive automated exports to their own storage, or escrow of data and documentation with a third party. For most small businesses, a monthly export of the records you cannot afford to lose, stored on your own systems, achieves most of the same protection at almost no cost.

A practical habit

For any system holding data you would not want to lose, run an export while you are still a customer and check that you can actually read and use it. That takes an afternoon, it tests the clause rather than trusting it, and it is far better done now than during a migration under notice. Repeat it once a year, and keep the exports in your own storage with access controls.

If the export turns out to be unusable, you have discovered that while you still have a relationship and leverage, which is the entire point.