IT IS VERY IMPORTANT THAT YOU READ AND FULLY UNDERSTAND THE FOLLOWING RISKS OF TRADING AND INVESTING THROUGH YOUR SELF-DIRECTED ACCOUNT ON STREAK WORLD
Market prices, data and other information available through Streak are not warranted as to completeness or accuracy and are subject to change without notice. System response and account access times may vary due to a variety of factors, including trading volumes, market conditions, system performance, and other factors.
No Investment Advice Provided
Any opinions, chats, messages, news, research, analyses, prices, or other information contained on Streak World or its affiliated Websites are provided as general market information for educational and for self-directed purposes only, and do not constitute investment advice. The Website should not be relied upon as a substitute for extensive independent market research before making your actual trading decisions. Opinions, market data, recommendations or any other content is subject to change at any time without notice. Streak World. will not accept liability for any loss or damage, including without limitation any loss of profit, which may arise directly or indirectly from use of or reliance on such information.
We do not recommend the use of technical analysis as a sole means of trading decisions. We do not recommend making hurried trading decisions. You should always understand that PAST PERFORMANCE IS NOT NECESSARILY INDICATIVE OF FUTURE RESULTS.
Create is a process to input entry and exit conditions involving technical indicators, stop loss percentage, take profit percentage, instrument, quantity of stocks etc and form a trading strategy, hereafter referred to as “trading algo” or “algo” or “algorithms” or “strategies”.
Backtesting is the process of testing a trading strategy on relevant historical data to ensure its viability before the trader risks any actual capital. A trader can simulate the trading of a strategy over an appropriate period of time and analyze the results for the levels of profitability and risk. Streak World Pvt. Ltd. (Streak.world) strives to give you accurate information on your trading strategies and your algorithms, however, methodology covers the PROCESS AND ASSUMPTIONS THAT ARE MADE DURING CALCULATING THE RESULTS OF THE ALGO(ALGORITHM) DURING BACKTEST AND THE DATA SHOWN AFTER DEPLOYMENT.
Using Streak World Pvt. Ltd. (Streak.world)’s Services, including its deploy services, presents several different types of risk. We have summarized these below. You should read and understand these risks before you use any of Streak World Technologies Pvt. Ltd. (Streak.world)’s services.
The risks that can arise from using Streak World Technologies Pvt. Ltd. (Streak.world)’s Site and Services fall into three broad categories:
1. Risks inherent generally in using Internet-based technology;
2. Risks inherent in creating, backtesting, and deploying trading algorithms; and
3. Risks inherent in engaging in live algorithmic trading.
ANY PERMUTATION OR COMBINATION OF THE OCCURRENCE OF THE POTENTIAL EVENTS THAT DEFINE THE RISKS DESCRIBED IN THIS DISCLOSURE STATEMENTS CAN LEAD TO A TOTAL OR PARTIAL LOSS OF OPERABILITY, RESPONSIVENESS, FUNCTIONALITY, AND FEATURES THAT COULD MATERIALLY AND ADVERSELY AFFECT YOUR USE OF STREAK.WORLD OR ITS AFFILIATES SITES.
Risks of Using Internet-based Technology – Generally
The Internet-related technological risks arising from using Streak World Technologies Pvt. Ltd. (Streak.world)’s Site and Services to write, test, analyze, and run trading algorithms and related trading strategies fall into three categories: (a) risks related to Streak World Pvt. Ltd. (Streak.world)’s software; (b) risks related to Streak World Pvt. Ltd. (Streak.world)’s computing and communications infrastructure; and (c) risks related to your software, hardware, and Internet connectivity. It is your obligation to thoroughly and appropriately test any trading algorithm before you deploy it and to continually monitor the operation of any deployed trading algorithm to ensure it is running properly and in compliance with any applicable rules.
a. Streak World Pvt. Ltd. (Streak.world)’s software/code might fail to work properly.
i. All software is subject to inadvertent programming errors and bugs embedded in the code comprising that software. Any of these errors and bugs can cause the software in which they are located to fail or not work properly. The application software used to operate Streak World Pvt. Ltd. (Streak.world)’s Site and Services depend is subject to this risk. Despite testing and on-going monitoring and maintenance, inadvertent errors and bugs may still cause a failure in Streak World Pvt. Ltd. (Streak.world)’s applications software.
ii. We may update or revise our applications software in ways that cause some of its functionality or features to be lost or diminished. Any such loss or diminution could make Streak World Pvt. Ltd. (Streak.world) less valuable to you, cause certain functions and features in your algorithms to fail, and require you to change your algorithms and related trading strategies.
b.Streak World Pvt. Ltd. (Streak.world)’s computing and communications infrastructure may fail.
The operation of Streak World Pvt. Ltd. (Streak.world)’s Site and Services depend heavily on our infrastructure of computing and communications systems. The operation of this infrastructure is subject to several risks:
i. Any or all of the systems comprising our infrastructure could entirely or partially fail, function erratically, or function very slowly (thereby leading to latency, i.e., delays in receipt of and response to user requests).
ii. We may inadvertently cause a systems failure during planned or unplanned system maintenance.
iii. We may undertake software upgrades, either planned or unplanned, that take longer to implement or that causes your computer system or Internet connectivity to fail.
iv. We may change or remove functions and features whose change or removal causes your system to fail, function erratically, or function very slowly.
c. Your computer system and your Internet connectivity may fail.
Any of the components of your computer system and/or your Internet connectivity could fail entirely, function erratically, or function very slowly. The result of any of these occurrences could make it difficult or impossible for you to access the Streak World Pvt. Ltd. (Streak.world) Site or use the Streak World Pvt. Ltd. (Streak.world) Services.
You may incur losses (or fail to gain profits) while trading securities. You should discuss the risks of trading with the broker-dealer where you maintain an account or other investment professional. Streak World Pvt. Ltd. (Streak.world) provides you only with trading technology and can provide no investment, financial, regulatory, tax or legal advice.
Risks in Create, Backtest, and Deploying Algos (Algorithms)
Creating, backtesting, and deploying computer-based trading algorithms is subject to several risks, any of which can cause your algorithms to not function as you had intended or fail to achieve one or more of the objectives of your algorithms. Algorithmic trading is rapidly changing as a practice and as an industry. Models of markets used to write and test trading algorithms are inherently limited and often fail to perform as expected. In addition, trading algorithms are implemented in software programming code, and no matter how well designed and thoroughly tested, any such code can have logical errors and bugs that cause the algorithms to malfunction or suggest trades that, if executed, would result in losses. It is your obligation to thoroughly and appropriately test any trading algorithm before you deploy it and to continually monitor the operation of any deployed trading algorithm to ensure it is running properly and in compliance with any applicable rules
a. Your algorithm may be designed on the basis of an incorrect understanding of technical indicators which may not work as expected.
b. Your algorithm may contain logical errors in the way you understand the indicators and comparators.
c. Errors may exist in the data used for testing your algorithm or the applicable model of the market.
d. Your algorithm might appear to succeed in a backtesting environment using historical data, but fail when using live data.
e. Your algorithm might appear to succeed with some data sources, but fail when using other data sources in our system.
f. Your algorithm may not achieve the returns you anticipate. There are no guarantees, or even expectations, that can be made about the future behavior of an algorithm.
Risks of Engaging in Live Algorithmic Trading and Related Strategies
Streak World Technologies Pvt. Ltd. (Streak.world) doesn’t allow you to engage in live trading directly without your use of your own exchange/broker account to actually execute the order, perform trades, manage funds and other trading and investment related services. Engaging in live trading subjects you to (a) the risks associated with trading generally, and (b) the risks associated with live algorithmic trading using Streak World Technologies Pvt. Ltd. (Streak.world).
THE OCCURRENCE OF ANY OF THE EVENTS ASSOCIATED WITH THESE RISKS, ALONE OR IN COMBINATION WITH ANY OF THE OTHER RISKS DESCRIBED IN THIS DISCLOSURE STATEMENT, COULD RESULT IN THE LOSS OF ALL OF THE MONEY YOU HAVE DEPOSITED IN THE BROKERAGE ACCOUNT YOU USE FOR LIVE TRADING BASED ON THE ALGORITHMS YOU WRITE, TEST, AND RUN ON Streak World Pvt. Ltd. (Streak.world). LOSSES CAN HAPPEN MORE QUICKLY WHEN USING ALGORITHMIC TRADING THAN OTHER FORMS OF TRADING. YOU SHOULD DISCUSS WITH AN INVESTMENT PROFESSIONAL THE RISKS OF TRADING IN GENERAL AND ALGORITHMIC TRADING IN PARTICULAR. YOU USE ANY ALGORITHM IN LIVE TRADING AT YOUR OWN RISK AND IT IS YOUR OBLIGATION TO THOROUGHLY AND APPROPRIATELY TEST ANY TRADING ALGORITHM BEFORE YOU DEPLOY IT AND TO CONTINUALLY MONITOR THE OPERATION OF ANY DEPLOYED TRADING ALGORITHM TO ENSURE IT IS RUNNING PROPERLY AND IN COMPLIANCE WITH ANY APPLICABLE RULES.
Certain Risks of Live Algorithmic Trading
In addition to all of the risks described above, live algorithmic trading is subject to the following types of types of risk:
i. Backtesting Cannot Assure Actual Results.
It is not possible for a computer model to truly predict what might have happened if an algorithm-based trading strategy was in play in a live trading environment. For example, the implementation of such a strategy can itself have an impact on the market, and the model may fail to account for real-life factors that impact the model. Moreover, the model may fail to account for execution costs including broker commissions, fees, and trading slippage.
A promising model result does not necessarily predict a successful strategy. Execution of the algorithm and the performance of that code may prove to be impossible in a live trading environment. Changes in various market factors not foreseen in a model can change, causing a strategy to fail. A backtest might be over-fitted to past data, and fail when the strategy is applied to new, live data. Orders that were executed correctly in the backtesting environment may be disallowed or rejected because of various reasons eg: margin requirement , illiquid stocks etc causing the algorithm to fail or otherwise not perform as expected. Attempts to create, exit, or cancel orders might fail, or might result in unexpected outcomes. Moreover, your algorithm might not handle market conditions that cannot be reasonably anticipated, i.e., a “flash crash” or an exchange outage. These market conditions, by definition, will not have been tested.
ii. The relevant market might fail or behave unexpectedly.
Market centers in which you seeking to implement your trading strategy may fail or behave incorrectly because of technical reasons relating to infrastructure, connectivity, and similar factors.
Your algorithm might suffer from adverse market conditions. Those conditions can include lack of liquidity, and abrupt and unwarranted price swings. Also possible are late market openings, early market closings, market chaos, and mid-day trading pauses, and other such disruptive events.
iii. Your broker may experience failures in its infrastructure, fail to execute your orders in a correct or timely fashion or reject your orders.
Streak.world infrastructure on which you are running your algorithm might fail. In addition, even if Streak.world infrastructure or your broker’s infrastructure and API are working correctly, the orders may get rejected in error or by design, incorrectly execute orders, or induce errors through unexpected behavior (such as returning messages out of sequence, incorrectly acknowledging orders, or posting incorrect execution reports). If at all, any losses arise from these risks, Streak World Pvt. Ltd. (Streak.world) bears no responsibility for this.
iv. The system you use for generating trading orders, communicating those orders to your broker, and receiving queries and trading results from your broker may fail or not function in a correct or timely manner.
Latency (i.e., delays) within and between your system, as well as those of your broker and the market in which you seeking to affect trades, might cause orders, corrections, and cancels to be placed or not placed in ways that are not desired. You may receive incorrect information, or be unable to get information, about your orders, your positions, or market conditions. Incorrect actions may be taken, or correct actions may not be taken, because of inaccurate or missing information. In addition, you may be unable to terminate or edit your algorithm.
v. Time lag at various point in live trading might cause unexpected behavior.
The time lag between the actionable alert generation time, the time at which you receive the actionable alert, and the time at which you take action on the alert, can cause a delayed order placement in the market, lead to cancellations, and cause you loss (or fail to gain profits) and may deliver unanticipated results vastly different from the backtest results.
vi. The systems of third parties in addition to those of the provider from which we obtain various services, your broker, and the applicable securities market may fail or malfunction.
Algorithmic trading depends on the availability of various services from third parties in addition to your service provider and your broker. These, for example, include providers of data services, computational services, and network connectivity. The operations of these third parties are beyond all of our reasonable control. Regardless of the reason for any failure by your broker, the market in which you seek to have trades executed, or these other third parties, we will not have any liability for any such failure.
Accurate and complete real-time price data is critical for the success of algorithmic trading. The systems of these data providers could experience failures, errors, and latency, which could result in missing, incorrect, or stale market data.
vii. Malicious and criminal activities might cause your algorithms and strategy to fail or your brokerage account to be compromised.
All computers and networks are subject to malicious “hacking” attacks and criminal activities designed to misappropriate intellectual property, compromise personally identifiable information, steal funds, or any combination of such purposes. These attacks might be attacks on a target of opportunity or specifically targeted. Each of the various systems described above that are necessary for you to engage in live algorithmic trading is subject to such attack. Any such attack could cause the system so attacked to function improperly or not at all and could result in the misappropriation of your intellectual property, the compromise of your personally identifiable information and personal financial information, the theft of your funds and can cause your algo be misbehave, malfunction or behave erratically.
The first time you login to Streak website, the web browser asks your permission to allow browser notification. Please allow the notification, else you won’t be getting any alerts on your system when the algo condition is met.
Users can check the sample algos provided on the dashboard to understand the working of indicators and how to use them. Streak is not responsible for any profits/losses occurred after deploying sample algos in the market.
Risks of Automated Trading Systems
Mechanical failures. The theory behind automated trading makes it seem simple: Set up the software, program the rules and watch it trade. In reality, however, automated trading is a sophisticated method of trading, yet not infallible. What that means is that if an internet connection is lost, an order might not be sent to the market. There is also the potential for a power loss, computer crash, or some other system quirk that could stop your algorithm from running or cause an anomaly.
Monitoring. Although it would be great to turn deploy your algorithm, and leave for the day/week, automated trading systems do require monitoring or an alerting system. This is due to the potential for mechanical failures, such as connectivity issues, power losses or computer crashes, and to system quirks as mentioned above or an exchange/broker account related issues. It is also possible for an automated trading system to experience anomalies that could result in errant orders, missing orders, or duplicate orders. If the system is monitored and/or has an alerting system, these events can be identified and resolved quickly.
Trading Experience. Your level of trading experience with automated trading systems is important in deciding how you should choose your overall trading strategy. Highly complex strategies with many variables make it more difficult to determine whether the trades that will execute are designed to be profitable. Starting with simple automation strategies will allow you to develop experience and learn methods of trading that work best for you.
Real-life discrepancies. There could be a discrepancy between the “theoretical trades” generated by the strategy during backtest and the order entry platform component that turns them into real trades. Most traders should expect a learning curve when developing automated trading systems, and it is generally a good idea to start with small trade sizes or conduct “paper trading” while the process is being refined.
No High Frequency Trading. This platform is NOT a high-frequency trading platform. While an automated trading strategy can send trades to the market at a high frequency, Streak does not support the necessary speed of either market data flow or trade execution speed necessary for a high-frequency trading program to function as intended. Automated trading strategies that have an over-reliance on the speed of market data and speed of execution will not be able to compete effectively with traders who have state of the art equipment and very short high-speed connections to the market, in particular when the connection you are using to the internet is via a residential internet service provider.
Reliance on Risk-Reducing Orders or Strategies. With automated trading, substituting manual market monitoring with the placing of certain orders (e.g. ‘stop-loss’ orders or ‘stop-limit’ orders) which are intended to limit losses to certain amounts may not be effective because market conditions may make it impossible to execute such orders. At times, it is also difficult or impossible to liquidate a position without incurring substantial losses and Streak’s platform does not provide a readily available manual intervention process.
Once the algo is live and an alert is generated based on the conditions in the algo, our systems attempt to deliver the alert to the user over the internet. By using this service, the user acknowledges they understand that the alerts’ delivery is dependent on many factors such as the internet connection of the user, location, time of the day, server load, data availability etc.
We recommend users to be logged in to streak.world, keep it open in their browser and maintain a fast uninterrupted internet connection to their devices to see the best alerts delivery.
Streak relies on third-party services for market data eg. Direct Exchange data feeds for ticks, OHLCV etc. If these services are down due to unforeseen circumstances or experience down time due to various technical / non-technical issues, Streak might not be able to generate and deliver the actionable alerts on time or at all.
Once a signal is generated, we try to send this signal to the user’s device over the internet. The delivery of these alerts are subject to network conditions of the user, internet services and technical issues.
Accurate and complete real-time price data is critical for the success of algorithmic trading. Our service providers or systems that provide data could experience failures, errors, lag, and latency which could result in missing, incorrect, or stale market data leading to no/wrong signals(alert) while triggering an alert.
All actionable order alerts are read-only market order alerts, where with a single click the user can send the order to the exchange. The actionable order alerts are made read-only in order to obtain consistency in the deployed and backtest results and to avoid any drastic increase in risk. If on any scrip/instruments such as Stock, Futures, Currency Futures etc., there is high volatility due to news-based or non-news based or any speculative events / positions, Streak is not responsible for higher slippages. You understand that volatility is the nature of the market.
Upon clicking on buy/sell on the order window, based on users network speed, network latency can be experienced and any rapid clicks on the buy/sell button through same or different windows can lead to multiple order placements. Users take full responsibility on making sure the actions on the notifications are their own actions and are fully aware of their positions and algo status when clicking on the buy/sell button.
Algo deployment cycle / Algo Cycle
The algo cycle Entry and respective exit of an algo is defined as an algo cycle.
Once an algo is deployed, the stocks are periodically tracked based on the conditions in the algo. The periodicity with which the market is tracked is the same as the candle interval selected by the user while backtesting the algo and shown in the algo summary before deployment. An algo’s ideal life cycle and the tree of events that can occur during an algo’s life cycle, called an “algo cycle”, has been explained below:
1. Waits for the first entry event as per the entry condition in the deployed section.
2. Once the entry event occurs, an entry signal (buy/sell) is triggered and an actionable alert is sent to the user.
3. The user can choose to act on the alert by clicking buy/sell or choose to ignore the alert and cancel it (canceling from the notification window will terminate the algo).
4. If the user has clicked on buy/sell in the alert, a market order is sent to the exchange (NSE).
5. The order will either be successfully placed by the exchange or it might get rejected due to reasons such as insufficient capital, etc. If the order gets rejected by the exchange, the algo gets terminated. Streak does not verify the margin requirement, exchange/broker determines the margin requirement as all orders are placed on exchange/broker.
6. After the successful placement of an order, the algo immediately triggers an SL-M order. This is a STOP LOSS order which the user can place or cancel. Canceling this order will NOT terminate the algo and your positions will be open and if your Stop Loss is triggered later, then a notification is sent again to the user. (If you have already placed the SL-M order then if the SL hits first then this order will get executed and position is closed).
7. The algo continues to track the stock waiting for the exit signal (SL or TP) or exit condition. Based on the entry price and the SL and TP percentages entered by the user, the SL and TP prices are calculated which are displayed to the user in the Deployed Page Subsection ENTERED.
8. When the SL/TP price occurs or if the exit condition is met, whichever occurs first, an actionable notification is sent to the user again. The user can then chose to act on it by clicking buy/sell or choose to ignore the alert and cancel it (cancel will terminate the algo). Note: If you cancel the SL or TP alert from the notification/alerts page the algo gets terminated. However, if you cancel the notification or alert from the order log in deployed page, the algo is not terminated.
9. If the user has clicked on buy/sell in the alert, a market order is sent to the exchange (NSE) and the algo’s life cycle is now complete.
10. The “algo cycle” sequence defined above is an ideal sequence and is subject to market conditions and user behaviour. Based on the user’s action or market conditions, the sequence might not completely occur in the same way as it is intended to, since this sequence may have been interrupted due to various reasons such as, the user stopping the algo, order rejection by the exchange, network lag, network error etc.
11. For both intraday and overnight algos, the algo cycle has to be defined by the user during deployment. Depending on the number of algo cycles, the algo moves to a ‘complete’ state and is stopped.
12. Margins are not blocked till the user acts on the actionable alerts (buy/sell) and the order is sent to the exchange.
13.The algo can be stopped by the user at any time in the life cycle of the algo by clicking on the “Stop” button. If the algo has not entered a position, it will be directly stopped otherwise the user will be presented with an option to either stop the algo by keeping the positions open or to exit positions at market and stop the algo. The algo will no longer be tracked and no further alerts will be sent to the user for the respective algo.
14. In cases where the user stops the algo and chooses to keep positions open, the responsibility of closing any and all positions is solely on the user, and user will get no alerts for that deployed instrument once the algo is stopped.
15. All actionable order alerts sent to the user can be used only once and will be active for only 5 minutes after which the alert expires in the notification/ alerts section. However, these alerts are actionable in the order log section of the Deployed Page.
17. All actionable alert orders are market orders and users can expect price variation from the price at which the alert was triggered to the price at which the order is placed. Slippages are expected to occur.
18. If the user’s order is rejected due to various reasons such as shortage of funds, circuit limit hit, no liquidity in market, etc, the algo will be stopped and no further alerts will be sent for that algo. This is done in order to avoid unnecessary tracking of instruments where the order placement failed. However, the user can deploy the algo again and take action on any new alerts that get generated.