Security

Email security@bingsustudio.com with what you found and how to reproduce it. You can also open a private report through GitHub's security advisories. We reply within three working days, keep you updated until it is fixed, and credit you in the release notes if you want.

Please give us 90 days to ship a fix before you publish, test only against your own installation, and never access other people's data. We will not take legal action against research done in good faith under these rules. Our security.txt has the same contacts.

• Recordings are files in a folder you choose, ~/Movies/Bingsu by default. Bingsu never uploads them.
• The command line and MCP server talk to the app over a local socket inside a folder only your user can open.
• The first time an agent asks to record your screen, Bingsu asks you. Settings, Agents lists every agent you allowed, with Revoke.
• The camera and microphones are a second, separate question for each agent. macOS also asks you before Bingsu can use the screen, camera or microphone.
• Each agent can stop or pause only the recordings it started. You see every recording in the menu bar and can stop any of them.

• Every release is built from a tagged commit by the release workflow in the repository.
• The app is signed with BingsuStudio's Apple Developer ID, uses the hardened runtime, and is notarized by Apple.
• Updates come through Sparkle, an open-source updater, and are signed with a key kept off the internet (EdDSA). The app refuses an update whose signature does not match.
• Each download's SHA-256 checksum is listed with its GitHub release; the download page shows how to check it.

A share page is a folder of static files, encrypted unless you make it public: the key travels in the link's fragment, which browsers never send to the host. It runs no code on a server and loads files only from its own host. Who can open it is decided by the host you publish it to.

bingsustudio.com is static files on Cloudflare. It loads nothing from other sites, uses no analytics, and its headers set a strict content security policy, HTTPS only (HSTS), and no embedding by other sites.