Privacy Policy
This policy explains what FormFlow collects, why, who else processes it, and how to get it deleted. It describes what the software actually does — not a generic template.
Two roles, two responsibilities. When you use FormFlow to build forms, we are the data controller for your account. When people answer a form you published, you are the controller of those answers and we act as your processor — we store and display them on your behalf and do not use them for our own purposes.
1. Who we are
FormFlow is operated by C2M Technologies, Inc., a company incorporated in Delaware, United States. For any privacy question, data export or deletion request, use our contact form. We aim to reply within 30 days.
2. What we collect
Account data (you)
| Data | Why |
|---|---|
| Email address | Sign-in identity, account recovery, service notices |
| Name (optional) | Display in your workspace |
| Password | Stored only as a salted scrypt hash — never in readable form |
| Organization name | Grouping your forms and teammates |
| Forms you build | The product itself |
Response data (people who fill in your forms)
| Data | Why |
|---|---|
| Answers submitted | Delivered to the form's owner — that is the purpose of the form |
| Uploaded files | Where a form asks for them |
| Hidden fields from the URL | Only the parameters the form owner declared |
| Browser user-agent and referring page | Basic diagnostics |
| IP address | Never stored. It is used transiently for rate limiting and kept only as a salted one-way HMAC hash that cannot be reversed to an address |
| Time taken to complete | Spam detection and the owner's statistics |
We do not sell personal data, we do not use response content for advertising, and we do not use it to train machine-learning models.
3. Cookies and local storage
We keep this deliberately small:
- Session cookie — set when you sign in, so the site knows
it is you. It is
HttpOnly, restricted to this site, and expires after 14 days. This is strictly necessary; the product cannot work without it. - Resume token — when someone starts filling in a form, their
browser stores a random token in
localStorageso they can pick up where they left off. It contains no personal data and is cleared on submission. - Advertising cookies — Google sets these on our public marketing pages — home, pricing, about, contact, the policy pages and the sign-in and registration pages — so we can measure which ad campaigns bring people to the product. They are not set in the form designer or on published form pages. See §5.
4. The AI form builder
If you use the assistant to draft or edit a form, the text of your request and the current structure of that form are sent to Anthropic to generate a response. This happens only when you choose to use the assistant.
Answers submitted to your forms are never sent to the AI — only the form's own questions and settings.
5. Analytics and advertising
We run ads for FormFlow, and we use the Google Ads tag on our public marketing pages to measure which campaigns bring people to the product. It sets cookies in your browser and shares data with Google, which acts as an independent controller for that data.
Where it does not run: the tag is never loaded inside the form designer, and never on a published form page. People answering your forms are not tracked by us for advertising — that is a deliberate boundary, not a configuration detail.
You can opt out with Google's opt-out add-on, or by blocking these cookies in your browser.
6. Who else processes data
| Processor | Purpose | Where |
|---|---|---|
| Amazon Web Services | Hosting, storage, database | United States (us-east-1) |
| Anthropic | AI form generation, only when you use the assistant | United States |
| Ad measurement on our public marketing pages only | United States |
We are a US company and our infrastructure is in the United States, so if you are outside the US your data is transferred there — including, where relevant, out of the EEA and the UK. For those transfers we rely on the European Commission's Standard Contractual Clauses with our processors.
7. How long we keep things
- Account and forms — until you delete them or ask us to close your account.
- Completed responses — until you delete them or delete the form; they belong to you.
- Unfinished (partial) responses — automatically purged after 30 days.
- Generated exports — deleted after 7 days.
- Webhook delivery logs — 90 days.
- Sign-in sessions — 14 days.
8. Your rights
Depending on where you live (including under the GDPR and the UK GDPR) you may have the right to access, correct, export, delete or restrict the processing of your personal data, and to object to it. You can export your form responses at any time from the product as CSV or Excel, and delete forms and responses yourself. For anything else, use our contact form and choose the privacy topic.
If you answered someone's form and want that response removed, contact the organization that ran the form — they control it. If you cannot reach them, tell us and we will help.
9. Security
Traffic is encrypted with TLS. Passwords are salted and hashed with scrypt. Every form and response is scoped to its organization and access is checked on every request. Uploaded files are stored under non-guessable names and served as downloads rather than rendered in the browser. No system is perfectly secure, but we treat your data as if it were our own.
10. Children
FormFlow is not directed at children under 16 and we do not knowingly create accounts for them.
11. Changes
If we change this policy materially we will update the date above and, for significant changes, notify account holders by email.