Support and transparency
Support should never be a blind payment.
If Maiks.yt accepts money, the purpose, costs, changes, and outcome should remain traceable. Support must stay voluntary, understandable, and separate from access to the community.
Before support opens
What you should know before giving.
These requirements apply whether support eventually arrives through a direct payment, platform subscription, Bits, membership, credit, or another provider.
- 01A named destination
Support should identify the project, item, or general purpose it is intended for before anyone pays.
- 02The costs around it
Provider fees, platform splits, taxes, and other known deductions should not be disguised as money available to spend.
- 03Rules for changed plans
If a goal changes materially, the original allocation and the available redirect, credit, or refund path should remain understandable.
- 04A useful public outcome
Public reporting should show progress and material corrections without exposing private donor, payment, or accounting records.
Money trail
Changes add records. They do not rewrite the past.
The planned accounting model keeps the original event and adds dated corrections. That makes fees, reallocations, refunds, and disputes visible instead of silently changing an old total.
- 01Received
Record the original amount, currency, source, and applicable provider costs.
- 02Allocated
Connect the usable value to its stated project, item, or approved purpose.
- 03Changed
Add a dated record for a correction, redirection, refund, or chargeback.
- 04Reported
Publish understandable totals and outcomes while the private ledger keeps the evidence.
Opening conditions
What still has to be decided.
A payment provider, fee model, currency handling, guest-support policy, refund and chargeback rules, project-allocation behavior, and public reporting boundary all need to be reviewed before accepting money. One or more ongoing court cases also need to conclude before this support system can be used as intended; no case details or conclusions are published here while those matters remain ongoing.
Platform support such as Twitch Bits, subscriptions, and YouTube memberships should be recorded as platform-derived value with the estimated or confirmed creator share. It should not be presented as if the full viewer payment arrived here.