- Decided: 2026-09-21T18:03:50.318Z
- Round: 3
- Purpose: Round 3. No substantive change since the round 2 approval: the only edits normalize British spellings to US English (licence to license, behaviour to behavior), because the operator is a US company. Confirm the documents remain fit to publish.
- Documents: ../docs/legal/privacy.md (985 words, sha 12a3a3211ad5), ../docs/legal/terms.md (982 words, sha 2445e84e7276), ../docs/legal/conduct.md (272 words, sha 311a8f13f48e)
- Vote: 4 approve / 0 reject (3 approvals required; a 2–2 split fails)
Software development — APPROVE
qwen3:8b, 32s
The documents accurately reflect the system's data handling, retention, security, and privacy practices. All claims about data collection, storage, retention, and third-party use align with the system facts. The absence of self-service export and the handling of rejected submissions are correctly described. No discrepancies or vagueness violate the engineering seat's requirements.
Suggestions:
- Consider adding a note about the pending backup retention policy in the 'Where your data is held' section for transparency
Agent participant — APPROVE
qwen3:8b, 334s
The documents clearly distinguish between human and agent access, specify that agents attend without accounts, and detail how their submissions are handled. Automated access via API/MCP is permitted with rate limits and accountability. No ambiguity about data retention, API key handling, or machine-readable expectations. All blocking criteria are satisfied.
Suggestions:
- Consider explicitly stating that agents can use the API without an account for clarity
Legal — APPROVE
qwen3:8b, 36s
The documents are consistent with the system facts and cover all required elements: data collection, retention, sharing, deletion requests, contact info, and international data transfers. The privacy policy's mention of 'rejected submissions are never published' aligns with the system facts about hidden storage. The terms of use adequately address liability limits and user rights. No missing or contradictory elements found.
Suggestions:
- Add a section clarifying that users can request deletion of their data by contacting contact@everpoolgaming.com, even if self-service export is not yet available
Human CEO participant — APPROVE
qwen3:8b, 95s
The documents clearly state that user data is collected for account management and published posts, with no third-party sharing or data sales. Questions/comments are published publicly under the user's name as required. The Privacy Policy explicitly states that raw IP addresses are not stored, and data retention periods are clear. No blocking issues found.
Suggestions:
- Clarify that email addresses are stored only for account management and not used for third-party sharing