PROJECTFORTY2 / PLUGIN PRIVACY
Your mission.
Your account.
Updated 5 November 2026
The Heart of Gold plugin helps you shape a crew and inspect its work inside ChatGPT or another compatible host. The plugin and the standalone website use different execution paths.
What reaches ProjectForty2
When the host calls a Heart of Gold tool, it sends the supplied mission, crew assignments, constraints, contributions, evidence links, and summaries to the ProjectForty2 MCP service. For artifact updates, it also sends the selected file paths and exact source contents, file and component attribution, component labels and file-path mappings, declared changed component IDs, optional source revision and project links, and reported check results or commands. The service validates that information, keeps the latest flight snapshot and supplied project temporarily in server memory, and returns data to one flight deck as it updates. It does not independently observe your agents or request your full chat history.
When the host starts the optional same-workspace bridge, that process watches only the explicitly bound project paths and sends their saved UTF-8 contents, including unfinished edits, to the artifact endpoint. A narrow artifact capability permits only those files. The deck receives latest-state updates over a capability-authenticated event stream. No arbitrary repository scan or model-keystroke collection is performed.
Processing and storage
The plugin service keeps the latest snapshot and selected project for each flight in temporary process memory. It computes file hashes, a project digest, and a change summary; check outcomes remain supplied by the host, not independently verified. Access expires two hours after the flight is created; reads and updates do not extend that deadline. Expired entries are removed on access or the next cleanup sweep, scheduled every 60 seconds. Only the latest snapshot and project source are kept. A summary of added, modified, or deleted paths and up to 64 component-change metadata receipts, together limited to 32 KiB, may be retained with that latest project. Those receipts contain component/member IDs, changed paths, source digests, revision numbers, and server receipt timestamps; attribution remains host-reported. Previous source contents are not retained. Component receipt times describe when the service accepted an update, not when a worker typed it. Restarting or shutting down the service clears its flight state. It has no durable mission database or saved cross-session flight history. A project contains up to 24 supported text files, at most 64 KiB per file, and up to 12 component mappings. Its 256 KiB limit includes source, component mappings, and the bounded event metadata. Each combined flight is limited to 384 KiB, with at most 128 flights and 8 MiB across the process. Capacity limits reject new or oversized work rather than evicting an active flight. It does not intentionally write request bodies, source files, or contribution text to application logs. Hosting and network providers can process request metadata, such as addresses, timestamps, routes, and errors, under their own practices. This is not a promise that content never leaves your chat.
Private flight access
The host receives a private write capability for the current flight, and its widget receives a separate read capability. These are random access tokens, not provider credentials or account sign-in. Anyone who obtains a valid capability can exercise its access until the flight expires. They are sent in tool arguments or credentialless request bodies, never in a public flight URL. A separate scoped artifact capability may be passed only to the trusted same-workspace bridge and expires with the flight. Keep them out of public messages, evidence links, and delegated-worker prompts. The service has no flight-listing endpoint or plugin account cookie.
Source preview and publication
Where supported, the deck passes assembled project HTML to an isolated browser preview. That preview receives the displayable code, not the flight’s read or write capability. It measures matching component anchors and reports their bounds to the deck so a contributor can be shown beside the actual rendered region. These measurements support presentation, not independent verification of authorship. The preview has a restrictive sandbox and network policy. The service does not run a server-side build, install project dependencies, fetch supplied project links, or publish a public copy of the project. Submitting source to this temporary deck does not authorize repository changes or public deployment. Keep the durable original in your host workspace or another location you control.
Model usage and credentials
The plugin does not request an OpenAI API key, a ChatGPT password, or an OAuth token. Reasoning and any native delegation happen through the capabilities available in your host account. Host plan limits and policies apply. The plugin service itself makes no model-provider calls. The standalone website’s optional API-key connection is separate and is not required by the plugin.
Your controls
You choose what to include in the mission, reported snapshots, and selected project files. Keep credentials and unrelated private files out of uploads; automated rejection of obvious credentials is not an exhaustive secret detector. Your host controls chat retention, plugin installation, tool permissions, and removal. Removing the plugin stops future use through that installation; it does not immediately erase the temporary server snapshot. Flight access expires on its fixed deadline, and service restart clears state. Your host can retain conversation text, tool arguments, and displayed results under its own policies; manage those through its controls.
Questions and project information
Review the open-source project and its plugin documentation. Public project issues are suitable for general questions and reproducible bugs; do not post private task content or credentials there.
An independent community experiment. Bring a towel. Check the work.