Community Guidelines
- Version
- 1.0
- Effective Date
- August 1, 2026
- Status
- Active
Version: 1.0 Effective Date: August 1, 2026 Status: Active
This document is part of the VesEvi Version 1.0 legal documentation package, effective August 1, 2026, using docs/platform/VesEvi-Version-1-Product-Book.md as the source of truth for product capability, and reflects the canonical moderation principle described in the platform's content-moderation specification: describe the asset, not the people. It uses conservative, industry-standard language appropriate for an early-stage software company; as with any company's policies, periodic legal review is expected as VesEvi grows, and future revisions will be published as Version 1.1, Version 2.0, and so on.
1. Purpose
These Community Guidelines describe how to participate constructively when your activity on VesEvi may be seen by others — other members of your workspace, or, if you choose to share, the public through Worldwide History. They supplement the Terms of Service and Acceptable Use Policy.
2. Respectful Participation
VesEvi is a platform for documenting asset condition, not for personal disputes. Keep inspection notes, findings, and any Worldwide History contribution factual, professional, and focused on the asset.
3. Property and Vehicle Privacy
When capturing evidence, be mindful of what is visible in frame. Avoid unnecessarily capturing or describing identifying details unrelated to the asset's condition (such as a neighboring property, other people's vehicles, or personal belongings) beyond what is needed to document the inspection.
4. Personal Information
Describe the asset, not the people. Do not include names, phone numbers, email addresses, booking or reservation numbers, access codes or passwords, or other personal or confidential information in inspection notes or any content intended for community or public visibility. Content that includes this kind of information may be automatically flagged, redacted, delayed for review, or rejected. See the Content Moderation Policy for how this is enforced.
5. Responsible Publication
Sharing an inspection to Worldwide History is a deliberate choice, and it should be made responsibly. Before confirming a share, review what will actually be made public and make sure it reflects only asset-condition information you intend to share. See the Worldwide History Policy.
6. Constructive Corrections
If you believe a property, asset, or inspection record contains an error — for example, an incorrect address or asset detail — use the Service's correction workflow where available rather than disputing it through inspection notes or public content. Corrections should be factual and should not be used to harass another contributor.
7. AI Findings
AI-assisted findings are a starting point for human review, not a final verdict. When reviewing AI-suggested findings, confirm, reject, or add findings based on what you actually observe. Do not treat an AI suggestion as automatically correct, and do not rely on the absence of an AI finding as proof that no damage exists. See the AI Transparency and Disclosure document.
8. Reporting Abuse
If you encounter content that violates these Guidelines, the Acceptable Use Policy, or you believe misrepresents an asset's condition, you can report it through the Service's reporting mechanism, where available, or by contacting Info@vespaan.com. Reports may be submitted anonymously where the Service supports it.
9. Moderation
Content intended for community or public visibility, including Worldwide History submissions, may be automatically screened and, in some cases, routed to human review before becoming visible, consistent with the Content Moderation Policy. Moderation decisions are made to protect the integrity and safety of the community, not to suppress legitimate, factual condition reporting.
10. Community Expectations
We expect participants to act in good faith: to capture and describe what they actually observe, to respect the privacy of people who are not party to the inspection, to use the correction and reporting workflows rather than public disputes, and to treat AI assistance as a tool, not a substitute for their own judgment.
This document must remain consistent with the Terms of Service, Acceptable Use Policy, Worldwide History Policy, and Content Moderation Policy, all part of the same VesEvi Version 1.0 legal package.