App Store Privacy, IAP & Version History | Appalize

Extract App Store privacy labels, in-app purchase prices, subtitles, version history and rating histograms. Compare snapshots to detect metadata changes.

Quick start

{
  "apps": [
    "570060128"
  ],
  "countries": [
    "us"
  ],
  "maxItems": 10
}

What it collects

• The app's own subtitle and current metadata.
• Developer-declared privacy groups, purposes and data types, plus privacy-policy URL.
• Public in-app purchase names and display prices, including distinct prices with identical names.
• Public version history and release notes.
• Full numeric rating count and five-star histogram, where Apple exposes them.
• Related apps shown by Apple, when present.
• Reusable snapshots and field-level differences against a supplied baseline.

Monitor changes

Run once and save each result's snapshot object. On the next run, pass those objects in baselineSnapshots. Match by numeric appId and country. changeStatus is baseline-required, changed or unchanged; each change carries before/after values. Only fields present in the baseline are compared. There is no automatic cross-run baseline storage. Use your workflow or data warehouse to pass the previous snapshots when scheduling.

Data limits

IAP prices are public display strings; billing period, product IDs and subscriber eligibility are not inferred. Apple may show only a subset. Privacy labels are developer declarations, not an independent assessment. not-observed does not mean no data collection or no purchases. Version history covers what the current page exposes, not every historical release. Page metadata is requested in English; the country selects the storefront. A changed Apple page structure fails the unit instead of fabricating empty fields.

Output, automation and cost control

Results are stored in the default dataset; use JSON to preserve nested arrays, or export CSV/Excel through Apify. RUN-SUMMARY contains counts and source failures. Each row has source and collection time. maxItems caps reports/snapshots, not nested reviews or cohort members. Checkpoints deduplicate resumed work; downstream consumers should also use recordId within a run because dataset/checkpoint writes are not atomic.

Use the Apify API, schedules, Make, n8n or MCP integration. No Appalize key, App Store Connect credentials or external LLM key is needed. Only Apple App Store is supported.

Pricing: $3 per 1,000 successful app/storefront snapshots, plus $0.00005 per Actor start (one event per GB, minimum one). Platform usage is included. Each result includes all nested data; failed units have no result charge. Use the live Pricing tab and maximum charge setting before running.

Built by Appalize. Report reproducible issues with a run ID and non-sensitive input in the Actor Issues tab.