Transparency
Transparency
What LotusMake has done under its rules: reports, actions by rule, appeals and their outcomes, legal requests, and who the admins are. Refreshed weekly.
Through 2026-11-03 Updated
IWhat this page is
Every enforcement action on LotusMake is logged in a record that is never edited. The tables on this page are generated from that record with a seven-day lag, refreshed weekly, and snapshotted to a PDF once a year. No handle appears on this page. Until the platform opens and the first action is taken, every count is zero.
IIHow to read the numbers
A report is a request for review, not a finding. The gap between reports received and actions taken is the measure we care about most. The share of actions taken without notice should match the legal-emergency count and nothing else. If the two numbers ever differ, we will say why on this page.
IIIReports
Reports received, broken down by category (rules A1 through A14, B1 through B11, copyright and unsure); reports closed with no rule applied; and cases closed because the creator fixed the content within the response window. The number of reports is never a reason for action.
| Measure | Count |
|---|---|
| Reports received | 0 |
| Reports closed with no rule applied | 0 |
| Cases closed because the maker fixed the content | 0 |
Reports by category: none yet.
IVActions by rule and step
Every action, by the rule it cited and the step of the ladder it took: warning, removal, feature limits, suspension and termination. Below the table: how many actions were preceded by notice, the median time from notice to action, and the count of processor actions, which are decisions Stripe made about a creator's payment account and are counted apart (by Stripe's reason under the next heading). Restores are not a step: content restored after a counter-notice is counted under the next heading, and actions reversed on appeal under Appeals.
No actions in this period.
Notices sent before action: 0 of 0 actions. Median hours from notice to action: none yet. Processor actions, Stripe's decisions counted apart: 0.
VActions taken before notice
The four legal-emergency cases and nothing else: CyberTipline reports filed under rule A1, court orders and sanctions, copyright removals on a valid notice together with the counter-notices received and the content restored, and intimate-image removals under rule A4. Processor actions by Stripe appear here by reason code. They are not platform decisions and are counted apart.
| Type | Count |
|---|---|
| CyberTipline reports filed (rule A1) | 0 |
| Accounts closed under rule A1 | 0 |
| Court orders and sanctions actions | 0 |
| Copyright removals on valid notice | 0 |
| Counter-notices received | 0 |
| Content restored after counter-notice | 0 |
| Intimate-image removals (rule A4) | 0 |
| Processor actions, by Stripe reason code | 0 |
VIAppeals
Appeals filed and their outcomes: upheld, overturned, modified down the ladder, or reversed automatically because no reviewer decided within fourteen days. Also who decided, a second admin or the external reviewer, the median days to a decision, and the recusals logged. Application appeals are counted in the same table.
| Measure | Count |
|---|---|
| Appeals filed | 0 |
| Upheld | 0 |
| Overturned | 0 |
| Modified (moved down the ladder) | 0 |
| Reversed automatically because no reviewer decided within 14 days | 0 |
| Decided by a second admin | 0 |
| Decided by the external reviewer | 0 |
| Median days to decision | none yet |
| Recusals logged | 0 |
VIIRepeat infringer terminations
Accounts closed after three upheld copyright notices in twelve months.
Accounts closed after three upheld copyright notices in twelve months: 0.
VIIIGovernment and law-enforcement requests
Requests received, requests complied with in whole or in part, and requests refused or narrowed.
| Measure | Count |
|---|---|
| Requests received | 0 |
| Requests complied with, in whole or part | 0 |
| Requests refused or narrowed | 0 |
IXTerminations this period
One plain sentence per terminated account: the rule id and the month, and nothing else.
None in this period.
XWho decides
The current admins and the external reviewer. A second admin account exists before the first non-emergency action is taken. The external reviewer is a named person under a written agreement with read-only access to moderation records, and decides appeals when a second admin is not available or the only admin is recused.
No admin is named here yet.
No external reviewer is appointed yet.
XIHow lists are ordered
Every ordered list on LotusMake, and its order. There is no hidden score.
Makers
- Top
- The founder first, then the makers with the most active supporters. Ties go to the newest post.
- Trending
- Makers who gained the most supporters in the last 30 days. Ties go to the newest post. The founder's posts count as three days newer.
- Newest
- Newest pages first. The founder's page counts as three days newer.
- For you
- The founder first when the fields match, then makers in the fields you chose and the fields of the work you have supported, newest first.
Projects
- Trending
- The founder's open project first. Then the most contributors in the last 14 days through this site; ties go to more raised in those days, then the newer project. One project per maker.
- Newly opened
- Open projects, newest first, one per maker.
- All projects, Newest
- Open projects first, then closed projects, each newest first.
- All projects, Top
- Ordered by funds raised through this site. Wallet totals a maker reports do not count.
- All projects, Trending
- Open projects with contributors in the last 14 days through this site, the most first; ties go to more raised in those days, then the newer project. One project per maker.
- For you
- Projects in the fields you chose and the fields of the work you have supported, ordered by funds raised through this site.
Posts
- Posts, and Reading on Home
- Newest first. Posts from the founder count as three days newer.
Search
- With words
- Best match for your words first, then newest.
- With fields or tags, no words
- Newest first. On the projects page, fields alone keep the order you chose.
Fields and tags
- A field or a tag page
- Newest first.
A maker's page
- Newest
- Newest first.
- Oldest
- Oldest first.
- A to Z
- By title, A to Z.
- Projects
- Open projects first, newest first. Then closed projects, most recently closed first.
- Updates on a project
- Newest first.
- Support page, Projects
- Open projects, newest first.
XIIRules page change log
The version of the rules page and every dated change to it. A change to the rules is announced 30 days before it takes effect, except an addition the law requires, which takes effect on publication and is marked "required by law".
| Date | Version | Change |
|---|---|---|
| 2026-10-30 | 1 | First publication: List A (A1 to A13) and List B (B1 to B11). |
| 2026-11-07 | 2 | Rule A14 added: a rating set below what the content shows is corrected the same day with the reason and the guideline, which is not a strike; explicit adult content rated below 18+ is a strike, and five strikes in twelve months are a suspension. Announced before launch. |
| 2026-11-09 | 3 | Charter article 2 amended, in effect from 2026-12-09, before any list ordered by reads or supporters goes live: "We host the work. We do not edit it or review it before it goes live. Where a list is ordered, the order is a plain fact printed beside it: newest first; most funded through this site; the most supporters, new supporters, contributors or reads over a stated number of days; how closely a page matches the words you searched; or the fields you chose. The Aeon Forge, which the people who run LotusMake also run, may come first, and the list says so. There is no hidden score." The rest of article 2 is unchanged. |
| 2026-11-10 | 4 | Charter article 2 on ordered lists now reads: "Where a list is ordered, the order is a plain fact, published on the transparency page one tap from the list: newest first, most supported, most funded through this site, or the fields you chose. The founder's page, projects and posts are placed ahead, as stated there. There is no hidden score." In force at once, in place of version 3. Every order is under How lists are ordered on this page. The rest of article 2 is unchanged. The Terms now say "the founder's page" where they said "the house creator", and no longer ask that an account be 24 hours old before it applies for a maker page; no rule changed. |
XIIIFees change log
Every dated change to the share the platform keeps of each payment. The share in force, with worked examples, is on the fees page.
- 2026-11-09: one share of every payment replaces the two creator plans and the separate project share, from 2026-11-09. It took effect at once because no maker had been approved under the earlier shares.
XIVCadence
Weekly refresh with a seven-day lag, so the current week is never shown. A PDF snapshot of the full year is published each January and linked here. The record this page is generated from is kept for three years after each action or the end of any appeal or dispute, whichever is later.