RiskCurrent support

Email [email protected]

To help us reproduce the issue, please include:

• Your device model
• Your Android version
• Your RiskCurrent version
• A description of the issue, including what you expected and what happened instead
• The name of the affected metric or screen, if the issue is specific to one

RiskCurrent is an informational monitoring tool and does not provide investment, legal, emergency, or professional financial advice.

If data is not updating:

• Check that your device has a working internet connection
• Retry the refresh — transient network failures are common on mobile
• Check whether the problem affects one metric or all of them

A failure at an upstream data provider or at the RiskCurrent backend can affect individual metrics without affecting the rest of the app. When a fresh value cannot be retrieved, a valid last-known reading may remain available, labeled with its state so you can judge how much weight to give it.

Every reading in RiskCurrent carries a state describing how fresh it is. The app determines these states; the definitions below explain what each one means in practice.

Current

The reading arrived within its expected refresh window. This is the normal state.

Delayed

The reading arrived later than expected. It is still recent enough to be useful, but it is behind its usual cadence.

Stale

The reading is older than expected for that metric. Treat it with more caution than a current one.

Last-known

A fresh reading could not be retrieved, so the most recent value that did arrive successfully is shown instead, with its age.

Unavailable

No usable reading is available. The source or the backend did not return data that met the app's checks.

• Enable notifications through your Android system settings and in RiskCurrent's own settings
• If you previously denied the notification permission, Android requires you to re-enable it through system settings — the app cannot re-prompt
• Notification delivery depends on the device, the operating system, battery optimization, and app refresh behavior, and is not guaranteed

Alerts are informational. RiskCurrent is not a real-time emergency alerting system and should not be relied on for time-critical warnings.

Watchlists are stored locally on your device. They are not synchronized to a cloud account, because RiskCurrent has no user accounts.

• Watchlists are preserved during normal in-place app updates
• Uninstalling the app may remove watchlists along with other local data
• Clearing the app's storage through Android settings may also remove them

Reports are generated locally on your device and are shared only when you choose to share them, using the Android share sheet.

Once a report leaves the app, the recipient and any external application involved handle it under their own privacy practices. See the Privacy Policy for detail.

Once public distribution begins, update RiskCurrent through Google Play like any other app.

During testing, in-place updates preserve local data as long as the package identity and signing remain compatible. Installing a build with a different signing identity is treated by Android as a different app and will not carry your existing local data across.

Work through these in order:

• Restart the app
• Confirm the device has working internet access
• Confirm notification permissions are granted, if the issue involves alerts
• Confirm you are on the current RiskCurrent version

Before clearing anything: clearing the app's cache removes temporary files and is generally safe. Clearing the app's data or storage is different — it removes local application data, which may include your watchlists, settings, snapshots, and alert history. Use it only as a last resort.

RiskCurrent supports Android 7.0 (API 24) and newer.

On older releases the app will not install. If you are on a supported version and still cannot install, include your device model and Android version when you contact [email protected].