Request Forms terms of service

Eligibility and accounts

You must be able to form a contract. You must be at least 13. You are responsible for your account, members you invite, API keys, OAuth grants, webhook URLs, custom domains, and embeds.

Keep secrets private. Do not share an account password. You must verify email for a password account before you sign in. Google sign-in requires a verified Google email.

We can refuse, suspend, or delete an account that breaks these terms, that we ban for abuse, or that creates legal risk we cannot accept.

The service

The product lets you build forms, publish a hosted link, embed a form, collect answers, upload files, take Stripe Connect payments, send webhooks, use API keys, and connect assistants through MCP. Most of the builder stays on the free plan, subject to rate limits. Paid is $23.20 per month billed yearly (20% off), or $29 per month. Paid features are hiding Request Forms branding and a custom domain. Prices are on /pricing.

We can change or end features. See /docs/deprecation for sunset rules. There is no support SLA on the public site.

Your content and respondent data

You own the forms you create and the answers you collect. You are the controller of respondent data. You grant us a license to host, store, display, transmit, export, and otherwise process that content as needed to provide the service.

Published forms are reachable without an account. Do not put secrets in a published form. You must have a lawful basis to collect the data you request. You must give respondents any notice the law requires.

File uploads and payment fields follow the privacy page. Signatures you collect are part of the answers. Theme import fetches a public HTTPS page you provide.

Acceptable use

Do not attack the service, probe it without permission, or scrape private workspace routes. Do not use the product to collect illegal content, malware, spam, or phishing. Do not collect data from children under 13. Do not infringe other people's rights. Do not send malware in uploads. Do not use the API or MCP to overload the service beyond published rate limits.

Do not present Request Forms as the controller of your respondent data when you are the controller. Do not hide the true purpose of a form. We can remove content or suspend the account when we find a breach of these rules.

Embeds and websites

You may embed a published form on a site you control or a site you have permission to change. You are responsible for that host page, its cookies, and its visitors. The embed still sends answers to Request Forms.

You must not wrap the service in a way that hides these terms from your organization. Custom domains stay on the paid plan and must point at the host we document. You must have the right to use that hostname.

API, CLI, and MCP

API keys, the CLI, and the MCP server are part of the same service. The same rules apply. Do not share API keys. Do not send a session cookie as a Bearer API key. MCP uses OAuth. You can revoke keys and grants. We can revoke them for abuse.

Webhooks

Webhooks you configure send submit payloads to the HTTPS URL you set. You are responsible for that URL, its access control, and what you do with the payload. You can set a webhook secret. We do not control retention on that host.

Paid plans and refunds

Paid plans bill through Stripe per organization, monthly or yearly. You can cancel a paid plan at any time from the organization billing portal. Cancel stops the next charge. Paid features stay on until the current period ends. After that, the organization returns to Free.

If you are not happy with the first paid charge on an organization, email support@requestforms.io from the account that owns that organization within 14 days of that charge. We refund that charge to the original payment method. We do not refund later renewals, unused time after those 14 days, or a later charge after we already refunded that organization once.

We can refuse a refund when the account broke these terms, when the charge is older than 14 days, or when the request is a chargeback for a charge we already refunded. For a billing dispute, email support first.

Form payments

Payment fields on a form send money to the organization's Stripe account. Those charges are not Request Forms fees. We cannot refund them. Ask the form owner. Stripe's terms also apply to those charges.

Disclaimer

The product is provided as is. We do not promise uptime, rank, or fitness for a specific legal, medical, or financial use. You are responsible for backups you need beyond the service, for the accuracy of answers, and for your compliance duties.

Liability

We are not liable for lost profits, lost data, indirect loss, or respondent claims that come from your forms. If the law still gives you a claim against us, our total liability is the fees you paid us for that organization in the 12 months before the claim, or 100 US dollars if you paid nothing.

Some places do not allow these limits. In those places, the limits apply to the full extent the law allows.

Indemnity

You will defend and cover Request Forms and Rami Rashid for claims that come from your forms, your respondent data, your embeds, your webhook destinations, your custom domain, or your breach of these terms, except to the extent the claim is caused by our willful misconduct.

Changes and end of service

We can update these terms. The date at the top is the current version. Continued use after a change means you accept the new terms. You can stop using the product and delete your account. We can stop the service with notice on the site or by email when we can.

Contact

Email support@requestforms.io. For privacy, open /privacy. For security, open /security. For product questions, open /docs. These terms are not legal advice.