Privacy Policy

This policy applies to Faye Codex Utility, Faye Coding Assistant, Faye Image Utility, Faye UI System Engineer, and the Faye Plugin Market website. Fayegram is the team publishing and maintaining these plugins. The plugins run inside the user's host environment and do not operate a Fayegram account service or backend.

Fayegram does not receive or retain plugin prompts, repository content, images, browser conversations, generated files, or usage telemetry on an independently operated server. The reviewed plugin packages contain no Fayegram analytics, advertising, tracking, account system, or independent network client.

The marketplace website is a static catalog. It has no sign-in, contact form, advertising, or Fayegram analytics. Its hosting provider may process ordinary request data such as IP address, device or browser information, requested URL, and timestamps to deliver and secure the site under the provider's own terms.

Depending on the workflow the user chooses, a plugin may handle the following data in the user's host environment for the purpose of completing that request:

• Prompts, instructions, task context, and limited conversation excerpts.
• Repository files, paths, source text, file sizes, line counts, Git state, test output, and other workspace evidence used for coding or source-file token estimation.
• Images, image paths, base64 image data, visible image content, prompts associated with images, and deterministic image measurements used for conversion, editing, artifact review, or user-requested age-rating estimates.
• When the user explicitly requests an image age-rating estimate, the visible image content may include mature or potentially sensitive subjects such as violence, blood or gore, nudity, sexual content, substances, horror, or strong language. The utility analyzes only what is visibly needed for the requested estimate and does not identify people or infer sensitive personal traits.
• Local saved-prompt notes, browser screenshots, compact session notes, reports, and generated image files when the user requests or authorizes those outputs.
• Supported ChatGPT/Gemini chat identity, limited conversation content, conversation URLs, and user-directed messages; when Browser Use is selected, relevant page and composer state.

The selected host and its model or subagent services process information under the user's account, workspace, and applicable provider terms. For Codex, these are the relevant OpenAI services and terms. Fayegram does not receive a separate copy merely because a Fayegram plugin was used.

The LLM Chat Operator uses a complete purpose-built ChatGPT capability when it covers the request, or supported ChatGPT/Gemini browser pages when Browser Use is selected or required. User-directed messages and explicitly authorized content are transmitted to the selected service, operated by OpenAI or Google. Fayegram is not an intermediary for that transmission, does not receive the content, and does not control the service's collection, use, retention, model-training choices, or account settings.

Other reviewed plugin scripts process files locally and do not independently call Fayegram or third-party network services. Users should not provide credentials, authentication secrets, payment-card data, government identifiers, protected health information, or other restricted data to a plugin.

Fayegram does not set a retention period for plugin content because Fayegram does not receive or store that content. Local notes, screenshots, reports, converted images, and edited images remain where the user or plugin placed them until the user deletes them. Repository history or backups may preserve copies according to the user's own tools and settings.

Host, model-provider, browser, workspace, and hosting-provider retention is controlled by those services and the user's account or organization settings. Users should review and use the deletion, temporary-chat, history, and privacy controls offered by the applicable service.

• Choose what prompts, files, images, paths, and context to provide.
• Do not invoke a workflow that is not appropriate for the content involved.
• Review proposed browser or file-changing actions and withhold authorization when needed.
• Delete local plugin outputs using normal filesystem and repository tools.
• Use the account, chat-history, temporary-chat, privacy, and deletion controls provided by the applicable host or service for content sent to it.

Fayegram may update this policy when the plugins, website, or applicable publication requirements change. The effective date above identifies this policy version when published. Fayegram does not offer individual privacy or technical-support correspondence for these plugins.