Electronic Records and Signing Disclosure

Last updated: October 29, 2026

Who is asking you to act?

The sender identified in your request is asking you to review or act on the document. Confirm the document, intended recipient, assigned action and any representative capacity. Contact the sender if those details are incorrect or you do not understand the transaction. Odella supplies the technical workflow; it is not your lawyer or a determination that you have authority to sign for someone else.

The requesting organisation generally controls its signing records and supplies the applicable request privacy/record-handling notice. Odella's own privacy contact is dsar@odella.ai. The Privacy Policy explains the distinction between customer-controlled records and Odella's own processing.

Electronic-record scope and your action

The disclosure in your signing interface applies to the request described there. Read the actual version shown to you before deciding. Your action may be a signature, approval, acknowledgment of review or another supported assigned action; they do not all mean the same thing. The exact role-specific statement shown with the affirmative action explains the intent being recorded.

Receiving an invitation, opening a page, allowing an AI tool, or a sender's authorisation to issue a request is not your signature. You must personally review and take your own required action. Do not use someone else's identity or ask an AI/administrator to adopt your mark or consent for you. Signing does not, by itself, create a paid Odella subscription, consent to marketing, or opt into training an AI model.

Access, downloads and keeping a copy

You need a supported web browser and the ability to open and save PDF documents. Check that you can access and read the actual document on your device before acting. Use the document menu for downloads made available to you, including your completed copy when it is ready. If you cannot access, read or retain the document, stop and contact the sender or support@odella.ai.

A request can require other participants' actions or final processing before it is completed. Your part being finished is not necessarily full execution. Download and retain records you need; platform access can depend on request expiration, account status and applicable record-handling terms. We do not promise indefinite download links or an automatic paper-delivery service.

Paper copies, alternatives and contact corrections

Contact the sender to ask for paper copies, alternative signing arrangements, corrections to your contact details, and any fees or consequences of choosing an alternative. The sender must identify the process and charges applicable to its transaction. If these are unclear or you need an accessible alternative, ask before signing rather than assuming the platform will mail documents or change the agreement automatically.

Declining or withdrawing electronic-record consent

You may decline the request or contact the sender about prospective withdrawal of consent to electronic records. Withdrawal does not itself undo a completed signature, cancel an agreement or recall records already delivered. Ask the sender about the effect on an incomplete transaction and any alternative way to complete it. Applicable contractual remedies and non-excludable rights are not determined solely by this technical workflow.

Changing marketing preferences, asking to remove a saved signature appearance and withdrawing electronic-record consent are separate actions. Privacy requests remain subject to applicable rights, lawful instructions and exceptions; request records are not silently edited to invent a different historical consent.

Authentication and the organisation seal

The identity and recipient-binding controls used in the request are not a promise of government-ID checks, biometric verification, notarisation or a qualified electronic signature. A person's stated name or representative capacity must be considered with the document and surrounding evidence.

Where cryptographic sealing is enabled, the actual certificate and deployed configuration determine the organisation sealing identity and trust profile. Provider information is available through the Privacy Policy and the issued certificate. An organisation seal protects verification of the signed bytes; it does not turn each human recipient into the certificate subject or guarantee the transaction's legal validity.

Certificate expiry, revocation, validation services and software trust policies can affect cryptographic verification. A downloadable transaction completion certificate is different from the CA-issued signing certificate. Do not assume either provides transaction insurance or permanent validation. See the electronic signing terms in Section 11 and the applicable certificate policies and reliance information identified through the issued certificate or provider privacy information. These references do not enrol every recipient as a certificate subscriber or accept all supplier terms on their behalf.

Information recorded and sharing

The supported workflow records the documents and the relevant identity/contact, mark, action/consent, version, timing, integrity and delivery information described in the request notice and Privacy Policy. Technical information such as IP address or browser/device details may be recorded where used. Access to final documents, completion certificates and private audit evidence is not the same for every person or ordinary document-store reader.

Completed files may be delivered by email under the applicable request policy. Copies already emailed or independently saved by participants cannot be recalled by deleting a platform account. Customer documents, Odella's administrative records and independent certificate-authority validation/status/publication information have different handling rules. A regional document bucket or signing key does not mean every authentication, mail or certificate-service data flow stays only in that region.

Which version controls the recorded action?

The exact request notice, role-specific statement and approved versions shown in the supported interface govern the evidence recorded for that action, together with the applicable agreements and law. A later revision of this public page does not replace the notice or consent that a person actually saw. If the page and interface appear inconsistent, stop and ask the sender or support before acting.

Changelog

• 2026-10-29: Published the recipient reference disclosure covering request-specific actions, access and downloads, alternatives and withdrawal, the organisation seal and record handling. This public revision does not replace historical request notices or consent evidence.