Privacy
Last updated 25 August 2026
This page describes what Seagit Forms does with data. It covers two different people: the form owner, who builds a form, and the respondent, who fills one in.
If you are filling in a form
The form belongs to whoever created it, not to Seagit. Your answers are sent to that person. If you are unsure who that is or why they are asking, ask them before you answer — they decide what the form collects and what happens to it afterwards.
What we store when you submit a form:
- the answers you entered
- your email address, if the form asked for it or the owner turned on email collection
- the time you submitted, and the form you submitted to
You do not need an account to fill in a form, and we do not ask you to create one.
If you build forms
Your forms and their responses are stored in Amazon DynamoDB. You can read, export and delete them from your dashboard at any time.
Deleting a form deletes its responses too. That is not reversible, so export anything you need first.
We identify you through your Google or GitHub sign-in. We store the account identifier that provider gives us, so we can show you your own forms and nobody else's.
Where responses can be sent
A form owner can configure storage destinations — an S3 bucket, a webhook, or a spreadsheet. When one is configured, each response is also sent there as it arrives. Those destinations belong to the form owner, not to Seagit, and once a response reaches them it is covered by whatever policy applies to that system.
Passwords on forms
If a form is password-protected, the password is stored as a SHA-256 hash. It is never stored in plain text and is never returned by the public form API, which serves only the fields needed to render the form.
Getting data removed
If you filled in someone's form and want your response removed, contact the form owner — they control that data and can delete it. If you build forms and want your account and everything in it removed, get in touch and we will delete it.