1. Information we collect
We collect account details, role, contact information, restaurant and menu details, order contents, delivery addresses, bids, payment status, credit transactions, support disputes, order messages, and operational event history. We do not store full card numbers or card security codes; Stripe processes payment credentials.
2. Driver location
Precise GPS is collected only after an assigned driver enables tracking and only while an order is picked up or out for delivery. The location is shared with the order’s restaurant and customer for coordination and safety. Tracking stops when the driver disables it or the delivery closes. Location history is retained only as long as needed for operations, dispute resolution, safety, and legal obligations.
3. How we use information
We use information to authenticate users, operate auctions and deliveries, process credit and payment events, provide live tracking and chat, prevent fraud, provide support, resolve disputes, maintain security, meet legal obligations, and improve reliability.
4. Sharing
Order participants see the details needed to complete the order. Unassigned drivers receive limited delivery information; exact customer contact and address details are revealed only after assignment. Service providers such as PostgreSQL hosting, Amazon SES or SMTP email delivery, consent-based Twilio SMS, Stripe, and map providers receive only the data needed for their services. We may disclose information when legally required or necessary to protect users.
Customers may use a private delivery tracking link without an account. Anyone holding that complete link can view delivery progress and its handoff code, and submit customer ratings after delivery. Keep it private; access expires seven days after closure. Private order data and driver locations are not cached for offline use.
Coordination-only deliveries have no customer portal or automatic customer messages. Driver minimum, ideal, and stoked quote preferences are private to that driver. Businesses and drivers receive payment confirmation for assigned jobs; competing drivers do not receive each other’s quotes.
5. Cookies and sessions
Ungouged uses a secure, HTTP-only session cookie for authentication and security. We do not use advertising cookies. Password reset and verification tokens are stored only as cryptographic hashes.
6. Retention and security
We use Argon2id password hashing, encrypted transport, role-based authorization, expiring sessions, audit events, and restricted operational access. No system is perfectly secure. We retain records according to operational, accounting, fraud-prevention, dispute, and legal needs, then delete or anonymize them when those needs end.
7. Your choices and rights
You can update account information in Settings and control browser location permission. Depending on your jurisdiction, you may request access, correction, deletion, portability, restriction, or objection. Some transaction records must be retained by law. Contact support to make a privacy request.
8. Children and changes
Ungouged is not intended for children under 13, or the minimum age required by local law. Material policy changes will be posted with a new effective date and, where appropriate, communicated to account holders.