Privacy
Privacy Notice
How Fygment handles account, workspace, skill, package, and runtime metadata during the V1 pilot.
Last updated: May 17, 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.
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 V1 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
The hosted pilot 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.
Review boundary
This notice describes the current pilot implementation and should be reviewed by counsel before broad public or self-serve launch.
Pilot note: these pages describe the current product and operating boundary for invited users. They should be reviewed by counsel before broad public launch.