Are electronic signatures legally valid?

Yes. Electronic signatures executed with intent and retained in a reproducible record are generally enforceable under the ESIGN Act (15 U.S.C. ch. 96) and state UETA laws, subject to statutory exceptions.

Do I need a HIPAA addendum?

If shared GIS data contains protected health information, include a HIPAA Business Associate Agreement and specify handling, encryption, and breach notification consistent with 45 CFR Part 164.

How should metadata be handled?

Require complete, machine-readable metadata (fields, CRS, temporal extent, lineage) as an exhibit. Metadata ensures usability and reduces disputes over data interpretation.

Can I revoke access after signing?

Yes, if the agreement includes revocation or termination clauses. Specify notice periods, post-termination access, and obligations to return or destroy copies.

What about cross-jurisdictional issues?

State privacy laws and the choice of governing law affect enforcement. New York uses ESRA; most states adopt UETA. Identify governing law and dispute resolution in the agreement.

How do I correct an error after signing?

Use an amendment or corrected exhibit signed by both parties. Document the change, update hashes or checksums for datasets, and retain both versions for audit purposes.

Electronic Signature
Templates
Miscellaneous
GIS Data Sharing Agreement

GIS Data Sharing Agreement

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

GIS Data Sharing Agreement

This GIS Data Sharing Agreement ("Agreement") is entered into as of by and between ("Provider") and ("Recipient").

WHEREAS

WHEREAS, Provider maintains geographic information system (GIS) datasets and related metadata necessary for planning, operations, or service delivery, and has authority to distribute specified datasets under the terms of this Agreement; and

WHEREAS, Recipient requires access to certain GIS datasets for the purpose of and shall use such data in accordance with the terms and restrictions set forth herein; and

WHEREAS, the parties desire to define the terms and conditions under which GIS data will be provided, used, maintained, and protected.

SCOPE OF WORK

Provider will deliver the datasets and associated documentation described below to Recipient. Provider agrees to provide data in accordance with the standards and schedule specified in this Agreement.

Project Name Datasets and Deliverables Standards, Formats, and Metadata

PAYMENT TERMS

Recipient shall compensate Provider for data preparation, delivery, and maintenance as follows.

Total Fee Payment Schedule Late Payment

Any overdue amount shall accrue interest at the rate of or the maximum rate permitted by law, whichever is less. Recipient is responsible for all collection costs and reasonable attorney fees incurred in enforcing payment obligations.

TERM AND TERMINATION

This Agreement commences on and continues until unless earlier terminated in accordance with this Section.

Notice Period for Termination

Either party may terminate this Agreement for material breach if the breaching party fails to cure such breach within the notice period set forth above. Provider may suspend data access upon nonpayment after providing written notice and a 10-day opportunity to cure.

CONFIDENTIALITY

Data designated in writing by Provider as Confidential shall be treated as confidential by Recipient. Recipient shall not disclose Confidential Data to third parties except as expressly permitted in this Agreement or with Provider's prior written consent. Recipient shall implement administrative, technical, and physical safeguards appropriate to the sensitivity of the Confidential Data to prevent unauthorized access, disclosure, alteration, or destruction.

Confidential Designation Procedure

DATA USE, OWNERSHIP, AND LICENSE

Provider retains all ownership and intellectual property rights in the datasets and underlying materials. Provider grants Recipient a non-exclusive, non-transferable, limited license to use the Data solely for the Permitted Uses described below and subject to the restrictions stated in this Agreement.

Permitted Uses Prohibited Uses

DATA SECURITY AND MAINTENANCE

Recipient shall implement and maintain reasonable security measures to protect the Data, consistent with industry best practices and applicable legal requirements. Recipient shall promptly notify Provider upon discovery of any actual or suspected unauthorized access, disclosure, or loss of Data and shall cooperate in any mitigation and remediation efforts.

Update and Maintenance Schedule

AUDIT, RECORDS, AND COMPLIANCE

Provider may, upon reasonable notice and during regular business hours, audit Recipient's use of the Data to verify compliance with this Agreement. Recipient shall retain records of Data use and dissemination for a minimum of years and shall make such records available upon request.

LIABILITY, INDEMNIFICATION, AND INSURANCE

Provider makes no warranty as to the accuracy, completeness, or fitness for a particular purpose of the Data. To the maximum extent permitted by law, Provider's liability arising from this Agreement is limited to direct damages not to exceed the total fees paid under this Agreement in the twelve (12) months preceding the claim. Neither party shall be liable for consequential, incidental, special, or punitive damages.

Indemnification Insurance Requirements

NOTICES

All notices required or permitted under this Agreement shall be in writing and delivered to the parties at the contacts set forth below.

Provider Notice Contact Provider Notice Address Recipient Notice Contact Recipient Notice Address

GOVERNING LAW & ENTIRE AGREEMENT

This Agreement shall be governed by and construed in accordance with the laws of without regard to conflict of laws principles. This Agreement constitutes the entire agreement between the parties with respect to the Data and supersedes all prior and contemporaneous agreements, understandings, and representations, whether oral or written.

MISCELLANEOUS

No waiver of any breach of this Agreement shall be deemed a waiver of any subsequent breach. If any provision of this Agreement is held invalid or unenforceable, the remaining provisions shall remain in full force and effect. Neither party may assign this Agreement without the other party's prior written consent, except to a successor in interest in connection with a merger or sale of substantially all assets.

Additional Provisions or Special Conditions

Provider - Printed Name:

By:

Date:

Recipient - Printed Name:

By:

Date:

What a GIS Data Sharing Agreement Covers

A GIS Data Sharing Agreement is a legally binding contract that defines how geospatial datasets, associated metadata, and derivative products are exchanged, used, and protected between parties. It sets scope, permitted uses, access levels, formats, retention, attribution, and liability for data providers and recipients. The agreement addresses technical details (file formats, coordinate systems), operational rules (provisioning, updates), and compliance obligations (privacy, security, intellectual property) so both parties understand rights and responsibilities before data is transmitted or published.

Why a Formal Agreement Matters for Shared GIS Data

A clear GIS Data Sharing Agreement reduces ambiguity about permitted uses, limits legal risk, documents security controls, and preserves data provenance. It helps protect sensitive information, ensures compliance with federal and state privacy rules, and establishes procedures for updates, corrections, and dispute resolution.

Who Typically Signs a GIS Data Sharing Agreement

Typical signers include public agencies and private organizations that collect, manage, or consume geospatial data.

Local government GIS departments and planning agencies managing authoritative spatial datasets for public use and interagency exchange.
Utility and telecom companies sharing network maps, asset locations, or as‑built drawings for operations and emergency response.
Real estate, engineering, and environmental firms that exchange parcel, survey, and site condition data during transactions and projects.

Parties should confirm authorized signatories and any organizational approval steps before executing the agreement.

Core Clauses to Include in a Professional GIS Data Sharing Agreement

A complete agreement balances technical detail with legal clarity so recipients can reliably use shared datasets while providers retain necessary protections.

Parties

Identify full legal names and contact information for data provider, recipient, and any custodians or stewards responsible for data management and dispute notices.

Data Description

Define datasets, layers, coordinate reference systems, file formats, versioning rules, and required metadata to ensure compatibility and reproducibility.

License Terms

Specify permitted uses, redistribution rights, derivative works rules, attribution requirements, commercial restrictions, and duration of the license.

Security Controls

State access levels, authentication methods, encryption standards, breach notification duties, and any handling restrictions for sensitive or regulated data.

Quality & Update Rules

Set accuracy tolerances, refresh schedules, error correction procedures, and responsibilities for corrective action when datasets are found inaccurate.

Liability

Allocate risk with indemnities, disclaimers of warranties, limitation of damages, and insurance requirements appropriate to data sensitivity and value.

Step-by-Step: Preparing and Executing the Agreement

Follow these sequential steps to prepare, review, and finalize a GIS Data Sharing Agreement with clarity and compliance.

01

Inventory Data: List datasets, schemas, and sensitive attributes for review.
02

Define Terms: Draft license, access, and metadata requirements aligned with policy.
03

Security Review: Confirm encryption, authentication, and breach procedures.
04

Execute Signatures: Obtain authorized signatures and distribute executed copies.

Configuring an Online Workflow for the Agreement

When building a digital workflow, set authentication, routing, and retention rules before sending to signers.

Field	Configuration
Authentication	Email token or SMS code; consider MFA for sensitive data
Access Controls	Role-based permissions and time-limited links
Metadata Requirements	Attach schema and README as required exhibits
Audit Trail	Capture IP, timestamp, and action logs

Technical and Security Requirements for eSubmission

Use a platform that supports strong transport and storage security, flexible authentication, and exportable audit logs.

Security: TLS 1.2/1.3 in transit; AES-256 at rest
Integrations: Connectors for GIS repositories and cloud storage
Formats: PDF, DOCX, and GIS formats such as GeoJSON and shapefile

Ensure any chosen vendor can supply a Business Associate Agreement for HIPAA or attestations for SOC 2 / ISO 27001 when required.

Where to Send and How to Route the Executed Agreement

Map routing so final copies reach legal, data stewards, and archival storage after signatures are complete.

Upload Master: Store executed PDF and original source data manifest
Distribute Copies: Send executed copies to provider, recipient, and legal counsel
Register Access: Provision accounts or tokens based on agreed access level
Archive: Place final agreement into secure records management

Typical Timelines and Service Expectations

Set explicit timing for each operational step so access and compliance obligations are measurable and auditable.

Response Time:

Provider acknowledges request within 5–10 business days

Access Provisioning:

Grant access within 10 business days after execution

Data Refresh:

Define refresh frequency (monthly, quarterly, annually)

Review Cycle:

Schedule annual contract and data quality review

Notice Period:

Specify termination or amendment notice (e.g., 30 days)

Common Mistakes to Avoid When Preparing the Agreement

Using vague data descriptions that omit CRS, extents, or file formats, which leads to incompatibility and disputes.
Failing to assign explicit access roles and authentication methods, creating security gaps or unauthorized access.
Omitting metadata requirements or provenance statements, which undermines reproducibility and legal attribution.
Neglecting to document breach notification procedures and timelines required by privacy or industry regulations.

Primary Risks and Potential Consequences

Breach Liability: Civil exposure and contractual damages

Regulatory Risk: Fines for privacy violations under state or federal law

Data Loss: Operational disruption and restoration costs

Injunctions: Court orders to cease use or distribution

Reputation: Loss of trust among partners and users

Indemnity Costs: Defense and settlement obligations

Comparing eSignature Providers for Executing the Agreement

Basic pricing and capability points to consider when selecting an eSignature vendor for GIS Data Sharing Agreements.

	signNow	DocuSign	Adobe Sign	PandaDoc	HelloSign
Starting Price	$8/user/mo	$15/user/mo	$14/user/mo	$19/user/mo	$15/user/mo
Free Trial	7-day free trial	Yes, limited trial	Yes, limited trial	Yes, limited trial	Yes, limited trial
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No
Envelope Cap	No envelope cap	100 envelopes/user/year	Varies by plan	Varies by plan	Varies by plan

Common Questions About GIS Data Sharing Agreements

Answers to frequent questions about enforceability, privacy, versioning, and revocation to help resolve common execution issues.

Need help? Contact support

Are electronic signatures legally valid?
Yes. Electronic signatures executed with intent and retained in a reproducible record are generally enforceable under the ESIGN Act (15 U.S.C. ch. 96) and state UETA laws, subject to statutory exceptions.
Do I need a HIPAA addendum?
If shared GIS data contains protected health information, include a HIPAA Business Associate Agreement and specify handling, encryption, and breach notification consistent with 45 CFR Part 164.
How should metadata be handled?
Require complete, machine-readable metadata (fields, CRS, temporal extent, lineage) as an exhibit. Metadata ensures usability and reduces disputes over data interpretation.
Can I revoke access after signing?
Yes, if the agreement includes revocation or termination clauses. Specify notice periods, post-termination access, and obligations to return or destroy copies.
What about cross-jurisdictional issues?
State privacy laws and the choice of governing law affect enforcement. New York uses ESRA; most states adopt UETA. Identify governing law and dispute resolution in the agreement.
How do I correct an error after signing?
Use an amendment or corrected exhibit signed by both parties. Document the change, update hashes or checksums for datasets, and retain both versions for audit purposes.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now