Demand
Orders from verified kitchens & future grocery aisles — same-day growth as Porto expands.
EU · Halal logistics layer
Halal-first runs with clear handoff rules and upfront fees — launching in Portugal, then more EU cities. Selling instead?
For dispatch timing, fees, and compliance detail, see FAQ.
Quick signup. Add your details — we’ll invite you when dispatch opens in your area. App, Maps, and Play Console notes are in the FAQ.
Orders from verified kitchens & future grocery aisles — same-day growth as Porto expands.
See distance, fee, and estimated time before you accept. No blind batching in rider app MVP.
Per-drop fees + tips routed through a licensed PSP (e.g. Stripe Connect) when accounts are enabled.
Rider location is processed under GDPR / Lei 58/2019 — purpose-limited to dispatch, ETA, and incident review. Customers do not get your personal phone number in-app chat MVP.
24/7 safety escalation and order issue queue ship with production ops — this static page is UX only.
Three-step offer → deliver → earn loop — built for halal-only pickups with clear proof-of-delivery rules.
Pickup, drop-off, distance, fee before accept.
Navigation, in-app chat, photo / PIN proof of delivery.
Per-drop fees + tips; weekly payout after fraud checks.
We prioritise predictable offers, a halal-only partner network, and EU-grade compliance — clear rules and documentation instead of opaque gig churn.
You’ll receive platform-assigned halal pickups with proof of delivery. Per-drop fees stay visible before you accept, with tips and payouts routed through a licensed payment provider when accounts are enabled — first in Portugal, then more EU markets.
Yes — base city + radius you set in rider profile; offers only inside that polygon.
Allowed where law permits; GO does not exclusivity-lock riders in pilot phase.
Roadmap: rider beta after merchant CSV import + PSP — watch this page or email eathalaleu@gmail.com from the waitlist.
Offers, turn-by-turn navigation, proof of delivery, and earnings — once native rider apps ship.
Pickup, drop-off, distance, and fee before you accept.
Navigation, chat, and handover confirmation.
Per-drop fees and tips, tied to payouts when payments are live.
Two tracks: Google Play for publishing the customer and rider apps; Google Maps Platform for routing and (later) live location. Live rider dots need GPS → your backend → a map SDK, with EU privacy and foreground-service rules in mind.
lat,lng to your server; clients subscribe over your channel of choice. Apply GDPR minimisation, retention limits, and Android foreground-service requirements in the EU.
Maps Platform terms (Google).