CD-02 · reviewed 2 June 2026
Licence Grant
How long a licensed build may be run, who owns it while you run it, and the one table that separates use from breach. It supplements the fill contract (CD-01) rather than replacing it.
standingWords defined in the fill contract (CD-01) carry the same meaning here. Where CD-01 and this document overlap, this document decides every question of use.
§1
Term
§1.1
The commercial fact first: the grant runs for 12 months, day for day from the settlement date printed on your fill page. No clause here and no product on this site confers permanent, perpetual or open-ended use.
§1.2
Within that term Algo Flexs licenses you to install and run the build for the grade you paid for. The licence is non-exclusive — others hold the same build under their own fills — non-transferable, and revocable on breach.
§1.3
On the last day the licence lapses. Detach the build from every chart and delete every copy you hold, backup included.
§1.4
Shortly before that day a note arrives quoting what a further term would cost. Say yes and a fresh ticket is issued; say nothing and the matter closes. No card is charged except by a ticket you execute yourself.
§1.5
Nothing depends on a code being typed anywhere. The build runs as delivered; the Execution Key and the fill reference exist so the desk can recognise your build when you write.
§2
Ownership
§2.1
The build is licensed, never sold. Copyright, know-how and every other right in it stay with Algo Flexs during the term and after it ends.
§2.2
What the grant conveys is use. It conveys no title, no share and no claim on the model behind the build.
§3
Use
§3.1
One table, read across. The left column is what the grant plainly allows; the right is what ends it. Anything in neither column belongs in §6.
§3.2
| aspect | permitted | forbidden |
|---|---|---|
| Accounts | Any trading account held in your name or under your sole control, at any broker, in any number. | Operating it for other people: no managed accounts, no copy-trading feed, no signal distribution. |
| Machines | One installed copy on a computer you own and one on a hosted server you administer. | An installation on a machine you neither own nor administer, or one left with a third party. |
| Copies | A copy on storage you control, so that a dead disk does not cost you the package. | Placing the file or any part of it on a file host, in a repository, a forum, a marketplace or a chat group of any size. |
| Transfer | Nothing. The grant names you and stays with you. | Selling it, lending it, renting it out, giving it away or sublicensing it. |
| Internals | Reading the manual's parameter profile and setting any input the build exposes. | Decompiling, disassembling, debugging into or otherwise recovering the source, and defeating any check the build performs. |
| Derivatives | Your own notes, presets and journals built around how you run it. | Building a product or a service on top of it for anyone else. |
| Revisions | Any revision the desk issues for your grade while the term runs, under this same grant. | Stripping, obscuring or altering a copyright or ownership notice on any file in the package. |
scroll sideways for every column →
§3.3
A build that reaches a third party ends this grant on the day it happens, with no refund and no notice period. The desk sells one file; nothing short of ending the grant is proportionate to losing control of it.
§4
Termination
§4.1
The desk may end the grant before expiry on a breach of the forbidden column of §3, or of CD-01 §7.
§4.2
You may end it whenever you like by deleting the build. Doing so does not entitle you to a refund.
§4.3
§2, §3 and the liability clauses of CD-01 survive expiry and termination alike.
§5
Revisions
§5.1
MetaTrader ships new terminal builds and brokers rename symbols. The desk works to keep each build running through such changes and issues revisions for the affected grades when it can.
§5.2
The desk gives no undertaking that a build will survive every change a platform or a broker makes, and a change that stops one is not by itself a ground for reversal (see reversals CD-03 §3).
§6
Uses this document does not settle
§6.1
A use that the permitted column of §3 does not plainly allow and the forbidden column does not plainly forbid should be described to [email protected] before you rely on it. A written answer from the desk settles it, and is kept on file against your fill reference.
The build is delivered as it is. It can lose money and the desk does not promise otherwise. The exposure notice (CD-04) and the performance basis (CD-05) are incorporated into this grant.
questions about this document: [email protected] · quote the clause number