Privacy policy

Information used on your device

• Website content: the current visible asset label in the enabled Pocket Option tab. Any asset label is supported, including currency pairs, commodities, crypto, and stocks.
• Financial information: only when you request a simulated signal, the extension reads the visible real-account balance before the signal and checks it again after expiration. Numeric balances and their currency/account identity stay in transient content-script memory. They are not written to extension storage or sent to the hosted widget. The derived PROFIT/LOSS outcome and event timing are sent to the widget.
• Tab connection information: the active tab ID, permitted page URL, and random connection identifiers are used to bind the overlay to one Pocket Option tab and validate messages. The extension does not collect general browsing history.
• Your settings: target text, seven-day plus base, confirmed-profit records, language, color theme, and layout are saved in local extension storage. Random private control/view capabilities identify your widget session; they are not Pocket Option credentials.

The extension does not read passwords, cookies, payment-card details, private messages, or general trade history. It does not click trading controls or place trades. Balance reading is inactive outside a requested signal observation. Hidden, ambiguous, or changed-account readings are left unconfirmed.

Information sent to the hosted service

The hosted interface receives the asset label, win/loss counters, widget size, timeframe, UTC offset, target text, seven-day plus total, language, theme, and layout so your panels share the same state. Anonymous session capabilities authorize these HTTPS requests. The random simulated direction, expiration, and derived outcome are processed by the hosted interface; the raw balance is not.

The companion application runs in separate hosted iframe panels. Privileged extension scripts are packaged with the extension. The hosted interface communicates through narrowly validated messages; it is not allowed to run arbitrary extension commands.

Railway and its infrastructure providers deliver the service and necessarily process network connection information such as IP addresses and request metadata. Provider operational logs are separate from the application's in-memory session state. The application contains no advertising, analytics, or tracking SDK.

Purpose, sharing, and limited use

Data is used only to provide, synchronize, and secure the visible session-tracking features. We do not sell user data, use it for advertising, or use it to determine creditworthiness. Data is not shared with an AI model or used to train models. The BUY/SELL generator is an explicitly random demonstration, not AI market prediction or financial advice. Other account activity can affect the balance comparison, so an outcome is only an estimate.

Data is transferred only as necessary to operate the hosted widget through its infrastructure providers, for security, or when legally required. We do not routinely allow people to inspect your data; access is limited to your specifically authorized support request, security investigations, or legal requirements.

Our use of information complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.

Retention and your controls

• Local extension preferences, capabilities, and manual plus values remain until you change them or remove the extension. Confirmed profit events are limited to the latest seven days and at most 2,000 records, pruned when the profile is processed. Temporary tab and bridge state uses browser-session storage.
• Hosted scores and profile data live only in the running server process. They expire after 24 hours without private controller activity and are lost on a server restart or redeployment. Read-only viewing does not extend that period. Provider operational logs are not covered by this session expiry.
• You can edit the target and settings, set the seven-day plus total in Settings, reset session counters, close individual panels, or click the toolbar button to disconnect the overlay. A browser profile shared by several people also shares its widget data.
• Uninstall the extension to remove its local storage. If you also used the companion website directly, clear that site's browser storage separately. Its preferences and private capabilities may otherwise remain in that browser profile.

Keep private control capabilities to yourself. Anyone with a private capability can use its permitted features; the application does not provide an account-recovery service.

Contact and policy changes

Contact the publisher using the support contact provided in the Chrome Web Store listing for Oleksiy Stream Asset Sync. This page will be updated if data handling changes, and the store disclosures will be kept consistent with it.