Back to landing

Transparency log

Usage pulses and accountability records.

TradeReality is membership-funded, so the best proof is public numbers. This log aggregates usage pulses, support responsiveness, changelog commits, and downtime summaries without leaking trader data or implying performance.

Data ownership: exports run on demand, journals stay yours, and nothing links to brokers. Scope guardrails live in /legal/education-only.

Weekly usage pulses

These counts are posted in the changelog each Friday. Anyone can verify them.

Manual sessions logged

Updated every Friday with anonymized totals straight from Supabase.

CSV exports requested

Shows how often traders back up their own data. No trade-level details are exposed.

Goal Lab toggles

Counts how many desks enabling/disabling Goal Lab so expectations stay calibrated.

View the public changelog →

Support responsiveness

Median first reply stays under eight weekday hours. Anything older than 12 hours is escalated to the founders. We publish those timestamps in the Ko-fi support walkthrough so you can see the raw numbers.

Inspect support workflow →

Roadmap + downtime receipts

Every feature ship, bug fix, and outage is logged publicly. This section links the transparency log to the root references so search engines and humans see the same data.

Product changelog

Weekly posts covering new Learn modules, tool updates, and notification tweaks.

Open changelog

Downtime log

Any outage longer than five minutes is listed with cause, fix, and mitigation.

View downtime log

Guardrails

  • No testimonials or screenshots are posted here. Everything is numeric or process-oriented.
  • We never mention individual accounts, brokers, or balances.
  • Each metric links back to a changelog or downtime entry you can audit yourself.

Suggested internal links

Everything above references public artifacts.

Open transparency sources

TradeReality shares process metrics only. We never imply future performance or regulated advice.