Terms of Use

These terms describe the intended use of the current ConflictRegistry MVP. They are a project-level usage statement and should be replaced with deployment-specific legal text before production launch.

Acceptable use

• Submit only event information you are authorized to publish.
• Do not use the service to publish false, misleading, or abusive content.
• Do not attempt to bypass rate limits, token controls, or other workflow protections.

Public registry model

ConflictRegistry is designed as a public pre-announcement registry. Verified event data may be visible to other users and downstream integrations that consume the public API.

No guarantee of conflict avoidance

Conflict signals are advisory. They help organisers assess timing and audience overlap, but they do not guarantee completeness, exclusivity, or scheduling outcomes.

Service evolution

The product, API, workflows, and visual interface may change over time as the registry evolves. Versioned API paths are the main mechanism for protecting external integrations from breaking changes.