Corrections Policy
Our Commitment to Factual Accuracy
At Mobile Phn, we are committed to providing the most reliable, comprehensive, and up-to-date consumer device reference on the web. Despite our rigorous verification protocols, the fast-moving nature of smartphone releases means that specification errors, omissions, or outdated pricing may occasionally occur.
When an error is discovered, our policy is to investigate and correct it promptly, transparently, and thoroughly.
How We Handle Corrections
- Typographical & Specification Errors: Typographical errors, incorrect sensor details, wrong battery figures, or misstated dimensions are corrected directly in the database as soon as verified.
- Substantive Editorial Revisions: When a major factual error occurs in an article or editorial review, we correct the text and append a visible editorial note stating the date of the correction and the nature of the update.
- Historical Integrity: We do not silently rewrite articles or reviews to alter our published historical perspective without clear justification or updated firmware re-testing disclosures.
How Readers Can Report an Error
We welcome and appreciate feedback from our readers, industry researchers, and device manufacturers. If you spot a factual inaccuracy, please follow these steps to submit a correction request:
- Provide the URL: Include the exact link to the device datasheet or article page on Mobile Phn.
- Specify the Inaccuracy: Clearly indicate which specification field or sentence is in error.
- Provide Verifiable Sourcing: To maintain database integrity, all correction requests must include a reference to a credible primary source—such as an official manufacturer whitepaper, user manual, regulatory agency filing (FCC, TENAA, BIS), or an official press release.
Submitting Your Correction:
- Submit via our web form: Contact Us Page
- Or send an email directly to: support@mobilephn.com with the subject line:
[Correction Request] - [Device or Article Name]
Verification Timelines
Our editorial team reviews incoming correction requests within 24 to 48 business hours. Once verified against official documentation, the database is updated immediately, and the revision timestamp is logged.