Skip to content

Data handling

Roles

The researcher who builds a survey is the controller of the data it collects, they decide what is asked, hold any required approvals and consents, and answer to their participants for it. The platform processes that data on the researcher's behalf, stores it, serves the survey, and returns the data to the researcher. Questions about a specific survey's data belong with the researcher running it.

What the platform stores

  • Researcher account data, username, email, name, hashed password, theme preference.
  • Survey content, questions, logic, settings, uploaded library files.
  • Response data, answers, per-page timings, orderings, custom variables, and participant-uploaded files for surveys that ask for them.
  • Operational web-server logs (IP address, user agent, path, timestamp) for security and operations, log content excludes survey answers.

The platform does not require participants to identify themselves, whether a survey collects identifying data is the researcher's design decision.

Retention

Data is kept while the owning account and project exist. Specific lifecycles

  • Preview and test responses are purged automatically, on every publish and nightly.
  • Researchers delete individual responses or whole projects at any time, deletion erases the underlying files from storage, not just database rows.
  • Recycle bins (projects, assets, in-survey edits) hold soft-deleted content until restored or permanently deleted, permanent deletion is byte-level.
  • Account deletion removes everything the account owns, with an explicit per-project choice to transfer shared projects to a collaborator instead, see the in-product flow.
  • Server logs rotate on a fixed schedule.

Portability

Researchers export their own data self-service at any time, XLSX, CSV, Stata, SPSS, with an optional ZIP including all participant-uploaded files. No request process is required.

Location

Hosting is in the United States, single region, no cross-border replication. Where European law applies to a transfer, recognized safeguards (standard contractual clauses with providers) apply.

Cookies

Only strictly necessary cookies, the session cookie (sign-in, and keeping an in-progress response attached to its browser), the CSRF protection cookie, and Google reCAPTCHA where a survey enables bot protection. No advertising, analytics, or cross-site tracking cookies. The full statement lives in the Privacy Policy linked from every page footer.