◆Transparency commitments
What we will publish,
including the parts
that cost us
Six commitments with triggers and deadlines, made while all six are empty and therefore free — which is the only honest time to make them.
What we commit to publishing
Six things. Each has a trigger and a deadline, because a commitment without a deadline is a preference.
| What | In what form | When |
|---|---|---|
| Every payout, and every refusal | Settled and refused requests in one table, refusals carrying the clause they were made under. No filter that hides the second kind. | From the first request |
| The refusal rate, monthly | Requests refused over requests decided, as a percentage, with both raw counts beside it. Published whatever it is. | Monthly, from launch |
| Every declared outage | Start and end timestamps, what was affected, and what we did about breaches recorded during it. Posted within one hour of the outage ending. | Within 1 hour |
| Every pricing gap that triggered a review | The instrument, the size of the gap, and how many breaches were reversed because of it. | Same day |
| Every rulebook version | Each version stays online at its own address, permanently, so that the document an account is bound to remains readable rather than replaced. | On change |
| Every correction to anything we have written | Dated, with the previous wording, rather than a silent edit. | On change |
Every one of these is currently trivial to honour, because all six are empty. That is the point of writing them down at this moment rather than later: the commitments were made when there was nothing embarrassing in them, and they can be checked against whatever fills them.
Why this, and why now
The prop-trading category has a specific credibility problem: the marketing claims that matter most are the ones nobody can check. Payout totals are self-reported. Pass rates are self-reported or absent. Rule changes are made to a live document with no version history. Outages are acknowledged when a forum notices them.
The response to that is not louder claims. It is a smaller number of claims that happen to be checkable, made before there is any commercial pressure to shade them.
This is also why there is no incident log below with three tidy resolved incidents in it, no uptime percentage, and no count of disputes upheld in traders’ favour. Those numbers would be flattering, and we do not have them.
Outages, and the word “declared”
Any breach recorded during a declared outage is void, and open positions during an outage are closed at the pre-outage price where that is better for the trader. The weak point in that sentence is who declares the outage, so:
- An outage is declared by us, in public, with start and end timestamps, within one hour of it ending — not when a trader reports it and not when it becomes convenient.
- If a trader can demonstrate a platform failure we did not declare, the breach is void anyway and the incident is added to the log retroactively with a note saying we missed it.
- The log records incidents nobody complained about. An outage at 03:00 UTC with no open positions still gets a row.
0
Incidents recorded: none. There is no platform yet, so there is nothing to record. The first entry will appear here, dated, whether or not it cost anyone anything.
The rules do not change on a live account
This is the commitment we expect to be tested on first, so it is stated as a mechanism rather than as an intention:
- Every account records the rulebook version it opened under, and is governed by that version for its entire life.
- A new version binds only accounts opened after it — including when the change is in the trader’s favour. Selective retroactivity is how a policy becomes discretionary.
- Every version stays published at its own permanent address.
The current version and its changelog are on the rulebook page.
Corrections
If something on this site is wrong — a figure, a description of someone else’s published terms, a broken commitment — write to hello@upme.com. Corrections are made with a dated line saying what changed, and the previous wording stays visible. Pages are not silently edited.
This applies to the research library as well. Anything we write about another firm is drawn from that firm’s own published terms or from a primary document, and if a term has changed since we read it we would rather be told than be stale.
Questions
What does upme actually publish today?
The challenge rulebook with a version number and date, the payout policy, an empty payout ledger, an empty incident log, and its legal status. Every one of those is currently zero or a rule; none of them is a claimed result.
Can upme change its rules on an account that is already open?
No. Every account is bound to the rulebook version it opened under for its entire life, a new version binds only accounts opened after it, and every published version stays online at its own permanent address.
Who decides when an outage counts?
upme declares outages in public with start and end timestamps within one hour of the outage ending. If a trader demonstrates a platform failure that was not declared, any breach recorded during it is void anyway and the incident is added to the log with a note that it was missed.