Collect with a purpose
For each field, identify the decision it supports. Make optional details clearly optional and explain why identifying information is needed.
Security and privacy resources
Start with a clear purpose for the data you collect. Review access, connected tools and retention alongside the respondent experience so your team knows how the information will be used.
Start free · Preview your flow · Choose a plan around your needs

Build with care
For each field, identify the decision it supports. Make optional details clearly optional and explain why identifying information is needed.
Assign a form owner and identify the people who need to review responses. Review workspace permissions when responsibilities change.
A connected spreadsheet, inbox or other service creates another place where data is handled. Check destination access and test field mappings with synthetic data.
Decide how long records are useful and who handles exports, access requests or removal. Include copies and connected destinations in that routine.
Review the details
Prepare a useful review
If your organization has security, contractual or regulatory requirements, document the exact workflow and request current evidence before choosing a configuration.
| Area | What to clarify | What to request |
|---|---|---|
| Data handling | What information will be collected, where will it go, and who will access it? | Current documentation for the intended service and connected destinations. |
| Account controls | Which roles, authentication methods and account-management controls are required? | A demonstration of the controls available for the plan and workspace you will use. |
| Storage and retention | What location, retention, backup and deletion requirements apply to this workflow? | Current service details and contractual commitments that address those requirements. |
| Independent assurance | Does the organization require a particular audit report, certification or agreement? | The current document, its scope and validity, and confirmation that it covers the intended service. |
This page provides a review checklist. It does not establish certification or suitability for a regulated use case. Confirm current evidence and contractual requirements with the relevant team.
Trust is easier to build when people understand the request and the next step.
A template is a starting point for questions. Your data, configuration, connected tools and organizational requirements need their own review before use.
Use the help and support resources to describe the workflow and request current documentation. Include the controls or agreements your team needs to evaluate.
Use synthetic information during evaluation. Verify access, destinations and retention requirements before collecting real responses.