> For the complete documentation index, see [llms.txt](https://help.fielddoc.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.fielddoc.org/changelog/2026.md). # 2026 {% updates format="full" %} {% update date="2026-06-12" %} ## Updates to FieldDoc Legal Terms and Privacy Statement We updated the FieldDoc Terms of Service and Privacy Statement to better reflect how FieldDoc is used today and how the platform may grow over time. These updates also support the introduction of the FieldDoc Platform Master Service Agreement, which provides a common framework for organization-level subscriptions, applications, support, professional services, and related agreements. These updates are intended to make our documents clearer, more consistent, and better aligned across the FieldDoc Platform, including FieldDoc Data Manager, Groundwork, and other applications, modules, tools, and services that The Commons may make available. ### What changed #### We clarified that FieldDoc is a platform with multiple applications The updated documents now describe FieldDoc as the broader **FieldDoc Platform**, which may include FieldDoc Data Manager, Groundwork, and other applications or services. This helps explain how the same general terms apply across different FieldDoc tools, subscription tiers, program workflows, and service arrangements. #### We clarified user and organization responsibilities The Terms of Service continue to focus on individual user accounts, account security, user authority, Organization membership, acceptable use, platform conduct, and data responsibility. The updated Terms make clearer that users must have authority to use FieldDoc in connection with their Organization and that Organizations are responsible for managing their users, permissions, records, collaborators, and account responsibilities. #### We clarified how collaboration, Programs, Pacts, and exports work FieldDoc is a collaborative platform. The updated Terms and Privacy Statement provide clearer language about how data may be viewed, shared, exported, or made available through Organization permissions, workspaces, Programs, Pacts, integrations, dashboards, exports, and other platform features. The updates also clarify that FieldDoc permission settings may not control data after it has been exported, downloaded, transmitted, or shared outside the platform by an authorized user or recipient. #### We updated data responsibility, retention, and deletion language The updated documents provide clearer explanations of data ownership, user responsibility for data accuracy, deletion, account closure, backups, and retention. In particular, the updates clarify that deleting an individual user account does not necessarily delete Organization records, Program records, Pacts, Activities, files, metrics, reports, geospatial information, model outputs, or other records created or managed on behalf of an Organization or Customer. #### We updated privacy explanations The updated Privacy Statement better explains what information The Commons may collect, how we use it, how it may be shared, how long it may be retained, and what choices or privacy rights users may have depending on applicable law. The Privacy Statement also makes clearer that The Commons does not sell personal information or User, Organization, or Customer content, and does not use personal information or Customer Data for targeted advertising. #### We clarified third-party services, integrations, and professional services The updated documents better describe how FieldDoc may rely on or connect with third-party services, APIs, integrations, mapping tools, model APIs, hosting providers, support tools, and other systems. The Terms also clarify that professional services, such as onboarding, configuration, training, data migration, reporting support, GIS support, dashboard development, Digital Services, Data Concierge, and Conservation Concierge, are only included when expressly provided through a separate agreement or service arrangement. #### We introduced a public Master Service Agreement The FieldDoc Platform Master Service Agreement establishes baseline terms for organization-level subscriptions, applications, support, professional services, fees, usage limits, security, confidentiality, service changes, termination, and related responsibilities. Because FieldDoc may be used through different subscription tiers, applications, programs, order forms, statements of work, grants, or other written arrangements, the Master Service Agreement serves as a common foundation. More specific terms may apply through subscription documentation, application-specific terms, data processing terms, grant or program agreements, or negotiated customer agreements. ### What is not changing The Commons remains committed to operating FieldDoc as a mission-aligned platform for conservation, restoration, nature-based work, environmental data stewardship, reporting, collaboration, and related services. The Commons does not sell personal information or User, Organization, or Customer content. Users and Organizations continue to own or control the data they enter into FieldDoc, subject to applicable Program requirements, Pact relationships, collaboration settings, grant agreements, or other written agreements. ### What users should do Please review the updated Terms of Service, Privacy Statement, and, if applicable, the Master Service Agreement. Continued use of the FieldDoc Platform after the updated documents become effective means that you accept the updated Terms and acknowledge the updated Privacy Statement. If you have questions about these updates, please contact The Commons at . {% endupdate %} {% endupdates %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.fielddoc.org/changelog/2026.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.