Consent Forms & Online Signing
Dolyu supports online consent forms, letting customers confirm or sign a consent form when booking — no paper needed.
Creating a consent document (merchant side)
Go to Settings → Documents (it's not in the panel's left-hand main navigation — you get there via Settings). When creating a document, you can set:
- Content: upload a PDF or image, or type the content directly into the rich-text editor — pick one mode.
- Signing method: require a handwritten signature, or just a checkbox confirmation.
- Signing frequency:
Every booking(re-signed every time the customer books) orSign once(customers sign once per version and it's reused automatically after that). - Applies to: apply to all services, or specific ones. You can also do it the other way around — from a service's edit screen, choose which documents that service requires. Both approaches produce the same result; which one you use is just a matter of habit.
Documents have three states — Draft/Live/Archived: a new document defaults to Draft and won't appear in the customer booking flow until you manually switch it to Live; an archived document is pulled from the flow, but its existing signature records are fully kept.
There's no global on/off switch
Whether consent signing is active at all depends entirely on whether you have any document set to "Live" — there's no master toggle. If you previously turned off the old site-wide consent setting, that setting is now retired, and your document statuses stay exactly as they are.
Version history: editing the content of a Live document (text or the uploaded file) creates a new version and requires every customer to re-sign the new version — adjusting metadata like the name or sort order alone doesn't trigger a version bump. The system warns you before saving: "This will create a new version and require all customers to re-sign." The document list shows each document's current signature count collected, and you can filter by status or signing frequency.
Customer signing flow
At step 3 of the booking flow (right before final submission), customers see a list of applicable documents (tap to expand and read the full content):
- Documents requiring a signature: sign directly on screen with a signature pad.
- Documents requiring only confirmation: just check the box.
If the customer already signed the same version before, and that document is set to "Sign once," they see a read-only notice like "Signed on X — reused for this booking," along with a "Sign again" button they can use voluntarily (for example, if they want to leave a fresh signature) — they're never forced to re-sign. Guests (not logged in) are always treated as needing to sign again — no history is ever reused for them.
Version consistency check
If a merchant switches a document to a new version between the moment a customer opens the booking page and when they actually submit, the system re-checks the version at submission time, rejects submitting against the old version, and asks the customer to review and sign the latest version instead — this prevents a customer from signing terms that have already been superseded.
How merchants view signature records
- By appointment: an appointment's detail view shows which documents were signed for it, the signature image, and whether it was "signed this time" or "reused an earlier signature."
- By document: on the Documents list, the three-dot menu on each row offers "View signers," listing every customer who's signed that document, the version they signed, its status (fresh/reused/anonymized), and the timestamp.
Once created, a signature record can't be edited or deleted — with only two exceptions: the "copy delivered" field the system fills in automatically when a customer reuses a signature, and the PDPA anonymization process described below.
Personal data retention and erasure
Signature records are stored in a tamper-evident way, including a snapshot of the document version at the time of signing. If you need to erase personal data at a customer's request (for example, deleting a signature image), this is a manual, support-side operation — it's not a self-service feature in the dashboard, and there's no automated schedule for it. Today, only the platform side can run the anonymization command. Once run:
- The signature image is deleted, along with technical identifiers like IP address and device info.
- The factual record — "this document was signed at this time" — and the document version itself are kept, as proof of service delivery; nothing is deleted wholesale.
Can't anonymize while the customer has a pending or confirmed appointment
If the customer still has an appointment in "Pending" or "Confirmed" status, the system blocks the anonymization request — this is exactly the point at which the evidentiary value of the signature matters most. You'll need to confirm the customer has no active appointment, or have the platform side explicitly set a force flag, before it can proceed.
Common Questions
Is a consent document the same as the cookie consent banner on the website? No, they're completely unrelated. The "consent documents" on this page are custom terms of service, waivers, or statements defined by the merchant. The cookie banner is a site-wide compliance feature. The two are entirely independent — don't confuse them.
Can a customer sign without reading the content? No. The document content must be expanded and viewed before a customer can sign or check the box — the flow doesn't allow skipping straight to submission.
Does changing a document's "applicable services" affect signatures already collected? No. Existing signature records are an immutable historical snapshot. Adjusting the applicable scope only affects future bookings' decision on whether to require a signature — it never retroactively changes or deletes old records.
Can the same document require both a signature and a checkbox? No, the signing method is a single document-level setting (handwritten signature or checkbox confirmation — pick one). If you need both, create two separate documents.
Troubleshooting
A customer says the signature pad won't work, or their signature fails to submit: this is usually because the signature image is too large (over roughly 700KB) and gets rejected. The screen will prompt them to sign again — ask them to use a finger or stylus and avoid leaving excessive fine strokes on the pad.
A customer says they had to re-sign after I edited a document, but I only meant to change the name: check whether what you changed was the "name" or the "content" (the PDF/image/rich-text content) — only a content change bumps the version and requires everyone to re-sign; changing the name, sort order, or applicable scope doesn't trigger re-signing.
I want to delete a customer's signature record, but there's no delete button in the panel: there's no self-service deletion in the panel. If a customer requests personal-data erasure, contact platform support to handle PDPA anonymization.