1. A. Restaurant Partner Agreement
For the restaurant and its agreed participating branches only. Captain terms are separate and do not become restaurant obligations.
1.1. Parties and separate scope
This proposed agreement is between the participating restaurant’s identified legal operator (TBD) and U-Turn’s legal company (TBD; registration number and address TBD). It applies only to the restaurant relationship and participating branches identified in a separate agreement. It does not bind the restaurant to the Captain Agreement. Signing parties, authority to sign and the effective date must be confirmed before activation.
1.2. Menu accuracy, food safety and handover
The restaurant is responsible for accurate menus, prices, availability, ingredient and allergen information, required licences, lawful trading, food hygiene, safe preparation, suitable packaging and correct handover. Keep the dashboard current and notify U-Turn promptly of errors or outages. Do not represent allergen safety or availability that has not been verified; customer questions requiring restaurant knowledge must receive an accurate response.
Check the order identity, approved items, quantities and food amount at handover, and record discrepancies through the available process. Neither dashboard records nor the captain’s acknowledgment excuse supplying unsafe, incomplete or incorrect food. Required receipts and lawful invoice duties must be fulfilled; the precise issuer arrangements and tax responsibilities requiring confirmation remain TBD.
1.4. Food payment and records
Under the proposed model, the captain pays the confirmed food amount to the restaurant at pickup, irrespective of the customer’s offered delivery payment method. A pickup customer pays the restaurant directly. Confirm the amount and provide the required receipt; report a shortfall or mismatch before treating the handover as settled. U-Turn’s payment records do not replace the restaurant’s own lawful accounting duties.
1.5. Customer-caused food loss: proposed commercial allocation
Prominent pilot term: after a human investigation verifies a customer-caused failure, the restaurant bears the resulting food loss under this proposed agreed commercial allocation. This is not a finding that the restaurant caused the failure. If the captain already paid for the food, the proposed pilot arrangement requires the restaurant to return the food amount actually received, after applicable credits and adjustments. This allocation requires express agreement and Palestinian legal review before it is used.
U-Turn reimburses the captain independently of collecting from the restaurant or customer. A captain report is not sufficient evidence of customer fault; the review must assess location, timing, reasonable contact attempts, waiting time, payment and relevant explanations, including emergencies or faults by other parties. No automatic debit or assumed admission of liability is created by this page.
1.6. Weekly statements, disputes and recovery
The proposed administration is an itemized weekly statement identifying each affected order, evidence of the verified outcome, the food amount received, credits or recoveries and the balance claimed. The restaurant has seven days from receipt to dispute the statement and provide evidence. The repayment deadline is TBD and must be agreed and disclosed. A disputed item requires human review; a missed internal dispute period does not waive mandatory rights.
Any offset against another amount requires express agreement and legal permission; a ledger entry alone is not permission to take money. An unresolved overdue balance may lead to pausing new orders after notice, while active orders must be safely resolved. Do not charge the restaurant and retain customer money for the same food loss. Any later customer recovery must credit the person or party who ultimately bore that loss, with an updated explanation and statement.
1.7. Other losses and shared responsibility
U-Turn bears verified resulting food loss where it authorizes preparation and then cannot arrange delivery. Restaurants bear verified losses caused by their own incorrect food, unsafe preparation or inadequate packaging. Delays, damage or mixed causes must be investigated on the evidence rather than allocated automatically. Reasonable steps to reduce a loss must be considered without compromising food safety or mandatory rights.
1.8. Pilot and subscription pricing
The proposed pilot involves one or two restaurants for approximately four weeks. Each participating branch must receive clearly specified free-trial start and end dates (both currently TBD). There is no automatic paid renewal during the pilot. Participation in a review page or continued discussion does not start a paid subscription.
Before any paid period, agree the price, included order allowance, excess-usage treatment, taxes, renewal, cancellation and grace periods; all currently remain TBD. There is no percentage commission on food sales under the current model and no surprise overage fees. Any future package or charge must be clearly disclosed and agreed prospectively before it applies.
1.9. Confidentiality and customer-data use
Protect confidential business information and customer data, limit access to authorized staff, and use data only to prepare, identify and resolve the relevant order or satisfy a lawful obligation. Do not copy contact details for unrelated marketing or disclose them outside that purpose. Use separate optional permission for marketing where lawful; ordering is not blanket marketing permission.
The intended restaurant view is limited to information needed for preparation and handover; pickup may require a customer’s name and phone. The Privacy Policy distinguishes verified controls from proposed ones. Report suspected unauthorized access or disclosure promptly to U-Turn; the incident channel and response period remain TBD.
1.10. Suspension, termination and dispute review
U-Turn may propose proportionate suspension for food-safety concerns, credible serious misconduct, unresolved material breaches or overdue agreed obligations, with notice and human review where appropriate. Urgent safety restrictions may be temporary pending review. A restaurant may request to end participation through support; ordinary notice periods are TBD and must be agreed. Neither party should abandon active orders or necessary customer support.
Ending or suspending participation does not erase approved amounts payable, lawful refunds, disputed items awaiting review, confidentiality duties or necessary record retention. Provide a final itemized statement and resolve outstanding obligations without duplicate recovery. Support channels, review response periods and formal dispute/jurisdiction arrangements remain TBD, subject to Palestinian legal review and access to competent authorities and courts.
2. B. Captain Agreement
For the captain relationship only. Restaurant terms are separate and do not become captain obligations.
2.1. Parties, eligibility and legal status
This proposed agreement concerns the individual captain or authorized contracting party (TBD) and U-Turn’s legal company (TBD; registration and address TBD). It is separate from the Restaurant Partner Agreement. The captain must provide accurate identity and eligibility information, required driving and vehicle licences, a roadworthy vehicle and required insurance. Insurance details and any unconfirmed eligibility conditions are TBD and must be verified before work starts.
The intended working model includes agreed availability, but calling a captain independent or freelance does not determine legal classification. Status, rights and obligations depend on applicable law and the actual working arrangements. No wording removes mandatory employment, social-protection, safety or other rights where they apply. The final contracting model requires Palestinian legal review.
2.2. Availability and one active delivery
Agree availability arrangements honestly and report inability to attend or continue as soon as reasonably possible. Under the initial model, handle one active delivery at a time. U-Turn does not guarantee a number of offers, completed deliveries, hours or income. Do not accept overlapping assignments or use another person to perform an assigned delivery without prior authorization and the required verification.
2.3. Food advance and accepting an offer
Before acceptance, the offer must show the confirmed food advance required, restaurant and route information needed for the decision, the quoted delivery fee and the customer collection amount where relevant. A captain may decline an order they cannot fund. The personal-funding limit is TBD and must be agreed before operation; no undisclosed minimum float or unlimited funding obligation is created here.
Pay only the authorized food amount at pickup, obtain the required proof of payment and report any mismatch before proceeding. Use only payment or collection methods actually offered for that order. Electronic collection and payout functionality in the inspected version uses a logging/sandbox provider; live provider, payment availability and the normal electronic-payment payout schedule are TBD.
2.4. Delivery earnings and statements
For a completed delivery, the current model allocates 100% of the quoted delivery fee to the captain. The authorized food advance is accounted for separately from delivery earnings. There is no extra waiting charge under this proposed pilot policy. Any future captain membership fee requires clear advance disclosure and agreement; it must not be introduced as an undisclosed deduction.
Statements should separately identify food advances, delivery earnings, approved compensation, collections already received, lawful adjustments and amounts payable. Report discrepancies for human review. Ordinary payout timing, transfer method, provider charges and any other unconfirmed commercial detail remain TBD until agreed; these pages do not promise an operational withdrawal service.
2.5. Safe delivery and honest evidence
Check the order at pickup without opening sealed food unnecessarily, protect temperature and packaging, travel safely and hand over to the correct recipient. Follow lawful road and safety requirements; no target time requires unsafe driving or checkpoint crossing. Report closures, delays, accidents, damaged food and inability to continue promptly, giving accurate information rather than fabricating location, calls, waiting time or delivery confirmation.
For an ordinarily unreachable customer, make two reasonable contact attempts and wait ten minutes at the correct accessible location. Safety exceptions must be explained to support; do not remain in danger to satisfy a timer. A refusal or unreachable report must be investigated, and app records are evidence rather than conclusive proof. Contact-attempt records do not by themselves mean call audio is recorded.
2.6. Verified customer-caused failure: proposed compensation
After human review verifies a customer-caused failure and an authorized delivery attempt at the correct location, the proposed pilot compensation has two separate components. Evidence, prior recoveries, safety exceptions and the captain’s explanation must be reviewed. Claiming compensation must not require an unsafe attempt or a false statement.
- Food advance: the verified authorized food amount actually paid by the captain and not already recovered.
- Delivery attempt: the normal quoted delivery fee for the verified attempt at the correct location. There is no extra waiting charge.
- Deduct amounts already recovered for the same expense and explain each credit. Payment to the captain must not depend on U-Turn successfully collecting from a restaurant or customer.
2.7. Proposed claim handling and payment targets
Proposed pilot commitments requiring operational confirmation: decide straightforward claims within one business day and pay approved amounts within two business days. The meaning of a business day, payment method and practical handling of complex claims must be confirmed (TBD) before these commitments take effect. If more evidence is reasonably needed, explain what is missing and keep the captain informed; do not silently defer payment until third-party collection.
2.8. Misconduct, accidents and deductions
Investigate suspected captain misconduct separately from the customer-failure claim. An accident, allegation of damage or disputed incident does not automatically authorize a deduction or transfer all liability to the captain. Any claim or adjustment requires evidence, a lawful basis, notice of the calculation and meaningful review. Insurance coverage, reporting duties and incident-specific responsibility remain subject to confirmed arrangements and applicable law; insurance details are TBD.
2.9. Privacy and use of customer information
Use customer details only for the assigned delivery, necessary support and lawful records. Do not retain or reuse contacts or precise locations for unrelated purposes or marketing. Protect access to the device and account and promptly report unauthorized disclosure. U-Turn processes verification documents, vehicle information, availability, payouts and location as described in the Privacy Policy. The current implementation’s limits on post-completion location access are disclosed there and require verification before launch; do not assume the data disappears when a job closes.
2.10. Ending participation and dispute review
A captain may request to leave through support. Ordinary notice periods and final payout procedures are TBD and must be agreed; active deliveries must be safely resolved or transferred through support. U-Turn may impose proportionate restrictions for credible safety or serious misconduct concerns pending review, with an explanation and opportunity to respond where appropriate. Support and dispute access must remain available.
Termination does not erase approved earnings, authorized unrecovered advances, lawful confidentiality obligations or disputed claims awaiting review. Provide a final itemized statement. Support contacts, review response periods and formal dispute or jurisdiction arrangements are TBD, subject to Palestinian legal review, mandatory rights and access to competent authorities and courts.
3. Operator and contact details — to be confirmed
- Legal company name
- TBD
- Registration number
- TBD
- Registered address
- TBD
- Support email
- TBD
- Support phone
- TBD
- Support WhatsApp number
- TBD
- Privacy contact
- TBD
Contact channels are not yet confirmed. TBD values are not working contact links. U-Turn must publish usable support and privacy channels before these drafts take effect.
4. Versioning and future changes
These Version 1 terms are prepared for U-Turn’s initial pilot. Updates will be communicated before taking effect, with renewed acceptance where required. Revised charges and loss-allocation rules apply prospectively. Existing orders remain subject to the terms applicable when confirmed, together with mandatory legal rights.