Community and publisher policies

Once Marked creates a shared place around a specific public URL. Disagreement, criticism, and unpopular viewpoints are allowed. Harm, fraud, and manipulation are not.

Eligible anchors

Safe public HTTP and HTTPS pages, paywalled pages, and PDFs may be marked. Private-network services, malware, phishing, illegal material, doxxing, credible threats, non-consensual sexual content, sexual content involving minors, and explicit adult content are not eligible during the beta.

Conversation

Discuss the anchor and other participants in good faith. Spam, impersonation, targeted harassment, threats, exposure of private information, and attempts to evade a safety action may be removed. Authors can edit for 30 minutes and delete at any time; a tombstone remains when replies need its place in the thread.

First marks and influence

The first valid person to surface an anchor keeps visible discovery credit. A mark grants no ownership, metadata, moderation, publisher, or private-data authority. Influence reflects eligible comments and upvotes from other people around those marks. Downvotes, self-activity, duplicated activity, spam, invalid anchors, and removed content do not count and may be reversed.

Privacy

Saves are private and create no public count or activity. Net vote scores are public, but voter lists and profile vote histories are not. The embed does not create a persistent analytics identifier before interaction and does not inspect host-page content beyond its declared URL and configuration. Submitted URLs are fetched only for bounded metadata extraction; reports and moderator review enforce the content policy.

Publisher and platform authority

A verified publisher may configure its embed, correct presentation metadata for its own domain, and hide a comment from its own embed. A publisher-local hide does not erase the public discussion. Platform safety actions are separately authorised, recorded, and apply across surfaces. Canonical identity, aliases, and merges require platform review.

Reports and appeals

Reports are reviewed for the scope and rule identified. Moderators record a reason for each dismissal or restriction. Affected people may request an appeal through the beta feedback channel; another moderator should review it when practical.