Site usage and privacy
Covers FrontMCP 1.10.10 as of
Playground code executes in your browser. Code you add can make network calls permitted by its runtime. Downloading runtime files, searching the docs and using external services also uses the network. The site records limited aggregate usage events to understand which examples and actions work.
Usage events
The page sends event names, page paths, example positions, selected fixed labels, startup/call durations and test counts to this site's /api/events endpoint. The receiver also obtains an approximate country from the hosting request metadata. New call-completion events distinguish successful results, tool errors, protocol errors and transport failures; an intentionally refused example can still be correct.
The event schema does not collect code, prompts, tokens, tool arguments, tool results or raw search text. It has no visitor or session ID. Counts and event ratios do not identify unique people or establish a person-level conversion funnel.
Global Privacy Control
When your browser enables Global Privacy Control, the page's usage-event sender does not send its batches. That control does not imply zero requests: server-side assistant-referral classification and browser Content Security Policy reports are separate paths. Referral records use the recognized source and page path, not a copy of the whole referrer URL. CSP reports describe blocked resources; they are diagnostic reports rather than Playground source uploads.
Sharing examples
The Playground's Share/Open links carry example files in the URL fragment. Anyone you send that link to can read those files. Keep credentials and private code out of shared examples. Downloadable projects contain the published fixtures, not your local edits.
Corrections
See maintainers and corrections for documentation feedback and Security for private vulnerability reporting.