How AppPriceData collects and compares app prices.

Coverage

Records separate an app's download price from publicly visible in-app purchases. Country pages preserve the observed local amount, currency, storefront, and update time rather than replacing the source price with a converted estimate.

• App identity, developer, category, icon, and official store link
• Country-specific download price and availability
• Publicly visible in-app purchase names and prices
• Regional observations, rankings, promotions, and update dates
• Public TestFlight invitation status and validation time

Public sources

Apple app identity and download prices come from Apple's public catalog and Search/Lookup services. Public in-app purchase items are collected from information exposed on App Store product pages. The related-app rail follows Apple's public customers-also-bought list for the selected storefront, with a labeled local fallback only when that list is unavailable. Overall and category rankings come from Apple's public chart feeds. iOS, iPadOS, and macOS rankings are stored separately and refreshed as independent daily snapshots.

Google Play app metadata, download prices, and ranked collections are observed from public Google Play pages using country-specific parameters. AppPriceData does not claim access to private developer account data for third-party apps.

Limited-time promotions and TestFlight links can originate from public community sources. A promotion keeps its source link and publication time; TestFlight links are checked against Apple's invitation page before they are shown as active.

Collection and update timing

Public pages show the latest stored observation available to AppPriceData. Automated jobs refresh iOS rankings, promotions, TestFlight invitations, selected Google Play records, and reference exchange rates. iPadOS and macOS rankings refresh on first access each UTC day unless they are added to the configured daily platform list. Apple app metadata and regional download prices are collected when regional data is missing; afterward, one explicit user update can start a new regional collection when the app is outside its 6-hour refresh cooldown. Normal page visits reuse stored data. Public in-app purchases are collected on first need and are refreshed afterward only by an explicit in-app-purchase update.

Currency conversion and regional comparison

Local store prices remain the source record. Cross-country comparison views add a dated reference conversion using the configured ECB and exchange-rate feeds. Converted values are informational and can differ from card settlement, taxes, or the final store checkout.

1. Preserve the original local amount and currency.
2. Attach the storefront and observation timestamp.
3. Convert compared values with one dated rate snapshot.
4. Keep uncertain product matches separate rather than merging them.

Known limitations

• Public in-app purchase lists can be incomplete.
• Availability, taxes, and checkout eligibility can vary by account.
• Google Play public pages do not expose every private product or offer detail.
• Rankings are dated snapshots and may change between collections.
• Promotions and TestFlight capacity can end without advance notice.
• Store pages and parsers can change, causing temporary gaps or stale records.

Corrections and verification

Each price page links to the corresponding official store listing so readers can verify the current value. Corrections, stale records, and source concerns can be reported to [email protected].