Privacy Policy

This page describes the current MVP handling of personal and event-related information within ConflictRegistry. It is a project-facing policy summary, not a substitute for jurisdiction-specific legal advice.

Information we store

• Public event details submitted through the registry.
• Organiser name and organiser email needed for verification and edit workflows.
• One-time token records used for verification and edit links.
• Operational metadata such as timestamps and stored conflict records.

How the information is used

• To publish verified public event records.
• To send verification and edit-link emails.
• To compute and display conflict signals between relevant events.
• To operate, debug, and improve the registry service.

Public and non-public data

Event details are intended for public display once verified. Organiser email addresses and token values are not part of the public event page and are used only for workflow and operational purposes.

By submitting an organiser contact, you represent that the contact details are already public, are appropriate for public-facing event administration, or are generic role-based addresses such as info@ or events@. ConflictRegistry is intended for public event coordination, not for the collection of private personal contact details.

Contact

If this policy needs to be expanded for production deployment, it should be reviewed and replaced with deployment-specific legal and operational language.