Support

Current routes for account, research content, security, and policy support.

link to this sectionSupport

Effective 2026-08-31 for Public Preview. Coverage, ownership, and response targets are required before Public Beta.

Support is currently handled by project maintainers. EviMesh does not yet promise a response time, continuous coverage, or a public service-level commitment.

Include the affected route, stable object ID, revision, approximate time, and request ID where available. Never send a password, API token, recovery code, or private signing key.

link to this sectionContact routes

Account, access, identity, export, and deletion: email support.
Research content report: email content support.
Moderation appeal: email an appeal.
Security vulnerability: GitHub private vulnerability reporting.

Do not publish an exploitable vulnerability in an issue or research object. Use the private security route whenever available.

link to this sectionHonest service status

A dedicated public status service is a pre-Beta requirement but is not stated as active during Public Preview. Project application and membership interfaces may also be unavailable. Contact support rather than bypassing roles or writing directly to research storage.