Data processing

Prompt plugins

For a hosted prompt plugin, Cofr loads its vaulted instructions and sends them with the tool input to OpenAI through its API. The external MCP host receives the tool result and may process the surrounding conversation under its own terms.

OpenAI's API data-sharing controls for inputs and outputs, model feedback, and evaluation or fine-tuning data are disabled for Cofr's organization. OpenAI states that API data is not used to train models by default unless an organization opts in. This describes training and sharing settings, not retention or Cofr's separate invocation records.

The stored instructions are not published in the MCP tool listing. Cofr keeps the invocation records described below.

Connected plugins

For a connected tool, Cofr calls the configured service through a vaulted connection credential. Some connections can create binary artifacts. This path does not invoke Cofr's prompt runtime. The configured service and external MCP host may have their own handling obligations.

Accounts, vault, and billing records

Cofr uses an authentication service for account sign-in and private storage for hosted plugin packages. Cofr stores payment-provider customer, subscription, and price references with subscription status to apply billing access. Payment details entered at checkout are handled by the payment provider.

These account, package, and billing records are separate from payment card details entered in the provider's checkout. For questions about access or deletion, contact hello@cofr.io.

Invocation history and memory

Cofr writes usage metadata separately from invocation records. Prompt invocations store clipped user input and output. Connected invocations store an input summary of argument names and string lengths, plus clipped output; dashboard tests store argument names. For deployment-bound prompt execution, a tool can write client or person memory; both write flags default to off. Those flags do not disable reads of existing memory or invocation records. Cofr's connected-tool path does not call its memory writer, though a configured backend may keep its own records.

Email hello@cofr.io to ask about a specific record or initiate a deletion request. Cofr's team will review the request manually.

Responsibilities and requests

Cofr handles website inquiries for its own business. When a specialist uses Cofr to deliver a product, the specialist decides what information that product collects and which connected services it calls. Contact hello@cofr.io about Cofr's handling of information or to ask about available contractual terms.

Specialists must describe their own product's data sources, purposes, external hosts, and connected backends in their own policies.