Community boundary
Respect people
No harassment, threats, stalking, hate, dehumanization, targeted humiliation, or disclosure of another person’s private information.
Policy for a future beta
The community opens only after the safeguards do
No public posting, accounts, comments, reactions, or file uploads are enabled today. These standards describe the minimum conduct and provenance boundary for a future invitation-only beta; they do not claim that moderation operations already exist.
Current state: planning document
Invitations, identity, file quarantine and scanning, moderation, rights handling, appeals, and incident response must be tested before any community write feature is opened.
Community boundary
Own the provenance
Post only work you may share. Name authors, source versions, licenses, remixes, AI assistance, and material changes accurately.
Community boundary
Show the real status
Separate concept, slicer check, test print, community result, and qualified application. Do not hide failures or imply a rating that does not exist.
Community boundary
Do not turn danger into a shortcut
No instructions designed to evade safety controls, access controls, law, inspection, or rights. High-risk weapon, medical, structural, and regulated claims require stricter review or refusal.
Community boundary
Protect privacy and minors
Do not post sensitive records, precise private locations, identifying details without permission, or content that exploits or endangers minors.
Community boundary
Report with context
Provide the page, version, concern, and relevant evidence. Good-faith reports, corrections, and appeals are part of the system—not retaliation targets.
Future moderation
Human review, notice, and an appeal path.
A future beta should support proportionate action: warning, label, visibility limit, removal, temporary restriction, or permanent restriction. Urgent safety and rights issues may be removed first and reviewed afterward. Creators should receive a reason and a practical appeal route when it is safe and lawful to provide one.
Rights process
Takedown is not a substitute for provenance.
The future service needs a documented notice, counter-notice, repeat-infringer, and record-preservation process appropriate to where it operates. Until that process is staffed, PrintMason will not host public user files.
Send beta-policy feedback ↗