Agreements completed through the bookyour.place signing flow record consent and finalized-field events and preserve a completed PDF. Bookings whose host records an off-platform contract do not use this electronic-signing flow.
After the host accepts a booking request, the booking can enter the contract stage. The selected signing order determines whether the host signs first or the guest receives signing access first. For an external guest, the platform records when the invitation is created and when its link is accessed. Possession of that bearer link is not, by itself, independent proof of identity.
Before signing, the signer uses the signing name on the account or, for an external guest, enters or confirms a name. We preserve the submitted name and its recorded source. A self-attested name does not, by itself, verify identity.
The signer is presented with an Electronic Signature Disclosure and accepts it before signing. For that consent request, we record the disclosure version, server timestamp, IP address, and user-agent. Each finalized field is recorded separately. Read the disclosure
The first signer completes the assigned fields in-browser or on a phone. Each finalized field receives its own server timestamp and capture method, such as drawn signature, typed name, or automatic date.
The host or guest completes second, according to the selected order. After all required signatures are captured and final artifact generation succeeds, the current completed PDF includes one appended execution-certificate page showing the contract ID and completion timestamp. Registered booking parties can access it in the app. For an eligible external signer who has not claimed an account, the platform starts an email delivery attempt containing a time-limited read-only link; provider acceptance and inbox delivery are not guaranteed.
A server-side UTC timestamp for consent and a separate timestamp for each finalized field.
Captured as technical context for the consent request. These values do not independently identify a person or device.
Each invitation is tied to its intended signer. The bearer link must be kept private; possession of it is not independent identity verification.
The submitted name is preserved with its recorded source, such as self-attested. The source label says how the name entered the record; it is not a blanket identity guarantee.
The disclosure version, server timestamp, IP address, and user-agent are recorded for the consent request, separately from each finalized-field event.
The final PDF includes an appended certificate page with the contract UUID and execution timestamp. It records which platform contract the artifact represents without covering any original contract content.
Example data based on the event types the platform records. Authorized registered parties can view the available chronological log on the in-app audit-trail screen.
| Event | Signer | Timestamp (UTC) | Consent-request IP |
|---|---|---|---|
| Contract created | — | 2026-06-14 14:58:00 | — |
| Signing invitation created | Guest — Jane R. | 2026-06-14 15:00:00 | — |
| Invitation link accessed | Guest — Jane R. | 2026-06-14 15:02:17 | — |
| Electronic-signature consent recorded (disclosure version 1.1) | Guest — Jane R. | 2026-06-14 15:03:41 | 72.14.x.x |
| Guest signature finalized | Guest — Jane R. | 2026-06-14 15:05:23 | — |
| Electronic-signature consent recorded (disclosure version 1.1) | Host — Mike D. | 2026-06-14 17:10:12 | 198.51.x.x |
| Host signature finalized | Host — Mike D. | 2026-06-14 17:11:05 | — |
| Contract fully executed — all required signatures captured | — | 2026-06-14 17:11:05 | — |
The final execution event uses the latest required signature timestamp; PDF artifact generation follows separately. After the current completed artifact is ready, registered booking parties can access it in the app. For an eligible external signer who has not claimed an account, the platform starts an email delivery attempt containing a time-limited read-only link; provider acceptance and inbox delivery are not guaranteed.
The audit trail records the disclosure version, server timestamp, IP address, and user-agent for the consent request, plus a separate timestamp and capture method for each finalized field. It also preserves the submitted name and its recorded source. After final artifact generation succeeds, registered booking parties can access the current completed PDF in the app. For an eligible external signer who has not claimed an account, the platform starts an email delivery attempt containing a time-limited read-only link; provider acceptance and inbox delivery are not guaranteed. The appended execution certificate shows the contract UUID and completion timestamp. These records document the workflow; they do not independently verify identity or determine how a later dispute will be resolved.
The completed PDF contains the captured signatures plus an appended execution certificate with the contract UUID and completion timestamp. Submitted names and their recorded sources are associated with the consent and signing-event records available to registered booking parties in the app. After final artifact generation succeeds, registered booking parties can access the current PDF there. For an eligible external signer who has not claimed an account, the platform starts an email delivery attempt containing a time-limited read-only link; provider acceptance and inbox delivery are not guaranteed. We do not arbitrate disputes or guarantee a legal outcome; a party or adviser can evaluate the agreement and its records for the specific circumstances.
Whether an agreement is legally binding depends on the agreement, the parties, applicable law, and the surrounding circumstances. Our flow records electronic-signature consent and signing events and preserves the completed artifact, but the platform does not make a legal-validity determination. Consult a qualified lawyer for advice about a specific agreement or dispute.
DocuSign is a general-purpose e-sign tool you configure for many kinds of documents. Ours is vacation-rental-specific: the submitted guest name and booking dates can flow into a rental-agreement template, the contract stays attached to the booking record, and the invitation is associated with the intended signer's email. An invitation or self-attested name is not independent identity verification, and we do not claim that the products or their records have identical legal effect.
Before completion, a registered booking party can use the in-app decline action. An external guest can choose not to consent or sign, or can leave required fields incomplete, but leaving the external flow does not itself record a formal decline. Incomplete fields are not treated as signatures, and the platform does not publish a completed PDF unless all required signatures are captured and final artifact generation succeeds.
Founding hosts get 1–3 years free. List your property, upload a template, and create a contract for an eligible booking.
