osu!ReqTrac
Privacy policy
Last updated: 25 October 2026
This policy covers the osu!ReqTrac desktop application and its optional Google Sheets export. SEApodEErman develops and maintains the app. For questions about this policy or your data, contact [email protected].
Your local workspace
ReqTrac stores requests, notes, categories, tags, history, preferences, cached beatmap information, and connection settings in a SQLite database on your computer. It does not send your workspace or Google tokens to a server operated by the developer.
When you use osu! integration, the app contacts osu! to retrieve beatmap and user information and downloads cover images from osu!'s asset service. Packaged builds also contact GitHub's release infrastructure to check for and download app updates. These providers receive ordinary connection information, such as your IP address. ReqTrac has no built-in advertising or usage analytics.
Google access and its purpose
Google Drive connection is optional. Authorization takes place in your browser on Google's website; ReqTrac does not receive your Google password. Google supplies access and refresh tokens that let the app publish and update a request spreadsheet on your behalf.
The app uses Google APIs to create its export spreadsheet, read its tab structure and formatting, replace exported values, apply formatting, and enable anyone-with-the-link viewing. It stores the export spreadsheet's ID, URL, last sync time, and connection status locally, alongside the tokens.
New connections in the updated app request https://www.googleapis.com/auth/drive.file, which permits access to files created by or explicitly shared with the app. ReqTrac uses this access for its own export spreadsheet. It does not browse your Drive, read unrelated documents, or request Gmail, contacts, or Google profile permissions.
Older releases also requested https://www.googleapis.com/auth/spreadsheets, which permits access to all your Google Sheets. Their export feature still works with the app's own spreadsheet. Updating the app does not remove an existing Google grant; revoke the old connection in your Google Account and reconnect with an updated build to grant narrower access.
What publishing shares
Publishing sends an export of your osu! requests directly from your computer to Google Sheets in your Google Drive. Exported information can include artist and song titles, creators, difficulty counts and star ratings, game modes, map and request statuses, priorities, deadlines, added and completed dates, notes, tags, category names, and osu! links. The dashboard includes totals, yearly summaries, and completed-request counts by requester username. Manual, non-osu! requests are excluded.
Each publish or sync enables anyone with the link to read the spreadsheet. People who receive the link can copy or redistribute its contents. Review your notes and other fields before publishing. Google may also display the file owner's identity as part of its own interface.
Disconnecting or deleting local requests does not delete an existing export. A sync replaces exported ranges in the app's dashboard and current category tabs; it does not remove old category tabs, other copies, or Google's version history. To remove an export, manage sharing and delete the spreadsheet in Google Drive. A later sync can enable link sharing again.
Storage, security, and retention
Google tokens are kept in the local settings database until you disconnect or delete the app's data. The desktop app uses Electron's secure storage when encryption is available. If it is unavailable, including standalone backend use, tokens may be stored without that encryption. The app does not promise that the whole database is encrypted.
Local data stays on your computer until you remove it. Exported JSON backups include settings and can contain Google tokens and other credentials; keep them private and delete copies you no longer need. Restoring a backup can restore connection data. Published spreadsheets remain in your Google account until you delete them, subject to Google's retention and deletion practices.
Disconnect, revoke access, or delete data
- In Settings → Google Sheets → Disconnect, remove the locally saved Google tokens and export spreadsheet reference. This leaves the file and its sharing permissions in Drive, and does not revoke the grant in your Google Account.
- To revoke Google's authorization, remove osu!ReqTrac from your Google Account connections.
- To stop sharing or remove an export, change its sharing settings or delete it in Google Drive. Delete it from Trash too if you want to remove it permanently, subject to Google's policies. Copies held by other people are outside the app's control.
- Use the app's Delete all data setting to clear its database records. Remove backups separately. Uninstalling the application may leave its data directory on your computer.
Use of Google user data
Google user data is used only to provide the export feature described here. It is not sold, used for advertising, used for credit decisions, or used to develop, train, or improve AI or machine learning models. The developer does not routinely receive or review your Google data. If you choose to send information for support, share only what is needed and remove credentials first.
osu!ReqTrac's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
Other services and policy changes
Google processes authorization and hosted spreadsheet data under its Privacy Policy. Your use of osu!, GitHub, and any files you choose to share is also subject to those services' policies.
This policy may be updated as the app changes. The date above identifies the latest revision. Changes to Google data use that require new consent will be disclosed before that new use begins.