Electronic Communications and Signature Consent

Version: 1.0
Last updated: August 20, 2026
Effective date: September 1, 2026
Website: https://www.hisicar.com

1. Scope of consent

This Consent governs electronic records, notices, clickwrap acceptance and electronic signatures used for HISICAR Platform Services and B2B vehicle transactions.

By actively accepting this Consent, the individual confirms that:

• the individual agrees to use electronic records and signatures for the covered matters;
• the individual can access, read, download and retain the records;
• the individual has authority to act for the identified Buyer; and
• the email address and account used for the transaction are controlled by the individual or Buyer.

This Consent does not convert an otherwise non-binding draft PI into a binding offer. Contract formation follows the Terms and Conditions, B2B Vehicle Sales and Export Terms and the wording of the PI.

2. Covered records

Electronic delivery and signature can be used for:

• Terms and Conditions;
• Privacy Policy and Cookie choices;
• account registration, login, MFA and security notices;
• business verification and authority records;
• inquiries and quotations;
• PI, vehicle report and incorporated Policies;
• amendments and approvals;
• payment instructions, receipts and refund notices;
• inspection, reconditioning, export and customs records;
• shipping, tracking, delivery and insurance records;
• warranty, recall and after-sales notices;
• complaints, claims and settlement documents;
• trade-compliance declarations; and
• other records expressly presented for electronic acceptance.

3. Records not covered where law prohibits electronic form

This Consent does not apply where mandatory law requires a paper original, wet-ink signature, notarisation, legalisation, government platform, physical title document or another form that cannot be replaced by agreement.

The Seller/exporter supplies an original or uses the required government process for such a record. Electronic copies can still be provided for information and evidence.

4. Hardware and software requirements

To receive and retain records, the user needs:

• an internet-connected device;
• a current browser supporting TLS, JavaScript and secure Cookies for account functions;
• a valid email address;
• software capable of viewing HTML and PDF;
• sufficient storage or printing capability; and
• access to the authentication method used for the account.

If requirements materially change so that prior records cannot be accessed, HISICAR provides notice and a reasonable alternative.

5. Electronic delivery

Records can be delivered through:

• the authenticated HISICAR account;
• the email address associated with the account or PI;
• a download link;
• a secure electronic-signature service;
• WhatsApp Business, WeChat or Telegram where expressly agreed for the record; or
• another electronic channel stated in the PI.

An ordinary message app is not used as the sole delivery channel for a high-risk legal record unless the parties agreed to that channel and the record can be reliably retained and authenticated.

The Buyer must keep account and email details current. A change must be made through an authenticated process or sent to info@hisicar.com and verified.

6. When an electronic record is sent and received

Unless the PI states otherwise:

• a record posted to the authenticated account is sent when it becomes available to the intended account and a notice is generated;
• an email is sent when it leaves the sender’s controlled system without a known permanent delivery failure;
• a record is received when it enters the designated account or system and can reasonably be retrieved; and
• a message received outside the recipient’s ordinary business hours is treated as received on the next Business Day for a deadline, unless mandatory law or urgent notice requires otherwise.

“Business Day” means a day other than Saturday, Sunday or an official public holiday in Shanghai.

A provider status is evidence but not conclusive if reliable contrary evidence exists.

7. Electronic signatures and acceptance methods

An electronic signature or acceptance can include:

• checking an unchecked acceptance box and selecting a clearly labelled acceptance button while authenticated;
• entering a one-time verification code linked to the transaction;
• applying a signature through an approved electronic-signature provider;
• signing a PDF or digital document with an accepted certificate;
• sending an express acceptance from a pre-authorised business email where the PI permits it; or
• another method that reliably identifies the signatory and indicates intent.

The interface must state the legal consequence before the action. A button labelled only “Continue” is not used to hide a binding PI acceptance.

8. Reliable electronic signature

A clickwrap acceptance can form an electronic contract and evidence intent. It is not automatically represented as a statutory “reliable electronic signature” equivalent to a handwritten signature or seal unless the method meets the applicable legal requirements.

Where a reliable signature or company seal is required, HISICAR uses an approved signature/certificate method or obtains the required signed/sealed document.

9. Material standard terms

Before acceptance, HISICAR conspicuously presents and, where requested, explains material standard terms, including:

• B2B limitation;
• Seller and payment-recipient identity;
• deposit and cancellation;
• used-vehicle condition and claim process;
• risk and title transfer;
• import responsibility;
• sanctions and compliance holds;
• warranty exclusions;
• liability limits;
• governing law, CISG exclusion and arbitration; and
• Personal Data cross-border processing where applicable.

The material acknowledgement is not preselected and is separate where appropriate. A footer link alone is not used as the only evidence of assent to a binding vehicle transaction.

10. Signatory authority

The signatory represents that the signatory has authority to bind the Buyer. HISICAR may require:

• business email verification;
• corporate role confirmation;
• power of attorney;
• board or management approval;
• company seal/signature specimen;
• identity verification; or
• re-authentication before a high-risk action.

If authority changes, the Buyer must revoke access immediately. The Buyer remains responsible for an authorised user’s action made before effective revocation, subject to applicable law and fraud evidence.

11. Attribution and security

HISICAR can attribute an action using:

• account/user and Buyer;
• authenticated session;
• MFA or provider verification;
• email/telephone verification;
• IP and device/security information;
• PI and policy version;
• timestamp;
• click event;
• authority documents; and
• content hash and audit log.

No single signal is necessarily conclusive. HISICAR evaluates the complete evidence where compromise, error or unauthorised action is alleged.

The user must not share credentials or OTPs and must report suspected compromise immediately to info@hisicar.com.

12. Review and correction before acceptance

In a binding acceptance flow, before acceptance the user must be able to:

• review the complete record;
• navigate to incorporated Policies;
• download or print the document;
• correct account or transaction input;
• request explanation of a material term;
• decline and exit; and
• report an error.

A material correction to party, VIN, price, currency, quantity, destination, payment, Incoterm, warranty or dispute clause requires a new version and fresh acceptance.

13. Contract formation record

For a binding PI, the acceptance is not complete unless HISICAR preserves:

• PI number and frozen version;
• rendered PI and incorporated Policies;
• vehicle, Buyer, price and export snapshots;
• Seller signature/seal status;
• signatory, Buyer and authority;
• language;
• conspicuous acknowledgements;
• date/time and time zone;
• account/session and security evidence;
• text/file hash;
• download/availability evidence; and
• later amendment, cancellation or dispute record.

The record must be protected from silent overwrite. A correction must create a new version and audit entry. A legacy acceptance action that lacks this record is not represented as the reliable binding event described in this Consent.

14. Copies and access

Before a binding acceptance, the interface must permit the Buyer to download the relevant electronic record. After acceptance, HISICAR must keep the accepted PI and transaction record available through the account for a reasonable period or supply a verified copy on request to info@hisicar.com.

No fee is charged for a reasonable electronic copy. Reasonable production or courier cost for a requested certified/paper copy can be charged after disclosure.

15. Withdrawal of electronic-delivery consent

The Buyer can withdraw consent for future electronic delivery by writing to info@hisicar.com.

Withdrawal:

• does not invalidate a prior electronic record or signature;
• does not cancel an accepted Vehicle Sales Contract;
• can require a paper or alternative process;
• can delay a transaction where an electronic process is operationally required; and
• does not stop legally required electronic security or transaction records where no paper alternative is available.

HISICAR explains any consequence before applying withdrawal. If the service can only lawfully and reasonably be provided electronically, the Buyer may need to stop future use after completing existing obligations.

16. Paper copies

The Buyer can request a paper copy through info@hisicar.com. Original government, customs, title and transport documents are supplied in the format required by the PI and law.

An electronic version remains authoritative where the parties designated it as the signed record, unless a certified original controls by law or the PI.

17. Changes

A change to this Consent applies prospectively from its effective date. A material change affecting an existing transaction requires notice and fresh agreement where required. Historical versions are available from info@hisicar.com.

18. Language

English is the controlling language for this Consent except to the extent a mandatory PRC used-vehicle export-licence or filing rule requires a filed Chinese translation to prevail. Any filed Chinese translation must be complete and accurate. A material inconsistency must be corrected before filing and requires fresh acceptance when it changes an agreed term.

19. Contact

Electronic-record, access, signature or authority questions: info@hisicar.com.