Sender-Driver Delivery Agreement
Effective October 12, 2026
Standard terms incorporated into each accepted Delivery
This Delivery Agreement is a contract directly between the person or organization requesting the delivery (“Sender”) and the person or business accepting it (“Driver”). It covers the delivery of the small parcel identified in the Transaction Record. Schedule A (Prohibited Items and Packaging Requirements) and Schedule B (Delivery, Proof, and Claims Procedures) are part of this Agreement. RouteCart LLC (“RouteCart”) provides technology and limited administrative services, but it is not the transporter and is not a party to this Agreement except as expressly stated in Sections 2, 7, 11, 13, and 15.
1. Definitions and Transaction Record
1.1 Key Terms. In this Agreement: “Delivery” means the transportation of the identified package from the stated pickup location to the stated delivery location. During RouteCart’s initial Florida launch, a Delivery is eligible only if both locations are in Florida, the transportation remains entirely within Florida, and the Delivery is not a segment or continuation of a prearranged through or continuous interstate movement. “Delivery Request” means the Sender’s offer for that Delivery. “Platform” means RouteCart’s website, application, and related technology. “Transaction Record” means the electronic record for the Delivery. “Recipient” means the person designated to receive the package. “Fare” means the amount charged to Sender for the Delivery, including any disclosed adjustments. “Driver Earnings” means the amount payable to Driver after disclosed RouteCart fees, refunds, reversals, taxes, offsets, and adjustments. “Platform Terms” means the separate RouteCart terms accepted by Sender or Driver, as applicable. “Jurisdiction-Specific Addendum” means a state or local contractual addendum that expressly states it modifies this Agreement, RouteCart identifies as applicable to the Delivery, and RouteCart presents to each affected party before or at that party’s acceptance. “Schedule A” and “Schedule B” mean the versions identified in the Transaction Record.
1.2 Transaction Record. The Transaction Record identifies the Sender, Driver, package description and category, declared value, recorded exterior condition, pickup and delivery locations, requested time windows, Recipient or contactless instructions, Fare, Driver Earnings, additional disclosed charges, acceptance timestamps, and the versions of these standard terms and the incorporated Schedules. It also identifies by title and version each Jurisdiction-Specific Addendum incorporated into this Agreement, the party or parties to whom it was presented, and the applicable presentation and acceptance records. A party-specific disclosure, coverage notice, or Platform Terms addendum may be identified for recordkeeping without becoming part of this Agreement. If another listed item does not apply or was not provided, the Transaction Record may omit it.
1.3 Contract Documents. The Transaction Record, these standard terms, Schedule A, Schedule B, and each Jurisdiction-Specific Addendum identified in the Transaction Record as modifying this Agreement together form the complete “Delivery Agreement” for the Delivery. No Platform Term, party-specific disclosure, or coverage notice is part of the contract between Sender and Driver unless this Agreement or an applicable Jurisdiction-Specific Addendum expressly says otherwise. Section 16 explains how the parties may change this Agreement and which terms control if the documents conflict.
2. Formation and RouteCart’s Limited Role
2.1 Formation and Authority. The Sender submits the Delivery Request as an offer to any eligible Driver to whom the Platform presents it. This Agreement forms only when a Driver affirmatively accepts the Transaction Record or, if an optional automated matching feature is offered, affirmatively confirms a reserved match after receiving a conspicuous notice and reasonable confirmation window. A failure to confirm allows the opportunity to lapse without penalty. Each individual entering this Agreement confirms that the individual is at least 18 years old, has legal capacity to contract, and has authority to bind any organization identified in the Transaction Record. Each party agrees to use electronic records and signatures and may download or request a copy of the Agreement.
2.2 RouteCart Is Not the Transporter. Sender hires Driver, and Driver independently agrees with Sender, to transport the package. RouteCart does not take custody of the package, operate the vehicle, choose the route, employ Driver to perform the Delivery, guarantee transportation, or assume Driver’s responsibility for the package. RouteCart’s technology may calculate and display the price, automatically apply objective compatibility filters to display opportunities, record acceptance, process payment, display location, preserve proof, and provide administrative support.
2.3 Limited Agency. Driver appoints RouteCart only as Driver’s collection agent for amounts that Sender owes Driver. Sender appoints RouteCart only to transmit instructions, records, and administrative claim communications. These limited appointments do not allow RouteCart to change a material Delivery term without the affected party’s consent, decide or settle legal liability, or take custody of the package.
2.4 RouteCart Enforcement Rights. RouteCart is an intended third-party beneficiary of provisions that disclaim or limit its role or liability, protect its intellectual property or data, require indemnification or cooperation, or govern disputes involving RouteCart, and may enforce those provisions directly. No other nonparty is a beneficiary.
3. Sender Obligations and Warranties
Sender warrants that: (a) Sender owns the contents or has authority to send them; (b) the description, weight, dimensions, value, category, addresses, timing, access conditions, and Recipient information are complete and accurate; (c) the package and its transportation comply with Schedule A and all laws that apply along the reasonably expected route; (d) the contents do not require any undisclosed license, placard, shipping paper, temperature control, age verification, security measure, specialized equipment, or insurance; (e) the packaging is adequate for ordinary transport in a passenger vehicle; and (f) the Recipient agreed to receive the package, and Sender has the right to provide the Recipient’s information and instructions.
Sender must provide a safe, lawful, reasonably accessible, and adequately lighted pickup location; secure pets; disclose known hazards and access restrictions; avoid requiring Driver to enter a residence or unsafe area; and make an authorized person available for pickup. The same duties apply to a delivery location Sender controls. Sender may not require Driver to encounter an unsecured animal, handle a weapon, or perform an undisclosed service. Sender bears the risk and cost caused by prohibited, dangerous, illegal, incorrectly described, poorly packaged, defective, or perishable contents, except to the extent that another party’s separate wrongful conduct caused the loss.
4. Driver Obligations and Warranties
Driver warrants that Driver and any qualified substitute selected by Driver: (a) meet the objective identity, safety, license, vehicle, screening, and insurance requirements applicable to the opportunity; (b) hold every license, registration, operating authority, insurance policy, and endorsement required for the vehicle, route, compensation, and Delivery; (c) will use a safe, registered, insured, and suitable ground motor vehicle; and (d) have reviewed the material terms of the opportunity and can lawfully and safely perform the Delivery.
Driver will use reasonable care to achieve the pickup, custody, delivery, proof, and return results accepted in the Transaction Record and described in Schedule B; protect the package and confidential information; and comply with law. Driver controls the route, sequence, stops, vehicle, equipment, and manner and means of performance. Safety and events beyond Driver’s reasonable control take priority. Lawful Recipient and Sender instructions govern the accepted destination, access, package handling, proof, contactless placement, and return result, not Driver’s route, driving technique, or day-to-day work methods. Driver may make reasonable stops and combine compatible work if doing so does not put the accepted Delivery at risk.
Driver must not open, use, tamper with, photograph the contents of, take, abandon, pledge, sell, or allow unauthorized access to the package. Driver must not take the package aboard an aircraft, through airport passenger or baggage screening, into a secured airport area, or transfer it to another carrier or unqualified person. If Driver suspects danger or illegal contents, Driver must put safety first and follow lawful instructions from authorities and the applicable documented emergency procedures in Schedules A and B, which address the safety event rather than Driver’s ordinary work methods.
5. Custody and Chain of Handoff
Custody passes from Sender to Driver when Driver physically receives the package and records the pickup. Custody remains with Driver until: (a) delivery to the verified Recipient; (b) placement at the exact contactless location authorized by Sender, with reasonable proof; (c) a recorded return to Sender; or (d) a documented transfer to a qualified substitute permitted under the Driver Terms. RouteCart never has custody. Custody does not transfer ownership or give Driver a lien or other interest in the package, except for a right that applicable law does not allow the parties to waive. Driver must keep the package in an enclosed, secure area, out of public view, and reasonably protected from movement, weather, contamination, animals, and unauthorized access.
A substitute transfer must identify both Drivers, the time and place of transfer, the package’s visible condition, and each person’s electronic confirmation. The original Driver remains responsible as stated in the Driver Terms, and RouteCart’s record of the transfer is evidence rather than a conclusive determination.
6. Delivery, Proof, Recipient, and Failed Delivery
6.1 Proof and Verification Method. The Transaction Record will identify the result-based proof method accepted by Sender and Driver, which may include timestamps, approximate geolocation, exterior package or placement photographs, a Recipient name or signature, or a one-time code. A service option involving a higher-value or higher-risk package may specify stronger proof before Driver accepts the Delivery. Unless a separate legally compliant program says otherwise, Driver may visually review identification only when the Transaction Record requires it and may not photograph, scan, or retain the identification. Driver should avoid capturing faces, private interiors, access codes, identification documents, and unrelated personal information. These records may help show what happened, but no single record automatically decides a dispute. Sender, Driver, RouteCart, an insurer, an arbitrator, or a court may consider all reliable evidence that applies.
6.2 Contactless Delivery. If Sender authorizes unattended placement in the Transaction Record, risk transfers to Sender after Driver places the package at the authorized location and records the required proof, except for loss caused by Driver’s wrongful act. Sender bears post-delivery theft, weather, animal, and premises risks. A Recipient may change the placement instruction only through an authenticated Platform method permitted for the Delivery.
6.3 Failed Delivery. If delivery is unsafe or cannot be completed because of access, recipient unavailability or refusal, inaccurate instructions, or another condition not caused by Driver, Driver will follow the recorded fallback or return instructions. Sender will pay disclosed waiting, return, redelivery, storage, or lawful disposition charges. Driver may not abandon the package, keep it without instructions, or leave it with an unverified person.
6.4 Redirection and Recipient Changes. A destination, Recipient, or material delivery-instruction change must be requested through an authenticated Platform method. RouteCart may require account reauthentication, a one-time code, or comparable verification. A change that materially affects distance, timing, risk, handling, or price requires a recorded adjustment and Driver’s affirmative acceptance. A call, text, or message outside the Platform does not by itself authorize redirection.
7. Fare, Collection, and Adjustments
Sender will pay the Fare and any disclosed adjustments. Driver authorizes RouteCart and its payment provider to collect Driver’s portion as Driver’s limited collection agent and to remit Driver Earnings after the disclosed RouteCart fees, refunds, reversals, taxes, offsets, and adjustments. Sender’s payment to the payment provider satisfies Sender’s payment obligation to Driver to the extent the provider receives the funds. RouteCart may administer a refund or Platform credit, but doing so does not make RouteCart the carrier or decide liability between Sender and Driver.
RouteCart does not solicit, display, collect, or process tips at launch. The Fare and disclosed adjustments are the complete amounts processed through the Platform. If RouteCart later enables tipping, the applicable Platform Terms, disclosures, and transaction records will be revised before the feature is used.
A material change to destination, package, timing, stops, or handling requires a recorded repricing and Driver acceptance. Neither party may move this Delivery off Platform to evade fees, records, safety processes, or payment protections.
8. Cancellation, Delay, and Events Beyond Control
Before Driver acceptance, Sender may withdraw the offer. After acceptance, the cancellation, waiting, return, and redelivery charges displayed with the transaction apply. Driver may cancel for a genuine emergency, unsafe or illegal condition, vehicle failure, material package misdescription, or other reasonable inability to perform and must promptly notify Sender through the Platform. The Platform may make a new opportunity available to eligible Drivers through its objective compatibility filters. A subsequent Driver acceptance creates a new Delivery Agreement and does not transfer the original Driver’s obligations without notice.
Neither Sender nor Driver is liable for delay or failure caused by an event beyond reasonable control, including severe weather, road closure, government action, emergency, crash not caused by the affected party, or Platform outage, if the affected party uses reasonable efforts to protect the package and communicate. This does not excuse payment already earned, cargo protection, or a failure to obtain legally required qualifications.
9. Loss, Damage, Tampering, and Claims
9.1 Administrative Procedure. Sender and Driver will follow Schedule B to report suspected loss, damage, tampering, mis-delivery, or non-delivery and to preserve and submit supporting evidence. Any preferred administrative reporting period does not shorten a minimum claim or suit period required by nonwaivable federal or state law.
9.2 Investigation. The parties will preserve and provide the records identified in Schedule B and cooperate reasonably. RouteCart may preserve Platform records and facilitate communications but does not adjudicate liability, settle a claim for either party, or guarantee payment.
9.2A Insurance and Recovery. Each party must give timely notice to any applicable insurer and may not impair subrogation, inspection, or salvage rights. A chargeback, refund, Platform credit, insurer payment, or administrative account action is not an admission and does not permit a double recovery.
9.3 Agreed Value and Choice of Liability. The Transaction Record must show the standard $100 liability limit before Sender submits the Delivery Request. If RouteCart offers a higher declared-value option for an additional charge, Sender may choose it before submitting the Delivery Request, and the chosen amount and charge must appear in the Transaction Record. Sender and Driver agree that the selected liability level may affect the Fare. For ordinary negligence, Driver’s maximum cargo liability will be the lowest of: (a) the value entered by Sender; (b) the package’s documented actual value; or (c) the liability limit selected and shown in the Transaction Record. A liability limit applies only to the extent that Sender received clear advance notice, had a reasonable opportunity to select any available higher level of liability, agreed to the selected level in the Transaction Record, and applicable law permits the limit. If applicable law requires a different process or minimum liability, or does not permit the limit, that law controls. No limit applies to Driver’s theft, conversion, fraud, willful misconduct, or other liability that applicable law does not permit the parties to limit. Sender must not tender property worth more than the maximum declared value the Platform permits.
9.4 Exclusions. Driver is not responsible for loss caused by prohibited or misdescribed contents, inadequate packaging not reasonably apparent at pickup, inherent defect, ordinary wear, temperature sensitivity, lawful seizure caused by Sender, inaccurate instructions, or post-delivery events after authorized contactless placement, except to the extent Driver’s independent wrongful conduct contributed.
10. Personal Injury, Property Damage, and Insurance
Driver is responsible for operation of the vehicle and for bodily injury, property damage, traffic, parking, and other claims arising from Driver’s or Driver personnel’s acts or omissions. Driver will maintain applicable insurance and promptly notify the insurer and affected parties as required by law. Sender is responsible for unsafe premises, dangerous contents, and instructions. Nothing releases a party from liability that cannot lawfully be waived.
11. RouteCart Disclaimer and Limitation
To the maximum extent permitted by law, RouteCart provides only technology and limited administrative services “as is” and “as available.” RouteCart is not liable for the acts or omissions of Sender, Driver, a Recipient, or any other person; for a vehicle or package contents; or for loss, damage, delay, theft, seizure, mis-delivery, personal injury, or property damage not caused by RouteCart. RouteCart’s total liability arising from a Delivery will not exceed the greater of $100 or the RouteCart platform fee for that Delivery. RouteCart will not be liable for consequential, special, incidental, exemplary, or punitive damages or for lost profits, data, or goodwill. These exclusions and limits do not apply to RouteCart’s fraud or willful misconduct, gross negligence where it cannot be limited, or any other liability that cannot lawfully be waived. If applicable law does not permit liability for a particular matter to be excluded entirely, RouteCart’s liability for that matter will be limited to the lowest amount the parties may lawfully agree upon. If applicable law permits only a partial exclusion or limitation, the exclusion or limitation will apply to the fullest extent permitted by law.
12. Indemnification Between Sender and Driver
12.1 Sender’s Indemnity. Sender will defend, indemnify, and hold Driver harmless from third-party claims, governmental proceedings, fines, cleanup costs, injuries, and property damage arising from prohibited, dangerous, illegal, incorrectly described, or inadequately packaged contents; unsafe pickup or delivery premises controlled by Sender; Recipient information or instructions; or Sender’s breach, negligence, fraud, or willful misconduct. Sender does not have to indemnify Driver for Driver’s separate wrongful conduct.
12.2 Driver’s Indemnity. Driver will defend, indemnify, and hold Sender harmless from third-party claims, governmental proceedings, injuries, property damage, and cargo loss arising from Driver’s vehicle operation, personnel, custody of the package, failure to maintain required authority or insurance, breach, negligence, fraud, theft, conversion, or willful misconduct. Driver does not have to indemnify Sender for Sender’s separate wrongful conduct.
12.3 Procedure. A party seeking indemnification must promptly give the other party written notice of the claim and provide reasonable information and cooperation. Late notice reduces the indemnifying party’s obligations only to the extent the delay materially harms the defense. The indemnifying party may control the defense with qualified counsel reasonably acceptable to the indemnified party. The indemnified party may participate with its own counsel at its own expense. The indemnifying party may not settle a claim without the indemnified party’s written consent if the settlement requires an admission, payment, nonmonetary obligation, or release by the indemnified party. Consent may not be unreasonably withheld when the settlement fully releases the indemnified party and requires only payment by the indemnifying party. If the indemnifying party does not promptly assume the defense, the indemnified party may defend the claim and recover reasonable covered costs.
13. RouteCart Indemnification
13.1 Indemnity in Favor of RouteCart. Each party will defend, indemnify, and hold harmless RouteCart, its affiliates, licensed operators, service providers, and personnel from third-party claims, regulatory proceedings, fines, losses, and reasonable attorneys’ fees arising from that party’s package, vehicle, personnel, premises, instructions, personal information, breach of this Agreement or the applicable Platform Terms, violation of law, fraud, negligence, or willful misconduct. A party does not have to indemnify RouteCart for RouteCart’s separate wrongful conduct.
13.2 Procedure. RouteCart will give the indemnifying party reasonably prompt notice and cooperation. Late notice reduces the indemnifying party’s obligations only to the extent the delay materially harms the defense. RouteCart may assume control of the defense with counsel of its choice at the indemnifying party’s expense. The indemnifying party may participate with its own counsel at its own expense. No settlement may impose liability, an admission, a release, or a nonmonetary obligation on RouteCart, or fail to provide RouteCart a full release, without RouteCart’s written consent. If RouteCart does not control the defense, the indemnifying party must use qualified counsel reasonably acceptable to RouteCart and keep RouteCart informed of material developments.
14. Disputes Between Sender and Driver
14.1 Informal Resolution. Before starting arbitration, Sender and Driver must give each other written notice through the Platform’s support process. The notice must describe the facts, the legal or contractual basis of the claim, and the relief requested. The parties will try in good faith to resolve the dispute for 30 days after both parties receive the notice. A party may seek urgent temporary relief when waiting would cause immediate and irreparable harm. RouteCart’s participation in the support process is administrative and does not make RouteCart a party to the dispute.
14.2 Small Claims Option. Either party may bring an individual claim in a small-claims court that has jurisdiction, as long as the claim remains only in that court and is not transferred, removed, or appealed to a court of general jurisdiction. All other disputes between Sender and Driver arising out of or relating to the Delivery, this Agreement, or the parties’ relationship will be resolved by individual binding arbitration.
14.3 Arbitration Administrator and Rules. The American Arbitration Association (“AAA”) will administer the arbitration. The AAA Consumer Arbitration Rules will apply if Sender requested the Delivery mainly for personal, family, or household purposes. Otherwise, the AAA Commercial Arbitration Rules will apply, including any Expedited Procedures that apply. If AAA declines or cannot administer the case, the parties will try to select another neutral administrator. If they cannot agree, a court with jurisdiction will appoint an administrator or arbitrator under the applicable arbitration law. The administrator’s current rules are available at www.adr.org.
14.4 Governing Arbitration Law. The parties intend the Federal Arbitration Act (“FAA”) to govern the interpretation and enforcement of this Section to the fullest extent it applies. If a court with jurisdiction decides that the FAA does not apply, including because 9 U.S.C. § 1 exempts this Agreement, the Revised Florida Arbitration Code will govern to the fullest extent permitted by law. The parties intend their agreement to arbitrate to remain enforceable under applicable state law even if the FAA does not apply.
14.5 Arbitrator, Hearing, Costs, and Award. One neutral arbitrator will decide the dispute. A court will decide whether an arbitration agreement exists and whether this Section is enforceable or applies to a dispute. The arbitrator will decide all other issues, including the merits and procedural questions. The arbitration will ordinarily proceed by documents, telephone, or video. If an in-person hearing is required, it will take place in the county where the respondent lives or has its principal place of business, unless the parties, the applicable rules, or nonwaivable law require another location. Filing fees, administrative fees, and arbitrator compensation will be allocated under the applicable AAA rules and law. Each party will pay its own attorneys’ fees and costs unless this Agreement, applicable law, or the award allows recovery. The arbitrator may award any individual remedy a court could award and must issue a written, reasoned decision. A court with jurisdiction may enter judgment on the award.
14.6 Individual Proceedings and Jury Waiver. Sender and Driver agree that each may bring claims only in an individual capacity. To the fullest extent permitted by law, no arbitration or court proceeding may be brought or conducted as a class, collective, consolidated, coordinated, or representative action. The arbitrator may not combine claims of different persons without the written consent of every party. If a claim proceeds in court, Sender and Driver each waive a jury trial to the fullest extent permitted by law.
14.7 Severability of Dispute Terms. If a court finds that part of this Section cannot be enforced, that part will be narrowed or removed only to the extent necessary, and the remainder will continue in effect. If the individual-proceeding requirement cannot be enforced for a particular claim or request for relief, that claim or request must be decided by a court after any arbitrable claims are completed.
15. Disputes Involving RouteCart
A claim by Sender or Driver against RouteCart is governed by the dispute resolution provision in that claimant’s applicable RouteCart Platform Terms, including its provisions addressing informal notice, arbitration law, individual proceedings, mass filings, opt-out rights, severability, forum, and jury waiver. A claim solely between Sender and Driver remains governed by Section 14 of this Agreement. Adding RouteCart to a dispute does not replace the dispute procedure that otherwise applies to each claim, to the fullest extent permitted by law.
16. Entire Agreement and Other Legal Terms
16.1 Entire Agreement and Amendments. The Transaction Record, this Agreement, Schedule A, Schedule B, and each incorporated Jurisdiction-Specific Addendum are the complete agreement between Sender and Driver for the Delivery. The parties may amend the Delivery Agreement only through a change recorded by the Platform and affirmatively accepted electronically by each affected party, except to the extent nonwaivable law requires a change without assent. A purchase order, receipt, policy, message, side agreement, prior statement, course of dealing, course of performance, or trade usage does not amend the Delivery Agreement. Any attempted amendment outside the Platform is ineffective for purposes of the Delivery Agreement and cannot change RouteCart’s rights or protections or impose any obligation on RouteCart without RouteCart’s written consent.
16.2 Priority and Governing Law. If the documents directly conflict, an applicable Jurisdiction-Specific Addendum controls to the extent it expressly modifies this Agreement or nonwaivable law requires. Subject to that rule, a transaction-specific term in the Transaction Record controls over these standard terms and the Schedules. These standard terms control over a Schedule on substantive liability, agreed value, dispute resolution, governing law, RouteCart’s role, and rights that cannot be waived. The Schedules control the operational details they address. Florida law governs this Agreement, without regard to its conflict-of-law rules, except where federal law or another nonwaivable law applies.
16.2A Jurisdiction-Specific Addenda and Notices. A Jurisdiction-Specific Addendum is incorporated into this Agreement only when it is presented to each affected party before or at that party’s acceptance, identified in the Transaction Record as modifying this Agreement, and accepted where assent is required. It controls only to the extent it expressly says so or nonwaivable law requires. Applicability may depend on a party’s location, vehicle location, pickup or delivery location, place of performance, or another legally relevant connection. A party-specific Platform Terms addendum, disclosure, coverage notice, or other notice does not become part of this Agreement solely because RouteCart provides or records it, unless the document expressly states that it modifies this Agreement and applicable law permits that treatment.
16.3 Assignment, Severability, and Waiver. Neither party may assign or transfer an accepted Delivery without the other party’s consent recorded through the Platform, except that Driver may use a qualified substitute as permitted by the Driver Terms and the Transaction Record. If a provision is invalid or unenforceable, it will be enforced to the maximum lawful extent, and the rest of the Agreement will remain effective. A party’s failure or delay in enforcing a provision does not waive the right to enforce it later, and a waiver on one occasion is not a waiver on another occasion.
16.4 Notices, Survival, and Headings. Notices under this Agreement may be sent through the Platform, to the email address or telephone number in the party’s account, or by another method stated in the Transaction Record. Each party must keep its contact information current. Provisions concerning payment, custody, claims, confidentiality, indemnification, liability limits, dispute resolution, and any other terms that by their nature should continue will survive completion, cancellation, or termination of the Delivery. Section headings are included only to make the Agreement easier to read and do not change its meaning.