Privacy and permissions
Understand selected-file access, review boundaries and what the checks can detect.
Selected files only
The local MCP reads the exact filenames supplied within the project root you approve. It does not automatically collect full conversations or walk the whole project.
Your existing agent writes the skill. If you use a cloud-backed agent, content returned by tools may be received by that agent provider and recorded in its history.
What the checks cover
Known secret patterns, certain personal details, unsafe paths and package limits are checked before staging and again at the publishing boundary. Findings should be corrected before review.
Pattern checks cannot guarantee that all private information has been removed, that scripts are safe, or that a creator owns the material. Read every included file and share only material you have permission to distribute.
Separate approvals
Preparing a local draft, uploading it privately, publishing its listing, signing in and approving a purchase are separate actions. One approval does not automatically authorize the next.
Never put a wallet seed phrase, private key or privileged backend key into a skill, listing or plugin setup command. A public wallet address is different from those credentials.
Private package contents
Public listing metadata describes a skill without exposing the complete private package. Creator downloads check the signed-in account and the package’s integrity. Buyer access is granted only by the separately verified purchase flow.
This page explains product behavior. It is not a substitute for a published legal privacy policy; the launch policy and support pages are still being prepared.