Terms of Service

1. Scope and contracting parties

These Terms apply to all contracts between Orion Quant Technologies GmbH, Ober-Roden-Straße 3, 5760 Saalfelden am Steinernen Meer, Austria, commercial register number FN 674111 s, VAT ID ATU83149647, telephone +43 676 5423969, e-mail info@orionquant.com (the "Provider"), and its customers for the OrionQuant Backtesting Engine and the related services. In these Terms, "customer" and "user" refer to the same contracting party, and "buyer" refers to the customer in a one-off purchase.

They apply to consumers and to businesses. Consumers and businesses are the persons referred to as such in section 1 KSchG (Austrian Consumer Protection Act).

The version in force when the contract is concluded applies. The German version is authoritative. The English version is a translation.

The website orionquant.com concerns a different product with its own terms.

2. What the software does

The Provider supplies backtesting software. It runs strategies written by the user against historical price data and shows what the calculated outcome would have been. Depending on the plan, this includes optimisation, risk analysis, audits, exports, a market data archive, execution on the Provider's servers and community features.

Depending on the plan, a strategy can also be run as a Live-Deployment against a live price data stream, and the desktop application can be connected to a demo account with a broker. Section 38 governs both.

The Provider does not execute orders in financial instruments for customers or hold customer funds, and it has no access to live (real money) accounts. It does not provide investment advice, portfolio management or any other investment service within the meaning of the WAG 2018 (Austrian Securities Supervision Act 2018).

Every decision about what the user writes, how the user configures it and what the user does with a result is made by the user.

What is owed follows from the agreed plan and the service description that applies when the contract is concluded. The service description is the plan overview on engine.orionquant.com.

3. Risk warnings and hypothetical results

The OrionQuant Backtesting Engine is software for analysis and strategy development. The Provider is neither a broker nor an investment adviser.

The Provider gives no commitment regarding returns, performance or preservation of capital. What the user does with a result is at the user's own risk. The Provider's liability under section 10 remains unaffected.

4. Plans, term and cancellation

The software is used on a plan: Free, Pro, Max or Enterprise. In addition, there are the perpetual licence (section 32) and packs (section 33).

The paid plans are subscriptions for an indefinite term. They are billed monthly or annually in advance and continue for one further billing period at a time until they are cancelled.

The user can cancel a subscription at any time with effect from the end of the period already paid for, in the account settings or by e-mail to info@orionquant.com. The account then reverts to Free and continues to exist.

The Provider reminds consumers of the renewal of an annual subscription by e-mail 14 days before the end of a contract year. The e-mail states the date of the renewal, the price for the following year, how to cancel, and the consequence that the subscription runs for a further year if it is not cancelled.

The Provider can cancel a subscription by giving 30 days' notice to the end of the period already paid for. Either party can terminate the contract with immediate effect for good cause.

Prices apply in the currency shown on the order page. Before each order, consumers are shown the total price including value added tax. For businesses, prices are exclusive of value added tax. Section 34 applies to changes of plan, and section 35 applies to promo codes.

A plan applies to one user account unless otherwise agreed. Section 39 governs teams.

Pro and Max are available at a reduced founding price in accordance with section 29.

Consumers' statutory rights of cancellation and withdrawal remain unaffected.

5. Rights of use and protection of the software

The software and all rights in it remain with the Provider. The customer receives a limited, non-transferable right to use it on the agreed plan. Open source components included in it are subject to their own licences, which are listed in the application.

Passing on, sublicensing and assigning the rights of use to third parties require the Provider's prior consent. The customer may copy the software to the extent necessary for its intended use and for backup copies.

Reverse engineering, decompiling and disassembling are prohibited except where mandatory law permits them, in particular in order to achieve interoperability.

The user may use and adapt the Provider's templates, example strategies and documentation for the user's own purposes, including in exported form. The user may use market data from the Provider's archive within the software for the user's own purposes and may not pass it on to third parties.

Strategies written by the user belong to the user. The Provider stores, processes and displays them only to the extent necessary for the agreed features (sections 21, 28, 30 and 38) and to the extent described in sections 19, 20, 26, 36 and 37.

6. Obligations of the user

• The user must be of legal age and have legal capacity to contract, and confirms this by registering. Anyone acting for a business thereby also confirms that they are authorised to do so.
• The user also keeps their own backup of strategies and results that are important to them.
• The user is responsible for the strategies they write, for the data they bring in and for the settings they choose.
• The user must hold the rights to the data and code they upload. This also applies to market data from the user's own sources.
• Execution on the Provider's servers is intended for backtests, optimisations, audits and Live-Deployments. The user may not use it for anything else, may not attempt to break out of the isolated environment or to reach the network from there, and may not deliberately exhaust shared capacity.
• The user complies with the rules for community content (section 36).
• The user is responsible for complying with the law that applies to them.

The Provider is not responsible for the user's decisions and settings. The Provider's liability under section 10 remains unaffected.

7. Third-party services and trade marks

The software works together with services that the Provider does not control. These include the AI providers whose keys the user stores (section 22), Stripe for payment, GitHub (section 28), cTrader by Spotware for the broker connection (section 38), Databento for order book data with the user's own key, Google for the documentation assistant, Dukascopy as the source of the market data archive and of the price data stream, and data sources and economic calendars that the application retrieves from the user's device at the user's request. They also include AI applications that the user connects to their account (section 30).

The availability, terms, prices and quality of these services are determined by their operators. The Provider does not owe them. Costs incurred there are borne by the user. The Provider's liability for its own fault under section 10 and the statutory warranty rights of consumers under section 9 remain unaffected. If a feature promised in the plan ceases to exist because a third-party service ends or changes, section 13 applies.

A list of compatible services is technical information and not a recommendation.

Names such as cTrader, MetaTrader, MQL5, TradingView, Pine Script, QuantConnect, Dukascopy, Databento, ForexFactory, Topstep, FTMO and FundingPips are signs belonging to their respective owners. The Provider is not affiliated with these companies. The names only indicate what the software works with or what it replicates.

8. Availability, maintenance and updates

A backtest runs on the user's device or, if the user so chooses, on the Provider's servers (section 21).

The Provider does not promise uninterrupted availability of execution on the servers. Maintenance, faults and restrictions imposed by upstream services do occur.

For consumers, the Provider keeps the software in the condition owed for the duration of the contract and supplies the updates necessary for this, including security updates, as required by the VGG (Austrian Consumer Warranty Act). Section 32 applies to the perpetual licence. Beyond this, there is no entitlement to particular new features.

The desktop application checks the licence online at regular intervals and continues to run without a connection for up to seven days. It searches for updates automatically and installs them when it is closed. This can be switched off. The Provider is not liable for defects that are due solely to a consumer not installing an update that was made available, despite having been notified of it (section 7(3) VGG).

Statutory warranty rights (section 9) remain unaffected.

9. Statutory warranty

For consumers, the statutory warranty applies, in particular under the VGG for digital services and under the ABGB (Austrian Civil Code). These Terms neither restrict nor exclude these rights.

The Provider warrants that the software conforms to what was agreed and is fit for the use intended under the contract. In the event of a defect, the consumer has the statutory rights.

For businesses, the Provider first fulfils the warranty by repair or replacement. If that fails, the customer can reduce the fee or terminate the contract. For subscriptions, the warranty applies during the term. For the perpetual licence, it applies for twelve months from supply. For businesses, the warranty does not cover defects that are due to the customer's settings, to third-party services or to circumstances outside the Provider's responsibility.

The warranty concerns the technical functioning of the software. It is not a commitment to economic results (section 3).

10. Liability

Towards consumers, the Provider is liable in accordance with the statutory provisions for damage that it or the persons it uses to perform the contract cause intentionally or through gross negligence, and for personal injury. Liability for damage to property and financial loss caused by slight negligence is excluded.

Towards businesses, the Provider's liability is unlimited for intent, for blatant gross negligence and for personal injury. For other gross negligence, liability is limited to the fees that the customer paid in the twelve months before the event giving rise to the damage. Towards businesses, liability for slight negligence and for lost profit and consequential damage is excluded, except in cases of intent and blatant gross negligence.

The Provider does not owe any economic success. Whether and how the user trades on the basis of a backtest is the user's own decision (section 3). This paragraph describes the service owed and does not limit liability under the two preceding paragraphs.

The Austrian Product Liability Act, Art. 82 GDPR and other mandatory provisions remain unaffected.

11. Right of withdrawal for consumers

A consumer who concludes a contract at a distance can withdraw from it within 14 days without giving reasons. Austrian law calls this right "Rücktritt", and the statutory model texts call it "Widerruf". Both mean the same right, which these Terms call withdrawal. The period begins on the day the contract is concluded. If a subscription begins with a free trial, that is the day on which the free trial starts.

Subscriptions and packs. These are digital services. The Provider begins performance before the end of the withdrawal period only if the consumer expressly requests this when ordering, when starting a free trial or when changing plan. If the consumer withdraws after that, the consumer pays a proportionate amount for the service provided up to that point: for subscriptions by days, and for packs by the portion used. The consumer is refunded the remainder (section 16 FAGG (Austrian Distance and Off-Premises Contracts Act)).

Perpetual licence. This is digital content that is not supplied on a tangible medium. The right of withdrawal ceases as soon as the Provider has begun to supply it, if the consumer expressly consented to supply beginning before the end of the withdrawal period and confirmed that they thereby lose their right of withdrawal, and the Provider has sent them the confirmation of the contract (section 18(1) no. 11 FAGG). The order page asks for both.

Exercising the right. Withdrawal does not require any particular form. It can also be declared online using the button labelled "Withdraw from contract" ("Vertrag widerrufen"), which is available throughout the withdrawal period in the account settings under Billing and in the footer of engine.orionquant.com. The Provider confirms receipt by e-mail without undue delay.

Withdraw from contract

Businesses have no statutory right of withdrawal.

The withdrawal instruction is set out in section 17, and the model form in section 18. The page "Withdrawal and Refunds" explains the same right in plainer words. If it differs, these Terms apply.

12. Payment and default

Fees are due in advance. Payment is processed through Stripe. The order page shows which means of payment are available.

If a payment fails, collection is attempted again several times, and the user receives an e-mail about this. During that time, the user remains on the paid plan. If payment is still not made after that, the subscription ends and the account reverts to Free.

For subscriptions, the Provider issues invoices electronically. For one-off purchases, the customer receives a payment receipt and, on request, an invoice.

Statutory default interest remains unaffected.

13. Changes to these Terms and to the software

Changes to these Terms. The Provider can change these Terms with effect for existing contracts if

• a change in the law or a decision of a court or authority requires it,
• new features or services are added and rules are needed for them,
• a provision is clarified or an error is corrected without any change in the substance of rights and obligations, or
• a third-party service under section 7 changes and a provision has to be adapted to it.

A change under the second bullet point applies only to the new features and services. Rights of the user under the existing contract are not restricted in this way, and no new obligations are imposed on the user for services already agreed, unless a change in the law under the first bullet point requires exactly that.

Fees under existing contracts are not increased in this way, the Provider's main services are not restricted in this way, and the relationship between service and fee is not shifted to the user's disadvantage in this way. Such changes require the user's express consent.

The Provider gives notice of a change by e-mail at least 30 days before it takes effect, with a summary and a link to the new version. If the user does not object before the change takes effect, the change is deemed accepted. The notice specifically points out this consequence and the deadline.

If the user objects, the contract continues on the previous terms. The right of both parties to cancel under section 4 remains in place. Alternatively, the user can cancel free of charge with effect from the day the change takes effect and is refunded prepaid fees for the time after that.

Changes to the software. Beyond the updates owed, the Provider can change the software where there is a valid reason. Valid reasons are adaptation to a new technical environment or to increased usage, the security of the service, the further development of features, a change in the law, and the change or discontinuation of a third-party service. The user does not incur any additional costs as a result, and the Provider gives clear and comprehensible information about the change.

If a change impairs a consumer's access to or use of the software more than only slightly, the Provider notifies the consumer by e-mail, reasonably in advance, of the features and time of the change and of the consumer's right to terminate. The consumer can then terminate the contract free of charge within 30 days. The period begins on receipt of the information or at the time of the change, whichever is later. The consumer is refunded prepaid fees for the time after that. The right to terminate does not exist if the consumer can continue to use the software unchanged at no additional cost and it remains in conformity with the contract (section 27 VGG).

The two preceding paragraphs do not apply to the perpetual licence. In that case, the buyer can decline a changed version and continue to use the previous one.

14. Applicable law and place of jurisdiction

Austrian law applies, excluding its conflict of law rules and the CISG.

Towards consumers, this choice of law applies only to the extent that it does not deprive them of the protection of mandatory provisions of the country in which they have their habitual residence.

For actions against a consumer, only the court of the consumer's domicile, habitual residence or place of employment has jurisdiction (section 14 KSchG). For contracts with businesses, the court with subject-matter jurisdiction at the Provider's registered office is agreed.

15. Complaints and dispute resolution

The Provider accepts complaints at info@orionquant.com and on +43 676 5423969. Every complaint is handled personally by a member of staff.

The Provider does not take part in proceedings before a consumer arbitration body and is not obliged to do so. The competent body would be the Schlichtung für Verbrauchergeschäfte (the Austrian consumer arbitration board).

16. Severability

If a provision is or becomes invalid, the remaining provisions stay valid. Towards consumers, the statutory rule takes the place of the invalid provision.

17. Withdrawal instruction for consumers

Right of withdrawal

You have the right to withdraw from this contract within 14 days without giving any reason.

The withdrawal period will expire after 14 days from the day of the conclusion of the contract.

To exercise the right of withdrawal, you must inform us (Orion Quant Technologies GmbH, Ober-Roden-Straße 3, 5760 Saalfelden am Steinernen Meer, Austria, telephone +43 676 5423969, e-mail info@orionquant.com) of your decision to withdraw from this contract by an unequivocal statement (e.g. a letter sent by post or e-mail). You may use the attached model withdrawal form, but it is not obligatory.

You can also exercise your right of withdrawal online using the button labelled "Withdraw from contract" in the account settings under Billing and in the footer of engine.orionquant.com. If you use this online feature, we will send you an acknowledgement of receipt of the withdrawal on a durable medium (e.g. by e-mail), including its content and the date and time of its receipt, without undue delay.

Withdraw from contract

To meet the withdrawal deadline, it is sufficient for you to send your communication concerning your exercise of the right of withdrawal before the withdrawal period has expired.

Effects of withdrawal

If you withdraw from this contract, we shall reimburse to you all payments received from you without undue delay and in any event not later than 14 days from the day on which we are informed about your decision to withdraw from this contract. We will carry out such reimbursement using the same means of payment as you used for the initial transaction, unless you have expressly agreed otherwise; in any event, you will not incur any fees as a result of such reimbursement.

If you requested to begin the performance of services during the withdrawal period, you shall pay us an amount which is in proportion to what has been provided until you have communicated us your withdrawal from this contract, in comparison with the full coverage of the contract.

Special note on the perpetual licence

In the case of the perpetual licence, your right of withdrawal expires as soon as we have begun to supply it, if you expressly consented to supply beginning before the end of the withdrawal period and confirmed that you thereby lose your right of withdrawal, and we have sent you the confirmation of the contract.

18. Model withdrawal form

Complete and return this form only if you wish to withdraw from the contract. Use of the form is not obligatory.

To Orion Quant Technologies GmbH, Ober-Roden-Straße 3, 5760 Saalfelden am Steinernen Meer, Austria, info@orionquant.com:

I/We (*) hereby give notice that I/We (*) withdraw from my/our (*) contract for the provision of the following service (*):

Ordered on (*)/received on (*):

Name of consumer(s):

Address of consumer(s):

Signature of consumer(s) (only if this form is notified on paper):

Date:

(*) Delete as appropriate.

19. Staff access to strategy source code

Staff with the relevant role can read the source code of every strategy stored on the Provider's servers. This is technically necessary for support requests, for reviewing published strategies and for investigating misuse, and it is how the audits under section 26 are reviewed.

Every individual access is logged. The log records who accessed which strategy and when, and it is kept for the period stated in sections 6 and 13 of the Privacy Policy.

Anyone who does not want to store their strategies on the Provider's servers can use the desktop application without signing in. The strategies are then stored locally and are not transmitted to the Provider.

20. Publication on the leaderboard

Publication on the leaderboard is voluntary and takes place only through an express action by the user. For each strategy, the user chooses whether it stays private, whether only its result is shared, or whether its source code is disclosed as well.

The leaderboard can be read without signing in. An entry shows the username or, if none is set, the display name, together with the profile picture, country, verified mark and number of followers, as well as the name of the strategy, the instrument, timeframe, period, key figures and equity curve of the result.

By publishing, the user grants the Provider the simple, non-exclusive right to display what was published in the product, to execute it and to make it available to other users. Copyright remains with the user.

A publication can be withdrawn at any time. The entry is then removed. Copies that other users made beforehand remain with them. Withdrawing a publication takes effect for the future.

21. Execution on the Provider's servers

A backtest runs on the user's device or on the Provider's servers. In the desktop application, the user chooses this for each run. In the browser application, every run takes place on the servers.

For execution on the servers, the source code of the strategy is transmitted there and executed in an isolated environment without network access. The source code, configuration and result are stored. The runs of all users share one queue, so waiting times are possible. Computing time is counted in server minutes (section 23).

Execution on the user's own device does not transmit the source code to the Provider. The exception is audits graded A or B under section 26. Rust strategies, too, are compiled on the user's own device for a run there, and on the Provider's servers only for a run on those servers. Regardless of where execution takes place, source code reaches the Provider or third parties if the user stores strategies in the account, uses the strategy assistant (section 22), synchronises with GitHub (section 28), or publishes or shares strategies (sections 20 and 36).

22. The user's own API keys

Users can store their own API keys for AI providers and for data providers. The Provider does not supply a key or a preset AI provider for the strategy assistant. The assistant is switched off until the user enters a key.

Keys are stored on the device in encrypted form. If the user is signed in, each key entered is also stored in the account, encrypted with AES-256-GCM, so that it is available on other devices and in the browser application. Keys are never displayed in full. If a key stored in the account is missing on a device, the desktop application downloads it automatically after sign-in and stores it there in encrypted form. Each such retrieval is logged.

There are two routes to the AI provider. If the key is on the device, the request goes directly from the user's computer to the AI provider and does not touch the Provider's servers. Otherwise, for example in the browser application, the Provider's server decrypts the key from the account and makes the request on the user's behalf. The content of the request then reaches the Provider's servers.

On this second route, the Provider stores neither the request nor the response. The AI provider, the model and a token count are logged.

An AI token within the meaning of these Terms is a unit of account of the Provider. A relayed request currently uses one AI token from the allowance of the plan (section 23), regardless of its length. The costs charged by the AI provider are incurred in addition. Requests that go directly from the device to the AI provider do not use any AI tokens.

The destination of a relayed request never comes from the request itself. It comes from a fixed list in the source code. For AI providers on this list that are based in a country without an adequacy decision or can forward data to such a country, currently DeepSeek and OpenRouter, the application obtains the user's express consent once before the first such request. Section 12 of the Privacy Policy describes the processing.

Use is subject to the terms of the respective AI provider or data provider, including as regards what it does with the content of a request. Costs incurred there are borne by the user.

23. Allowances and limits of the plan

The plan determines which features are available and which allowances apply, in particular for stored strategies, server minutes, audits, AI tokens and Live-Deployments. The figures are set out in the service description of the plan.

Monthly allowances apply per calendar month in Coordinated Universal Time (UTC), regardless of the billing period. Unused allowances expire at the end of the month.

If an allowance is exhausted, the action is refused and the limit is stated. Operations already in progress are not aborted. Additional allowances are available as packs (section 33).

Runs on the user's own device do not use any server minutes.

24. Early product stage and suspension of the service

The software is at an early product stage and is under continuous development. Changes are made in accordance with section 13. The statutory warranty under section 9 applies without restriction.

The Provider can suspend the service in order to avert damage, in particular in the event of a security incident, misuse or an error that would produce incorrect results. In the event of a suspension, the application stops at the next start and states the reason.

If a suspension lasts longer than seven consecutive days, a paying customer can cancel with immediate effect, and the Provider refunds the part of the period already paid for in which the service was not provided. Statutory warranty rights remain unaffected.

Runs that are in the queue at the time of the suspension are not executed. Stored strategies and results are retained.

25. No commitment as to accuracy

Depending on the accuracy level, the engine calculates on candles or on ticks. On a candle basis, the price movement within a candle is modelled and not replayed. For positions whose stop and target fall within the same candle, for news events and for weekend gaps, the result can differ from the real course of prices.

Exported strategy code behaves differently on another platform, because the engine, execution model and data there are different. Results cannot be transferred.

The prop firm section of the audit replicates rules of third-party companies as they were published on their websites. These rules can change. The terms of the respective company are decisive.

The Provider therefore does not promise any particular degree of agreement between a backtest and a real trading result. This describes what the software does and does not limit a consumer's statutory warranty rights under section 9. A deviation from the objectively required characteristics is effective towards a consumer only if it was agreed separately and expressly.

26. Review of audits graded A or B

Audits graded A or B are shared with the Provider. If a signed-in user audits a backtest in the application and the audit awards the grade A or B, the Provider receives and stores a copy for review by its staff: all key figures of the audit, the configuration of the run, the version of the engine, the list of trades, the name and source code of the strategy, together with the account and the time. Audits graded C, D or F and backtests that have not been audited are never transmitted.

The purpose is to assess and improve the audit and the product. Staff read the copies in a read-only view. They are prohibited from executing, changing, publishing and passing on the strategies. The Provider does not acquire any rights in them, and copyright remains with the user. Every opening of the source code of a copy is logged in accordance with section 19.

The copies are held in the EU. They remain stored until the user deletes their account or their stored content, or objects to the review in the settings under Privacy. An objection also deletes the existing copies. Section 18 of the Privacy Policy describes the processing.

27. Username, display name, profile picture and country

The username is the name under which others see the user on the leaderboard, in the forum, in profiles and on the marketplace. If none is set, the display name is shown. Both are public, and on the leaderboard they are visible without signing in.

A username has 4 to 24 characters and must comply with the rules shown in the application. The Provider does not permit names that could be mistaken for the Provider, its staff or features of the product, or names that are unlawful, offensive or misleading. Further names on an unpublished blocklist are also not permitted, such as names of companies and well-known persons in the financial sector, religious names and vulgar terms. The check runs automatically when a name is chosen or changed, and it also applies to the display name. A username can be changed twice. A name that has been released remains blocked for 30 days. Names chosen before October 2026 under the rules in force at the time remain valid. If a name that has already been assigned breaches these rules, the Provider can change it and informs the user of this.

The profile picture and country are optional. Anyone who sets them makes them public: both appear next to the name in the profile, on the leaderboard, in the forum and on the marketplace, other users can filter by country, and the picture can be retrieved via its address without signing in.

• The user uploads only pictures to which they hold the necessary rights.
• If a picture shows other persons, the user needs their consent.
• A picture may not show anything unlawful, offensive or misleading, and may not give the impression that the user is the Provider or is acting for someone else.

By uploading, the user grants the Provider the non-exclusive right, free of charge, to store the picture, reduce its size and display it in the product for as long as it is set.

The user can remove the picture and country in the settings at any time. The picture is then deleted from the Provider's servers. The Provider cannot reach copies in the cache of other people's browsers.

The Provider can remove a picture that breaches this section. Section 36 governs the procedure.

28. GitHub and the notebook

Linking with GitHub is voluntary. The user authorises the OrionQuant GitHub App, installs it in the user's own GitHub account and chooses there which repositories it may write to. The Provider acts on GitHub only when the user triggers a synchronisation, and only in the repository and folder chosen by the user.

• The user transfers only content to which they hold the necessary rights.
• The user decides whether a repository is private or public and is responsible for that decision.
• The user's GitHub account and repositories are subject to GitHub's terms. The Provider is not a party to them.

The software is built so that it does not overwrite changes on GitHub: if a file there differs from what was last transferred, nothing is written, and the user is offered a new branch instead. Section 7 applies to the availability of GitHub and to what happens to a repository on GitHub.

Disconnecting in the settings uninstalls the app from the user's GitHub account. What has been transferred remains in the user's repositories.

The notebook of a strategy belongs to the user and is not part of a run. During synchronisation with GitHub, it is transferred if the user ticks the relevant box. It is published with a marketplace entry only if the user ticks the relevant box, and it is then as visible as the entry. Section 20 of the Privacy Policy describes the processing.

29. Founding price and founding codes

For the Pro and Max plans, the Provider offers a reduced founding price. It is given to accounts that take out a subscription while one of the 50 founding seats is free, and to accounts that redeem a valid founding code. Everyone who joins the waitlist with a confirmed address receives a personal founding code. The number of founding codes is not limited. Whether the founding price applies is determined when the subscription is taken out. The price is shown before purchase. The founding price applies only to subscriptions taken out through the software or the Provider's order page.

A founding code is intended for the person to whom the Provider sent it. It is checked before payment and can be redeemed once. After that, it belongs to the account that redeemed it and is rejected for every other account. A founding code has no monetary value and is not paid out. Other discount codes are not applied in addition to the founding price.

In the German version of the website, the application and marketing mails, the founding price is called "Frühbucherpreis", the founding code "Frühbuchercode" and the founding seat "Frühbucherplatz".

The founding price applies for as long as the subscription runs without interruption, including when the user switches between Pro and Max and between monthly and annual billing.

The founding price ends

• when the subscription ends, which in the case of a cancellation is the end of the period already paid for (section 4), and
• when the subscription is paused, at the start of the pause. Before a pause, the application shows the price that applies after the pause. The pause begins only once the user expressly confirms it.

If the Provider cancels without good cause, the founding price is retained if the user takes out a new subscription within 30 days of the end.

If the user retracts a cancellation before the end of the period already paid for, the founding price remains in place.

A founding price that has ended is not revived, and a founding code that has been redeemed cannot be used again. If the user later takes out a new subscription, the price that the Provider offers at that time applies.

Statutory consumer rights, in particular the right of withdrawal (section 11), remain unaffected.

30. Connected AI applications

The user can connect an AI application, such as Claude, ChatGPT, Le Chat or Cursor, to their account through "AI apps in the cloud". The application acts under the user's account and on the user's behalf. What it does through the connection, in particular starting or cancelling a server run, counts as the user's own action. Such a run uses the user's server minutes, and allowances, packs and every other rule of these Terms apply to it as to a run the user starts in the software (sections 21 and 23).

The user decides which application to connect and what to allow it on the consent screen, including whether it may start server runs and up to which monthly minute ceiling. The user is responsible for that choice. Applications the Provider has not verified can be connected as well. The consent screen marks them as not verified and names the exact address the approval is sent to. The user decides whether to trust them.

The connection can read and, where allowed, start and cancel server runs. It cannot change or delete strategies, settings or the account. Staff accounts cannot connect.

Whoever operates the application processes what it receives under their own terms. The Provider is not a party to those terms and is not answerable for the application or for what it does with what it receives (section 7).

The results an application reports are the same backtests the software produces. They are hypothetical results and not investment advice (sections 3 and 25). What the application writes about them is its own output and not the Provider's. The user is responsible for decisions taken on that basis. The Provider's liability under section 10 remains unaffected.

The Provider can switch the feature off, refuse a connection, or end one or all connections where the security of the service or of an account requires it, including without prior notice. A connection also ends after 90 days at most, or after 30 days without use.

The feature is offered as a beta. It may change or be withdrawn (sections 13 and 24), and no particular availability is owed for it (section 8). The statutory warranty under section 9 remains unaffected.

31. Conclusion of contract, account and blocking

Account. The account is created when the user confirms their e-mail address with the code or link sent to them, or signs in through Google, GitHub or their company's sign-in. This concludes the contract for the Free plan.

Paid services. The presentation of the plans is not yet a binding offer. The user places an order by pressing the button that indicates the obligation to pay, on the order page or, in the case of a change of plan, in the application. Until then, the user can check and correct their entries. The contract is concluded when the Provider confirms the order by e-mail or activates the service. The confirmation contains these Terms, the service description of the plan, the withdrawal instruction with the model withdrawal form, and the declarations made by the consumer under section 11 when ordering.

Contract text. For each account, the Provider stores which version of these Terms applied when the contract was concluded. The current version is available at engine.orionquant.com/terms, and the Provider sends earlier versions on request. The contract can be concluded in German or English.

Use without an account. The desktop application can be used locally without an account. Sections 1 to 3, 5 to 10, 13, 14, 16, 22, 24 and 25 apply to this use.

Deletion by the user. The user can delete their account in the settings at any time. This ends a current subscription, unused packs and a perpetual licence. Before deletion, the application states in detail what is forfeited and requires express confirmation. Section 14 of the Privacy Policy describes what is deleted.

Restriction and blocking by the Provider. If a user breaches section 27 or section 36, the Provider can restrict the community features of the account. The Provider can temporarily block the entire account if the user seriously breaches sections 5, 6 or 36, or does so repeatedly despite a warning, if a payment is charged back or another person's means of payment is used, or if the security of the service requires it. The user receives an e-mail about this which states the measure, its duration, the underlying facts, the provision breached and how to complain. The Provider can terminate the contract only for good cause. It then refunds prepaid subscription fees for the time after that. A perpetual licence remains in place for use on the user's own device as long as the user does not breach section 5. Statutory claims of both parties remain unaffected. Section 31 of the Privacy Policy describes what the Provider stores in connection with a block.

32. Perpetual licence

The perpetual licence is a one-off purchase for one user account. It covers the features of the Max plan that run on the user's own device. Server minutes, Live-Deployments and an AI token allowance are not included.

The perpetual licence covers all versions of the software with the major version number 1. Later major versions with a new range of features are not included. The order page points out this limit. The statutory obligation to supply the updates necessary for the software to conform to the contract remains unaffected. Retrieval of market data from the archive is included for as long as the Provider operates the archive.

A reduced founding price applies to the first 50 purchases. This quota is separate from the 50 founding seats for subscriptions under section 29. The price is shown before purchase.

If the buyer has a current subscription, it ends at the end of the period already paid for when the perpetual licence is purchased. The order page points this out.

To the extent that the Provider offers a monthly add-on subscription for server services with the perpetual licence, the rules for subscriptions apply to it.

Section 11 applies to the right of withdrawal.

33. Packs and credits

Packs are one-off purchases of additional server minutes, audits or AI tokens. They do not expire as long as the account exists. They are used only once the monthly allowance of the plan is exhausted, and they are retained when the user switches to a lower plan.

Packs are tied to the account, are not transferable and are not paid out. If the Provider ends the contract or the service without the user having given cause for this, it refunds the price of purchased packs that have not been used. The right of withdrawal under section 11 remains unaffected.

Credits that the Provider grants voluntarily, such as a welcome credit or a gift, do not create any entitlement to receive them again.

34. Change of plan

Higher plan. A switch to a higher plan takes effect immediately. Beforehand, the application shows the proportionate amount due for the rest of the current period. On confirmation using the button that indicates the obligation to pay, the means of payment provided is charged this amount immediately. Section 11 applies to the switch. The period begins with the switch. If the consumer withdraws, the previous plan applies again.

Lower plan and different billing period. A switch to a lower plan or between monthly and annual billing takes effect from the end of the period already paid for. There is no proportionate offsetting.

Consequences of a lower plan. Stored strategies are retained. New ones can be created only up to the limit of the new plan. Live-Deployments that the new plan does not cover end with the period already paid for. Packs are retained.

Pause. To the extent that the Provider offers the pausing of a subscription, the founding price ends at the start of the pause (section 29).

35. Promo codes

The Provider can issue promo codes that reduce the price for a specified period. The conditions of a code, in particular the amount, the duration and who is eligible, are shown before purchase. After it expires, the regular price applies, which is also shown before purchase.

Promo codes have no monetary value and are not combined with the founding price.

36. User content: forum, marketplace, sharing

What is covered. This section applies to everything that users make available to others: forum posts, marketplace entries with description, source code and notebook, ratings, shared strategies, leaderboard entries, and names and profile pictures.

Rights. The content remains with the user. The user grants the Provider the non-exclusive right, free of charge, to store it and to display it and make it available in the product to the users for whom it is intended in each case, for as long as it is posted. Anyone who publishes a strategy on the marketplace or shares it with another user grants each recipient the non-exclusive right, free of charge, to use and adapt it for the recipient's own purposes. Publishing it again requires the author's consent. Copies that recipients have received remain with them if the author withdraws the content.

Rules. Content is not permitted if it

• breaches laws or infringes third-party rights, such as copyright, trade mark rights or personality rights,
• insults, threatens, discriminates or harasses,
• deceives about origin, author or results, in particular invented or embellished results and promises of profit,
• gives personal investment recommendations or advertises financial products, signal services or paid third-party services,
• contains malicious code or is intended to circumvent the isolated execution environment, or
• is spam or distributes contact details in order to initiate business outside the product.

Moderation. The Provider does not check other users' content before it appears. Other users' strategies are third-party program code that the user executes on their device or in their account. The "verified" label is awarded by the Provider. It says nothing about the correctness of results. The Provider's staff review content that has been reported or that stands out. They can hide or remove posts, lock topics, remove marketplace entries and profile pictures, change names and, in the event of serious or repeated breaches, block the account (section 31). Only usernames and display names are checked automatically, at the time they are chosen (section 27). All other decisions are made by a human.

Reports. Anyone can report content that they consider unlawful, using the report function on the content or by e-mail to info@orionquant.com. A report should identify the content precisely, give reasons why it is unlawful, and contain the name and e-mail address of the person reporting. The Provider confirms receipt, decides in a timely manner and informs the person reporting of the decision and the available remedies without undue delay.

Statement of reasons and complaints. If the Provider restricts content or an account, it informs the user concerned of the measure, its duration, the facts, the provision breached, the involvement of automated means and the possibility of complaining. Complaints sent to info@orionquant.com are reviewed by a member of staff. Recourse to the courts remains open.

Point of contact. The point of contact for users and authorities under Regulation (EU) 2022/2065 is info@orionquant.com. The languages are German and English.

Account deletion. If a user deletes their account, their forum posts and the topics they opened, including other users' replies, and their marketplace entries, including ratings, are deleted. Their leaderboard entries, the strategies they shared as held by the recipients, and the installations of their marketplace entries held by other users are also deleted, to the extent that these are stored on the Provider's servers. Copies on other users' devices remain. Sections 14 and 25 of the Privacy Policy describe the processing.

37. Internal evaluation of results

The Provider evaluates results in order to understand and improve the product. Only staff see these evaluations. They are not published, and the Provider does not acquire any rights in them.

• Runs on the servers. From every completed backtest on the servers that does not end with a loss, the Provider takes the key figures and the name of the strategy into an internal ranking. This also applies to private strategies.
• Runs on the user's own device. If the user is signed in to the desktop application and a backtest ends with a positive result, the application sends its key figures and the name of the strategy to the Provider, without code, parameter values and trades. The user can switch this off in the settings under Privacy. Key figures already sent are then deleted.

The user can object to the inclusion of server runs in the internal ranking by e-mail to info@orionquant.com. Sections 22 and 26 of the Privacy Policy describe the processing.

38. Live-Deployments and broker connection

Live-Deployments. In a Live-Deployment, the Provider runs a strategy on its servers against a live price data stream and generates signals from it. The Provider's servers do not transmit orders to a broker. These results are also simulated (section 3.2). The plan determines how many Live-Deployments can run at the same time.

Broker connection. On the Max and Enterprise plans, the desktop application can be connected to an account with cTrader. Only demo accounts are permitted. The software rejects connections to live (real money) accounts. Sign-in takes place via the Provider's server. The access tokens are then stored in encrypted form on the user's device and not on the Provider's servers. If the user signs out, a Live-Deployment running on the device ends. To the extent that the desktop application transmits orders to the connected demo account, they concern only that demo account and no real money.

No recommendation. Signals, results and exported code are not an invitation to buy or sell a financial instrument. Anyone who uses them for real trading outside the software does so at their own risk (sections 3 and 25). The Provider's liability under section 10 remains unaffected.

The account with cTrader is subject to the terms of the broker and of Spotware (section 7). Section 30 of the Privacy Policy describes the processing.

39. Teams and Enterprise

For Enterprise, the Provider and the customer conclude a separate agreement on seats, term and fee. It takes precedence over these Terms to the extent that it differs from them. Unless otherwise agreed, invoices are payable within 30 days.

Owners and administrators of a team invite members, assign roles and remove members. In doing so, they see the e-mail address, role, status and joining date of the members.

A team can set up sign-in through its own identity provider and make it mandatory for its domains. Other sign-in methods are then closed for those addresses. A seat is occupied when a member signs in for the first time. The customer is responsible for the identity provider and its settings. If the owner deletes their account, the team is deleted. Section 32 of the Privacy Policy describes the processing.

The customer ensures that its members comply with these Terms.