February AIContract Templates

India · Business & partnerships

Data Sharing Agreement
Contract Template for India

Indian data sharing agreement defining permitted purpose, lawful authority, minimisation, security, onward disclosure, incident response and deletion.

Governing law: IndiaPublished templateUpdated 2026-10-12
DATA SHARING AGREEMENT
DATA SHARING AGREEMENT India Date: [date]. Disclosing Party: [full legal name, constitution, registration number and address] (Discloser). Receiving Party: [full legal name, constitution, registration number and address] (Recipient). The parties wish to share the dataset described in Schedule 1 for the Approved Purpose. Dataset means the data, documentation and permitted updates listed there. Personal Data means digital personal data about an identifiable individual. Approved Purpose means only the purpose stated in Schedule 1. 1. Conditions before sharing Before any transfer, each party must confirm its authority and lawful basis for its part of the sharing, complete Schedule 1, and provide or obtain any notice, consent, approval or permission required by law. The Discloser must not provide data it is prohibited from sharing. The Recipient must not ask the Discloser to collect or disclose unlawfully. The parties are independent for their respective decisions and compliance unless Schedule 1 expressly records another lawful relationship. This Agreement does not itself authorise a disclosure that applicable law forbids. 2. Permitted use The Recipient may use the Dataset only for the Approved Purpose during the Use Period. It must not use the Dataset for advertising, unrelated profiling, automated decisions about individuals, re-identification, contact of an individual, or development of another product unless Schedule 1 expressly permits that activity and it is lawful. Access is limited to the Recipient's personnel named by role in Schedule 2 who need it, are trained and are bound by confidentiality. The Recipient may create derived results only as described in Schedule 1. It must not disclose the Dataset or record-level derivatives to another person without the Discloser's written approval. 3. Quality and minimisation The Discloser will take reasonable steps to provide the Dataset in the agreed format and to identify known material limitations. Except for that promise, it does not warrant completeness or fitness for a conclusion the Recipient draws. The Recipient must use only fields reasonably necessary for the Approved Purpose and must not rely on the Dataset outside the stated context or limitations. The parties will use the correction and update process in Schedule 1. If either learns that data is materially inaccurate, excessive or unlawfully included, it must notify the other promptly and cooperate on correction, restriction or deletion. 4. Security Each party must maintain reasonable technical and organisational safeguards for the Dataset in its control. The Recipient must at least use access control, multi-factor authentication where appropriate, encryption in transit and at rest, secure configuration, logging, vulnerability management, protected backups, retention controls and trained personnel as detailed in Schedule 2. The Recipient must keep the Dataset logically separated from unrelated data unless Schedule 1 permits integration. It must not remove protections or transfer the Dataset to an unapproved location. It must review access at least every [three] months and revoke access promptly when no longer required. 5. Incidents and individual requests A party must notify the other without undue delay and within [24] hours after becoming aware of loss, unauthorised access, disclosure, alteration or misuse affecting the Dataset. The notice must include available details, likely consequences and containment measures. The parties must preserve evidence, cooperate on remediation and coordinate legally required notices. Each party will promptly assist the other with a request, grievance, investigation or correction concerning shared Personal Data. The party responsible under law will decide and issue the response. Neither party may make a public statement naming the other without prior consultation unless legally required. 6. Onward sharing and location The Recipient may use only approved service providers listed in Schedule 2. Each must be bound in writing to use the Dataset solely for the Approved Purpose, maintain equivalent protection and delete it when required. The Recipient remains responsible for them. Storage, remote access and any cross-border transfer must remain within the locations and safeguards in Schedule 2 and comply with restrictions then applicable under Indian law. 7. Rights and confidentiality No ownership transfers. The Discloser retains its rights in the Dataset; the Recipient retains its independently created tools and lawful aggregated results. The Discloser grants a non-exclusive, non-transferable, revocable right to use the Dataset only as this Agreement permits. Nothing grants a right to use a party's name or trade mark. Each party must protect the other's confidential information and use it only for this Agreement. This duty does not cover information lawfully public, previously known without restriction, independently developed or lawfully received from elsewhere. Required disclosure is permitted after notice where lawful. 8. Review, end and deletion The parties will review the sharing at the intervals in Schedule 3, including necessity, proportionality, accuracy, access, security and legal changes. Either party may suspend sharing immediately for a material security or legality concern. Either may terminate on [15] days' notice or immediately for an uncured material breach after [10] days' notice. At the end, the Recipient must stop use and within [30] days return or securely delete the Dataset and record-level derivatives, then confirm deletion. It may retain only what law requires, isolated and protected. Approved anonymised aggregate results that cannot reasonably identify a person may be retained if Schedule 1 permits. 9. Liability and general Each party is responsible for its breach and for persons acting for it. Liability is limited to [amount or basis], except for fraud, wilful misconduct, breach of confidentiality, unauthorised use or disclosure, or liability that cannot lawfully be limited. Notices must be sent to Schedule 3 contacts and take effect on proven receipt. Neither party may assign without consent except to a successor that assumes this Agreement. Changes must be signed. Counterparts and valid electronic signatures may be used, subject to applicable stamp and execution requirements. Indian law governs. Courts at [city, State/Union Territory] have exclusive jurisdiction, subject to mandatory law. SCHEDULE 1 - DATA AND APPROVED PURPOSE Dataset, source, format and transfer method: [details]. Approved Purpose, permitted users, operations and results: [details]. Lawful authority, notices or consents: [details]. Use Period, corrections, updates and limitations: [details]. SCHEDULE 2 - ACCESS, SECURITY AND PROVIDERS Authorised roles and locations: [details]. Security controls and access reviews: [details]. Approved providers and safeguards: [details]. Incident contacts: [details]. SCHEDULE 3 - GOVERNANCE Review dates and responsible representatives: [details]. Notice details: [details]. Liability amount or basis: [details]. SIGNED Discloser: [name, position, signature and date]. Recipient: [name, position, signature and date].

Licensed under CC BY 4.0. Attribution is required when you publish or redistribute this Template or an adapted version to the public. Attribution is not required merely because you use or adapt the Template for your own business or legal purposes, including preparing, negotiating, signing, or exchanging an agreement with a counterparty. License details.

More templates for India