Privacy
Privacy Notice
How Fygment handles account, workspace, skill, package, and runtime metadata.
Last updated: October 10, 2026
What we collect
Fygment stores the account and workspace data needed to operate an AI skill registry: email address, workspace membership, skill metadata, package checksums, approvals, audit events, external source references, and connected harness metadata. For MCP requests and authentication failures, Fygment also logs IP addresses, browser or device information from user-agent strings, and per-request diagnostics for security and troubleshooting. These runtime logs are retained for 30 days.
Skill packages and content
Imported skill packages are stored so they can be versioned, exported, and resolved by approved runtimes. Package bodies are visible only to users with workspace access and are not shown in platform-admin aggregate views.
Runtime privacy boundary
Fygment is designed around metadata-only runtime diagnostics. The CLI receipt and execution-log planning flows avoid capturing stdout, stderr, prompts, local paths, package bodies, secrets, or customer content by default.
Third-party services
Fygment uses infrastructure services for authentication, database storage, package storage, hosting, email delivery, logging, and error monitoring. GitHub imports fetch the repository archive and store source metadata for update tracking.
Retention and deletion
Workspace owners can archive a workspace from settings. Archiving hides the workspace from normal access and revokes active credentials. For account or data deletion help, contact support from the Support page.
Changes to this notice
We update this notice when the way Fygment handles data changes. The date at the top shows when it last changed.