Exness Legal Documents
A document has a date of writing, a date it starts to govern and a moment it was accepted, and those are rarely the same moment. What the gap means for something already open, and what it means for the next action.
Open Exness Account →The date printed at the top of a document is not the date it started to matter. A version is written at one moment, published at another, becomes effective at a third and is accepted by a particular account at a fourth — and the practical questions all live in the gaps between them. What a change reaches depends on which of those moments an action fell between, and a completed action keeps the version that was in force when it happened.
Four different dates on one document
- The revision date says when the text was written. It is the least useful of the four, because a text can be written long before it takes effect.
- The effective date says when a version starts to govern. Until it arrives, the previous version is still the one in force even though the newer text is already published.
- The acceptance moment is personal: it records when a particular account agreed to a particular version, and it is kept per account rather than per document.
- The notice period is the gap deliberately left between publication and effect, so that a change can be read before it applies rather than after.
- Reading only the first of the four produces the most common misunderstanding — treating a newly published text as though it already governs everything.
- A completed action keeps the version that was in force when it happened; later text does not reach backwards to re-describe it.
What a new version reaches
| Situation | Governed by | Why |
|---|---|---|
| An action taken before the effective date | The version in force at that moment | Terms are read against the moment of the action, not the moment of reading |
| Something still running when a version takes effect | Split: terms describing the original act stay, terms describing ongoing conduct move | Some clauses describe an event and some describe a state |
| Anything begun after the effective date | The new version, in full | There is no earlier situation left for the previous version to describe |
| A record of something already finished | Neither — it is closed | A finished action is not re-governed by text published afterwards |
Written, published, effective, accepted
Four separate moments hide behind what most people read as one date. Writing produces the text. Publication makes it readable. The effective moment is when it starts to govern. Acceptance is when a specific account is recorded as bound by that specific version.
They usually occur in that order and rarely close together. A text can be readable for a long stretch before it governs anything, which is the entire purpose of a notice period: it exists so that a change can be read while the previous version is still the one in force.
Acceptance is the only one of the four that is personal. The other three are properties of the document and identical for everyone; acceptance is a property of an account and is recorded per account, which is why two accounts can sit under different versions at the same instant.
Why a published change is not yet a change
The most common misreading is to treat publication as effect. A newer text on a page is not a statement about what currently applies; it is a statement about what will apply, and reading it as the present produces confident conclusions about rules that are not yet in force.
The correction is small: look for the effective moment rather than the revision line. If it is in the future, the document being read describes a future state, and anything happening today is still governed by the version it replaces.
There is a reason the gap is deliberate. A change that took effect at the instant it appeared would be unreadable in advance by construction, and the notice period is precisely the interval in which reading is still useful.
What a change reaches and what it leaves alone
A completed action is finished business. It happened under a particular version, and text published later describes situations that occur later; it does not travel backwards to re-describe events that already closed.
Something still running at the moment a version takes effect is the interesting case, and it usually splits. Clauses that describe the act of starting something attach to the moment it was started and stay with the old version. Clauses that describe ongoing conduct describe a state that continues into the new period, and those move.
Anything begun after the effective moment is entirely under the new version, with nothing to reconcile. This is why the cleanest way to avoid a split situation at all is to know when the boundary falls rather than to discover it afterwards.
Reading a change without reading everything again
A new version does not require a fresh reading of the whole text. What is worth reading is the difference, and the difference has a date attached to it. Two questions handle most cases: when does this start, and does it describe an event or a state.
An event clause is safe to check once and forget, because it will only ever be applied to things that happen after the boundary. A state clause deserves more attention, because it is the type that can attach to something already running.
Where the current version of a document sits, and which version an account has accepted, is shown in the account area rather than inferred from a page. That is the record that settles the question when it matters, and it is the only one that is per account.
Reading a document change in six moves
- Find the effective moment first, not the revision line. If it is in the future, nothing in the text applies yet.
- Check whether anything of yours is already running across that boundary; if nothing is, the whole question of split application disappears.
- For each changed clause, decide whether it describes an event or an ongoing state — that is what determines whether it reaches something already open.
- Treat completed matters as closed. Text published afterwards describes later situations and does not reopen them.
- Use the notice period for what it exists for: reading while the previous version is still the one in force.
- Confirm which version an account is recorded against in the account area, since acceptance is per account and not per document.
This page describes how versions and dates work, not the contents of any particular document. Current versions are published in the account area.
The four dates and what each one answers
| Date | Answers | Same for everyone | Where it is found |
|---|---|---|---|
| Revision | When the text was written | Yes | On the document itself |
| Publication | When it became readable | Yes | On the document itself |
| Effective | When it starts to govern | Yes | Stated in the document |
| Acceptance | When one account became bound by it | No | The account area |
Only the last row is personal. Disagreements about which rules applied are almost always disagreements about the third and fourth rows.