Home / Privacy
Privacy
bridgeplay.dev has no accounts, no ads and no cookies. Vercel Web Analytics counts visits, a few outside services load parts of the pages, and game reports you send from the app are published on GitHub.
Who runs this site
Raymond Chin, who maintains Bridgeplay, runs bridgeplay.dev. Vercel hosts it and, like any web host, sees your IP address and browser details when it serves a page.
Analytics
The site uses Vercel Web Analytics, which works without cookies. Vercel identifies a visit with a hash of the request and discards it after 24 hours. Each page view records the page, the referrer, filtered query parameters, your rough location, browser, operating system and device type.
The site adds two events of its own: download when you click a Download link, and send_to_mac when you tap Send to Mac on a phone or PC. Each one records which link you used.
The Check your Mac button on the home page runs in your browser and sends nothing.
Other services your browser contacts
Some parts of the pages load from other companies’ servers, and those companies see your IP address and browser details.
| Service | What it loads | Where |
|---|---|---|
| GitHub | The star count, from api.github.com | Every page |
| shields.io | The star count, when GitHub’s API refuses | Every page |
| GitHub | Contributor avatars, from avatars.githubusercontent.com | Home, How it works |
| GitHub | Compatibility data, from raw.githubusercontent.com | Compatibility list |
| Valve | Game images, from Steam’s image servers (cdn.akamai.steamstatic.com, shared.akamai.steamstatic.com) | Compatibility list, game pages |
There are no ad networks, social widgets or other trackers. Fonts and the home page video come from bridgeplay.dev itself.
Game reports from the app
The Bridgeplay app sends a report when you answer How did it run?, or after each game if you turn on Share automatically after each game. The report goes to bridgeplay.dev/api/report, which posts it to Compatibility reports in Bridgeplay’s public GitHub Discussions under a bot account, so you don’t need a GitHub account. Anyone can read it, and it counts on the compatibility list.
What a report publishes
- The game’s name and Steam AppID, how it ran, the main problem if you picked one, and anything you wrote (up to 1,000 characters).
- Your Mac’s model, chip, GPU cores, memory and displays, and whether it was on battery, in Low Power Mode or running hot.
- Your macOS and Bridgeplay versions, the engine, graphics backend and High Resolution setting.
- How long the session ran and how it ended.
- The game’s logs. Reports marked Has issues or Didn’t run also carry longer log tails as comments.
Before a log leaves your Mac, the app removes your home folder, user and computer names, Steam account name, Steam ID, email addresses and external drive names. The server repeats most of that as a second pass.
What stays private
The app also sends a random install ID, and the server sees your IP address. The site’s code uses them only to limit how many reports come in, keeps them in memory and never publishes them.
Contact and removal requests
To remove a report, email hello@bridgeplay.dev with a link to it, and the maintainers will delete it. The same address takes any other privacy question.
Takedown requests go there too. If you own game art, a name or anything else on this site, send the page link and what you want removed.
For bugs, open an issue on GitHub.