Security and privacy of the Beatra Skill

Every action runs one of three bundled scripts: mcp_client.py calls Beatra, authorize.py handles sign-in, and uninstall.py removes the connection. Packages from SkillHub, ModelScope, and WorkBuddy also include auto_update.py, which updates the Skill's own files.

Requests use HTTPS. Packages from SkillHub, ModelScope, and WorkBuddy always use the mainland China hosts: www.beatra.cn, mcp.beatra.cn, api.beatra.cn, and cdn.beatra.cn for updates. Other packages use beatra.ai, mcp.beatra.ai, and api.beatra.ai on the international network, or the same mainland hosts in mainland China; once a day they ask Beatra which network suits this computer, in a small request that carries no credential and no installation identity. A file you choose to upload goes only to the one-time upload address Beatra issues for it.

Everything is written under ~/.beatra; on macOS and Linux only your user account can open it (folder 0700, files 0600), and nothing is written inside the installed Skill. It holds the device credential, the installation ID, the agent the Skill runs in and the device name when one is known, the network route, and the list of Beatra Skills installed on this computer; for each installed copy, the time of the last version check, where it was installed from, and a cache of its last registration. Two short-lived records are removed once they are no longer needed: a sign-in still waiting for your approval, and a note after a request is refused for low credits. Packages from SkillHub, ModelScope, and WorkBuddy also keep their automatic-update setting and the list of files they own, and while an update runs, a backup of the files it replaces.

The Skill registers its installation on first use, and again when one of these details changes or a day has passed: the package and version, the agent it runs in, the store or tool it came from, the network route, and coarse runtime facts (operating system, processor architecture, Python version, interface language, and time-zone offset). Each tool call also names the Skill and the agent, so every task can be traced to the Skill that made it. How Beatra uses this is in the privacy policy.

Copies installed from GitHub, the skills CLI, ClawHub, or this site update through that tool. At most once a day the Skill reads Beatra's public version list and, when a newer version is out, prints one line with the update command. Packages from SkillHub, ModelScope, and WorkBuddy instead check at most once a day and install the new version themselves after matching every file's SHA-256 against the published manifest. To turn that off, run python3 scripts/mcp_client.py update --auto off in the Skill folder.

When you uninstall the last Beatra Skill on a computer, uninstall.py asks Beatra to revoke the device credential, then deletes the files it created in ~/.beatra. You can also disconnect any device under Devices in the console.

Email security reports to support@beatra.ai with the steps to reproduce.