Last updated: May 1, 2025
Subject to a valid subscription, FormGrid grants a limited, non-exclusive right to access and use the software for legitimate form-building and response-collection workflows within the purchased plan. The license follows the capabilities and limits shown for that plan.
The form owner retains rights in the forms they create and the response data collected through those forms, subject to the permissions necessary for FormGrid to host, store, route, present, and export the information. FormGrid does not claim ownership of the underlying respondent data.
Response data belongs to the form owner. We never sell or mine your respondents' data. The owner is responsible for determining what information to request, providing required notices, and choosing a lawful purpose for collection.
Access follows the active subscription. Plans renew monthly unless cancelled. A cancellation made in account settings has no cancellation fee and normally continues through the current billing period.
You may not use the service to collect spam lists, harvest email addresses for unsolicited marketing, conduct unlawful surveillance, or otherwise violate applicable law. Payment or sensitive-information fields should be configured only when the owner has an appropriate collection purpose.
Your license remains subject to the stated form, response, field, logic, integration, branding, and seat limits. Attempting to bypass those controls or presenting a limited feature as unlimited to respondents is not permitted.
Where export features are provided, the form owner may use them to preserve response records outside the service. The license ends when the subscription ends or access is terminated under the service terms.
The EULA can be updated when the software or legal framework changes. The Last updated date identifies the version published on the site, and material terms should be reviewed before a production rollout.
The license is intended to keep commercial scope visible while a workspace grows. Review form capacity, response allowance, integrations, branding requirements, and seat count before publishing a collection workflow. When those needs change, use the account plan controls rather than bypassing the stated capabilities.