Privacy

Your screenshot is private. The shared statistics are public.

What we store

Uploaded screenshots, extracted earnings, optional account details, optional city, state, ZIP code and vehicle details, and processing records and consent. Unrecognized screens, additional metrics and uncertain or suspicious extractions are stored in a private research inbox to improve supported analytics. Selected technical metadata includes file hashes, format, dimensions, software tags and timestamps; GPS and owner/device identity tags are not collected. We use a first-party, HttpOnly session cookie to connect uploads in this browser. A local browser marker remembers interface preferences; it cannot authenticate you. Pending uploads are also saved in this browser so they can resume after a refresh. These local file copies are removed after the server confirms receipt; failed uploads remain until you remove them or clear site data. Resume requires the same browser identity. Clearing browser storage or cookies can interrupt recovery.

Anonymous means your name is not published. It does not mean the service cannot link your submissions. We do not fingerprint your device, infer your work location from IP, or recreate deleted cookies. A short-lived keyed hash of your network address helps rate-limit abuse. Web-server logs may record network addresses.

Image processing

We validate and re-encode screenshots to strip metadata, then send the normalized image to the OpenAI API for extraction. Cover personal names, faces, addresses, plates and customer details before uploading. The extractor is instructed to omit personal identifiers. We request that API responses not be stored; provider abuse-monitoring retention may still apply.

Raw screenshots are kept for up to 90 days when scheduled maintenance is running. Structured reports remain until you delete them. Screenshots are never published or placed in public asset folders. Only your current valid browser session or account can access your report history.

Community and communication

Community chat is visible to registered members. Chat images are separate from earnings contributions. Leaderboard names are anonymous by default; registered users can choose to display their name or nickname. Karma reflects contributions and chat reactions. Email progress updates and chat notifications can be turned off separately. Sign-in links are single-use and expire after 24 hours.

Accounts and notifications

Registration or login links only the current browser’s anonymous contributions. Clearing cookies can disconnect anonymous history. Signing out starts a new anonymous session. Notification subscriptions are encrypted, optional and revocable. They do not verify identity.

Google sign-in

If you choose Google sign-in, RideWage receives your Google account identifier, your email address and its verification status. RideWage uses them to create your account or sign you in. We keep the account link so you can sign in again. Google access tokens are used during sign-in and are not stored.

Browser history

RideWage uses a random cookie to recognize this browser. After you log out, this browser can show a list of screenshots originally uploaded as a guest and later linked to an account. Sign in to see the report or the screenshot.

Karma and chat moderation

Accepted screenshots earn karma. Clearly unrelated or manipulated uploads can reduce it. Individual screenshot deletion removes the report and image while its karma entry stays with your account or browser. Chat reactions change karma, and enough weighted dislikes from different drivers can hide a message. Deleting your account removes the karma linked to it.

Your controls

Use your dashboard to export structured data, delete individual reports, delete all accessible contributions, or turn off reminders. Deleted reports are removed from the public aggregate. Profile changes apply to future uploads only. Without a valid session or account, we cannot safely identify anonymous reports as yours.

We use a mail service to deliver account and notification emails. Operational backups can temporarily contain data removed from the live service. Contact [email protected] with privacy questions.

Last updated November 14, 2026.