Privacy-First — Zero Response Storage

Forms that never
store your data.

Define forms in code. Submissions route directly to your webhook or inbox — we never write a response to disk. Zero GDPR exposure. Zero breach risk.

Request Access See How It Works

Storage: Never written to disk
Delivery: Webhook or email
Authoring: DSL in version control

        intake_form.srp
        .srp
      

# Patient intake form
page "Contact" do
  OpenEnded "full_name" do
    text "Full name"
    required
  end

  OpenEnded "email" do
    text "Email address"
    required
  end

  OpenEnded "phone" do
    text "Phone number"
  end
end

page "Reason for Visit" do
  SingleSelect "visit_reason" do
    text "Primary reason for visit"
    option "Annual checkup"
    option "Follow-up" do
      segment "needs_notes"
    end
    option "Urgent care" do
      segment "needs_notes"
    end
  end

  OpenEnded "notes" do
    text "Additional notes"
    show_only_if "needs_notes"
  end
end

How submissions work

Browser → POST /f/:slug → Honeypot check → Forward to webhook → Discarded ✕

Nothing is written to the database. The submission hits the server momentarily, is forwarded to your destination, and is gone. No logs, no storage, no data lake.

Storage: 0 bytes
Retention: 0 days
Breach risk: None

Built for regulated industries

The teams that can’t afford a data breach.

Syrup Forms is designed for organizations where response data is too sensitive to hand to a third party — and where "no storage" isn't a feature, it's a compliance requirement.

Healthcare

Patient intake without HIPAA exposure

Route patient intake responses directly to your EHR webhook. Nothing touches a form builder's servers. PHI never leaves your control chain. We are a processor, not a controller — eliminating the most common source of third-party HIPAA liability for intake workflows.

Legal

Client intake with privilege intact

Client matter intake, conflicts checks, onboarding questionnaires — responses go to your practice management system directly. Not to Typeform's cloud.

Finance

KYC and onboarding that doesn't accumulate PII

Customer onboarding and KYC questionnaires route directly to your compliance stack. No third-party storage of sensitive identity data.

For developers — forms in code, reviewed in pull requests

Form definitions live in your repo alongside your app. Changes go through code review. No GUI drift, no surprise question changes, no exported CSVs in someone's Downloads folder. Try the DSL in the Playground →

How it works

From form definition to live form — in three steps.

Write the form in the SRP DSL, publish it, configure your destination. That's the entire workflow.

Define your form in the DSL

Write the form as plain text. Fields, conditional logic, required validation — all code-reviewable and version-controlled alongside your application.

Publish and configure destination

Choose webhook or email delivery. Point it at your endpoint — your own server, Zapier, Make, n8n, or any service that accepts a POST.

Respondents submit. Data goes to you.

Your form lives at a clean public URL. Submissions forward immediately to your destination and are discarded from our servers.

The SRP DSL

Forms that look like what they are.

Form definitions are plain text files. They commit to git, travel through code review, and deploy like any other change. When a question changes, you see it in the diff.

contact_form.srp

page "Your Message" do
  OpenEnded "name" do
    text "Your name"
    required
  end

  OpenEnded "email" do
    text "Email address"
    required
  end

  SingleSelect "topic" do
    text "Topic"
    option "General"
    option "Sales"
    option "Support" do
      segment "support_topic"
    end
  end

  Discussion "message" do
    text "Message"
    required
  end

  OpenEnded "order_id" do
    text "Order ID"
    show_only_if "support_topic"
  end
end

01 — Version control

Every form change is a diff

Commit form definitions to git. Review them in pull requests. When a question changes, you see it in the diff — no GUI-induced mystery state, no silent question additions.

02 — Conditional logic

Fields show and hide based on answers

The show_only_if directive handles conditional display. Same system used across Field Surveys, battle-tested in thousands of completions.

03 — Question types

19 types for real-world forms

Open-ended, single/multi-select, date pickers, phone, address, NPS, rating. Everything needed for intake forms — without the research-only complexity.

04 — Try it now

Live in the Playground

The DSL Playground is live, no account required. Write a form, preview the output, explore conditional logic.

Why Syrup Forms

A form builder built around your data architecture.

01 — No storage

Responses are never written to disk.

The submission hits our server once, is forwarded to your configured destination, and is gone. No database row. No log entry. No cloud storage. You can verify this with a network inspector — the payload never comes back out of our API.

02 — DSL-defined

Forms live in your repository, not in a GUI.

The SRP DSL produces forms that are plain text files. Committed, reviewed, and deployed like code. No GUI drift, no surprise changes, no mystery state that requires logging into the form builder to debug.

Webhook delivery

POST JSON to any URL — your server, Zapier, Make, n8n, Slack. Standard HTTP, no proprietary integration.

Email delivery

Route submissions to an email address. Each arrives as a structured email. No webhook infrastructure required.

Spam protection

Honeypot field baked into every form. Rate limiting by IP. No CAPTCHA to degrade completion rates.

How it compares

What you give up with typical form builders.

Typeform, Jotform, Google Forms — they all store your responses. That’s their product. Your respondents are their data.

	Syrup Forms	Typeform	Google Forms	Formspree
Response storage	✓ Never stored	Stored in their cloud	Stored in Google	Stored 30–90 days
Code-defined forms	✓ DSL in git	✗ GUI only	✗ GUI only	✗ HTML + config
Conditional logic	✓ Full DSL support	✓ Paid plans	Limited	✗
Webhook delivery	✓ All plans	Enterprise only	✗ Native	✓ All plans
GDPR / HIPAA posture	✓ Processor only	Controller + processor	Controller + processor	Controller + processor

Forms that neverstore your data.