Your forms now explain how details are used — and never lose a submission halfway
Public and in-app forms show a clear privacy notice, record the legal basis you chose instead of always claiming consent, and save every part of a submission together.
Every form you publish now shows a short, plain-language note above the send button explaining that the details entered are used to handle that request, with a link to the privacy notice. It appears on your public form pages and on embedded forms. Forms also record the right legal reason for holding someone's details. Until now every submission was filed as "consent", even when you had chosen contract, legitimate interest or legal obligation for that form. Each submission now stores the basis you actually picked, and a consent form only counts as consented when the person ticks the consent box themselves. Because of that, publishing a form set to "consent" now requires a consent checkbox that is always shown on the form. If one is missing — or if it is set to appear only after certain answers, so some people would never see it — you will see a message explaining exactly what to add, or you can switch the form to a different legal basis. New forms from the template gallery now start with a basis suited to their purpose instead of all defaulting to consent. Health and waiver templates add the required consent choice automatically; a new blank form starts with legitimate interest, which you can review and change before publishing. Marketing permission is no longer assumed. A submission is only marked as marketing consent when the person ticks a marketing opt-in box — the type of form no longer implies it. Finally, a submission is now saved as one piece. Previously a hiccup partway through could leave a record of someone's permission without the message it belonged to, or create a duplicate conversation in your inbox if they pressed send twice. Either the whole submission arrives — permission record, conversation, submission and first message — or nothing does. Pressing send again after a dropped connection now shows the original submission instead of creating a second conversation, a second permission record and a second follow-up task. If someone changes an answer before trying again, that counts as a new submission rather than a repeat, so a correction is never quietly replaced by the earlier version — they are asked to reload and send it once more. Booking inquiries remain available to signed-in prospective clients who have not joined your venue yet. Their retry protection now covers changed contact details as well as changed answers, so an earlier inquiry cannot be replayed over updated information.
Safer appointment payment linking
Paid appointment promotions now stop for review instead of changing an appointment whose date, status, client, service, option, or payment link no longer matches the sale.