Content Policy
Draft for reviewWhat belongs on Lettrim, what does not, how licensing works when you publish, and how problems get handled.
What belongs
Your original writing — fiction, essays, poetry, scripts, academic work — at any stage of polish. Drafts are the point. So are briefs, notes, and the process of rewriting.
What does not belong
Unlawful content, child sexual exploitation material, grooming, harassment, threats, plagiarism and infringement are prohibited across Lettrim. Lawful explicit sexual material and graphic depictions of violence belong in private projects. Lettrim considers the context of literary depictions of abuse when assessing public suitability.
Licensing when you publish
Publishing requires choosing a license for the edition. All rights reserved preserves your rights, subject to permissions you grant and applicable law. CC BY 4.0 permits sharing and adaptation with attribution, including commercial use. CC BY-NC 4.0 permits noncommercial sharing and adaptation with attribution. CC0 dedicates the work to the public domain to the extent permitted by law.
Reader copying is off by default. If you enable it, a reader can create a private fork subject to the Terms and the applicable license. Existing forks can remain after you disable copying or unpublish.
You can only license what you own. Do not publish writing you did not write or do not control.
Reporting
Every public edition carries a “Report this edition” control: copyright, offensive, spam, or other, with an optional note. Reports land in the publishing writer’s moderation queue, where they can dismiss the report or unpublish the edition themselves.
Lettrim may restrict public access or suspend an account as described in the Terms. A public operator contact for other reports and appeals is pending.
Copyright reports
A copyright report should identify the copyrighted work, the address of the reported material, how to reach you and your authority to act. The final policy will specify the public contact and any applicable notice or counter-notice process.
The writing process
Revision history is private by default. Public projects can expose branches and revision history. A published edition may also show eligible history if the writer enables process sharing.