LEGAL

Privacy Policy

Last updated September 21, 2026.

Formantly (“Formantly,” “we,” “us”) provides lead-capture forms, AI follow-up, and an AI chat widget for home-service businesses. This policy explains what we collect, why, and how long we keep it, both for the business owners who use Formantly and for the visitors who submit a form or chat with one of our customers’ widgets.

Questions about this policy or your data: email hello@formantly.com. We don’t have a phone line or physical office set up for this yet, email is the fastest way to reach us.

Our role

For account and billing data about business owners, Formantly is the data controller. For the enquiries and chat messages that visitors send to a business through a Formantly form or widget, the business is the controller and Formantly acts as its processor: we handle that data on the business’s instructions to provide the service. If you are a visitor and want to exercise your rights over an enquiry, you can contact the business directly or email us and we will help route the request.

What we collect

From a business owner (our customer)

  • Your account email and login credentials.
  • Business details you provide: business name, trade, website, phone, service areas.
  • Billing information, handled directly by Dodo Payments, our payment processor. We never see or store your card number.

From anyone who contacts us or visits our website

  • What you send through our contact and feedback forms: your name, email address, your message, the topic you chose, and the page you were on. If you are signed in, we also link the message to your account.
  • Visits to our public website pages, measured with Google Analytics: which pages are read, roughly where from, and what kind of device and browser. Google Analytics is not used inside the dashboard, the admin area, the sign-in pages or on forms that Formantly shows on its own pages.

From a visitor submitting a form or using an AI chat widget

  • Whatever the business’s own form asks for: typically name, email, phone, address, and a description of what they need. Photos, if the business’s form accepts them.
  • The full text of an AI chat conversation, if the business has AI Chat turned on.
  • Technical data needed to operate the service: your IP address (stored only as a one-way hash, never in plain text), browser user agent, and the page that referred you.

How we use it

  • To deliver the lead to the business (notification email, dashboard entry).
  • To power the optional AI features (Pro plan): reading a submission or chat message, drafting a follow-up, deciding whether a lead is ready to hand off to a human. This is done using Google’s Gemini API, sent only the details from that specific enquiry. Formantly does not use enquiry data to train any model. How Google handles data sent to its API is set out in Google’s own Gemini API terms.
  • To prevent spam and abuse: hidden honeypot fields, rate limits and spam scoring on every form, and Cloudflare Turnstile bot verification on forms shown on Formantly pages and on a business’s verified custom domain (Turnstile cannot run on a form embedded in a business’s own website).
  • To operate and improve Formantly itself (aggregated usage, not individual visitor profiling).
  • To provide support: a Formantly team member can view a workspace’s data in read-only mode (“View As”) when investigating a support request or a suspected abuse issue, and every such session is logged. Our admin tools also show a workspace’s recent leads, including contact details, to the team members who handle support and abuse reports. We also keep a log of administrative actions (who did what, and when).

AI, disclosed honestly

When a business turns on AI follow-up or AI Chat, the AI chat widget is labelled “AI assistant for” the business, and every AI follow-up email is signed as the AI assistant and ends with a line saying it was written by the AI assistant for that business. The AI is instructed never to pose as a person on the business’s team, never to invent prices or binding quotes, and never to make guarantees the business hasn’t actually made. A chat conversation can contain anything a visitor chooses to type, which occasionally may include sensitive details volunteered unprompted (for example, a health or safety detail mentioned while describing an urgent repair). We treat this the same as any other data in this policy and don’t use it for any purpose beyond handling that enquiry.

Cookies and browser storage

Formantly’s own dashboard uses a session cookie to keep you logged in, nothing else. On our public website pages, Google Analytics sets its own cookies to count visits; it is switched off on the dashboard, the admin area, the sign-in pages and forms Formantly shows itself. We also remember your light or dark theme choice in your browser’s localStorage, which stays on your device. See our Cookie Policy for the details. A form or chat widget embedded on a business’s site writes nothing to your browser until you actually interact with it: opening a chat and sending your first message stores a session identifier (in sessionStorage, not a cookie, and not before that first message) so the conversation can continue if you keep chatting. It’s cleared when you close the tab, and stops working on our end after 7 days either way.

Who we share data with

We use the following sub-processors to run Formantly. Each only receives what it needs to do its job:

  • Supabase, for our database and account authentication.
  • Google (Gemini API), for the optional AI analysis, follow-up drafting, and chat features.
  • Resend, to deliver notification and follow-up emails. Resend keeps a copy of each email it sends for a period it sets.
  • Cloudflare, to run our public form/chat endpoints, verify visitors aren’t bots (Turnstile), receive email replies to AI follow-ups, and store uploaded photos.
  • Vercel, to host the Formantly dashboard and website.
  • Dodo Payments, to process Pro subscription payments.
  • Sentry, to record technical errors so we can fix them, and for a sample of visits to record how a page behaved, with all text and form fields masked. Error reports are meant to contain technical details only, not lead content.
  • Upstash, to apply rate limits to sign-in and other sensitive actions. These are short-lived counters that include your IP address and, for sign-in, your email address.
  • Google Analytics, to measure visits to our public website pages (not the dashboard).

If a business owner sets up an outgoing webhook (for example to Zapier or Make), lead data is also sent to the endpoint they chose. That destination is the business’s own choice and responsibility, not one of our sub-processors.

We do not sell personal data, and we don’t share it with anyone outside this list except where required by law.

How long we keep it

  • Uploaded photos are deleted automatically: after 30 days on the Free plan and 365 days on Pro.
  • Leads, conversations and contact details are kept until the business owner deletes them (one at a time or several at once) or deletes their account. They are not currently deleted automatically.
  • A chat conversation that never turns into a real lead (the visitor leaves before sharing contact details) is deleted after 30 days, regardless of plan.
  • When a business owner deletes their account in Settings, their workspace, leads, files and billing customer record are deleted right away. We may keep a minimal record that a deletion happened, and billing records that the law requires us to keep.
  • Contact and feedback messages are kept for as long as we need them to reply and follow up, and are deleted on request. The log of administrative actions is kept for accountability.

Your rights

Wherever you are, you can ask us what data we hold about you, ask us to correct it, or ask us to delete it, by emailing hello@formantly.com. If you submitted a form or chatted with one of our customers’ widgets and want your enquiry removed, tell us which business it was sent to and roughly when, so we can find it. We respond to these requests within 30 days. Depending on where you live, you may also have the right to object to or restrict certain processing, or to complain to your local data protection authority.

Changes to this policy

If we make a meaningful change to how we handle data, we’ll update the date at the top of this page. Continued use of Formantly after a change means you accept the update.

Privacy Policy