RiskCurrent Privacy Policy

RiskCurrent is developed and published by Wolfpack Byte, a division of Crème Mind AI. The Android package identifier is com.wolfpackbyte.riskcurrent. References to “we,” “us,” and “our” in this policy mean Wolfpack Byte acting as the operator of RiskCurrent.

This policy covers the RiskCurrent website and the RiskCurrent Android application.

The RiskCurrent Android application does not collect:

• Account registration details — the app has no user accounts and no sign-in
• Your name, email address, or profile information
• Your contacts or address book
• Precise location data
• User-created public content — the app has no public posting or social features

Advertising and subscription components are addressed in the Advertising and RiskCurrent Pro and subscriptions sections below.

The Free version of RiskCurrent may display limited banner advertising on certain app screens, including Overview, Metrics, History, and Watchlist. RiskCurrent does not use interstitial, rewarded, app-open, or popup advertising formats.

Advertising is delivered using Google Mobile Ads (AdMob). To deliver, measure, secure, and — where permitted — personalize advertising, Google Mobile Ads may process information such as:

• Device or app identifiers
• IP address and network information
• Ad interaction information
• Diagnostic information
• Coarse device and app information

RiskCurrent itself does not receive Google's complete advertising profile. For more information, see Google's Privacy Policy and Google AdMob's data practices.

Advertising is suppressed in the following circumstances:

• RiskCurrent Pro — advertising is not shown to verified Pro subscribers
• Unknown or unavailable entitlement — if subscription status cannot be verified, advertising is suppressed rather than shown by default

RiskCurrent includes Google User Messaging Platform (UMP) consent infrastructure. Where required by applicable law, RiskCurrent may request advertising or privacy consent before initializing or requesting advertising services.

Consent requests are determined by applicable legal requirements and may not appear in all regions. Consent is not required in every jurisdiction.

RiskCurrent Pro is a paid subscription tier that removes advertising and unlocks additional functionality. Subscriptions are offered and processed through Google Play.

RiskCurrent uses RevenueCat to support subscription entitlement verification. RevenueCat may process information to determine subscription and purchase status, including:

• App user or device-linked identifiers used to associate entitlement state
• Product and subscription identifiers
• Purchase, restoration, and transaction metadata supplied by the app store

RevenueCat does not process your full payment-card number, and RiskCurrent does not directly handle payment-card details. For more information, see RevenueCat's Privacy Policy.

Android subscription purchases are processed by Google Play. RiskCurrent does not receive or store your full payment-card details. Subscription and transaction status may be available to RiskCurrent through Google Play and RevenueCat.

You can manage or cancel your RiskCurrent Pro subscription at any time through Google Play. On Android, this is accessible via the Google Play app under subscriptions, or through your Google account subscription management settings.

RiskCurrent keeps your working data on your Android device rather than in a user account on our servers. This includes:

• Watchlists
• Preferences and settings
• Metric readings retrieved by the app
• Snapshots
• Alert history
• Report configuration
• Reports generated on the device

Because this data lives on the device, uninstalling RiskCurrent may remove local application data. Clearing the app's storage through Android settings may also remove it.

Android backup is currently enabled for RiskCurrent. Depending on your Android and Google account backup settings, application data may be included in device backups handled by the platform.

Backup behavior is controlled in part by your device and your Google account settings rather than solely by RiskCurrent. You can review and change backup settings through your Android system settings.

The app contacts the RiskCurrent backend over HTTPS to retrieve metric data. As with any ordinary internet request, technical information such as your IP address, the time of the request, and basic request metadata may be processed as part of delivering the response.

We do not use this information to build a profile of you, and the app does not send an account identifier, because there are no accounts. Where server log retention is concerned, we describe only what we can confirm; this policy will be updated if retention practices are formalized or changed.

Metric data originates from third-party data sources and is retrieved through the RiskCurrent backend rather than directly by your device.

• Provider credentials remain server-side and are not included in the mobile application
• Your device identity is not intentionally transmitted to market-data providers
• Providers receive requests from our backend, not from your device

Notifications are controlled through Android notification permissions and RiskCurrent's in-app settings. Notification content may appear on your lock screen depending on your device settings.

Notification delivery depends on the device, the operating system, and app refresh behavior, and is not guaranteed. RiskCurrent is not an emergency alerting service and should not be relied on for time-critical warnings.

Reports are generated locally on your device. Sharing happens only when you choose to share, using the Android share sheet.

Once you share a report, the receiving application or service handles that content under its own privacy practices, which we do not control.

The RiskCurrent website does not collect email addresses. There is no waitlist form, signup form, or other personal-data form on this site.

The website is served through Cloudflare, and uses Cloudflare's web analytics (Cloudflare Web Analytics / Insights) to measure aggregate traffic. To do so, Cloudflare may process ordinary technical information — such as IP or network data, request details, and browser type — as part of delivering, protecting, and measuring the site.

• Website analytics is used for aggregate traffic measurement, not to build advertising profiles
• The website itself carries no advertising SDK and displays no ads
• The website does not set cookies for advertising or cross-site tracking

The live values shown in the metric explorer are fetched directly from the RiskCurrent metrics API. That request is made from your browser to the API, which processes it as an ordinary HTTPS request.

The website and app may link to external sites and services. Those destinations operate under their own privacy policies, and this policy does not apply to them.

Communication between the app and the RiskCurrent backend uses HTTPS. Provider credentials are kept server-side, separated from the mobile application.

We apply reasonable safeguards appropriate to a product that does not hold user accounts or personal profiles. No method of transmission or storage can be guaranteed to be completely secure.

Local application data remains on your device until you clear it, reset the app, or uninstall RiskCurrent.

Reports you have shared are retained by whatever destination you sent them to, under that service's practices. We do not state backend retention periods that we have not confirmed; this section will be updated as those practices are documented.

RiskCurrent is not directed to children under 13, and we do not knowingly collect personal information from children. If you believe a child has provided personal information to us, contact us at the address below.

We may update this Privacy Policy from time to time. Updates will be posted on this page with a revised “Last updated” date. Material changes to how information is handled will be reflected here before they take effect where practical.

Questions about this Privacy Policy or how information is handled can be sent to:

[email protected]

For product help, see the support page. For general inquiries, see the contact page.