RoR2 Run Tracker stores the runs you enter so you can continue on another browser and share an active run with friends. It does not read your installed game or automatically detect pickups.
Sign-in information
Google sign-in is handled through Supabase Authentication. The app requests basic identity scopes: OpenID, email and profile. It uses your account identifier to keep personal saves separate and displays your email while you are signed in. It does not request access to Gmail, Google Drive, contacts or calendar data. Your Google password is entered with Google, not into this tracker.
Your run data
Cloud saves contain the run names, inventory quantities, settings and other gameplay values you enter, together with saved runs, presets, exclusions and revision information. Undo and Redo history is part of the personal profile. The backend records operation identifiers and acknowledgments to handle synchronization and avoid accepting the same operation twice.
Storage on your device
The app uses browser storage for your signed-in session, personal and shared-run state, pending changes, remembered room information and display preferences. When offline support is enabled, it caches application files. An offline page or pending edit is not evidence of a cloud save. Signing out does not erase retained pending work. Clearing browser data can remove work that has not reached the cloud; export a backup and pending recovery first.
Shared runs
A room code or invitation link grants editing access to that shared active run. Share it only with people you intend to invite. Joining does not grant access to your personal saved-run library. Shared edits are stored on the backend so participants can synchronize. Returning to your personal run does not delete the shared room. The room owner can revoke access or close the room.
Exports and imports
Exports download JSON files to your device. A full backup can contain your personal run library and history. A completed-run export contains the selected active run, its item quantities and the save status at export time. Files you share afterward are outside the tracker's control. Importing requires selecting a file and reviewing the proposed change; the app does not automatically read other local tracker installations.
Service providers and requests
Cloudflare serves the website, and Supabase supplies authentication and cloud storage. Requests to these providers include information needed to serve and secure the service, such as the request address and network connection information. Their own privacy policies describe their handling of service data. The reviewed tracker source does not include advertising or third-party analytics scripts.
Cloudflare privacy policy · Supabase privacy policy · Google privacy policy
Retention and choices
Run data and synchronization records remain stored unless removed through an applicable app or administrative process. Moving a saved run to recovery is not permanent deletion. You can export your data and choose not to share a room. The reviewed app does not currently offer a self-service account-deletion control.
A pending-recovery export preserves queued edits and their status for inspection and recovery. It does not automatically merge a conflict or apply blocked edits. If a blocked shared-room edit still needs to be made, compare the current room with the saved recovery record and manually reapply only the missing edit. Check for an existing saved copy first to avoid applying it twice.
Operator and contact
RoR2 Run Tracker, operated by John Stamper. For privacy questions or deletion requests, email jwstamper1106+ror2tracker@gmail.com. Requests are reviewed by the operator; identity and the requested data must be confirmed before an administrative deletion. Sending a request does not itself delete an account or its records. No response deadline or retention period is promised here.