Privacy and data handling notice

Forge is designed for on-premises deployment. The default product does not require product telemetry or a hosted control plane. Plant data remains on the customer-managed host unless an administrator explicitly configures an external integration.

Forge stores local license state (installation identifier, trial timestamps, reset count, and last-seen time) in the installation database. This state is used to enforce the two-hour evaluation and does not require a network call.

Marketing website contact forms

When you submit the download form or “Follow the release” form on forge-mes.com, we store your name, email, optional company, form source, and a hashed network identifier in a Forge-operated database so we can respond to evaluation requests. We do not sell this information. Contact hello@forge-mes.com to request deletion.

Data paths administrators must review

• Configured notifications and external database connections
• OIDC/LDAP identity attributes
• Backups copied outside the plant
• Agent context sent to a configured LLM provider (cloud Anthropic/OpenAI, or a customer-operated local Ollama / OpenAI-compatible endpoint). Local model traffic stays on customer infrastructure but remains plant data under the customer's processing policy.

The customer is responsible for selecting retention, access, backup, and regional processing policies appropriate to its plant and jurisdiction. Pilot-specific data-processing terms supersede this technical notice where applicable.

This page mirrors PRIVACY.md in the Forge source repository. If the two ever disagree, the file in the repository at the time of your agreement governs.