Contact Formaly

Email support@formaly.io for anything about using Formaly: a form that will not generate, a respondent who could not submit, an analysis that looks wrong, an export you cannot open, or a question about how a feature is meant to work.

Include your account email and, where relevant, the form's URL or ID. If something failed at a specific moment, the approximate time helps a great deal - it is what makes the failure findable in the logs. Support enquiries are usually answered within one business day.

Email support@formaly.io with the subject "Enterprise Plan Inquiry" for volume pricing, custom credit allocations, invoicing, security review paperwork, data processing agreements, or a walkthrough of whether Formaly fits a particular research programme.

Tell us roughly how many forms and responses per month you expect and which integrations matter - the answer is much more useful with those two numbers in hand.

Formaly runs on credits: generating a form, regenerating questions, and producing an AI summary each consume a small amount, and conversational responses cost a fraction of a credit. New accounts start with 50 free credits and no card on file.

For a refund request, a duplicate charge, a receipt or invoice, or a credit balance that looks wrong, email support@formaly.io from the address on the account and include the payment date and the last four digits of the card used.

Send access, correction, export, and deletion requests to support@formaly.io. Requests are handled by Arindam Majumder, who owns and operates Formaly. See the privacy policy for what is collected and why, and the terms of service for the agreement governing use of the product.

If you are a respondent rather than an account holder and want your answers to a specific form removed, contact the organization that sent you the form first - they control that data. If you cannot reach them, write to us and we will help route the request.

Please report suspected vulnerabilities privately to support@formaly.io with "Security" in the subject line rather than opening a public issue. Include the steps to reproduce and the impact you believe it has. Reports are acknowledged quickly and we will keep you updated until the issue is resolved.

Please do not run automated scanning, load testing, or denial-of-service testing against Formaly, and do not access or modify data belonging to other accounts while investigating.

If you are integrating Formaly rather than using the dashboard, start with the developer documentation - it covers the REST API, the MCP server, the JavaScript SDK, embeds, and webhooks. Machine-readable entry points live at /llms.txt, /AGENTS.md, and /openapi.json.

Email support@formaly.io for API keys with unusual scope requirements, rate-limit increases, or MCP integration questions.