LogoLogo
Back to studio
  • Formsort documentation
  • ⏩Quickstart
    • 🟒Get started with Formsort
    • 🍎Core concepts
    • ℹ️Question and content reference
    • πŸ“•Key terms
    • 🏞️Create your first flow
    • πŸ“–Add content and collect answers
      • 🀳Capture demographic data
      • ℹ️Add informational content
      • πŸ” Review your variable schema
    • 🎨Create a theme
      • Set brand guidelines
    • 🀹Personalize your flow
      • 🌟Template your variables
      • 🧠Add conditional logic
      • πŸ’«Using conditional logic with Calculated and API variables
      • πŸ”šEnd the flow
    • πŸ”€Set up integrations
    • πŸš€Go live
      • Auditing your flow for content, functionality, and design
    • πŸ’ΌCommon use cases
      • πŸ’”Disqualify responders
      • πŸ—“οΈAdd a scheduling option
      • πŸ“„Allow responders to read and accept your company policies
  • πŸ—οΈBuilding flows
    • Flows and variants
      • Flow starts
    • Adding content
      • Groups
      • Steps
        • Settings
        • Logic
        • Style
      • Questions
        • General Settings
        • Style
        • Address
        • Comparison
        • Confirmation
        • Date
        • Date & Time
        • Email address
        • File upload
        • Grid choice
        • Iframe
        • Image upload
        • Number
        • Payment
        • Phone number
        • Postal code
        • Question group
        • Region
        • Select
          • Providing choices via API or calculation
        • Signature
        • SSN
        • Text questions
        • Yes/No
      • Content
        • General Settings
        • Statement
        • Image
        • Video
        • Next button
        • Divider
        • Map
      • Endings
      • Using markdown
      • Using variable templating
        • Template formatting functions
      • Copy-pasting form content
      • Content library
    • Conditions and logic
      • Logical operator reference
      • Advanced logic
    • Variables (answers)
      • Variables from questions
      • Externally provided variables
      • Calculated variables
      • API lookups
      • System Library variables
      • Orphaned variables
    • Schemas
      • JSON Schemas
      • Validating flow schemas
    • Redirects
    • Styling and themes
      • CSS Reference
      • Overriding theme styling
      • Custom CSS overrides
      • Content area
      • Animations and transitions
      • Form Layout
      • Typography
        • Adobe Fonts
        • Hosting custom fonts
      • Color variables
      • Dimension variables
      • Question containers
      • Assets
      • Form Buttons
        • Select buttons
      • Inputs and dropdowns
      • Checkmarks
      • Tables
      • Sliders
      • Divider lines
      • Progress bar
      • Comparison cards
    • Variant settings
      • Form behavior for returning responders
      • Group ranking API
    • Publishing and versions
      • Preview window
      • Deploying
      • History
  • πŸ’ΎHandling data
    • Philosophy and data retention policy
    • Viewing form answers
    • Responder UUIDs
    • Environments
      • Loading different environments
    • Passing data in
      • URL parameters
      • POST body
      • Embed query parameters
    • Custom validators
    • Form answers and events
      • Analytics events
      • Signed requests
      • Event payload shape
      • Submission frequencies
      • Runtime error reporting
      • Admin API
      • Flow content data format
    • Integration reference
      • Amplitude
        • Amplitude cross domain tracking
      • BigQuery
      • FullStory
      • Google Analytics
        • Updating from Universal Analytics to GA4
      • Google Cloud Storage
      • Google Sheets
      • Google Tag Manager (GTM)
        • JavaScript triggered by flow events
      • Hubspot
      • Jornaya
      • Optimizely
      • PostgreSQL
      • Redshift
      • Rudderstack
      • S3
      • Salesforce
      • Segment
        • Segment Setup
        • Segment cross domain tracking
      • Stripe
      • TrustedForm
      • Webhooks
        • Zapier
  • πŸ“ΊGoing live
    • Custom domains
    • Built-in analytics
    • Embedding
      • Web-Embed API
        • React-embed
      • Adding authentication
      • Embedding forms in iOS and Android
      • Setting up a dev environment
    • Split testing
    • Preflight checklist
  • 🏒Teams
    • Accounts
      • Roles and permissions
    • Events subscriptions
    • Workspace domain detection
Powered by GitBook
On this page
  • How Formsort stores answers
  • Returning responders and response storage
  • Downloading answers
  • Archiving answers
  • Managing answer access with user groups and access policies
  • Email notifications for form answers
  • Data security and retention

Was this helpful?

  1. Handling data

Viewing form answers

Formsort securely stores form answers, allowing you to view, manage, and download them from the responses table. Responses are encrypted and stored in compliance with HIPAA standards.

PreviousPhilosophy and data retention policyNextResponder UUIDs

Last updated 1 month ago

Was this helpful?

How Formsort stores answers

All answers, including partial ones, are automatically saved and accessible from the Responses tab in the Formsort dashboard. Once a responder starts filling out a form, their answers are saved by default, even if they don’t finish the form (moving it to a finalized state).

Answers cannot be deleted from this table but can be archived to remove them from the active response view.


Returning responders and response storage

The responses table shows the latest answer set for a specific responder_uuid. As a result, answers are saved and displayed depending on your flow settings.

You can control whether returning responders' answers overwrite previous responses, create new responses, or are blocked from submitting again.

  • Replace previous responses with new answers

    • Enable "Restart once flow completed" and disable "Start each session as a new responder."

    • Each time a responder returns, their new answers overwrite the previous response.

  • Save each new session as a separate response

    • Enable both "Restart once flow completed" and "Start each session as a new responder."

    • A new responder_uuid is assigned for each session, storing submissions separately without overwriting previous responses.

  • Prevent responders from submitting again

    • Disable both "Restart once flow completed" and "Start each session as a new responder."

    • Once a responder completes the form, their response remains stored, and they cannot submit another.

These settings determine how responses appear in your responses table and how new or returning responders’ data is recorded.


Downloading answers

Answers can be downloaded in CSV format. If no specific answers are selected, all answers for the flow will be included in the download.


Archiving answers

If an answer is no longer needed in the active view, it can be archived. Archiving removes answers from the default table view while keeping them stored securely.


Managing answer access with user groups and access policies

Email notifications for form answers

You can receive email notifications when new responses are submitted. Choose from two options:

  • Every response – Receive an email immediately when a form is completed.

  • Daily summary – Get a single email at 5 PM UTC with a summary of all responses from the day.

Email notifications help you stay updated on new submissions without manually checking the Responses table.

Notifications are sent to Formsort users, not form responders. These emails are meant for your internal team and will not be sent to the person filling out the form.

Notifications include a link to view the response in the Formsort dashboard. A Formsort account is required to access the response data.

Notifications are only available for responses stored in Formsort. If your account is configured to opt out of data storage, you will not receive email notifications.

Data security and retention

All stored responses are encrypted and comply with HIPAA standards. Formsort does not delete responses, but users can manage response access and visibility through archiving.

Enterprise users can disable response storage - Formsort will not store your form responses on the platform. Instead, responses are held in a secure, encrypted S3 bucket for 21 days only, after which they are permanently deleted. Use external integrations to manage your long-term data storage.

Formsort allows you to control who can access answer data using and .

πŸ’Ύ
user groups
access policies
Formsort form responses
Formsort notifications