Billing and security
Security and privacy boundaries
What Fygment does and does not expose in docs, support reports, admin views, imports, MCP, and billing metadata.
- Audience
- Workspace operators, support reviewers, and users checking trust boundaries.
- Updated
- 2026-10-25
The Fygment trust model is metadata-minimizing: keep customer Skill content, package bodies, prompts, secrets, tokens, and raw local paths out of admin, support, analytics, and billing surfaces.
Data minimization rules
Platform-admin views are for support and aggregate operations. They must not expose customer Skill bodies, package contents, proposal patches, feedback bodies, secrets, tokens, prompts, stdout, stderr, or raw local paths.
Billing metadata should stay workspace-scoped and minimal: workspace id or slug, initiating user id, plan key, status, quantity, and mode-style fields only.
Where your content is processed
Some import steps send Skill package contents to outside AI services. When you import a Skill, the final trust review sends selected package contents to Azure OpenAI. Fygment keeps only bounded trust metadata from that review.
If you turn on AI-assisted normalization, Fygment sends package contents to an AI model through the Vercel AI Gateway to repair the package into a reviewed draft.
Sign-in with an emailed code uses a Cloudflare Turnstile human check.
Controls you have
Imports fail closed. If the trust scan cannot finish or cannot clear a package, the package is not imported. See the trust review guide at /docs/skills/trust-review.
Owners and admins can use "Revoke all workspace credentials" in workspace settings. It revokes every active MCP OAuth token and legacy workspace API key, and connected clients must sign in again.
Sensitive admin actions, such as creating an invite, ask you to re-verify your identity first.
Enterprise
Enterprise requirements
For enterprise requirements such as SSO, SCIM, SIEM export, on-premises deployment, or SOC 2 Type II support, talk to Fygment support about your needs.
Related docs
- Troubleshooting
Start with safe, non-sensitive checks. Fygment support reports should capture bounded diagnostics, not package bodies, secrets, raw prompts, or local paths.
- Billing and plans
Billing uses a workspace effective tier: Solo remains free for the local creator loop, Advanced / Teams (Fygment Team) unlocks paid collaboration and external import actions, and Enterprise is support-managed.
- Review and approve Skills
Members can use the Skills they import right away. Review is for sharing more widely and for new versions. Each decision is made by someone with authority over that Skill or team, and every version approval re-runs the trust review.