Security and privacy resources

Make trust part of the form, from the first question.

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

Illustration of a teal ribbon connecting incoming response cards, an organized stack and a completed task.

Build with care

Four decisions to make before collecting responses

Collect with a purpose

For each field, identify the decision it supports. Make optional details clearly optional and explain why identifying information is needed.

Know who needs access

Assign a form owner and identify the people who need to review responses. Review workspace permissions when responsibilities change.

Review each destination

A connected spreadsheet, inbox or other service creates another place where data is handled. Check destination access and test field mappings with synthetic data.

Set a retention routine

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

Find the information your team needs

Prepare a useful review

Bring specific requirements to the conversation.

If your organization has security, contractual or regulatory requirements, document the exact workflow and request current evidence before choosing a configuration.

AreaWhat to clarifyWhat to request
Data handlingWhat information will be collected, where will it go, and who will access it?Current documentation for the intended service and connected destinations.
Account controlsWhich 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 retentionWhat location, retention, backup and deletion requirements apply to this workflow?Current service details and contractual commitments that address those requirements.
Independent assuranceDoes 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.

Give respondents a clear explanation.

Trust is easier to build when people understand the request and the next step.

  • Identify who is asking and why.
  • Explain how the response will be used.
  • Distinguish required answers from optional context.
  • Provide a relevant contact or support route.
  • Review the privacy notice before publishing.

Common questions

Does a form template establish compliance?

A template is a starting point for questions. Your data, configuration, connected tools and organizational requirements need their own review before use.

Where can I ask about specific security requirements?

Use the help and support resources to describe the workflow and request current documentation. Include the controls or agreements your team needs to evaluate.

How should I test a sensitive workflow?

Use synthetic information during evaluation. Verify access, destinations and retention requirements before collecting real responses.