Feedback submissions
When you press Send suggestion in Fwoosh, we receive the form text, request type and app version, linked to your connected account. No hardware data or logs are attached by the form. Avoid personal information. Failed delivery keeps a local draft and does not retry automatically.
Local launch preparation preview. Server collection of real user reports is not enabled yet.
Steam sign-in stores a pseudonymous account key, sessions and connected devices. Payment records reference the merchant’s Stripe customer and subscription IDs. They are separate from game reports.
CoinGate processes the payment. Fwoosh stores order and access records separately from game reports. Payment does not enable analytics or public sharing.
The launch target is Hetzner with a private persistent database. This local preview stores synthetic test data on this PC. Public hosting, backup retention and the operator contact are not configured yet.
What is sent
Structured report only: random ID, client version, measurement day, game Steam App ID, build if known, graphics API, GPU and CPU models, memory size, driver version, recorded settings, and FPS metrics with measurement limitations.
Steam App ID identifies the game, not the player’s account. The report excludes the user’s Steam ID, Windows username, paths, process PID, full logs, screenshots, and hardware serial numbers. The server rejects fields outside the allowed schema.
Two independent permissions
- Report storage: A report is uploaded after a one-time approval or under separate permission for automatic uploads of new reports.
- Community database: Public parameter sharing requires a fresh, separate approval. Old report community consent never publishes a card by itself. The public card includes the game, GPU, resolution, settings and measured FPS. Your CPU, driver, report date and private report ID stay private.
The agreement and permission for automatic uploads are approved separately. Withdrawal stops future uploads; saved reports can be deleted in your account. Public sharing and analytics require their own permissions. User agreement
Where and how data are stored
Optional product analytics contains only an event name and app version, grouped by server day. No game names, hardware, paths or logs. Reports and public sharing require separate approval.
Consent version, sending time, and community-use permission are recorded. Reports remain until the user deletes them; the pilot allows up to 100 per visitor. The site is available to the project owner; operators with database access may maintain storage.
The authentication and hosting platform processes requests under its own rules. A report lacking identifiers does not mean the infrastructure never sees IP addresses or sign-in data.
Deletion and permission withdrawal
In the section “My reports” Active records are deleted immediately. Backup erasure requires the operator’s retention policy; it has not been independently verified. Withdraw public card
Before public launch
The legal entity or owner, data-request contact, provider terms, and backup retention terms must be specified. Until then, the site remains a closed pilot. This page describes implemented behavior and does not claim legal certification.