Edit survey — compiled preview, as respondents will see it

Survey language

Title style

How editing works

Sets the survey's language for screen readers and translates the words Nodeform adds — Continue, Required, error messages. Your own questions, options and descriptions are shown exactly as you wrote them; they are not translated. The document preview in Edit Survey stays in English.

Click directly on the title, description, or any question text in the document to edit it in place. Nothing about the node structure (question type, required, branching, option count…) can be changed from here — just the words, and pictures.

Pictures

Drag an image's bottom-right corner to resize it, or drag the picture itself to pan which part shows.

Pages

Click a wire on the canvas, then use its "New page" button — or drag "New page" from the palette onto a wire — to split the survey here. A page break on a wire feeding (or leaving) a node applies to all of that node's wires.

Branches

Wherever the survey branches, a branch picker appears in the document below — pick a branch to preview that path instead of the automatic example.

Branding

Preview as respondent — the exact survey participants will take

Nodeform

See the logic.
Trust the survey.

Nodeform draws your survey as a graph. Every skip, split and loop is a wire you can follow with your finger. Respondents never see it: they get a clean survey, one page at a time.

The real builder, with example surveys. No account, and nothing you do in it is saved. It opens on a phone, but the canvas is made for a larger screen.

Scroll the sheet to see the whole graph.

1Condition gate. Only people who drink coffee daily continue; everyone else goes to a short end screen.
2Random split. Half see packaging A, half see packaging B.

Example survey, drawn live by Nodeform itself, not a screenshot. The photographs on this page are generated illustrations.

Question types

4Logic nodes

Condition, random split, section loop, repeat block.

3Ways in

Paste, a Word document, or a Google Form.

Respondent languages

English and Danish.

The problem

You have made this page.

A printout, a pen, and arrows from "No" to question 7. It works until question 7 moves.

Most survey tools keep the same arrows. They are just somewhere you can't see them: one rule at a time, in a side panel, on the question it starts from. Nobody can look at the whole thing, so nobody checks the whole thing.

You find the broken path when a respondent does.

A printed questionnaire covered in hand-drawn arrows, with notes such as "if no, skip to 7" and "only if yes". — Illustration Skip logic, kept by hand.

How it works

Draw it once.
The survey follows.

Conditions are boxes on the canvas.
A gate sits between two questions and says who goes where. You read it left to right, like the survey itself.
Split and repeat without copying.
Send half of your respondents to concept A and half to B, or ask the same block once per product. Nothing is duplicated: change the block once and every pass changes.
Find the broken path before a respondent does.
Validate lists every issue in the graph. Test a rule against sample answers, or simulate 30 respondents and watch where they go.
The analysis knows the graph.
Compare the people who saw A with the people who saw B, and cross-tabulate one question against another, without rebuilding the split in a spreadsheet.
Bring what you already wrote.
Open a Word document, paste a list of questions or bring a public Google Form. From a document, "if no, skip to 7" becomes a condition on the canvas, and the review tells you what it could not place.

The same survey, from both ends

What a respondent sees.
What you get back.

The example above, drawn live from its 40 example answers.

What the respondent sees: page 1.

The example survey's Summary in Analyze, from its 40 example answers.

This survey is in the demo.

Questions

Before you open it.

Is a graph too much for a simple survey?

Three questions in a row are three boxes in a row. You only meet the rest when you need it.

Do respondents see the graph?

Never. They get a normal survey on their phone or laptop, one page at a time, in a keyboard-friendly, accessible player.

I already have surveys elsewhere.

Paste them, open the document, or bring a public Google Form. Past answers and links you already sent do not come across; the lists exactly what does.

Can my AI assistant build a survey here?

As a draft, yes. Connect an assistant that supports connectors (MCP) to your workspace and ask it for a survey. You open the draft, check it and switch its link on yourself. If you allow it, the assistant can also read totals from the answers, never what a person wrote. It is set up inside a workspace, under AI assistants.

Can I run sessions in person?

Yes. In conducted mode a facilitator fills the survey in for each participant and adds notes. Blind sample codes keep participants from knowing which product is which.

What happens to respondents' data?

Answers are anonymous unless you ask for identity, and identity is kept separate. You can erase one respondent's data; the erasure is logged.

Can I use it for real today?

The demo is the real builder, but it saves nothing and can't collect answers. Hosted workspaces, where surveys are saved and shared by link, are invite-only while Nodeform is in beta.

Yes. Create an account and what you make is saved, shared by link and collects answers. The Free plan costs nothing.

What will it cost?

Free costs nothing. There are four plans: Free, Student, Solo for one person, and Business for teams. Student is free with a university email address, for study and research. Logic is never behind a paywall: plans differ in volume and people, not in what a survey can do.

Who makes it

Why I made it.

I'm an engineer, and I have worked in UX and UI for 3.5 years. In that time I have built surveys in SurveyXact, Microsoft Forms, SurveyMonkey and Google Forms.

In all four, I set the logic one rule at a time, on the question or page it starts from, and never saw the whole route a respondent takes as one picture.

Nodeform is the tool I wanted: the survey drawn as a graph, so the logic is the first thing you see.

Constantin SagosMaker of Nodeform

Open it and follow a wire.Draw your first survey.

One click. No account.

Coming from another tool?

Switching

Bring your survey
with you.

Paste your questions, open the document they're written in, or bring a public Google Form. From a document or a form, sections and branching come across too. You check every question before anything is created. Past answers stay where they are.

The real builder, with example surveys. No account, and nothing you do in it is saved.

From any tool

Paste your questions.

Copy the questions out of the tool you use now and paste them in. You see every line Nodeform read before anything is created.

Questions and options. A numbered line, or one that ends in a question mark, starts a question. Lines starting with a dash, a bullet or a) are its options.
Types from the wording. “0–10” becomes NPS, “select all that apply” becomes checkboxes, and (required) marks a question required. You can change any of it in the review.
A CSV works too. Its first row has to be a header that starts with a question column: question, type, options, required.
Nothing is dropped quietly. A line Nodeform can't read is shown as Not recognised, for you to delete or turn into a question.

From a document

Open the document you wrote it in.

Choose a Word (.docx), OpenDocument (.odt) or text file. Nodeform reads it in your browser — however it's laid out — and shows you the survey it found before anything is created.

Your layout, not ours. Numbered or not, bulleted or lettered, headings in bold or in Word styles. You don't have to rewrite anything first.
Skip instructions become branching. Lines like “If no, skip to Q7” become Condition nodes, and the review lists every one before anything is created.
Sections become pages. Each heading starts a section, and each section is its own page. Rating tables become grid questions.
Nothing is dropped quietly. Pictures, comments and text that isn't a question are named in the review, under Not brought over.

From Google Forms

Bring a public Google Form.

Questions, sections and branching come across. Each section stays a page, and the form's “go to section” choices become Condition nodes on the canvas.

From its link. Paste the link from the form's Send button. The form has to be open to anyone with the link.
Or from its page source. If the link can't be used, copy the source of the page people fill in and paste that.
Branching you can see. The review lists every branch, and what happens otherwise, before anything is created.
What's left out is named. Images, videos, descriptions, validation and shuffled options are listed in the review, under Not brought over.

In this demo, use the example form or paste a form's page source. Loading a form from its link needs the hosted app.

What comes across

What comes across, and what doesn't.

Every way in brings the survey itself. Its past answers stay where they are.

Comes across

Questions and their optionsAll
Required marksAll
Question types, read from the wordingPaste
Question typesGoogle Forms
Sections, each as its own pageGoogle Forms
“Go to section” branching, as Condition nodesGoogle Forms
The form's title and descriptionGoogle Forms
Question types, read from the wordingDocument
Sections, each as its own pageDocument
“Skip to” instructions, as Condition nodesDocument
Rating tables, as grid questionsDocument
The document's title, as the survey nameDocument

Changes on the way

Linear scales become multiple choice, one option per value with the end labels kept. A 0–10 scale about recommending becomes NPS.Google Forms
“Other” becomes an option, with a text box under the question.Google Forms
Date-and-time questions keep the date. Time and duration questions become short text.Google Forms
A branch back to an earlier section continues to the next section instead, marked Changed.Google Forms
Each question goes on its own page, unless you turn that off in the review.Paste
A numbered scale becomes multiple choice, one option per value with the end labels kept. A 0–10 scale about recommending becomes NPS.Document
A skip back to an earlier question continues to the next section instead, marked Changed.Document
A follow-up like “If yes, which?” is asked of everyone until you add a Condition node.Document
Without headings, each question goes on its own page, unless you turn that off in the review.Document
Tracked changes are read as if accepted.Document

Stays behind

Answers you already collected. They stay in the tool that collected them.All
Links you already sent. They still lead to the old survey.All
Descriptions, images, videos and text blocksGoogle Forms
Response validation, shuffled option order and quiz scoringGoogle Forms
File-upload questionsGoogle Forms
The form's theme and settings, such as its confirmation messageGoogle Forms
Branching. Add Condition nodes on the canvas afterwards.Paste
Matrix and image-choice questionsPaste
Pictures, text boxes, comments, footnotes, headers and footersDocument
Introductions and instructions to interviewers. The review lists them under Other text.Document
A skip instruction Nodeform can't follow. The review names it.Document

Up to 60 questions per import, 20,000 characters per paste, and 20 MB per document. PDF and older Word (.doc) files can't be read; save them as Word (.docx) first. A Google Form that asks people to sign in to Google can't be loaded from its link.

Google Forms is a trademark of Google LLC. Nodeform isn't affiliated with Google.

After the import

Check it, then issue it.

Step 01 · Review

Read the review.

Nothing is created until you've seen every question, its type, and what wasn't brought over. Change a type or remove a question there.

Step 02 · Check

Validate and preview.

Validate lists any issue in the graph. Preview as respondent shows the survey page by page, the way people will answer it.

Step 03 · Issue

Issue a new link.

Turn sharing on and the survey gets its own link and QR code. Links you sent for the old survey still lead there.

Bring your first survey over.

The real builder, with example surveys. No account, and nothing you do in it is saved.

Privacy policy

Version 1.5 · Last updated 18 October 2026

Version 1.5, not yet reviewed by a lawyer. This text is written from our own build documents and describes how Nodeform is designed to handle data. We publish it early so you can check our intent before you trust us with anything. No lawyer has reviewed it yet.

1. What this covers

Nodeform is survey software: a builder for designing surveys, a player for running them, a dashboard for analysing the answers, and tools for managing a panel of testers. This policy explains what data the software handles, who is responsible for it, and what we do and do not collect. Two ways of using it are distinguished throughout: the demo, which runs only in your browser and keeps nothing, and the hosted service at nodeform.app, where you log in and what you make is stored on our server.At nodeform.app you use Nodeform by logging in: what you make is stored on our server.

2. The demo: your survey data never leaves your browser2. Your account

The demo on this site runs entirely in this page. Surveys, responses and profiles live in your browser's memory while this tab is open, and are gone when you reload it. No Nodeform server stores them, there is no account behind them, no analytics script watches you use it, and the demo sets no cookies. One exception, and it is not about your data: this page loads its typefaces from Google Fonts, so your browser makes a request to Google's font servers when it opens. We intend to self-host the fonts so even that request goes away.

If you log in, that changes. Logging in creates an account on our server: we store your email address, the name you choose to give, and the surveys you make with the answers they collect. The login code we email you is stored only in hashed form and stops working after ten minutes. Logging in sets one cookie, nf_session, which keeps you logged in for 30 days from your last visit; it is needed for logging in and is not used for tracking. If someone invites you to a workspace, your email address is stored with that invitation before you have ever visited.

Logging in creates an account on our server: we store your email address, the name you choose to give, and the surveys you make with the answers they collect. The login code we email you is stored only in hashed form and stops working after ten minutes. Logging in sets one cookie, nf_session, which keeps you logged in for 30 days from your last visit; it is needed for logging in and is not used for tracking. If someone invites you to a workspace, your email address is stored with that invitation before you have ever visited. This site loads its typefaces from Google Fonts, so your browser makes a request to Google's font servers when it opens a page. We intend to self-host the fonts so that request goes away.

News by email. When you log in you can tick a box to get news about Nodeform by email. It is never ticked for you, and saying no changes nothing about your account or what you can do with it. If you tick it, we store with your account that you said yes, when, the wording you agreed to and the language it was in. You can stop it at any time under Account, or with the link in every newsletter, which works without logging in; we then store when you stopped. The list of people who said yes is used only to send that newsletter. It is not sold, shared or used for anything else. If the newsletter is sent through an email service, that service receives your email address and the newsletter, and it will be named here before the first newsletter is sent. Deleting your account deletes all of this with it.

3. Who is responsible for respondent answers

When you build a survey and someone answers it, you are the data controller for those answers — the person or organization who decided to collect them and what they're for. Nodeform is the processor: the software you used to do it. If you took someone's survey and want your answers removed, ask the person who ran it — they have a one-click tool for exactly that (see section 12).

4. Anonymous by default

A public survey response stores the answers you gave, a submission timestamp, and nothing else: no IP address, no cookie, no device fingerprint, no advertising or tracking technology of any kind, and no third-party trackers on the survey page itself. Two things are used to protect a survey, and neither is stored with your answers. If a survey allows only one answer per browser, a random identifier is kept in your browser so it can recognise a second attempt; it identifies the browser, not you, and clearing the browser's site data removes it. And to limit abuse, such as one machine sending thousands of answers or guessing a survey's password, your network address is used in hashed form to count requests; those counts are deleted after a day. Most surveys built with Nodeform never touch personal data at all.

5. Anonymized collection

Survey owners can turn on a per-survey switch that goes further than the default: it coarsens each response's timestamp down to the day, and drops completion-duration metadata, so that responses become harder to correlate against an outside record (for example, a building access log) even by someone who already knows roughly when you responded.

6. Identity is pseudonymous and separate

A survey sent to known testers through Nodeform's community tools stores only a random tester ID with each response — never a name or an email address. The link from that ID back to a real person exists in exactly one place: the tester's profile. Where onboarding requires accepting a document (an NDA, a consent form), the accepted text, its version number and the timestamp of acceptance are recorded alongside the tester's consent.

7. Conducted sessions

When a member of a survey owner's team fills in a survey on a participant's behalf (a "conducted" session — used for in-person or moderated research), the response records which workspace profile conducted it, and any notes that team member added. Those notes are stored beside the answers, never inside them, so they never appear in exports or charts as if they were the participant's own words. The participant's identity stays optional in this flow and defaults to an anonymous session ID.

8. Files respondents attach

If a survey asks for a file, the file is stored in Cloudflare R2 object storage on behalf of the survey's owner. Only signed-in members of that workspace can download it, and only after the respondent has sent their answers. A file that is never sent is deleted automatically after 24 hours. Deleting a response, all responses, or a survey deletes its files. Files are not scanned or inspected by Nodeform.

9. Payments

If you buy a plan, you pay on Stripe's pages, not ours. Stripe receives your card details, your billing address, a VAT number if you give one, and from us the email address of the person buying and an internal identifier for the workspace. Nodeform never receives or stores card details. With the workspace we keep Stripe's customer and subscription identifiers, the plan and its size, whether it is paid monthly or yearly, the currency, the subscription's status and the date the paid period ends. Stripe keeps invoices and payment records under its own privacy policy, and may process data outside the EU.

10. The Student plan

If you apply for the Student plan, we store the university email address you give with the workspace while it is on that plan, and the date the plan ends. If the address is not the one you log in with, we email it a code, stored only in hashed form, that stops working after ten minutes. If the address is at a domain we do not recognise, the address and your account's email address are sent to the person who runs this Nodeform, who decides and whose answer is emailed to you; an undecided application is deleted after 30 days. We do not contact the university and do not check who you are.

11. AI assistants

Where this Nodeform offers it, a person with an account can connect an app, such as an AI assistant, to a workspace they belong to. Nothing is connected until that person allows it on a Nodeform page, where they choose what the app may do. A connected app can read the workspace's name, the names of its surveys, their questions and answer options, how many answers each has and whether it is collecting. If allowed to make surveys, it can add draft surveys and replace a draft that no person has opened. If allowed to read totals, it can read, for each question with choices, ratings, rankings or numbers, how many people chose each option and the averages; a question with fewer than five answers gives only how many answered it, and where one to four people chose an option, that number is given as “fewer than 5”. It is never sent one respondent's answers, anything a respondent wrote in a text question, dates, files, tester or participant identifiers, interviewers' names or notes, the times of answers, or anyone's email address. Totals are still information about the people who answered: where few people answered, or all of them answered alike, a total can show what one of them said. What the app reads leaves Nodeform and goes to the company that runs the app, which handles it under its own terms and privacy policy and may process it outside the EU. Nodeform has no agreement with that company. With the connection we store the app's name, the address it gave, what it was allowed, when it was connected and last used, and its access keys in hashed form. The person can disconnect it at any time under AI assistants. It also ends if they leave the workspace or delete their account.

12. Your rights, and how they are served

Access and portability: every survey's response set can be exported as JSON at any time by its owner, filterable down to a single tester ID. Erasure: a survey's owner can erase a single response, or a survey's entire response set, in one click. Erasing everything tied to one tester in one step is not built yet (section 13). Rectification and objection are handled directly by the survey owner, since they hold the data. Every erasure is written to an erasure log that records that an erasure happened and when — the log stores the fact of the request, not the person.

13. What is not built yet

We would rather list a gap than imply it is covered. Automatic retention deletion — a setting that would delete raw responses after a chosen number of months on its own — is designed but not yet shipped. Until it ships, retention is a manual action taken by the survey owner, not something that happens for you automatically. Erasing every response tied to one tester in a single step is not built either; today the owner erases them one response at a time.

14. Where data lives, and who else handles it

The hosted service runs on Cloudflare. Its database, which holds accounts, workspaces, surveys and answers, was created under Cloudflare's EU jurisdiction, so what is stored in it stays in the EU. Requests are handled by Cloudflare's network close to whoever makes them, which can be outside the EU. Where a survey accepts files, they are kept in Cloudflare R2 storage, and no storage region is pinned for them. Emails are sent by Resend: log-in codes, invitations to a workspace, Student plan codes and the answer alerts a workspace member can turn on. Resend receives the recipient's email address and the email itself; an alert carries the survey's name, answer counts, times and a link back to Nodeform, never any answers. Resend keeps its own delivery logs, and its servers may be outside the EU. Where plans can be bought, Stripe takes the payments (section 9). (This section, like the rest of this policy, has not yet been reviewed by a lawyer.)

15. No advertising, no data sales, no model training

Response data is never sold, never used for advertising, and never used to train machine-learning models: the demo has no server to do any of that from, and the hosted service does none of it.Nodeform does none of it. One thing is outside this: if you connect an AI assistant (section 11), what it reads goes to the company that runs it, and whether that company trains models on it is set by its terms, not ours.

16. Changes

Material changes to this policy will be announced here with a new version number and date.

17. Contact

For a question about an account or a payment, write to .

No contact address is published here yet. A named controller contact, and a data protection contact where required, will appear here before plans are sold.

Terms of service

Version 1.4 · Last updated 18 October 2026

Version 1.4, not yet reviewed by a lawyer. This text is written from our own build documents and describes the terms we intend to operate the hosted service under. We publish it early so you can check our intent before you trust us with anything. No lawyer has reviewed it yet.

1. Status

Nodeform is in beta. Nothing can be bought on this site. The demo on this site creates no account and keeps nothing you do in it. If you log in, you create an account and what you make is stored on our server, as the Privacy policy describes. Nothing on this page currently creates a contract between you and anyone. News about Nodeform by email is sent only to people who ask for it, and stops when they say so (Privacy policy, section 2).

Nodeform is in beta. If you log in, you create an account and what you make is stored on our server, as the Privacy policy describes. A Free account costs nothing. If you buy a Solo or Business plan you enter a paid subscription with , on the terms in sections 3, 7 and 9. News about Nodeform by email is sent only to people who ask for it, and stops when they say so (Privacy policy, section 2).

2. What Nodeform is

Nodeform is software for designing surveys as a node graph, running them, analysing the answers they collect, and managing a panel of testers to send them to. Where it is offered, you can connect an app such as an AI assistant to a workspace. It can make draft surveys and read totals from answers, as the Privacy policy describes. It cannot put a survey live.

3. Workspaces, profiles and plans

A workspace is the billing unit. Profiles are individual logins inside a workspace, sharing that workspace's quotas. The plans are named on the Pricing page. None can be bought on this site and no charge is made.Free costs nothing. Solo and Business are subscriptions, paid monthly or yearly in euro or Danish kroner, at the price shown on the Pricing page on the day you buy. Prices exclude VAT, which is added for your country before you pay. Payment is taken by Stripe; Nodeform never receives your card details. A subscription renews at the end of each period until you cancel. You can cancel at any time under Plan and usage, Manage billing: the plan then runs to the end of the period you have paid for, and the workspace returns to Free. If a payment fails, Stripe tries the card again; if it keeps failing, the subscription ends the same way. When a plan ends nothing you collected is deleted, surveys that are open stay open, and the Free limits apply. Changing plan during a period charges or credits the difference. A cancelled subscription is not refunded for the time already paid for. The Student plan is free and is for one person's study and research, not for commercial work. It is given for a year to a workspace whose owner shows that a university email address is theirs, and can be renewed. When it is not renewed the workspace returns to Free and nothing collected is deleted. One address gives the plan to one workspace at a time.

4. Your responsibilities as a survey owner

You choose what to ask, whom to ask it of, and on what legal basis. You are responsible for having a lawful basis for collecting what you collect, for not asking for special-category data without one, for honouring respondents' rights when they exercise them, and for not using the tester panel to send unsolicited marketing. If your survey asks respondents for files, note that files are not scanned for viruses. If you connect an app, you choose to send it your survey questions and, if you allow it, totals from the answers. You are responsible for that being lawful toward the people who answered. The app's own terms apply to what it receives.

5. Acceptable use

You may not use Nodeform to run unlawful surveys, to attempt to identify anonymous respondents, to automate abuse of the service, or to upload content — including logos and pictures — that you have no right to use.

6. Your content stays yours

Your surveys, your responses and your tester data belong to you. We do not sell them, mine them for advertising, or use them to train machine-learning models. We access them only when you ask us to, or when needed to keep the service running.

7. Availability

During the prototype phase there is no uptime commitment, and the software is provided as is. Service-level commitments, if any, will be stated per plan at launch.

There is no uptime commitment on any plan, paid or free, and the software is provided as is.

8. Liability

Limits on liability will be stated here after legal review. We will not publish a number we have not had checked.

9. Ending the relationship

You may stop using Nodeform at any time. Before an account is ever closed, you will be able to export your surveys and responses as JSON. We may suspend an account for a breach of the acceptable-use terms above, with notice where the law requires it. Deleting your account cancels the subscription of any workspace that is deleted with it.

10. Governing law

The hosted service is intended to operate under Danish and EU law. The governing-law and venue clause will be confirmed here after legal review.

11. Changes

Material changes to these terms will be announced here with a new version number and date, and before they take effect for existing users.