Forms and submissions without a backend

No. The form posts to Tuqo, submissions are saved and shown in the panel. No server code and no database.

Out of the box: a honeypot field, a fill-time check, rate limits per site and IP, and binding to your site's domains. Spam goes to a separate folder.

They are not lost. Above the monthly limit a submission is saved, but its content is locked: you only see when it arrived. As soon as you upgrade your plan or buy a submission pack, the locked submissions unlock automatically (the most recent ones, up to the available capacity) and are marked as new. A new month does not unlock them: the monthly limit goes to new submissions. On the Free plan the number of locked submissions is capped; when the cap is reached, intake pauses and we notify you right away.

To the project panel and the notification bell. You can also set up delivery by email, to a project member or to an external address confirmed with a code, and as a message in Telegram or MAX.

Yes, on every plan and without a bot of your own. Link the messenger in your profile (Messengers → Link), then add yourself as a recipient under Forms → Submission delivery. A message from the Tuqo bot arrives right after the email, with the first eight fields of the submission. Different sites can have different recipients. Details are on the “Submissions to Telegram and MAX” page.

Yes, from the Start plan. Right after the form is sent, the person gets an email with your text: a confirmation, instructions or the promised file (a lead magnet such as a checklist, guide or price list). The file comes as a link in the email, so it only goes to a real address. Details are on the “Auto-reply and lead magnet” page.

Yes. Forms work on every site in the project by default, and the panel filters submissions by site.

In the project panel, on servers in Russia. This matters: once a site has a form, you collect personal data, and where it is stored becomes a legal question (in Russia, under the personal data law 152-FZ). With a foreign form service the data goes abroad, and you control neither access to it nor how long it is kept. Here the submissions are yours: they stay in the project panel, can be read through the REST API and MCP (get_form_submissions), and archived ones are deleted automatically after 180 days.

No. A submission is saved before any notification goes out: first the database, then the bell and the email. Mail problems cannot lose it — it is already in the panel. This is exactly how submissions quietly disappear for months in a “form → third-party script → email” setup.