Every factual correction published on proudtek.com, with the original text and the change

Corrections Log

ProudTek corrections log: transparency commitment

Quick answer

This page is the single public record of every correction we have issued on proudtek.com. Any time an article previously contained a factually wrong statement (a wrong number, a wrong standard identifier, a wrong chip family, a wrong regulatory date) the original statement, the corrected statement, and the date of the correction are logged here. Pages that carry a substantive correction are stamped with a banner at the top of the article and a link to this log. Typos, clarifications, and additions that do not change any factual claim are made silently under the rules at /about/editorial-policy/ and are not listed here.

  • We do not edit history silently. Any change to a factual claim appears here with the original text and the change.
  • Corrections are opened by readers, reviewers, or the editorial board; anyone can request one via editors@proudtek.com.
  • We respond to a correction request within 5 business days with either a correction or a written justification for keeping the original.
  • A retracted article is not deleted; it is replaced with a notice that explains why it was retracted and links to the superseding content.
10+ Years ISO 9001 500+ Clients 50+ Countries
  1. 2008 Founded — 18 yrs continuous operation
  2. 40+ Countries shipped to
  3. 6 Product families in-house
  4. 100% Functional read-test on every encoded unit
Chip vendors supported
  • NXP
  • Infineon
  • Impinj
  • Alien
  • EM Micro
  • Quanray
Compliance shipped with every order
  • ISO 9001:2015
  • RoHS 2011/65/EU
  • REACH SVHC
  • FCC Part 15 / 18
  • CE EN 300 330

At a glance

Use these short answers to decide whether this page matches the project before moving into the detail.

Key takeaway

We do not edit history silently. Any change to a factual claim appears here with the original text and the change.

How to request a correction

The process is deliberately simple so readers who spot an error actually send it in.

How to request a correction

The process is deliberately simple so readers who spot an error actually send it in.

  • Email editors@proudtek.com with the article URL and the specific claim you believe is wrong.
  • Attach or link a primary source (standards document, OEM datasheet, regulatory announcement) that contradicts the claim.
  • If you would like to be credited by name in the log, say so explicitly; we default to 'external reader' when the submitter has not opted in.
  • We acknowledge within 2 business days and resolve within 5 business days; exceptions (e.g. requires reproducing a lab test) are communicated with an ETA.

How corrections are classified

Not every change is a correction, and not every correction is a retraction. Three categories are used consistently on this log.

Silent update (not logged)

  • Typo, broken link, image filename updated.
  • Clarifying rewrite that does not change any factual claim.
  • Adding an entirely new section that does not contradict anything earlier.

Logged correction or retraction

  • Any number, date, standard identifier, chip name, regulatory deadline that was wrong when published.
  • Any attribution of test data to a lab or a standards body that turns out to be incorrect.
  • Any claim that had to be rewritten because the original was not defensible against its cited source. A full retraction of the original claim is logged even if the replacement is itself correct.

Correction banner rules

Once a correction is logged here, the corrected article receives a banner.

  • The banner stays at the top of the article for 90 days after the correction date.
  • After 90 days, the banner is removed but the correction remains logged here indefinitely.
  • Retracted articles keep the banner permanently; the page itself may be replaced with a redirect to the superseding content after 12 months.
  • modifiedAt on the JSON is updated; publishedAt is never changed.

Correction log

The list below is the authoritative record. When a correction is live the section grows; when no corrections have been issued in a quarter, the placeholder row below stays in place as an honest indicator.

Date Article Original claim Corrected claim Submitter / source
No corrections have been issued since this log was opened on 2026-04-17.

Useful next pages

Use these linked product, guide and comparison pages to keep the next click specific and practical.

Editorial standards

The sourcing and review rules that make corrections rare.

Testing methodology

How lab-measured numbers are produced. So we can verify whether a challenge is valid.

Who signs articles

The author and review-board pages that explain who is accountable for each byline.

FAQ

Why keep the original wrong text in the log?

Because 'fixed silently' is indistinguishable from 'never happened', and an editorial system without visible error has either never been challenged or is hiding its errors. Publishing the original text keeps us honest and keeps our sources verifiable by anyone who read the earlier version.

Do you ever remove a correction from the log?

No. A correction entry is permanent. The only exception is if the correction itself was wrong. In which case we add a new row that supersedes the earlier row, but neither row is deleted.

What counts as a 'primary source' when challenging a claim?

The issuing authority's own document: ISO / IEC / GS1 / NFC Forum / EPCglobal for standards; the chip manufacturer (NXP, Impinj, Alien, STMicro, Infineon, Samsung) for chip specs; the regulator (FCC, ETSI, EU Commission) for compliance claims; a peer-reviewed journal for academic claims. A secondary summary (even from a respected trade publication) is not sufficient to force a correction, though it can start a review.

Can I request an anonymous correction?

Yes. Submit via editors@proudtek.com and say you would like to be anonymous; the correction will log 'external reader' as the submitter and we will not share your identity.

10+ Years RFID Manufacturing
ISO 9001 Certified Factory
500+ Enterprise Clients
50+ Countries Served

Proud Tek is a Shenzhen-based RFID & NFC manufacturer supplying hotel chains, transit operators, event venues and retail brands worldwide. Every order includes free samples, RF testing and dedicated project support.

Get a Quick Quote

Tell us about your project and we'll respond within one business day. Fields marked (asterisk) are required.

We'll only use this to reply to your inquiry.
Optional, but helps us route your inquiry faster.
e.g. 5,000 pcs
e.g. hotel, event, asset tracking
Chip preference, timeline, special requirements...

Next step

Ready to discuss your project?

Use the contact route when you are ready for pricing, samples, or compatibility help, or continue into the linked product and comparison pages below.