Privacy Policy

UberEats Order Tracker Chrome Extension

This Policy Explains Exactly What Data The UberEats Order Tracker Extension Accesses, How It Is Used, Where It Is Stored, And Your Rights As A User, We Are Committed To Full Transparency - Your Data Never Leaves Your Device

No Data Collection
No Third-Party Sharing
No Remote Servers
Local Storage Only

Table Of Contents

  1. 01 What Data We Access
  2. 02 How The Extension Works
  3. 03 Permissions Explained
  4. 04 Local Data Storage
  5. 05 Third-Party Services
  6. 06 Security
  7. 07 Your Rights And Controls
  8. 09 Changes To This Policy
  9. 10 Contact

01 - What Data We Access

The Extension Reads The Following Data From Your Browser and The UberEats Service All Data Is Processed Locally On Your Device Only

UberEats Authentication Cookies

The Extension Reads Your Browser's Cookies For www.ubereats.com To Authenticate Your Session, Specifically, It Uses The Session Token And CSRF Token Stored In These Cookies, These Credentials Are Used Only To Make API Calls To UberEats On Your Behalf - They Are Never Transmitted Anywhere Else And Are Never Stored Persistently By This Extension

Order History

Past And Current Order Data Fetched Directly From The UberEats API Using Your Authenticated Session, This Includes Order Items, Restaurant Names, Prices, Delivery Details, And Timestamps This Data Is Cached Locally On Your Device To Enable Instant Loading

Account Profile

Basic Profile Information Returned By The UberEats API: Your Name, Profile Picture URL, Account Creation Date, Subscription Status, And Country. This Is Displayed In The Extension Popup And Cached Locally For Performance, It Is Never Shared Or Transmitted Anywhere Else

Location Locale

Your Country Code Is Extracted From The UberEats Location Cookie (uev2.loc) Solely To Correctly Format API Requests For Your Region (e.g. Currency Symbols, Locale Codes) No Precise Location Data Is Accessed Or Stored

02 - How The Extension Works

Understanding The Technical Architecture Helps Demonstrate That Your Data Remains Private

Authentication Via Browser Cookies

When You Open The Popup, The Extension's Background Service Worker Reads Your Existing UberEats Cookies From Your Browsers Secure Cookie Store, These Cookies Were Set When You Logged Into UberEats In Your Browser - The Extension Does Not Log You In Or Store Your Username Or Password

Direct API Calls To UberEats

Using Your Session Cookies As Authentication Headers, The Extension Makes HTTPS Requests Directly To www.ubereats.com - The Same Server Your Browser Communicates With, There Is No Intermediary Proxy Server, No Developer-Owned Backend, And No Third-Party Relay

Local Processing And Caching

All Data Returned By UberEats Is Processed In-Memory And Cached Using Your Browsers Built-In Local Storage API, Which Stores Data Only On Your Local Device, No Remote Database Is Involved

Incremental Refresh

On Subsequent Opens, The Extension Only Fetches Orders Newer Than Those Already Cached, Minimising API Calls, The Extension Does Not Run In The Background When The Popup Is Closed - It Is Entirely Passive

03 - Permissions Explained

The Extension Requests Only The Minimum Permissions Necessary To Function Here Is A Plain-English Explanation Of Each Permission

Permission Why It Is Required
Cookies To Read Your UberEats Session And CSRF Tokens From The Browser's Cookie Store These Are Used As Authentication Headers For API Calls, The Extension Only Reads Cookies For www.ubereats.com - It Cannot Read Cookies For Any Other Site
Storage To Persist Your Order History Locally Using Local Storage So The Popup Loads Instantly On Subsequent Opens Without Fetching All Data Again This Storage Is Local To Your Device Only
Host: ubereats.com Host Permission For https://www.ubereats.com/* Allows The Extension To Make Authenticated Fetch Requests To The UberEats API and To Set Custom Request Headers (Including The Cookie Header) - A Capability That Is Normally Restricted To Extensions For Security Reasons

04 - Local Data Storage

The Following Data Is Stored Locally Using Local Storage. This Storage Is Sandboxed To The Extension And Is Only Accessible By This Extension - No Website Or Other Extension Can Read It

Order History Cache

A Local Copy Of Your Fetched Order Data To Enable Instant Loading And Incremental Refresh

Profile Cache

Your Name, Profile Picture URL, Uber One Subscription Status, And Account Metadata Returned By UberEats

Cache Timestamp

The Time Of The Most Recent Successful Data Refresh, Shown In The Extension Header

Important: Cached Data Is Never Sent Anywhere It Exists Solely On Your Local Machine To Improve Performance. You Can Delete It At Any Time By Removing The Extension Or Clearing Extension Storage Via Your Browsers Developer Tools

05 - Third-Party Services

No Third-Party Data Sharing

Your Data Is Never Sold, Rented, Shared, Or Transmitted To Any Third Party, There Are No Analytics Services, Crash Reporting Tools, Advertising Networks, Or External APIs Involved

The Only External Network Communication This Extension Performs Is Directly To www.ubereats.com On Your Behalf - The Same Service You Are Already Authenticated With

All JavaScript Libraries Used By The Extension (Chart.js And Font Awesome) Are Bundled Locally Within The Extension Package, No CDN Requests Are Made, And No Remote Scripts Are Ever Loaded Or Executed - This Is Required By Chrome's Manifest V3 Security Policy

06 - Security

HTTPS Only

All API Calls Are Made Over HTTPS, No Plain-Text HTTP Connections Are Used

Manifest V3 Compliance

The Extension Is Built On Chrome's Latest Manifest V3 Standard, Which Enforces A Strict Content Security Policy, Prohibits Eval And Remote Code Execution, and Uses A Restricted Service Worker Model For Background Processing

No Persistent Background Activity

The Extension Uses A Manifest V3 Service Worker Which Is Terminated When Not In Use The Extension Performs No Background Monitoring, Tracking, Or Data Collection When The Popup Is Closed

Storage Sandboxing

Data Stored In Local Storage Is Sandboxed To This Extension, It Cannot Be Accessed By Web Pages, Other Extensions, Or Any Other Software

07 - Your Rights And Controls

You Have Full Control Over Your Data At All Times

Delete Cached Data

To Delete All Locally Cached Data (Order History, Profile), Remove The Extension From Chrome Via chrome://extensions. Alternatively, You Can Clear It Via Chrome DevTools (Application → Storage → Extension Storage)

chrome://extensions → UberEats Order Tracker → Remove
Revoke Cookie Access

You Can Revoke The Extension's Access To Your UberEats Cookies At Any Time By Removing The Extension, Logging Out Of UberEats In Your Browser Will Also Invalidate The Session Tokens, Making Any Cached Credentials Useless

No Account Required

The Extension Does Not Require You To Create An Account With Us, There Is No Registration, Login, Or Account Management Of Any Kind Within This Extension

08 - Changes To This Policy

If This Privacy Policy Changes, An Updated Version Will Be Included In The Next Chrome Web Store Release Of The Extension, Continued Use Of The Extension After An Update Constitutes Acceptance Of The Revised Policy

We Will Never Change Our Core Commitment: Your Data Stays On Your Device And Is Never Shared With Anyone

09 - Contact

If You Have Any Questions About This Privacy Policy Or How The Extension Handles Your Data, Please Open An Issue On The Chrome Web Store Listing Page Or Contact The Developer Directly Via The Support Link In The Extension's Store Listing

We Aim To Respond To All Privacy-Related Enquiries Within 7 Business Days
UberEats Order Tracker

This Extension Is Not Affiliated With, Endorsed By, Or In Any Way Associated With Uber Technologies, Inc. Or UberEats UberEats Is A Trademark Of Uber Technologies, Inc.

Last Updated: April 2026