Does a phone keep a history of the tags it has read?
Not at system level, on either platform. There is no list you can consult of tags a phone has read. That is a privacy property and a diagnostic problem at once, and it is why a reading tool that keeps its own log earns its place on a working phone.
There is no system log
Neither platform presents a history of tags read. There is no equivalent of a call log or a browser history for taps.
What you may find are traces of the consequences: a page in the browser history, a contact added, an application that was opened.
Those are records of what happened afterwards rather than of the tag, and they are incomplete. A tag that was read and produced nothing leaves nothing at all.
The privacy side
A phone that logged every tag it passed would be building a record of where its owner had been, since tags are fixed to places.
Not keeping that record is the right default, and it is consistent with the way both platforms treat proximity as something that should not accumulate silently.
It also means nobody with the phone in hand can reconstruct where it has been from its tag activity, which is a meaningful property for a device that goes everywhere.
The diagnostic problem
The same absence makes support harder. When someone says a tag did not work, there is nothing to consult.
You cannot establish whether the tag was read at all, which is the first question any diagnosis needs. Detection and action are separate steps, and without a record you cannot tell which one failed.
So every investigation starts by reproducing the problem rather than by examining evidence, which is slower and depends on the fault being reproducible.
For a deployment, this is an argument for server side visibility: if the tag points at an address you control, your server knows a tap arrived even though the phone did not keep the record.
Keeping your own record
Use a reading tool that keeps a history. It turns each read into something you can go back to, which is what makes production work reviewable.
Record what you wrote and to which tag, at the time you wrote it. A written record of the batch is worth more than any phone log afterwards.
Keep one reference tag per batch, labelled, so a suspect tag can be compared against a known good one.
And where a deployment matters, put the tags behind an address you control. That single choice gives you the visibility the phone deliberately does not provide.
Frequently asked questions
Can I see which tags my phone has read?
Not at system level on either platform. You may find traces of the consequences, such as a page in the browser history.
Does an app keep a history?
Some reading tools do, which is exactly why they are worth using for production work. That log belongs to the application rather than the system.
Can someone tell where I have been from my phone's NFC?
There is no system record of tags read, so there is nothing of that kind to reconstruct.
How do I prove a tag was read?
From your side rather than the phone's. A tag pointing at an address you control means your server sees the tap.