Support

Questions, problems and license inquiries all go to one address, and they are answered by the person who wrote the software.

Activation

Every client is issued an activation code with their invitation, entered once on first launch. It is stored on the device and, as set out on the privacy page, it is not sent anywhere unless you switch on alert notifications.

• “That code does not look right, check for a typo.” Almost always exactly what it says. Dashes, spaces and lower case are all fine, so the cause is a mistyped character. Copy the code from the invitation email rather than typing it from memory; if it still refuses, get in touch and it will be checked against the register.
• “Access for this installation has ended…” This is different, and retyping cannot fix it. The code may be perfectly correct. Get in touch, quoting the code, and it will be looked into.
• Reinstalling. The code is kept in the device keychain, so a reinstall on the same device usually finds it already there. If you are asked again, re-enter the code from the invitation, and it does not expire on reinstall.
• A new device. The same code activates your other devices. There is no per-device limit for your own use; codes are personal and may not be shared (§3 of the terms).
• Keep the invitation. It is the only copy of your code that you hold. If it is lost, get in touch. The code can be re-sent to the address it was issued to.

“Verifying your access” and “Could not verify”

The app confirms a license is current by downloading a small published file and checking it on the device. It keeps working for fourteen days after the last successful check, and says so plainly throughout that period, so a temporary loss of connectivity is visible well before it has any effect.

• “Verifying your access.” A fresh installation that has not yet managed its first check. Connect the device to the internet and try again. It only needs to succeed once.
• “Could not verify.” The fourteen days have run out. Same fix: get the device online and try again.

If either message persists on a working connection, get in touch. It is more likely to be something at our end than at yours, and it is quick to check.

Alerts and notifications

Alerts are off by default and are switched on in the app's own Alerts panel. Each category has its own switch and turning one off leaves the others running.

• Nothing arrives at all. Check three things in order: notifications are allowed for JOStocks in your device settings; Focus or Do Not Disturb is not suppressing them; and alerts are switched on in the app's Alerts panel. Also check that a pause is not still in force. See going away below.
• Signal alerts fire when a symbol's consensus changes stance on a timeframe you have selected. A reading that dips and returns is deliberately not announced twice.
• Economic-release reminders cover major scheduled US releases and are the same for every client, and are not derived from your watchlist. They carry the consensus figure beforehand and the published number when it lands, and they can be switched off on their own.
• Earnings reminders use symbols across your watchlists. Connected builds register those symbols with the notification service for server delivery.
• Trade, OTE, MACD and SAR alerts have their own category controls, symbol selections and event filters. Trade notifications describe a model setup, not an actual position or an order sent to a broker.
• A notification you disagree with is worth reporting rather than dismissing, see reporting something wrong.

Price targets

A price target notifies you when a symbol reaches a level you set, above or below the current price. Two kinds:

• One-shot: fires once and is done. This is the default, and it is what every target created before the option existed still does.
• Recurring: fires every time the level is crossed. It will not fire again until price has genuinely moved away and come back, so a price resting on your number does not notify you over and over.

Connected builds send target definitions to the notification service for evaluation and delivery. Check registration health in notification settings. A server interruption does not automatically switch delivery to the device. Targets are reminders, not broker orders, and delivery is not guaranteed.

Going away

Set a pause with an end date to suspend your notification categories and resume them afterwards. The pause travels with your server registration, so it requires successful synchronization. Previously queued notifications may still arrive.

Reading a cell

Selecting a cell in the grid opens the reasoning behind it: what spoke for the call, what spoke against it, what stayed silent, and how the symbol sits against the rest of the watchlist. The panel names every input by name, so the place to look is there rather than here. Two things about it are worth knowing in advance:

• A symbol you have just added may read differently from an established one. Anything without enough history behind it to be calculated stays out of the reading rather than being counted as neutral, so a cell firms up as history accumulates.
• A narrow majority does not turn a cell over. The reading is weighted, not counted, and it is deliberately harder to flip than to confirm, so a stance that changes on every disagreement would be noise wearing a verdict's clothes.

Market data and symbols

Prices and related information come from public endpoints and the software holds no exchange subscription: readings can be delayed, incomplete or briefly unavailable, and a provider changing or withdrawing an endpoint can interrupt coverage without notice. If a symbol shows no data for an extended period, please report it. That is usually something that can be fixed.

• US stocks and ETFs use their ordinary tickers.
• US futures use the =F symbology, for example CL=F, ES=F, GC=F.
• Brazilian B3 equities work either bare (PETR4) or with the .SA suffix.

For futures and B3 symbols the options-flow, capital-flow and news-sentiment inputs are not published at all, so they stay out of the reading. The full price and volume side still runs, and the cell says so.

Installing and updating

Clients are invited to install through Apple's distribution and update automatically from there, and nothing needs to be downloaded or replaced by hand.

If an app stops launching and asks to be updated, that is an install which has aged out rather than a license problem. The two look identical from the outside and are not. Get in touch and a fresh invitation will be sent.

Devices and syncing

On Apple devices your watchlists and alert settings follow you between your own devices through your personal iCloud account, so a symbol added on the iPhone is on the Mac shortly afterward. That synchronization is Apple's, under the Apple ID already signed in on the device; it goes to your iCloud account and nowhere else. API credentials you supply are excluded from iCloud synchronization and sent only to the issuing provider to authenticate the requests you enable. Optional Webull positions, authorization tokens and the local cost ledger do not sync through JOStocks or iCloud. Price targets are part of the supported synchronized settings.

Ending a license

You can stop using the software at any time. Deleting it removes it from your device; turning every alert category off requests withdrawal of that device’s notification registration. The service must successfully process the request; other devices and separate license or support records may remain. Uninstalling alone does not request server deletion. The grounds on which a license can end, and the notice you will receive first, are set out in §3 of the terms.

Reporting something that looks wrong

Readings that disagree with your own chart, notifications that arrive at the wrong time, or anything that simply looks incorrect are worth reporting even when you are not sure. A client comparing a notification against a real calendar is how a dating error in the economic calendar was found and fixed. It had been wrong for every client, and nobody else had said anything.

Please include the symbol, the timeframe, the time it happened, and a screenshot where you can.