ShiftKeep

Privacy policy

Last updated September 7, 2026

ShiftKeep is a take-home money app for delivery drivers. This page is the policy Google Play and the in-app Settings link should use. The marketing copy on the download page is not a substitute for it.

Who we are

ShiftKeep is operated as an independent Android app. We process data to calculate a tax cushion and a keep number, optionally back those records up, and email people who ask to hear when ShiftKeep Pro launches.

Data we collect

What we do not collect

How we use it

We do not sell personal information. We do not use your data for ads.

Sharing

Location

Location is optional. The app asks only after you tap Start tracking and confirm an in-app disclosure. A persistent notification stays up while GPS miles are recorded, including if you leave the app or turn the screen off. We do not request “always” / background location permission. You can log shifts manually instead.

Retention

Local records stay on the phone until you delete them or uninstall. Cloud backup stays until you delete the backup, delete the account, or confirm a web deletion request. Waitlist emails stay until you delete the account, confirm a web request, or we close the list.

Deletion

If you created an account, you can delete it in the app under Settings → Backup → Delete Account. That removes the account, cloud records, local ShiftKeep data on that phone, and any waitlist row for the same email.

You can also request deletion on the web at http://shift-keep.com/delete-account. We email a confirmation link that expires in 48 hours. After you confirm, associated data is deleted except records we must keep if a law later requires it. We do not currently retain copies after deletion.

Local-only use (no sign-in) has no cloud account. Use Settings → Delete All Local Data, or uninstall.

Children

ShiftKeep is for adult drivers. We do not target children and do not knowingly collect data from anyone under 18.

Security

Release builds talk to the API over HTTPS. Access to cloud records requires a signed-in token. No security measure is perfect.

Changes

If this policy changes in a material way, we will update this page and the date above. Continued use after an update means you accept the new policy.