↯ MODWIRE

Privacy and data handling

Updated November 5, 2026. Modwire is a desktop modding app in testing. This notice describes the current test releases and the managed candidate.

Website

The website provides downloads and an illustrative walkthrough. The password-recovery page sends the new password directly to Supabase. Customer sign-in and purchases are managed in the desktop app. Vercel hosts this site and the trusted API and receives connection metadata such as IP addresses and requested URLs. The previous Firebase-hosted test site remains available during migration. Installer downloads are hosted in the public leo-tang2/modwire-downloads repository on GitHub; GitHub receives connection metadata when you download an installer. Google Fonts receives requests when the home page loads its typeface. There is no Modwire analytics or telemetry uploader.

Desktop app

Chat messages, game context and file excerpts read by tools may be sent to the AI service. Earlier test builds connect to your own ChatGPT account; the managed candidate uses Supabase identity and a Modwire-funded OpenAI service when configured. Do not put passwords or unrelated private documents into selected game folders.

The game-finding assistant sends your request and detected game names/identifiers to the Modwire-funded AI service when you press Send. Installation paths and game file contents are excluded from this finder request. Installation detection reads launcher records and filenames locally. Starting with 0.1.4, discovery also requests Steam metadata for installed Steam identifiers to confirm single-player support and disclosed anti-cheat. Opening a game fetches publisher terms and sends that game’s name/identifier and the public terms to the managed AI service; it uses your AI allowance. These checks exclude installation paths and game-file contents. Publisher and store websites receive normal connection metadata. Prohibited assessments are saved locally for a day; successful assessments are held in memory for up to an hour.

The backend stores hashed account identifiers and minute-window request counters to limit API abuse. These counters contain no identity tokens, email addresses or IP addresses. Existing records are overwritten each window rather than saved as request history.

Tokens stay in the operating system credential store. Passwords are sent to Supabase for authentication and are not saved by Modwire. Mod sources receive download and page requests. The source browser may retain its own sign-in cookies.

Settings, downloads, original-file backups and recovery journals stay on your computer. They are not automatically deleted. Chat and activity display are held in memory. Preserve unfinished recovery journals when removing app data.

Native staging storage is limited to 8 GiB and 20,000 files/directories per game and 16 GiB and 40,000 across games, with a 1 GiB free-space reserve checked before transfers. Limits persist across restarts. Existing downloads and recovery data are preserved when the limit is reached; other applications can still consume disk space.

The 0.1.6 candidate shares server-created publisher assessments, public source hashes, restrictions and review timestamps across accounts. Cached reviews do not spend AI credits. Fresh reviews use the requesting account’s existing allowance. The shared policy record does not contain user paths, game files or account identifiers. Reading an installed app icon stays on your device and does not execute the game.

The Nexus catalogue candidate stores only public game names, Nexus identifiers and verified store-ID mappings. The operator initiates imports locally using a Nexus API key that is not deployed or shipped in the app. Nexus receives the submitted store identifiers without paths or game-file contents. This import does not download mods or artwork. Fresh verified matches can skip the publisher AI review at zero AI cost; unknown or expired entries use the normal review.

Managed service and requests

The managed beta records account identifiers, request receipts and usage in Supabase Postgres. Auth identity mappings preserve existing allowances during migration. Purchases are disabled. Account deletion and a production retention schedule are not yet implemented; do not assume sign-out deletes server data.

For privacy questions or deletion requests, contact leo.tang@alpha.school. Requests require manual review; this page does not promise automated deletion or a fixed response time.