CoinETFCoinETF website

CoinETF · Android app

CoinETF Android app — privacy details

Operator: CoinETF. Contact: contact@coinetf.net

What the app does

CoinETF displays market data, reference ETF estimates, charts and an on-device portfolio calculator. It does not execute trades, hold funds or require a CoinETF user account. Estimates are not guaranteed execution or opening prices. This notice covers the native app; an external website or share recipient applies its own policy.

The sections below explain target-price alert slots, optional rewarded ads and server purchase rechecks that maintain purchased access. Reading this notice or installing the app does not automatically request price alerts or rewarded ads. Ad availability and notification receipt depend on the app version, service connection, Google services and your device.

1. Market requests and local storage

The app requests public prices/charts from CoinETF's shared HTTPS service and saves bounded copies in its private cache. Requests include the selected public instrument and interval. Hosting/CDN services process connection information such as IP address and request time to deliver and protect the service. Necessary request/security processing and the evaluation/delivery of alerts you request remain separate from the usage-analytics setting. Actual connection logging depends on enabled infrastructure settings. Provider API secrets are not supplied to your phone.

Watchlist, display choices and portfolio purchase amounts/quantities/FX information are stored in the app's private device storage. Portfolio values and calculator inputs are not uploaded to CoinETF, Firebase Analytics or advertising. App backup is disabled. Delete individual holdings or clear local data in Settings. Uninstalling removes the app's private files; a market cache is not a cloud backup of your portfolio.

2. Optional price notifications

Turning on price notifications initiates Firebase/FCM delivery setup and an authenticated connection to CoinETF's notification service. It uses an internal installation/delivery identifier, installation-specific authentication capability, language/time zone and the conditions you choose (instrument, target direction/value or surge threshold/scope). These are needed to evaluate and deliver your requested alerts; they are separate from optional usage analytics. Authentication material is protected on the device and never added to analytics events.

Pausing notifications keeps saved conditions. Use Settings → Delete saved notification data to request deletion of this installation's notification conditions and delivery settings. The app confirms server deletion before claiming completion. Revoking Android permission or uninstalling cannot immediately tell the server to erase records. The service has a 90-day inactivity cleanup rule for notification installations; removal occurs when cleanup runs. Finished ordinary delivery-job records have a 30-day cleanup rule. Current surge deduplication records can remain for the current activation; older finished generations are eligible after 30 days. Shared market observations used for 12-hour surge comparison cover a bounded history of approximately 48 hours. These rules do not promise an unverified provider-log or backup deletion deadline.

One active target-price alert is free. Each rewarded ad completion verified by the server adds one slot for 14 days, up to five slots in total. Verified ad-removal owners can use up to five without watching ads or a 14-day reward expiry. Saved OFF and completed conditions are separate from the active allowance. If slot expiry reduces the allowance, the server turns excess conditions OFF while keeping their saved targets; obtaining another slot does not automatically turn them back on.

3. App verification and security

Protected production requests use Firebase App Check with Google Play Integrity to help reject requests from unauthorized apps. Google/Firebase may process app/device verification information and issue short-lived attestation tokens. This is a service-security check, not account login or permission to access another installation's data. Service authentication, rate limits and necessary security handling are independent of usage analytics and advertising choices. No precise location, contacts, microphone or camera access is requested by the current app.

4. Optional usage analytics

The usage-analytics preference is on by default and can be turned off in Settings, but this default or an older ON setting is not treated as prior consent. Open App information & privacy → Statistics & data to see the actual collection status, change your choice or withdraw consent. Prices, portfolio and price notifications remain available without allowing analytics.

Without valid prior consent, actual Firebase Analytics collection stays off until the CoinETF service verifies the request country. The service uses the country supplied by Cloudflare for the request, not your phone language, time zone or chosen currency. This check requires neither an account nor price-notification registration. For requests verified as United States, the usage preference applies; outside the United States, including the EEA, United Kingdom, Switzerland and South Korea, collection requires your prior affirmative choice. An unknown or invalid country determination does not enable collection from the default ON preference alone. A valid affirmative choice for the current notice version can allow collection within that permission even before the country check completes. This conservative product rule does not replace any applicable US consent requirement or claim to satisfy every region's laws.

An existing refusal or OFF setting is preserved across updates, restarts and local-data deletion. You can explicitly allow analytics again in Settings. Necessary choice evidence, such as the notice version, is stored on the device and evaluated separately from the product's default ON preference. Necessary service-request, security, requested notification and purchase-verification processing remain independent of analytics.

When collection is actually allowed, Google Firebase Analytics processes predefined screen/feature events, success/failure codes, coarse duration ranges and SDK app-instance/session, app-version and device information. Examples include chart/interval use, favorites, filters, manual refresh, alert setup, portfolio save/calculation success and image-share preparation. Search text, exact holdings, entered amounts, target values, notification identifiers, tokens, emails and credentials are excluded from custom events. A share preparation event does not prove a recipient received the image. These are limited pseudonymous app measurements, not exact people or live-connection counts.

The Analytics SDK uses app-instance identifiers and session/device information, and may derive an approximate country/city from masked IP information. This does not require GPS or precise-location permission. Omitting raw IP from the app's custom events does not mean Google never processes IP during communication. Google describes discarding GA4 IP addresses after deriving location and before logging. Retention of the derived region, events and app-instance identifier is separate; this is not an immediate-deletion promise for other services' connection logs.

Collection is bounded; events may be dropped or delayed. Turning analytics off or withdrawing consent blocks new events, disables SDK collection and attempts to reset pending local SDK analytics data. Actions taken while refused or the country is unverified are not separately queued for retrospective upload after a later allowance. Local-data deletion preserves the analytics setting and does not erase previously uploaded records remotely. Contact the operator for an applicable deletion request. The verified GA4 property uses two-month event retention, fourteen-month user retention and retention reset on new activity. These are not a single deletion deadline for every aggregate, provider log or backup; actual retention, access and deletion depend on the applicable service settings. Google advertising storage, ad personalization and ad-user-data consent are denied by the usage-analytics integration. The default preference, allowance and withdrawal of usage analytics are separate from advertising consent.

5. Advertising

The normal production app supports banner and in-list native ads, frequency-limited interstitials at completed-task boundaries, and explicitly chosen rewarded ads for alert slots. Interstitials do not appear immediately on app entry; they are limited to completed work such as reviewing a chart or calculation. Actual ad availability depends on the app version, service connection and Google's ad supply; playback and revenue are not guaranteed. QA and license-test configurations remain separate from live ads; a separately allowed private QA flow may use official Google test ads. Google Mobile Ads and the User Messaging Platform are used. UMP checks applicable advertising/privacy choices before ad requests, and an Ad privacy options entry is available in Settings where required. The app must not request ads while ad-removal ownership is unresolved or verified active. A rewarded ad is requested only after you review the reward terms and explicitly choose it. The free slot, prices and portfolio remain available without watching an ad.

When an ad is requested, Google may process the SDK's disclosed advertising, device, app and connection data under its policies and the choices applicable to you. Portfolio and alert input values are not supplied as targeting fields. Do not assume the website's AdSense choice also controls the native app.

Rewards use signed Google AdMob server-side verification (SSV); an SDK completion alone does not grant a slot. CoinETF sends a short-lived pseudonymous confirmation value as ad custom_data. It does not put names, emails, phone numbers, installation UUIDs, target prices or holdings in that field, and does not set an AdMob user ID. Because CoinETF can relate the value to an installation's reward request, it is not described as anonymous. The server checks Google's signature, transaction identifier, ad unit, reward type/amount and timestamps. Original confirmation values and transaction identifiers are processed transiently for validation; server records retain hashes and verification outcomes. Infrastructure request logging follows its separate configuration, so this is not an immediate-deletion promise for every provider log.

A reward challenge is valid for 30 minutes. Records contain its identifier, confirmation-value hash, installation linkage, status and timestamps; transaction hashes and outcomes prevent duplicate grants. Challenges and their related transaction records become eligible for cleanup 30 days after the challenge expiry time. Slot records are limited to four extra slots per installation and contain expiry/grant times and a transaction hash. Expired slot rows may remain until replacement or notification-installation deletion/inactivity cleanup. Confirmed deletion of saved notification data also removes that installation's challenges, reward transaction records, slots and billing-installation linkage. It does not delete separate Google Play purchase records or request a refund.

6. Google Play and lifetime ad removal

The one-time lifetime ad-removal product can be purchased through Google Play, and existing purchases can be verified and restored. The app queries actual localized product prices and owned purchases from Google Play. A new purchase proceeds when you review the account, price and terms in the Google Play checkout screen and explicitly confirm payment; reading this notice or installing/opening the app alone does not charge you. Restoration checks an existing purchase and does not initiate a new payment. Pending or unverified payment is not presented as completed. Separately authorized license tests are distinct from ordinary purchases and do not automatically make purchases free for every Google account. Testers must confirm the test-payment method and no-charge indication shown by Google Play.

Using purchase or restore verification sends the purchase token through protected CoinETF HTTPS processing with an independent billing installation identity. The server checks purchase and acknowledgement status with Google Play. Necessary verification/restoration still occurs when usage analytics is OFF; purchase verification itself does not require FCM registration. Server records contain a token hash, independent installation authentication hash/linkage, entitlement status, verification time and expiry. To apply five alert slots, the server checks both the separate billing installation proof and notification installation proof and links them. A local ad-free flag alone never grants that capacity. This integration does not newly enable an Analytics link for automatic Play purchase reporting.

In the background purchase-recheck configuration that maintains purchased alert access, a purchase token verified as active by Google is encrypted using a dedicated, separate server-only AES-GCM key and retained in the dedicated server database (D1). The purpose is to recheck purchased alert access while the app is closed. The decryption key stays in server secret storage, outside APKs, website source, analytics and ordinary reports. Raw tokens are processed only transiently during Google verification and encryption/decryption, not retained in plaintext database fields, application logs, the device entitlement cache or custom Analytics events. A configuration with this feature OFF does not newly begin encrypted-token retention.

During healthy operation, the server rechecks linked purchases with Google approximately every four hours. A verified entitlement has a maximum six-hour validity; errors do not extend it. Bounded batch sizes and request budgets may delay retries. Prolonged verification failure or a confirmed refund/cancellation can restrict extra alert slots and turn excess conditions OFF. Restoring connectivity does not automatically turn those OFF conditions back on. Six hours is a technical purchase-reverification window, not a purchase expiry or the 14-day reward period.

Only verified, acknowledged ownership grants app ad removal. A Keystore-protected device lease has a maximum six-hour validity and is refreshed on verification/restore. Invalid or expired cache cannot create ownership; refund/cancellation status is reflected when checked again with Google. Inactive billing installations become eligible for cleanup after 180 days, and old unreferenced purchase hashes use a 180-day cleanup rule; referenced records and actual cleanup timing can retain records longer. There is no promise of an immediate billing-record deletion button or immediate processing of every refund. Contact the operator about purchase-record questions or deletion requests. Uninstalling does not itself cancel/refund a Play purchase or immediately erase server records.

Encrypted tokens are removed when Google verification confirms an inactive/refunded purchase, and are deleted with unreferenced purchase records when those records are pruned. An active linked purchase being rechecked has no separate fixed calendar retention deadline; its record supports continued purchased access and duplicate verification. Deleting notification data removes its notification linkage and stops background checks performed solely for that linkage, but does not immediately erase the independent billing record or encrypted token. Unlinked records remain subject to the existing 180-day cleanup conditions based on references and verification timestamps. Maintenance runs on the configured operational schedule, and does not promise that provider logs/backups disappear at the same time.

7. Saving images, sharing, providers and your choices

Chart/watchlist PNG images are generated locally. When you choose Save image, Android 10 (API 29) and later save to the gallery under Pictures/CoinETF. Android 7–9 (API 24–28) use the system document picker to save to a location you choose. This does not request broad storage access or permission to read your entire photo library.

Share image is a separate action that grants temporary read access to the destination you select in Android's share sheet. Temporary generated cache files are pruned on later image activity, separately from exported copies. Clearing local app data, uninstalling or pruning the cache does not remove copies already saved to the gallery, a selected document location or a recipient app. You or the destination app/document provider control deletion of those copies. A cloud document location may process the image under that provider's policy. Images are not automatically uploaded to CoinETF's server, and no clipboard or share-recipient content is read for analytics.

Service providers include CoinETF hosting/Cloudflare, Google Firebase/FCM/App Check, Google Play, and Google Mobile Ads/UMP where activated. Their infrastructure may process data outside your country under their terms. Operator access is limited to authorized operations and analysis; no administrator credential is embedded in the app. Exact infrastructure log/backup fields and retention depend on enabled service settings.

Contact contact@coinetf.net for privacy questions or requests. Do not email passwords, API secrets or full purchase tokens. If an installation must be matched for a deletion request, the operator should provide a secure, limited identification method. A device-data reset, notification-server deletion, analytics-provider deletion and Play refund are different operations; one must not be presented as automatically completing all the others.

Google provider information:

https://firebase.google.com/support/privacy

https://firebase.google.com/docs/android/play-data-disclosure

https://support.google.com/analytics/answer/11582702

https://support.google.com/analytics/answer/11598602

https://policies.google.com/technologies/partner-sites

https://developers.google.com/admob/android/privacy/play-data-disclosure

https://developers.google.com/admob/android/ssv

https://policies.google.com/privacy

This notice describes implemented and explicitly marked prepared features. It is not a claim that a technical audit satisfies every country's legal obligations. Changes to active processing must be reflected in this notice and the app's store disclosures before release of those changes.

App analytics, choice evidence, retention and processing

The following settings apply to app usage analytics and choice evidence as of 22 October 2026. Unless stated otherwise, they do not describe retention across other Google services, connection logs, backups or all CoinETF server records.

  • Preference and actual collection: Default ON is not consent. Without valid prior permission, collection stays off until the country check. Verified United States requests use the saved preference; other countries require prior permission. Refusal prevails, and an unknown country does not enable default collection.
  • Change or withdraw your choice: Open Settings → App information & privacy → Statistics & data to see the actual status and change it. Prices, portfolio and requested alerts remain available if you decline.
  • Connection-country check: Only the country Cloudflare supplies for the request connection is used. VPNs and proxies may affect it; it does not establish citizenship, residence or precise location. This check does not retain a separate country history or raw IP address.
  • On-device choice evidence: The choice, notice version, device-clock selection time, app version and fixed UI source are stored. Country and IP are not stored in this record; local-data deletion does not turn the original refusal or choice into new consent.
  • Service operational metrics: Existing Cloudflare request, execution-failure, CPU/time metrics and protected operational-status reads are used. No new per-request D1 metrics storage or user tracking is added. Operational totals may include QA/test requests and are not people counts.
  • Event data retention: 2 months
  • User data retention: 14 months
  • Reset retention on new activity: On
  • Granular city-level location and device setting: On. This is not GPS or precise-location permission.
  • Google Signals / user-provided data: Signals not enabled / user-provided data not configured
  • App analytics advertising storage, ad-user-data and ad-personalization consent: All denied (DENIED)

Event retention and user retention are separate settings. Reset on new activity can affect the user-retention window. These periods do not promise immediate deletion of every aggregate report or previously transmitted record.

Usage analytics and advertising choices are separate. The app analytics integration denies advertising storage, ad-user-data and ad-personalization consent. Default-on usage analytics is not advertising consent. Current advertising and purchase feature states are described in the relevant sections above.

contact@coinetf.net