Privacy Policy
This document is a draft under attorney review. It is not legal advice.
Applies to the Swervo Android app and the optional companion server you can run on your own PC.
What changed in version 2.11
- Automation disclosure: clarified Uber capture X dismissal, separately enabled shift/reading controls and explicitly armed Auto acceptance. Google Play stays tap-free.
What changed in version 2.10
- Automatic backup waits until the backup disclosure has been presented through sign-in or accepted in Account. Older backups without an owner mark require Move it before transfer.
- Session backups exclude customer addresses, delivery instructions, spoken directions and order coordinates. Private backups can include your saved-place coordinates and the positions retained in Decision Records; these are separate from optional shift-data sharing.
What changed in version 2.9
- Private account backup: signing in links previously unowned phone records to your account. Automatic backup defaults on, runs after shifts and daily when connected, and can be turned off in Account. This is private storage, separate from optional shift-data sharing; sharing tiers and consent do not change.
- More backup coverage: session archives, decline attempts, action claims, expenses, schedules, zone waits, the hotspot table and platform labels. Credentials, collector identity, raw screens and diagnostics remain excluded.
What changed in version 2.8
- Decision Records: with Keep offer positions on, your position is rounded to about 11 m, with its accuracy and age; the drop-off area stays at about 110 m. Turning the switch off omits both positions. This does not increase the precision of automatic shift-data sharing.
- Beta tester reports: the optional direct-download tester mode and the file you choose to send are described in section 6. They are separate from automatic shift-data sharing.
What changed in version 2.7
- Request limits that count per day (new accounts from one address, backups from one account) are now kept until about an hour after that day ends; they used to be dropped after about 2 hours, which quietly reset the daily limit. Every other request limit is still kept about 2 hours (section 2b).
What changed in version 2.6
- Location is sampled more often while you drive: about every 3 seconds while the car is moving during a shift (it was about every 15 seconds), less often when parked. Where it goes and how long it is kept have not changed; a paired PC keeps only your latest position (section 2).
- Walking guidance, drop spots and notes (new rows in section 2): the spots and notes you save stay on your phone; the walking lookup goes only to your own paired PC.
- Uber screen capture also reads Uber's "You earned" screen after a trip to record the pay; pictures are still read and discarded on the phone (section 2).
- Weekly proof card (new row in section 2): worked out on your phone from your own records.
1. The short version
Swervo runs on your phone. In the default phone-only mode the only things that leave the phone are the address lookups and the map downloads in section 5 (the lookups differ between beta and release builds), your speech to Android's recogniser if you use voice commands, and, once an update channel is configured, a signed update check (section 5). If you choose to pair your own PC, the phone also sends its records to that PC, which you control. Sharing shift data with us is optional on every plan, the free plan included. The app sends us shift data (section 2) only if you choose to share it; it is off until you do, and every feature works the same whether you share or not. For automatic shift-data sharing, positions closer than about 7 miles are sent only if you separately choose "Share precise positions". Separately, you can choose to send a beta tester report containing rounded positions (section 6). We do not sell your personal data, and we share nothing with advertisers, data brokers or delivery platforms. (Sideload edition only; the Google Play edition sends none of it.) Optional account (sideload edition): if you sign in, your email, a cloud backup of your settings and records, and your subscription status are kept by us on Cloudflare, and payments go through Stripe; section 2b says exactly what. You don't need an account to use the app. Website waitlist: if you join it on swervo.app, we keep your email only to tell you about Swervo; unsubscribe any time (section 2c). We run no other service that receives your data, and the Google Play edition uploads nothing and has no account. Problem reports leave the phone only when you tap "Send a problem report" and pick where to send it.
2. What the app collects, why, and where it lives
| Data | Why | Where it lives |
|---|---|---|
| Screen content of delivery apps read through Android's Accessibility Service: offer cards, task lists, drop-off steps (payout, restaurant, addresses, distances, deadlines, button labels). The service is limited by its configuration to the delivery apps only (DoorDash Dasher, Uber Driver, Grubhub for Drivers, Walmart Spark); it cannot read any other app | To evaluate offers, respond at the level you chose, and guide drop-offs | Phone (app-private). Offer text is kept in the order record. PC if paired. |
| Map capture of the offer card, taken in memory | To read map pins for the drop-off area | Sent only to a paired PC, which keeps it 30 days. The phone stores no screenshot or map image. |
| Screen-capture reading of Uber offer cards (sideload edition only; off unless you turn it on in Settings › Screen reader). Uber hides its offer card from the screen reader, so with this on the app takes several pictures of the screen for each Uber offer, during a shift or Test Shift, while Uber is up or signals an offer (a few a second for up to 3 seconds after an Uber offer signal, then about one a second while Uber is on screen), using Android's screen capture: Android asks you first and shows its own recording indicator while it is on. Each picture is read on the phone and discarded; only the newest is held in memory until the next. No video is recorded and no picture is taken while Uber is quiet or outside a shift. A screen an app protects from capture comes out black and is not read | To evaluate Uber offers and speak a verdict, and, when a picture shows Uber's "You earned" screen after a trip, to record what that trip paid in the order record. Swervo never taps Uber Accept. In the direct-download edition, enabled screen capture above Observe can dismiss an Uber offer with its X after a countdown you can stop. Separate shift, map and reading controls can interact with delivery apps, including online/offline controls. The Google Play edition performs no automatic taps. | Phone, in memory only; the phone stores no picture. The text read goes into the offer record and Decision Record like any offer. If you paired a PC, the picture is sent to it as that offer's map capture and kept 30 days, exactly as the row above. Never part of shift data, never sent to us |
| Delivery-app notifications | Fast offer detection | Phone |
| Location during a shift: about every 3 seconds while the car is moving or has just stopped (as often as every 2 seconds when another app already has the GPS on), about every 20 seconds while parked, and every 3 to 15 seconds (your setting) while parked with an order in hand. It continues after a shift ends only while an order you took is still being delivered. Before the app decides on an offer it makes sure its position is no more than about 10 seconds old. While the directions view is on screen it also uses a position about every second. Not collected when no shift is running and no order is in progress | Arrival, pickup and delivery detection; mileage; judging each offer from where the car actually is; directions | Phone. If you paired a PC, each position is sent to it as it is taken (exact, with its time), so it arrives about every 3 seconds while you drive. The PC keeps only the latest position (each one replaces the last), to detect arrivals and judge offers, and keeps no log of them; it goes nowhere else. Sent to us only as the rounded area and optional positions described under "Shift data we receive", or as positions retained in an optional private account backup (section 2b) |
| Order and shift records: offers seen, verdicts and reasons, taps performed, pickups, deliveries, recorded payouts, times you stopped Autopilot, shift times; for accepted orders, the restaurant and drop-off coordinates | Reports, learning, earnings | Phone; PC if paired |
| Decision Records: one record per offer the app evaluated: the offer as read (platform, restaurant, pay, distances, deadline), the verdict, its reason and the version and settings of the rules that produced it, what the app did and what you did, and for offers you took the times of arrival, pickup and delivery, the pay and tip and where those figures came from, and any thumbs up or down you gave. Positions follow the "Keep offer positions" switch: the drop-off area to about 110 m and your own position to about 11 m, plus that position's own accuracy and how old it was, or none of it when the switch is off. The text read from the screen is kept with house and unit numbers, coordinates and customer names removed, and cut to 1,000 characters | To show you why each verdict was given, to measure whether verdicts were right, and to test changes to the rules against real offers | Phone (app-private), deleted 30 days after the session's last write; "Delete offer maps" in Settings deletes them all. PC if paired: the PC receives the records without the screen text and deletes them 30 days after their last event. Decision Records without screen text can be saved in your private account backup (section 2b). Separately, if you agreed to share delivery outcomes (row above), only the fields listed there are shared |
| Quest mode: a bonus you type in: orders left, the bonus amount, the deadline and, if you choose, the platform. The app never reads a bonus from a delivery app's screen or notifications | To count eligible offers toward the bonus you entered | Phone (one setting); PC if paired. Cleared when the quest completes, expires or you clear it |
| Routes (only when directions from a paired PC are in use): the ordered stops of the route, including your current position, exact | To calculate directions | Sent to your own paired PC only, which calculates the route itself from map data it holds and keeps no log of positions or street names. Never sent to us or to any mapping company. Phone-only drivers: no route request leaves the phone |
| Offer positions for the Test Shift map: for each offer the app evaluated, your position when it arrived, the restaurant's coordinates, the customer drop-off area (never the exact address or the customer's name), and your shift destination | To draw the detour map in Test Shift review so you can see why an offer was judged the way it was | Phone only. Deleted after 30 days; "Delete offer maps" in Settings removes every saved position and keeps the verdicts; "Keep offer positions for Test Shift maps" in Settings turns it off; never included in problem reports |
| Your drop spots and notes: where you actually left an order at an address, and a note you type for it (a gate code, "side door"), up to 200 characters | To take you back to the same door next time | Phone only. Stored under a salted fingerprint of the address (the file holds no address text), outside Android's backup and the app's cloud backup, and never sent to your PC, to us or anyone else, never in shift data or problem reports. Deleted 180 days after it was saved (at most 2,000 are kept); "Forget this address" on the walking screen deletes one at once; clearing app data or uninstalling deletes all |
| Walking guidance lookup (only with a paired PC): the drop-off address, the drop-off point and where you are standing | To find the building and door and the walking route to it | Sent to your own paired PC only, which answers from map data it holds and does not log, keep or forward the address or coordinates. If the PC lacks map data for the area, it asks OpenStreetMap's Overpass service for the map features in a box about 1.2 by 0.6 km around it (section 5), never the address or your position. Nothing is sent when no PC is paired: the phone uses a spot you saved or a straight line |
| Weekly proof card: the week's offers, what you took, recorded pay and hours, worked out from your own records | To show what your picks were worth against taking every offer | Phone; PC if paired, which works it out from its own copy. Share sends only the card's totals, to whoever you choose |
| Drop-off recordings ("DoorStep"): the text labels shown on delivery-app screens during a drop-off, no images. These can include customer first names, addresses, gate codes and delivery notes. | To learn and guide the drop-off flow | Phone only, app-private. Deleted automatically after 30 days; delete any time in Settings. |
| Settings: home and destination addresses and coordinates, cost per mile, thresholds, platform toggles, Autopilot level, shift schedules | Operation | Phone; PC if paired |
| Restaurant intelligence: names, coordinates, observed waits, blacklist flags | Verdicts | Phone; PC if paired |
| Debug screen dumps: text of delivery-app screens, written only in debug builds with spy mode on | Diagnosing screen-reading bugs | App-specific external storage; deleted after 30 days |
| Diagnostics: crash files, the app's own log lines, readiness lights, settings with secrets and home/destination removed | Fixing problems | Phone, until you send or clear |
| Consent records: document, version, time in UTC and local, time zone, app version, Autopilot level chosen | Proof that you saw and accepted each document | Phone; included in problem reports |
| PC pairing credentials (only if you pair a PC): one-time pairing code, device token | Authenticating your phone to your PC | Phone and your PC |
| Session archives: snapshots of past shifts (orders, payouts, miles, counts) | History | Phone until you delete them in Settings |
Observe never automatically accepts or declines offers. Separate shift and reading controls may still interact with delivery apps. In supported direct-download flows, Auto can accept eligible offers only after you explicitly arm acceptance following the risk warning. Acceptance remains blocked on Uber. Automatic input can breach a platform's rules and risk deactivation.
Shift data we receive (sideload edition only)
Sent only if you chose to share shift data, on any plan; nothing is sent until you tick the box on the shift-data screen, and you can stop at any time (section 8, step 9). Offers from Grubhub are never sent, because its terms for drivers bar compiling its content. The Google Play edition sends none of this. If you agreed to an earlier version of the shift-data question, the app keeps sending what that version described until you answer the new one or turn it off; it never answers it for you.
| Data | When it is sent (every plan) | Why | Where it goes, how long |
|---|---|---|---|
| Shift data: offers. For each offer: the delivery app, day and time, pay, restaurant name, verdict and reason, what you did and how many seconds it took, how the app noticed, which version of our rules decided, minutes and miles | Only if you chose to share | To improve verdicts | Our shift-data server (a database of ours hosted by Cloudflare in the United States, at api.swervo.app), under a random install id, encrypted, and kept apart from accounts. Deleted within about a day of turning 12 months old, or when you delete it. What an older version of the app sent before 2026-09-28 is in a spreadsheet of ours at Google (section 5) under the same rules |
| Shift data: deliveries you took. Minutes waiting and driving, total minutes, whether and how it was cancelled, the pay and tip shown on screen or typed by you (never an estimate) | Only if you chose to share | To measure whether verdicts were right | Same |
| Shift data: your feedback. Thumbs up or down and the reason | Only if you chose to share | Same | Same |
| Shift data: general area. Where your shift started, rounded to one decimal place of latitude and longitude (about 7 miles) | Only if you chose to share | To compare like with like across markets | Same |
| Shift data: how the app ran. What Start, going online and setup did, phone model, Android version, app version, edition, plan, time zone; never a position | Only if you chose to share | To find and fix problems | Same |
| Precise positions (optional on every plan). Your position when an offer arrived and your destination, rounded to about 110 m; the drop-off area, about 110 m; the restaurant's location. If your destination is your home, the area around it is sent, not the exact point | Only if you also said yes to this separate question | To improve detour and drive-time estimates | Same. This is precise geolocation, which state laws treat as sensitive data. |
Never sent through automatic shift-data sharing on any plan: any Grubhub offer, the text on your screen, customer names, addresses, gate codes or notes, drop-off recordings, your exact home or destination, your delivery-platform account, your name, email or payment details together with shift data.
2a. Why sharing is optional
Shift data helps make Swervo's verdicts better for every driver, and improving the verdicts and fixing problems is the only thing we do with it. But it is your data and your choice: no plan requires it, no price depends on it, and saying no, or stopping later, changes nothing about your plan or what the app does for you. We do not sell it or offer anything in exchange for it.
Not collected: platform logins or passwords; payment cards (payments, if any, are handled by Stripe under the Subscription Terms); contacts; photos; audio (voice commands use Android's SpeechRecognizer and the app stores no recording); advertising identifiers.
2b. Optional account, backup and subscription (sideload edition only)
An account is optional: the app works without one, and then your data lives only on your phone (and your PC if you pair one). If you sign in, in the app or on swervo.app/account, this is what we keep:
| Data | Why | Where it lives, how long |
|---|---|---|
| Sign-in: your email address and a user id, from Google Firebase Authentication (you sign in with Google or with a one-time email link; we never see a password) | To know which backup and subscription are yours | Firebase (Google) and our database on Cloudflare, until you delete the account |
| Cloud backup (automatically after sign-in, after shifts and daily while Automatic backup is on; also when you tap Back up now or Restore): app settings worth restoring (never a token, pairing code, install id or server address), the six modes' settings, saved places and pins, your mileage log and tip ledger, decision records with your thumbs up or down, learned restaurant waits, session archives, decline-attempt history, action claims, expenses, shift schedules, zone wait history, the carried hotspot table and signed platform labels | So a new phone can restore them | Our database on Cloudflare, encrypted with a key unique to your account, until you delete it or the account. Mileage and tip entries are never overwritten by a later backup (they are tax records); a conflicting entry is kept beside the old one |
| Subscription record: which plan (monthly, yearly or founders), its status, when the paid period ends, and the Stripe customer and subscription ids | To turn Autopilot on while you pay | Our database, until you delete the account |
| Payment: your card, name, billing address and email, entered on Stripe's own page | To take payment | Stripe only, under Stripe's privacy policy. We never see or store card details |
| A purchase made on the website before you had an account: the Stripe ids, the plan, and a keyed fingerprint of the email you gave Stripe (never the email itself) | So the purchase joins your account when you sign in with that email, or when you link it | Our database until it is claimed; an unclaimed purchase whose subscription has ended is deleted 30 days after it ended |
| Devices with Autopilot: a random id the app makes, the edition and app version, and when it last asked | Up to three phones per subscription | Our database; a phone that hasn't asked for a week gives its place up |
| A licence: a signed statement that this account has Autopilot on this phone, valid for 7 days and renewed while you are signed in | So Autopilot keeps working offline for a while | On your phone; we keep no copy |
| Request limits: a keyed fingerprint of your IP address (never the address) or your user id, with a count (the shift-data server keeps its own, with a different key) | To stop abuse | About 2 hours; the once-a-day limits (new accounts from one address, backups from one account) until about an hour after that day ends |
Never kept with your account: the shift-data install identifier, your delivery-platform logins, and the text of delivery-app screens. Shift data (section 2) is not linked to your account or email: it is kept in a separate database with nothing that joins it to an account.
Automatic backup and ownership. After the backup disclosure at sign-in, previously unowned records on this phone are saved to your account while Automatic backup is on. Existing sign-ins and returning email links that have not shown this disclosure wait for you to enable automatic backup in Account. Older backups with no recorded owner require Move it first. You can turn Automatic backup off in Account for manual-only backup. Failed transfers leave local data intact and transient failures retry with increasing delays. If the phone holds another account’s records, nothing uploads until you tap Move it; Keep it separate leaves those records on this phone without uploading them to the new account. Sign-out keeps local records and their owner. A new phone with an existing account backup offers Restore. Restored shift schedules start disabled. Flight-recorder data, raw screens, diagnostics, credentials, tokens, collector install identity and rebuildable caches other than the listed hotspot table are excluded. Session archives exclude customer addresses, delivery instructions, spoken directions and order coordinates. Saved places and settings can include your exact home and destination; Decision Records can include the positions retained by Keep offer positions. Backup is private account storage, not participation in shift-data sharing; sharing controls and tiers are unchanged.
Export and delete. On swervo.app/account (or in the app under Account) you can download everything our servers hold for your account (JSON, or mileage and tips as CSV) and delete the account. Deletion removes the backup, the device list, the subscription record and the sign-in, and cancels an active subscription at Stripe, within 24 hours (usually at once). Afterwards we keep only a keyed fingerprint of the account id and the time of the request, for one year, as proof that the deletion happened, and, if you paid the founders price, a keyed fingerprint of the subscription so the 200 places are counted correctly. Stripe keeps payment records it must keep by law. Data on your phone stays until you delete it there.
2c. The waitlist on swervo.app
If you join the waitlist on swervo.app, we keep your email address, whether you ticked "I drive on an Android phone", which delivery apps you ticked, the city if you typed one, which page the form was on, and when you joined. We use your email only to tell you about Swervo, such as when there is a place for you in the beta or when it launches. We don't sell it, share it or add it to anyone else's list, and the form loads no trackers. It is kept in our database on Cloudflare, not joined to an account or to shift data, until you unsubscribe. Unsubscribe any time: reply to any email we send, or write to support@swervo.app, and we delete it. To stop abuse, the form counts sign-ups by a keyed fingerprint of your IP address (never the address itself), kept about 2 hours.
3. Customer information
Delivery apps show customer names, addresses and notes. The app processes them only to help you complete the delivery you accepted, keeps them inside the order record and the drop-off recording on your phone, and sends them nowhere except to a PC you paired. Under the platforms' terms you are responsible for handling customer information; the 30-day prune and the delete button in Settings exist to help you keep nothing longer than needed.
4. Permission self-repair
With a permission you grant once from a PC over USB, the app can re-enable its own accessibility service and notification listener if Android disables them, only during an active, unpaused shift and only while recovery is enabled in Settings. This changes only Swervo's own two settings. It is disclosed here because it touches a system setting.
5. Third parties that receive data
| Recipient | What | When |
|---|---|---|
| Photon (photon.komoot.io, built on OpenStreetMap data; "© OpenStreetMap contributors" is shown where the suggestions appear) | The text you type in the home and destination fields during setup | All builds: address suggestions while typing on the setup screen |
| OpenFreeMap (tiles.openfreemap.org, operated by Hyperknot Software Kft., Hungary, and delivered through Cloudflare; map data © OpenStreetMap contributors, © OpenMapTiles; credited on the map) | Requests for the map tiles, fonts and icons for the area a map shows, carrying the tiles' map coordinates, your IP address and the app's user agent. The app sends no GPS position, account or identifier, but the area shown is usually where you are, so these requests can reveal your approximate or precise location to OpenFreeMap and Cloudflare. OpenFreeMap states that its logs do not contain IP addresses, except for up to 30 days during a security incident | All builds: only while a map is on screen (the Map screen, the Test Shift offer map and the driving view). While you are driving with Swervo directions the map stays on screen and follows you, so these requests continue for the whole drive. Tiles you have seen are cached on the phone and are not requested again |
| Android Geocoder (Google-backed on most phones) | Addresses and coordinates | All builds: turning a setup address into coordinates. Release builds only: the Home destination search and naming the town of a drop-off |
| Google Places Autocomplete and Geocoding APIs (maps.googleapis.com) | The text you type in the Home destination search; the address you pick | Debug and beta builds only, which carry a Google Maps key: called directly from the phone for the Home destination search and its lookup. Release builds ship no Google key and use Photon and Android's Geocoder for that search instead. The setup screen never uses Google Places in any build |
| Update manifest host (its address is published when the update channel is switched on) and Android DownloadManager | A request for the signed update manifest (no personal data in the request beyond what any HTTPS request carries: your IP address and the app's user agent); the APK download itself | Only when an update channel is configured in the build; off until then. The manifest's signature and the APK's SHA-256 and signing certificate are verified before anything is installed, and installation always asks you |
| Google speech services through Android's SpeechRecognizer | Your spoken commands; may be sent to Google for recognition depending on your phone's settings | Only when you use voice commands |
| Android text-to-speech engine | Verdict text | While speaking; on-device on most phones |
| Google Maps Platform (routing, geocoding, static map images) | Addresses and coordinates | Only through a paired PC; see the row above for the phone-side Places/Geocoding calls in debug and beta builds |
| OpenStreetMap Overpass | Drop-off coordinates, to check for apartment or hotel buildings; for walking guidance, only the edges of a map box about 1.2 by 0.6 km, to download its buildings and paths (the PC keeps them 30 days) | Only through a paired PC |
| Anthropic (Claude API) | The offer map capture and the fields extracted from it | Only through a paired PC; never in phone-only mode |
| Tailscale (optional) | Encrypted transport between your phone and your PC; Tailscale sees connection metadata, not your records | Only if you set it up |
| Shizuku (optional, on-device) | Screen-reading and wireless-debugging commands | Only if you installed it |
| Google Firebase Authentication (Google LLC) | Your email address, and your Google account's basic profile if you use "Continue with Google" | Sideload edition, only if you sign in (section 2b) |
| Cloudflare (Workers and D1, in the United States, which host our accounts service and our shift-data server at api.swervo.app) | Your account, backup (encrypted), subscription record and device list; shift data (encrypted, in a separate database, section 2); your IP address as part of every request | Sideload edition, only if you sign in, or when you open a page of swervo.app that shows prices or buy (the page asks api.swervo.app for the prices); shift data only while you have chosen to share (any plan) |
| Stripe (payment processor) | What you type on its checkout page; the plan; for purchases in the app, your account's email and user id | Only when you choose to buy or manage a subscription (section 2b) |
| Swervo (us), on our shift-data server at api.swervo.app (hosted by Cloudflare, row above) | Shift data and diagnostic events, as described in section 2, with a per-install identifier; stored encrypted (AES-256-GCM) under a keyed fingerprint of that identifier | Any plan: only while you have chosen to share |
| Google (a Google Apps Script web app and a Google Sheet in our Google account), for shift data sent before 2026-09-28 | Shift data and diagnostic events an older version of the app sent, with a per-install identifier | Kept under the same 12-month deletion; "Delete my uploaded shift data" deletes it there too. Versions of the app from before the move keep sending there until they are updated. Google processes it for us under Google's terms for our account |
| Delivery platforms | Only the taps the app performs inside their apps | At the level you chose |
| Whoever you send a problem report to | The report zip | Only when you tap "Send a problem report" and choose a recipient |
When the update channel is on, the update check is the only regular contact the app has with a server of ours unless you sign in to an account or chose to share shift data; the update check sends no identifier and no records. Sale and sharing: none. We do not sell personal information, we do not share it for cross-context behavioural advertising, and we have not done either in the past 12 months. We do not use advertising or analytics SDKs. We do not give shift data to delivery platforms, insurers, employers, data brokers or anyone else. Apart from the accounts service (section 2b) and the shift-data server (section 2), there is no server of ours between your phone and any of the services above.
6. Problem reports
A report is a zip built on your phone. It contains app and device facts, the app's own recent log lines, recent crash files, your consent records, and your settings with secrets (anything named token, secret, password, key, auth, cookie, credential or PIN) and your home and destination addresses and coordinates replaced by "[removed]". It may still contain restaurant names, offer amounts, timestamps and delivery-app text that appeared in the log. It leaves the phone only when you tap Send and pick where it goes.
Beta tester mode and “Send my shift” (direct-download edition)
Tester mode requires your agreement and keeps all delivery apps on Observe: it speaks and never automatically accepts or declines offers. Separate shift and reading controls may interact with delivery apps. It records the app's logs and redacted offer examples on your phone. Turn tester mode off in Settings → Help and feedback before choosing Autopilot.
“Send my shift to Swervo” creates a separate file and opens Android's share menu. Nothing is uploaded automatically: you choose the recipient and can cancel. The file contains shift summaries, logs, offer text, restaurant names, pay, miles, minutes, verdicts, reasons and your actions, labelled with a random tester number. Customer names, phone numbers, house and apartment numbers and secrets are removed; street names remain. Positions are rounded to about 110 m before export, including driver positions stored more precisely in Decision Records. Grubhub offers are excluded. Review the file before sharing it.
The first report covers up to the last seven days; later reports cover the period since the last share, up to fourteen days. Creating a new report removes the previous tester-report file from the app's cache. Uninstalling removes the app's private copies; files already exported or sent remain with the destination or recipient you chose. This manual report is separate from “Share shift data” and from the regular problem report.
7. Retention
| Data | Kept until |
|---|---|
| Order, shift and restaurant records | You reset the session (which archives it) or uninstall. On the PC: until you delete the database. |
| Session archives | You delete them in Settings, clear app data, or uninstall |
| Map captures, and the pictures taken by screen-capture reading | Never stored on the phone; the PC deletes them after 30 days |
| Drop-off recordings | 30 days, or when you delete them |
| Your drop spots and notes | 180 days after each was saved, or when you forget it on the walking screen |
| Positions sent to a paired PC | Only the latest is kept; each new position replaces it |
| Offer positions for the Test Shift map | 30 days after the session's last write, or when you delete them; off entirely if you turn the setting off |
| Decision Records | Phone: 30 days after the session's last write, or when you tap "Delete offer maps and decision records". Paired PC: 30 days after the record's last event |
| Quest you entered | Until it completes, expires or you clear it |
| Cached map tiles | Kept by the map component within its own size limit; removed by Android Settings → Apps → Swervo → Clear cache, or uninstalling |
| Debug screen dumps | 30 days |
| Diagnostics | Until sent or cleared |
| Consent records | While the app is installed |
| Account, cloud backup, subscription record, device list (sideload, only if you sign in) | Until you delete the account; deleted within 24 hours of the request (section 2b) |
| Unclaimed website purchase (keyed email fingerprint, Stripe ids) | Until claimed; 30 days after its subscription ended if never claimed |
| Proof of an account deletion (keyed fingerprint of the account id, times) | One year |
| Waitlist email and answers (swervo.app) | Until you unsubscribe (section 2c) |
| Shift data and precise positions sent to us (any plan) | 12 months from receipt, then deleted by a daily check; sooner when you delete it. Changing or ending your plan does not extend or shorten this |
The retention sweep runs every time the app opens and every time Settings opens. Uninstalling deletes all app-private data on the phone; PC data must be deleted separately.
8. Your choices and how to delete data
- 1. Stop collection. Home → Autopilot → Observe (no automatic offer acceptance or decline). Android Settings → Accessibility → Swervo → Off stops all screen reading. Settings › Screen reader › Read Uber offers from the screen → Off, or Stop in its notification, ends screen capture at once. Notification access → Off. Location → Deny.
- 2. Delete the current shift. Home → menu → Reset session. This archives the shift, then clears it.
- 3. Delete drop-off recordings. Settings → Device & Reliability → Delete drop-off recordings → Delete.
- 3a. Forget a drop spot or note. On the walking screen for that address, Forget this address → Forget. To delete all of them at once, clear the app's data (step 5).
- 4. Delete archived sessions. Settings → Device & Reliability → Delete archived sessions → Delete. Copies you exported elsewhere are not affected.
- 4a. Delete offer maps and Decision Records / stop keeping offer positions. Settings → Device & Reliability → Delete offer maps and decision records removes every saved position and every Decision Record on the phone; Settings → Keep offer positions for Test Shift maps → Off stops positions being kept in either.
- 5. Delete everything on the phone. Android Settings → Apps → Swervo → Clear data, or uninstall.
- 6. Delete PC data. Delete
data/delivery.db(which holds the PC's Decision Records), theuploads/folder and the offer archive on your PC. - 7. Revoke self-repair. Settings → Recovery → Off, or run
adb shell pm revoke <package> android.permission.WRITE_SECURE_SETTINGS. - 8. Unpair the PC. Settings → Server → Unpair, or revoke the device on the PC's security page.
- 9. Stop sharing or delete shift data.
- Delete (any plan): Settings → Device & Reliability → Delete my uploaded shift data. Every row this phone sent is removed. Your plan and features do not change.
- Stop (any plan): Settings → Share shift data → Stop sharing. Nothing more is sent, and nothing else changes: your plan and every feature stay as they were.
- Precise positions (any plan): turn Share precise positions off.
- After uninstalling: email support@swervo.app with the install id you noted from Settings. Without it we cannot tell which rows were yours, because we do not know who you are.
- 10. Delete your account, backup and subscription (sideload). swervo.app/account → Delete my account, or in the app: Settings → Account → Delete my account. Everything in section 2b is deleted within 24 hours and an active subscription is cancelled. Export on the same page first if you want a copy.
- 11. Leave the waitlist. Reply to any email we send, or write to support@swervo.app from the address you signed up with. We delete your entry (section 2c).
8. Editions
If a Google Play edition of Swervo is published, it contains Observe, Test Shift, reports and maps only: it reads offers and speaks, and never taps. It does not include Autopilot, scheduled go-online, drop-off guidance that opens the delivery app's camera step, the self-update channel or permission self-repair. Everything in this policy about those features applies only to the edition downloaded directly from us. Both editions keep your data on your phone; the sideload edition also offers the optional account in section 2b.
8a. Precise location and the law
Your position during a shift, and the coordinates above, are "precise geolocation," which state privacy laws (California, Maryland, Kentucky, Connecticut, Virginia, Colorado, Oregon, Texas and others) treat as sensitive data. Those laws regulate companies that collect and control such data. In the Play edition Swervo does not receive it: it is generated and kept on your own phone, by software you run, for your own use. For shift-data sharing, we receive precise positions only from drivers who separately chose to share them, on any plan; no plan requires them. Residents of Maryland are not offered that sharing choice until a feature that needs it exists [attorney]. Separately, optional private account backup retains saved places, location settings and any positions kept in Decision Records so you can restore them (section 2b).
9. Security
App data lives in Android app-private storage. The accounts service accepts only sign-ins verified with Google's keys, answers each person only about their own records, encrypts every backup record with a key derived for that account (AES-256-GCM), stores shared shift data encrypted (AES-256-GCM) in its own database under a keyed fingerprint of the install identifier, never beside an account, keeps no card data, and signs licences so the app can check them offline. PC pairing uses one-time codes and revocable device tokens; browser access to the PC requires a secure transport. No system is perfectly secure, and the security of a PC you pair is your responsibility.
10. Children
Swervo is not for anyone under 18. We do not knowingly collect data from minors. If you believe a minor has used it, contact us and we will help delete the data.
11. Your rights
Depending on where you live you may have rights to access, correct, delete or port personal data, and to opt out of sales or targeted advertising (we do neither). Because the data is on your own device, you can exercise most of these rights directly with section 8. For anything else, contact support@swervo.app. We will not deny you the app, charge you more, or give you a lesser plan because you asked to see, correct or delete your data, or because you chose not to share, or stopped sharing, shift data. We do not sell personal data, and we offer no payment, discount or plan in exchange for it.
11a. Notice at collection (if you share shift data)
| Category | Collected when you chose to share (any plan) | Purpose | Sold or shared for advertising | Kept |
|---|---|---|---|---|
| Identifiers (random install id) | Yes | Avoid double-counting; let you delete | No | 12 months |
| Commercial information (offer pay, tips) | Yes | Improve verdicts | No | 12 months |
| Internet or app activity (offers, verdicts, what you did, diagnostics) | Yes | Improve verdicts; fix problems | No | 12 months |
| Geolocation, approximate (about 7 miles) | Yes | Compare markets | No | 12 months |
| Geolocation, precise | Optional precise shift-data sharing; separately, optional private account backup | Improve estimates; restore your saved records | No | Shared shift data: 12 months. Private backup: until deleted (section 2b) |
| Sensitive personal information other than precise geolocation | No | — | — | — |
12. Changes
We update the effective date and version at the top, record changes in the changelog, and show material changes in the app.
Contact
Swervo, support@swervo.app.