Privacy policy

Who we are

Giga Driver is an app for gig delivery and rideshare drivers. It’s made by an independent developer in the United States.

This policy covers:

• The Android app, both the Google Play version and the direct-download version from gigadriver.app.
• The iPhone app.
• This website, gigadriver.app.

What we collect

Your account

There are three ways to sign in:

• With Google. We keep your Google account ID, email address and name. We don’t keep your photo.
• With Apple, on iPhone.
• With your phone number. We keep the number. Sign-in codes are texted from a phone we run, through its carrier, and are stored only in scrambled form (a salted hash).

Your phone and the app

• A random install ID. The app registers with our server the first time it opens.
• Your device model, operating system version and app version.
• The IP address of each upload, and the rough location (city, region, country and a rough map point) that our network provider, Cloudflare, works out from it.

Your location

Giga Driver needs your precise location to work during a shift. It doesn’t track you all the time. The Android app reads your phone’s last known location only at certain moments: when you open the app, when you tap GO, when an offer is shown, when a job changes stage, and, in the direct-download version, when it asks Apple Maps for the drive to an Instacart store.

The location is sent to our server so the app can show where each offer came from. To turn coordinates into street and place names, our server sends a point rounded to about 100 meters to OpenStreetMap’s Nominatim service.

When you open the app and when you tap GO, the app sends your position, rounded to about 1 kilometer, so our server can find your state or province, county and city. If you never changed a setting, the app then uses the minimum wage of that place as your target pay per hour. Our server keeps only the place it found for your install (country, state or province, county and city), not the position, and it remains in restricted history after account deletion.

In the direct-download version, while the Instacart Shopper batch list is on your screen or you open a batch, the app asks Apple Maps for the drive from your position to each batch’s store. Your phone sends your position and the store’s street address straight to Apple; they do not pass through our server. Our server only gives the app a short-lived Apple Maps key. The app keeps the drive time in minutes, never the street address.

Offers on your screen

With your permission, the app uses Android’s accessibility service to read the offer cards that DoorDash, Uber Driver, Lyft Driver and Instacart Shopper show on your screen. This is how it grades each offer.

It keeps offer details such as payout, distance, time, number of stops or items, store name and ride type. It also keeps the first lines of those apps’ pay screens.

It never accepts or declines offers for you. The Google Play version never taps anything. The direct-download version can tap the two map pins on a DoorDash offer to read the street names, but only if you turn that on.

Screen images

To read offer cards, the Android app takes temporary screenshots and reads them on your phone.

Newer versions of the Android app also send a picture of the whole screen to our server. They do this the first time that they read each offer card. The Google Play version and the direct-download version both do this. Our team uses these pictures to check what the app read and to make it read offers better.

• The picture shows all of your screen at that moment. Giga Driver’s own windows are black in it.
• The picture can show the store, the map, names, addresses, notifications or other details that are on your screen. For example, ride offer cards show the pickup and drop-off places.
• With each picture, the app sends the text that it read from the screen.
• Each picture is at most 900 pixels wide and at most 200 KB.
• The app sends at most 500 pictures in one shift.
• On mobile data, the app sends pictures only up to a limit for each shift, normally 5 MB. The other pictures wait until your phone is on Wi-Fi.
• Pictures and their text leave the active collection after 30 days and remain in restricted history.

Earlier versions send fewer pictures or none. Some send only a picture of a DoorDash offer card, not of the whole screen, when the app cannot tell the type of the offer. They send at most 20 in one shift.

There is no setting to turn off only these pictures. The app makes them only while it reads offers during a shift.

Screenshot offers is a separate, optional setting that is off by default. If you turn it on, the Android app saves a full-screen image of each detected supported offer to Pictures/Giga Driver/Offers in your phone’s gallery. These saved photos remain until you delete them; the 24-hour diagnostic limit does not apply. Giga Driver does not upload them. Your gallery or photo backup service may back them up according to your phone’s settings.

The direct-download version has a diagnostic calibration mode that you can start in Developer tools. While it runs, screenshots, cropped offer cards and diagnostic files are uploaded to our server to help the app read offers more accurately. The Google Play version doesn’t include this mode. Private diagnostic screenshots on the phone leave active capture storage 24 hours after the diagnostic session starts. Cleanup retains original files in the app’s private archive until you clear or uninstall the app.

Notifications

With your permission, the app reads notifications from DoorDash, Uber Driver and Instacart Shopper only. It ignores all other notifications. For pay notifications, it keeps the title and text, up to 160 characters.

Diagnostics

To keep the app working, it sends us:

• Battery level, your phone’s temperature status and free storage.
• Which permissions you’ve granted.
• Your network type, such as Wi-Fi or mobile data.
• Older versions of the Android app send the versions of the driver apps on your phone, such as Uber Driver and DoorDash. Newer versions do not send them.
• Crash reports, with the error and recent app log lines.

To help with a problem, the developer can ask the app on your phone to send its settings, status and recent app logs.

Your app preferences and discovery response

While you are signed in, the apps send your saved trip goals, time estimates and other app preferences to our server. These include language and, where available, enabled filters, watched apps, screenshot saving, display choices and your advertising measurement choice. We link these reports to your account to understand which defaults drivers change and calculate averages and choice counts. The preferences report keeps only the latest settings reported for each platform, not a change history. These reports are not sent to advertising services. After sign-in, the app asks where you first heard about Giga Driver. Select a category to continue. We keep your selected category, or a skipped status saved by an older app version, with your account to understand which channels bring drivers to the app and avoid asking again. This response is not sent to advertising services and remains in restricted history after account deletion.

Your answers about how you drive

After sign-in, the app also asks a few questions about how you drive: which gig apps you use, whether you drive full-time or part-time, how long you have been driving, what kind of area you drive in most, how you decide which offers to take, where you get tips from other drivers, and what you earn in a typical week from gig driving. For earnings, you can choose “Prefer not to say”. Earlier versions also asked which vehicle you use. We keep your answers with your account to understand who uses Giga Driver and to improve the app. Your answer about gig apps does not change which apps Giga Driver reads. These answers are not sent to advertising services and remain in restricted history after account deletion.

App journeys

The Android and iPhone apps send setup steps, permission requests and results, sign-in outcomes, app visits, shift-start outcomes, grade-presentation results, and paywall, plan-selection and checkout outcomes to our server. These records include timestamps, random event and session IDs, install ID, app version and platform, and the signed-in account ID when available. They use a fixed list of event names and outcomes, without passwords, sign-in codes, entered text, payment-card details, screenshots or additional location data.

We use these records to find where setup or checkout fails and whether people return and successfully grade offers. Account-linked activity stays with the account that produced it; earlier anonymous activity is not assigned to an account after sign-in. This analytics runs on our own backend, without a third-party mobile analytics SDK or advertising tracking.

Home cards are chosen using existing account details such as subscription or trial status, platform, app build, account age and recent app activity. We record when a card is shown, when its store or in-app destination opens, and when you dismiss it, with your account, campaign and event identifiers and timestamps. Opening the store does not tell us whether you submitted a rating. Dismissing a campaign hides it across your account’s devices; our team can explicitly restore it or change the selected campaign. These records stay on our own server and are not sent to advertising services.

Purchases

Subscriptions are sold through Whop (whop.com), which handles payment. We pass your email address to Whop’s checkout. From Whop, we get your membership ID, plan, status and renewal date.

Where available, subscriptions purchased in the Google Play version are handled by Google Play. The app sends the purchase token and product ID to our server so we can verify access with Google. We keep the token, its hashed identifier, the account association, and Google-verified product, plan, subscription status, expiry, renewal, trial and test-purchase information. For each charge that Google confirms, we also keep its order number, the amount you paid after any discount and with tax, the currency, when Google processed it and, when Google reports it, whether the order was refunded. Google handles payment details; we do not receive card numbers.

For subscriptions purchased through Whop or the App Store, we also keep provider-verified transaction and subscription events, such as trial starts, payments, renewals, payment failures, cancellation changes, refunds and expiry, when the provider supplies them. A checkout click or return to the app is not treated as payment confirmation.

Website subscriptions and sign-in

You can subscribe on this website after signing in with Google or Apple. Use the same sign-in method and account that you use in Giga Driver. We match the provider’s account identifier, not just an email address, so Google and Apple sign-ins remain separate accounts. Google provides your account ID, email address and name. Apple provides your account ID and an email address when available, which may be a private relay address.

Website sign-in creates a session that lasts up to 2 hours. Your browser tab stores the session token; our server stores only its hash. Apple sign-in also uses two temporary, secure cookies to connect Apple’s response to the browser that started sign-in and finish the sign-in safely. They last up to 10 minutes and 2 minutes, respectively, and are cleared when their steps finish. They are used for authentication, not advertising. We keep Apple authorization tokens with your account so we can revoke website access when you delete the account.

When you continue to Whop, we send your chosen plan, Giga Driver account reference and email address when available. Whop handles checkout and payment details. We keep the chosen plan, checkout link and creation time with your account so you can resume an unfinished checkout without creating another one. This record is closed after we verify the subscription or when you delete your account, and its history is retained. Returning from checkout alone does not activate access; our server verifies the subscription with Whop.

Our website’s subscription and plan-management pages do not load Google Analytics, the Meta Pixel or Whop’s advertising scripts. The separate Whop payment page follows Whop’s privacy policy. Subscribing on the website is optional; installing the app does not require a website subscription.

The former Google Play signup page

Giga Driver is now available directly on Google Play. Our Android download links open its store listing. Installing does not require joining a test group or signing in on this website. The following paragraphs explain records kept from our former Google Play test signup page.

The former page used Google sign-in. We keep your Google account ID, email address and name, as we do when you sign in with Google in the app. This is the same Giga Driver account that you use in the app.

When you sign in, your browser tab gets a session token. The session ends after 2 hours. Our server keeps the token only in scrambled form (a hash).

That page asked you to join a Google Group that we manage. You joined it yourself with your Google account. The group still exists for testers, but it is not needed to install the production app. Installing does not require a trial or subscription.

As the group’s owner, we can see the email addresses of its members. Other members cannot see them. You can leave the group at any time from its page, groups.google.com/g/giga-driver-android. Deleting your Giga Driver account does not remove you from the group.

Our server keeps records of steps and links from the former page: sign-in, reaching the installation instructions, and opening the group, test invitation and Google Play links. Earlier versions also recorded checkout starts. Each record is in your Giga Driver account and has the first time, the last time and the number of times. We use these records to understand the old signup flow. They used no cookies and no code from other companies. These records remain in restricted history after account deletion.

The former page ran Google’s sign-in button. While website advertising measurement was on, the Meta Pixel could also send a page view on its public entry page, using the saved preference described below. It did not run on checkout return pages. The page itself did not give the Meta Pixel sign-in details, contact fields or payment information. Our server can still send Meta trials and payments linked to saved advertising details, as the next paragraphs describe. Google Analytics and Whop’s tracking code did not run there.

When advertising measurement was on and you signed in on that page, we saved these advertising details with your Giga Driver account:

• The Meta click ID and campaign labels from the link of the ad that brought you there, if you came from an ad.
• Meta’s _fbc and _fbp cookies, if your browser has them.
• Your IP address and browser details.

We stop using these details after 180 days and retain their history. The campaign labels show us which ads brought drivers to Giga Driver. Our server does not send them to Meta.

While we keep these details, our server can tell Meta when you start a trial or pay for Giga Driver, so that Meta can measure our ads and show them to people who are more likely to subscribe. It sends only trials and payments that happen after we first saved the details:

• The start of a Google Play free trial, after Google confirms it.
• Payments that Google Play confirms, and payments that Whop charges automatically, such as renewals and the first payment after a free trial.

With each trial or payment, Meta gets:

• Whether it is a trial or a payment, and when it happened. For a payment, the amount and currency.
• A purchase reference that our server makes in scrambled form (a hash).
• Your email address and phone number, if your account has them, and your Giga Driver account ID, each in scrambled form.
• The saved Meta click ID, _fbc and _fbp cookies, IP address and browser details, and the address of the Google Play test page.

Meta can compare the scrambled email address and phone number with its own records to find your Facebook or Instagram account, and connect the trial or payment to an ad that you saw or tapped there. This is not anonymous reporting. Our server does not send Meta your name, payment card details, offers, shifts, screenshots or precise location.

To stop this, open the Android advertising details page linked below, sign in with the same Google account, and turn off advertising measurement. Our server then stops using your saved advertising details, retains their history, and cancels the trials and payments that it has not sent yet. Turning measurement off elsewhere on this website stops browser tracking; sign in on the linked page to apply that choice to your saved account details too. This page loads no advertising scripts and saves no new advertising details. A request already on its way to Meta can still arrive. Turning measurement off does not erase what Meta already has, and it does not change your trial or subscription.

Manage saved Android advertising details

Messages from the mail button are stored with your account and read by the team, including in restricted history after account deletion.

Reminders and offers

If you opt in to reminders and offers, we use your signup, shift and graded-offer activity and your trial and subscription status to choose relevant reminders and campaigns. We store your push token linked to your account, your phone’s time zone, language, notification permission and reminder preference, plus scheduling, delivery and opening records. Our server manages the campaigns. Apple Push Notification service delivers iPhone notifications; Google Firebase Cloud Messaging delivers Android notifications and uses a Firebase installation identifier. These services receive the push token, notification text and account identifier. You can turn reminders and offers off in Profile settings or turn notifications off in your phone’s settings. We stop future notifications after sign-out, when you opt out or when you no longer match the campaign. Subscribing stops trial reminders. Deleting your account stops notifications; notification history remains in restricted records. Provider acceptance does not prove that a notification was displayed.

This website

Google Analytics is on by default unless you turn it off in Privacy settings. It measures page visits and clicks on app-download links, using the public page, button placement, language, and download channel. These clicks do not prove an installation. Its advertising features are turned off. Cloudflare may measure page visits without using cookies. Google’s privacy policy

Google Analytics and advertising measurement are separate choices in Privacy settings at the bottom of the page. Both are optional and on by default. You can turn either off, and we honor your saved choices.

When advertising measurement is on, Whop’s tracking code measures visits to public website pages and clicks on app download links to help us understand which ads bring visitors. It uses cookies, browser storage and browser and device identifiers, including fingerprinting. Whop receives your IP address, browser and device details, full page URLs and referring URLs, including information in those URLs.

Whop’s advertising code can also collect names, email addresses and phone numbers from URLs or form fields when present. The public website pages where this code can run have no contact, sign-in or payment forms. It does not run on our subscription, plan-management or Android advertising-details pages, and did not run on the former Google Play signup page. Whop may link website activity to its customer records and share it with advertising partners for attribution and ad measurement. Whop’s privacy policy

When advertising measurement is on, the Meta Pixel sends Meta page views and app-download link clicks, cookies such as _fbp and _fbc, your IP address, browser details, and page URLs and referrers. Meta may match this activity to your Facebook or Instagram account to measure ads. This website does not give this pixel name, email or phone fields. Our server can send it trials and payments with a scrambled email address and phone number, as described above for the Google Play test page. Meta’s privacy policy

This website tracking does not send data from the Android or iPhone apps, such as offer details, shifts, screenshots or location. Download clicks do not tell us whether you installed the app. Apart from the trials and payments described above for the Google Play test page, we do not send app sign-ups or purchases through this website tracking.

You can change either choice in Privacy settings. We remember a saved opt-out in this browser until you change it or clear browser storage. Turning advertising measurement off saves that choice, clears the tracking cookies and browser storage we recognize on this site, and reloads the page to stop Whop’s and Meta’s code. Requests already queued may finish sending. Turning tracking off does not erase information already sent; see their privacy policies for retention and privacy choices.

Optional app advertising measurement

Where available, app advertising measurement is separate from website tracking. Supported iPhone releases can start private Apple aggregate reporting on for new installations; existing installations keep their previous choice. iPhone Meta tracking requires both your app choice and Apple’s tracking permission. Newer versions of the Google Play app can send events to Meta. The next paragraphs describe this. You can turn app ad measurement off in Settings. Declining does not change app access, prices or subscriptions.

In these Google Play versions, Meta measurement can start on by itself. It starts only when all of these conditions are true:

• This installation of the app has no earlier measurement choice.
• Our server finds that your current internet connection is in the United States. It uses the country that Cloudflare finds from your IP address. This is an estimate, not your precise location or proof of where you live.
• The app showed you its full ad measurement notice, on the sign-in screen or in Settings.

In all other cases, Meta measurement stays off until you turn it on yourself with the Ad measurement switch. You can turn it on in any country. The app then sends the same events and data, with the same limits.

When Meta measurement is on, the app can send Meta these events:

• An installation event, one time for each installation.
• A trial event, after our server confirms with Google that you started a new Google Play free trial. The event shows a value of zero.

With these events, Meta gets:

• An ID that Meta’s software makes for this installation of the app.
• The Google Play install referrer. It can show the ad or link that brought you to the app.
• Information about the app and your phone: app version, Android version, phone model, language and region setting, time zone, mobile carrier, screen size, number of processor cores and storage space.
• Your IP address. Meta can find your approximate location from it.
• For a trial event, the subscription product and a purchase reference. Our server makes this reference from Google’s purchase token in scrambled form (a hash).

Meta can use this information to connect the installation or trial to an ad that you saw or tapped on Facebook or Instagram. This is not anonymous reporting.

The app asks Meta to use these events only for analytics and ad measurement, not to target ads to you. The app also turns on Meta’s Limited Data Use option. Meta applies this option only in some US states.

The app does not send Meta your name, email address, phone number, account ID, payment card details, offers, shifts, screenshots or precise location. The Google Play app does not have Android’s advertising ID permission, so it does not send your Android advertising ID.

In newer Google Play versions, Meta measurement also lets our server tell Meta about your Google Play payments, including renewals and the first payment after a free trial. The app sends our server the ID that Meta’s software made for this installation, with your account and the app and Android versions. For each payment that Google confirms, our server sends Meta that installation ID, the amount, currency and time, and a payment reference made from Google’s order number in scrambled form (a hash). It uses the same Limited Data Use option and sends no advertising ID. This can happen while the app is closed. When Meta measurement started on by itself, the app renews this permission about once a week while you are in the US, and it ends 30 days after the last renewal. Turning measurement off, signing out, or a check that finds you outside the US ends it when the app next connects. A payment already on its way to Meta can still arrive.

To turn Meta measurement off, use the Ad measurement switch on the sign-in screen or in Settings. The app keeps this choice on this installation after you sign out and after app updates. If you turned measurement on yourself, signing out turns it off. When measurement is off, the app sends no new events. Events that Meta’s software already put in its queue can still go to Meta. When you turn it off, Meta does not delete data that it already has.

On supported iPhone versions, the app can ask Apple to report aggregate installation and trial milestones through SKAdNetwork. We send Apple conversion values rather than your account, email or advertising identifier. Apple controls whether, when and at what level of detail it sends an attributed report to an ad network. This private aggregate route does not require Apple’s tracking permission. It starts on only for new installations of a configured release; an upgrade does not override an earlier choice, and you can turn it off in Giga Driver’s Settings. The current aggregate mapping does not report paid revenue.

If you also allow Apple’s tracking permission, the supported iPhone app can send Meta installation and activation events, verified new trials, and verified initial paid App Store purchases. These events include the event time, product or plan, a conversion reference, amount and currency when relevant, plus technical app and device information, your IP address and advertising identifier. Meta may match this information to your Facebook or Instagram account. We do not provide your account name, email, phone number or payment-card details to Meta’s app measurement.

In supported iPhone releases, a new Ad measurement choice with Apple tracking permission can also allow our server to report verified automatic Apple and Whop subscription payments, including the first charge after a free trial. The server keeps your permission, app installation ID and advertising identifier linked to your account, and sends Meta the actual payment amount, currency, time and a payment reference. This can happen while the app is closed. Turning measurement off or changing Apple tracking permission stops server reporting when the app next connects and sends the change; requests already in flight can finish. Earlier choices do not automatically enable this route.

For a new Whop trial started from a supported iPhone app with Ad measurement allowed, our server temporarily links the checkout to your account, installation, plan and permission status. We check Whop’s records for a completed trial with a saved payment method before returning a measurement receipt to that same app account and installation. We keep payment references and the method type, not card numbers. A free trial is reported as a trial with zero revenue; it does not prove a future paid renewal. Existing memberships and simply returning from checkout do not create this event.

Older app versions and other builds may instead use Whop-based app ad measurement. With separate permission, and Apple’s tracking permission on iPhone, our server can send Whop a new-account signup and a verified initial paid App Store purchase, including the event time, account identifier, account email when available, and purchase amount and currency. Whop may match these records to its customers and share them with advertising partners. New iPhone versions using Meta app measurement do not use this account-and-email export route.

App advertising measurement never sends offer details, shift records, screenshots, location or the detailed app journey records described above. You can withdraw in the app’s Settings. On supported iPhone versions, this stops new Meta event handoffs and Apple aggregate updates, and discards pending measurement records. For the older Whop-based route, exports stop after the server receives the change. Requests already handed off may finish. Withdrawal does not erase information already sent or undo matches already made. Whop continues to keep its own payment records. Website and app choices are managed separately.

On iPhone

The iPhone app works a little differently from the Android app.

Before you agree

On iPhone, app journey events and shift diagnostics begin after you tap Continue in setup to agree. Earlier journey events are discarded, not saved for later upload. If you choose to sign in before agreeing, the app can register with our server and send the information needed to complete that sign-in.

App compatibility in your profile

App compatibility sharing is optional and off by default. If you turn it on in Settings while signed in, the iPhone app checks whether your phone can open links for a fixed list of known gig and driver-helper apps, at most once every seven days when you open Giga Driver. On your phone, the results help choose which Uber, Lyft and DoorDash offer readers to run; visible offer cards can override older results. We store the initial results and later changes in your account profile so authorized Giga Driver administrators can help troubleshoot problems. Unchanged scans add no profile record or update; the weekly scan schedule stays on the phone. An unavailable or unverified link does not prove that an app is absent. These checks do not reveal the app currently on screen, another app’s activity or settings, or whether you have a driver account.

We do not use app compatibility records for analytics, advertising or marketing, or send them to advertising services. Turn off Share app compatibility with my profile in Settings to stop new checks and uploads. Signing out also turns sharing off. Turning it off does not erase previously saved profile records; they remain in restricted history after account deletion.

How it reads offers

When you start a shift, you share your screen with Giga Driver using iOS screen sharing, and iOS shows a recording sign the whole time. The app reads the screen on your phone to find Uber, Lyft and DoorDash offer cards. It doesn’t read your notifications.

What it keeps from offers

For each offer it grades, it keeps the pay, distance, time, the grade and where your phone was when the offer appeared. It doesn’t keep store names or pay screens in these offer details, but the screen pictures described below can show a store name.

Offers it can’t grade

If it sees what looks like an offer card but can’t grade it within a few seconds, it sends up to 40 lines of text from inside that card, so we can fix the reader. This text can include names and addresses shown in the card.

Screen images

The iPhone app doesn’t upload screenshots or screen images.

Location

While a shift is running, the iPhone app reads your location to work out the drive to each offer’s pickup, and on to the drop-off, with current traffic, and uses it in the grade. It asks Apple Maps for the route, so Apple receives your position and the pickup and drop-off shown on the card. With each offer, when an Uber or DoorDash trip changes stage, when you open the app and when you tap GO, the app also sends your latest location to our server, so we can see where each offer came from and use it to grade offers better. When you open the app and at GO, the position is rounded to about 1 kilometer and used only to find your state or province, county and city for your default target pay per hour, as on Android. It doesn’t send a continuous record of where you go. When you stop the shift, the app stops reading your location, except to find your state or province, county and city when you open the app.

Diagnostics

On top of the diagnostics above, it sends:

• Memory and CPU use.
• Whether you’re on a call, using car audio, or have the phone locked.
• The app’s state, Low Power and Low Data Mode, and whether Live Activities and Background App Refresh are on.
• How fast it reads offers, and reports when the app freezes.

After a crash, it sends the end of its log the next time it opens, and we keep it active for 90 days and retain it in restricted history afterward.

Sign in with Apple

We keep your Apple user ID, your email (which may be a private relay address from Apple), and the name Apple shares on your first sign-in. If you delete your account, we also ask Apple to remove Giga Driver’s access to your Apple ID.

How we use it

We use your information to:

• Run the app: grade offers and show your shifts and earnings.
• Improve how the app reads offers.
• Keep the service working and fix problems.
• Handle subscriptions.
• Keep records from the former Google Play signup page and honor your advertising choices.

On Android and iPhone, we link the offer details already sent to our server to your signed-in account so your offer history can return when you reinstall the app or sign in on another phone. This restores offer details, not saved screenshots. The app keeps an offline copy for your signed-in account.

We do not sell your offer, shift, screenshot or location data or use it for advertising. Optional website and app advertising measurement uses only the information described above, with separate choices.

Who else gets it

These are the only other services that get your data:

• Cloudflare. All traffic to our server and this website passes through it.
• Google. It checks Google sign-in, keeps the member list of our Google Play test group, handles Google Play purchases where available and verifies their status for us, and runs website analytics unless you turn it off.
• Apple. It handles Sign in with Apple, App Store subscriptions, optional aggregate app ad measurement, and Apple Maps drive times (it receives your position and the pickup, drop-off or store address). Our nightly database backups are stored in iCloud Drive.
• Whop. It handles payments and website advertising measurement with its advertising partners unless you turn that measurement off. Older app versions and other builds may use its app advertising measurement with separate permission, as described above.
• Meta. It receives website advertising events unless you turn that measurement off, including trials and payments for drivers who signed in on the former Google Play test page, supported iPhone app advertising events only with both Giga Driver’s Ad measurement choice and Apple’s tracking permission, and Google Play app events when Meta measurement is on, as described above.
• OpenStreetMap Nominatim. It gets rounded coordinates only.
• Our phone’s mobile carrier. It carries the sign-in codes we text you.

We do not share offers, shifts, screenshots, location or detailed app journey records with ad networks. Optional advertising measurement shares only the limited website, account and conversion information described above through the applicable Whop, Meta or Apple route.

How we protect it

Everything sent to our server is encrypted in transit (HTTPS).

How long we keep it

Original records are retained for support, billing history and investigation. Account deletion and expiry hide records from normal use; they do not erase the retained copies. There is currently no automatic erasure date.

This includes your account and sign-in history, offers and shifts, support messages, billing and trial records, preferences, survey answers, mileage and fuel records, uploaded images and diagnostic files.

Uploaded images leave the active collection after 30 days, most diagnostic files after 90 days, and crash reports after 180 days. The files remain in restricted storage with their original records.

Detailed app journey events and Home card interactions leave normal reports after 90 days. Their original records remain available in restricted history.

Advertising permissions still expire or stop when withdrawn. Retained delivery records do not authorize new advertising events. Information already sent to Apple, Google, Meta or Whop follows each service’s retention policies.

The apps retain original local records when you sign out or delete data, outside the active account and upload queues. These copies remain in the app’s private storage until that storage is cleared or the app is removed.

Backups may contain these retained records. Rotating a backup does not erase the retained source records. Temporary credentials and reproducible caches can still expire or be replaced.

Deleting your account

In the app, go to Settings (Preferences in older versions) → Delete account. This signs you out and ends access. We retain:

• Your account: your name, email address, phone number, sign-in IDs, and trial and membership records.
• The offers, shifts, events and uploaded files from every phone that was ever signed in to your account.
• Your saved iPhone app compatibility results and change history.

Deleting your account does not remove you from our Google Play test group. To leave the group, use the group’s page.

A phone now signed in to someone else’s account keeps that account’s data. Your historical records remain separate and unavailable to that account.

Deleting your account ends access to its restored offer history; we retain the original records. Gallery photos and photo backups stay under your control and can be deleted in those services.

If you pay through Whop, deleting your account also ends your Whop plan at once, and you lose the days that are left.

If you pay through Google Play, cancel your subscription in Google Play first. Deleting your Giga Driver account retains account and billing history and does not cancel your Google Play subscription.

You can also email [email protected] from your account’s email address, or include the phone number you signed in with. We’ll delete your account within 30 days.

For step-by-step instructions, see Delete your Giga Driver account.

Children

Giga Driver isn’t for anyone under 18.

Changes to this policy

If we change this policy, we’ll update this page and the date at the top.

Contact us

Questions about your privacy? Email [email protected].