Resident information
X outreach, corrections, and opt-out
How Spruce-owned X posts work and how residents or responsible accounts can request a correction, hold, or takedown.
Last updated: 2026-08-29
Spruce is the publisher
Residents do not need to expose or tag from a personal social account. The beta uses only a secured Spruce-owned X account. A resident first approves the exact public case and exact initial copy; moderation, target revalidation, and operator review follow.
The post is public accountability outreach. It is not an official government filing and X engagement never creates civic truth, ranking weight, points, official status, or a Spruced outcome.
Responsible targets
Spruce may tag only reviewed institutional accounts and accountable professional roles from an effective-dated responsibility registry. It does not target ordinary employees, private accounts, or model-invented handles.
Corrections, holds, and opt-out
A resident can decline X amplification while still publishing a Spruce case, or revoke an authorized phase before its recorded point of no return. A resident, institution, accountable role, or affected person can request a correction, target review, privacy hold, or takedown through the contact below.
Spruce preserves the original evidence and the reason for a correction. It does not silently replace history. After dispatch, a material correction or takedown uses a reviewed append-only action and truthful public notice.
Positive resolution posts
When deterministic community verification establishes the promised outcome, Spruce may create one linked, operator-reviewed resolution post using the revalidated recipient graph. It credits the actual resolver when supported and includes the verification basis and time to resolution. Scout never creates that outcome by itself.
What Spruce cannot erase
Spruce can correct its canonical record and request action on its own X post. It cannot guarantee removal of screenshots, reposts, search caches, or third-party copies outside its control.