Data Corrections and Removal Requests
AppPriceData publishes dated public observations and can still be wrong, stale, duplicated, or missing context. We provide a direct correction process so problems can be reviewed against the underlying public source.
Last updated: August 19, 2026What you can report
- A stale or incorrect download price, availability status, ranking, or app metadata value.
- A public in-app purchase item that is mislabeled, duplicated, or no longer verifiable.
- A promotion or TestFlight record with an incorrect source, date, status, or association.
- A broken official-store or source link.
- A privacy, legal, or removal concern involving a page or submitted record.
What to include
Send the AppPriceData page URL, affected country or storefront when relevant, the value you believe is incorrect, and a public source that supports the correction. For privacy or removal requests, explain your relationship to the material and what action you are requesting.
How review works
We compare the report with the available public source, stored observation time, collection logs, and related records. Depending on the evidence, we may refresh the observation, correct metadata, mark a record unavailable, remove a submitted source, or leave the historical observation intact with its original date.
Historical observations are not automatically rewritten to match today's store value because that would destroy the record of what was observed at the time.
Privacy and removal requests
Requests involving personal information or content removal are reviewed separately from ordinary price corrections. We may ask for enough information to verify authority or identity before disclosing, changing, or removing material. We will also preserve records when retention is required for security, legal, or abuse-prevention reasons.
Send a correction
Use the AppPriceData contact page for corrections, source concerns, privacy requests, or removal requests. Providing a precise page URL and public evidence helps us review the issue efficiently.