Delivery Partner Terms & Safety

This is Rasoo.in’s original rider framework. It is not copied from another platform. Final commercial arrangements may be shown separately in the rider portal or onboarding approval communication.

1. Eligibility and verification

Delivery partners must meet applicable age and legal eligibility requirements, provide genuine identity and payout information, and keep required driving/vehicle documents current. Rasoo.in may verify documents and may pause access when eligibility cannot be confirmed.

2. Road safety comes before delivery speed

No order, incentive or target requires speeding, unsafe parking, red-light violations or phone use while a vehicle is moving. Riders must stop safely before interacting with the app. Protective equipment and traffic rules must be followed as applicable to the vehicle and law.

3. Vehicle and equipment

Motor-vehicle riders are responsible for maintaining valid licence, registration, insurance, pollution certificate and other legally required documents. Bicycle/e-bike requirements may differ by vehicle classification. Delivery bags and food must be handled hygienically and securely.

3A. Smart Batch / multiple food orders

Rasoo.in may offer more than one active food order to a rider only when the system determines that the pickup restaurants and customer drops are compatible with the same route and the Admin-configured capacity, wallet, added-ETA and food-in-bag safety limits are satisfied. The rider may accept or decline an offered add-on order. A rider must follow the route sequence shown in the app and must not expose one customer's identity, address or order details to another customer. Rasoo.in may stop adding orders, reroute, or reassign work if food readiness, traffic, safety, wallet status or customer delivery time is at risk.

4. App, location, dispatch coverage and privacy

Location is used for order allocation, navigation, customer tracking and delivery proof while the rider is online or handling an accepted delivery. Rasoo.in Administration privately controls dispatch coverage and broadcast radius; riders do not choose or receive the platform-wide radius setting. A rider may see order-specific pickup/drop details and estimated trip information needed to make a safe acceptance decision. Riders must not misuse customer, restaurant or platform data. Customer contact details may be masked or routed through secure calling where configured.

5. Order handling

Riders should accept only orders they can safely complete, follow pickup and delivery stages accurately, protect food from tampering, and use required customer codes or delivery proof. False location, fake proof, collusion, theft, harassment or deliberate misdelivery may lead to suspension or termination.

6. Customer and partner conduct

Respectful, non-discriminatory and professional conduct is required. Report threats, unsafe locations, accidents, harassment, damaged orders or other serious incidents to Rasoo.in support. In immediate emergencies, personal safety and local emergency services come first.

7. Earnings, payouts and cancellation compensation

Unless a written commercial schedule says otherwise, onboarding does not guarantee fixed earnings, minimum orders, fixed hours, loans, insurance or other benefits. The rider portal may show an estimated earning for an individual food-delivery offer and the final eligible earning in the rider ledger. Rasoo.in Administration controls the base/per-distance earning formula, payout status and audited adjustments. Where a customer cancels after rider assignment or pickup, a separately configured cancellation compensation may be credited when eligible; a rider-attributable cancellation does not earn that compensation by default. Applicable taxes, reversals and payout timing are recorded separately.

8. Rider Security Wallet and order eligibility

Rasoo.in may require an active Delivery Partner to maintain an Admin-configured operational security balance before a new food-delivery offer can be accepted. This security balance is separate from delivery earnings and is not represented as a bank deposit, savings product or withdrawable consumer wallet. The portal shows the current security balance and any recharge requirement. The minimum reserve and order-specific hold rules are controlled by Rasoo.in Administration and may differ for prepaid and cash-on-delivery orders.

9. Cash-on-delivery collection and settlement

When a Delivery Partner collects cash from a Customer for a COD order, the collected order amount belongs to the applicable order settlement flow and is not the Delivery Partner's earning. After verified delivery, the COD collection may be recorded as a debit in the Rider Security Wallet while the Delivery Partner's eligible delivery earning remains in the separate earnings ledger. The Delivery Partner must recharge or otherwise settle the outstanding security balance through the methods enabled by Rasoo.in before further normal orders can be accepted when the balance is below the required reserve.

10. Emergency delivery coverage

If no nearby free Delivery Partner with the required security balance is available, Rasoo.in may, when the Admin-controlled emergency setting is enabled, offer the order to one otherwise eligible and available nearby Delivery Partner even when the order hold would temporarily take that rider's security balance below zero. The configured maximum negative limit still applies. A busy rider is not forced to carry two active food deliveries at once. After an emergency exception, further normal order acceptance remains blocked until the rider recharges sufficiently to meet the configured reserve.

11. Admin controls and audit trail

Rasoo.in Administration may configure the minimum security balance, prepaid hold, COD hold percentage/minimum/maximum, emergency negative limit and whether emergency coverage is enabled. Every recharge, hold, release, COD liability and Admin adjustment is recorded in an auditable ledger. Manual Admin adjustments require a reason and do not silently alter the separate delivery-earnings ledger.

12. Fatigue and availability

Riders control when they go online subject to platform availability rules. Riders should pause when tired, unwell, distracted, or when weather/road conditions are unsafe. Rasoo.in may introduce safety reminders or temporary pauses to reduce fatigue risk.

13. Suspension and review

Accounts may be reviewed or suspended for expired KYC, serious safety violations, fraud, abuse, repeated delivery manipulation, unlawful conduct, or material breach of platform rules. Where appropriate, Rasoo.in may request clarification or fresh documents before restoring access.

14. Electronic acceptance

Acceptance is recorded with the rider account, terms version, timestamp, IP address and device/browser information for audit. Future material changes may require fresh acceptance before delivery activity continues.

Secure restaurant handover

Where enabled, a restaurant handover may require a one-time pickup code and package seal reference before an order can be marked picked up. The code is order-specific and is intended to reduce wrong-order handovers and disputes.

Multi-order and safety controls

Rasoo.in may offer compatible nearby orders as one smart delivery route only when system limits permit it. Order capacity, route compatibility, wallet/COD eligibility and customer ETA remain platform-controlled. Riders can use the in-app Safety Center to report an urgent operational safety event; this does not replace contacting the appropriate local emergency service where immediate help is needed.