Is AirTag location data admissible as proof?

It depends on the jurisdiction and on who is deciding, and nothing here is legal advice. In practice most disputes never reach a court: a claims desk settles them, and what moves a claims desk is a clear record with a known origin that has not been altered. A tag's route shows where a tag was, not what was in the box.

What is the question really asking?

Admissibility is not a property a file carries around with it. It is a decision a particular forum makes under its own rules about what it will let into the record in front of it. A CSV of coordinates is not admissible or inadmissible in the abstract, any more than a photograph is.

So the honest answer to "is AirTag data proof" is that it is a record, and records get weighed. Some readers weigh them under formal rules of evidence. Most weigh them by reading the email and deciding whether the person who sent it seems to be telling the truth.

This page describes the general shape of that question. It is not legal advice, it does not tell you what any court or tribunal will do, and if the amount at stake justifies it, the person to ask is someone qualified in your own jurisdiction.

Who is actually deciding your dispute?

Almost always: a claims adjuster, a moving company's dispute desk, an airline's baggage office, a retailer's support queue, sometimes a small claims process. Courtrooms are the rare end of the distribution, and planning your evidence around them is planning for the wrong reader.

• They work in email attachments and case files, not logins to live dashboards.
• They have no rules of evidence to apply, only an internal process and a queue.
• They spend minutes, not hours, and they read the covering note before the attachment.
• They check whether your account is internally consistent: whether the dates you assert match the dates in the file you attached.
• If they escalate it, somebody has to summarise your file to somebody else, which rewards a record that is easy to describe.

The realistic question is therefore not "would a judge admit this". It is "will the person reading this act on it", and that turns on clarity and candour far more than on format.

What gets asked about any record?

Formal and informal readers converge on roughly the same four questions. A court asks them in the language of rules; an adjuster asks them in the language of a raised eyebrow.

• Who generated this, and how? A record produced automatically by a system that was running anyway reads differently from one typed up afterwards.
• Can it be shown unaltered? Not proven cryptographically, just: is there an original, does it match, and has anything been cropped out.
• Was it made at the time? A log written while events happened carries more than a reconstruction from memory.
• What does it actually demonstrate? Every record has a narrow literal claim and a wider one people try to hang on it.

AirTag History's answer to the first three is plain enough: reports are polled every 5 minutes and saved with their timestamps whether or not anything ever goes wrong, and the export is a copy of those saved rows. We do not certify it, notarise it, or sign it. It is a record we produced from data we recorded for your own tags.

What does the data actually demonstrate?

One thing: that a tag reported from a set of coordinates at a set of times, as far as the Find My network saw it. Everything past that sentence is inference, and the inference is where disputes are won and lost.

• It does not show what was in the box. An AirTag reports its own position and nothing about its surroundings.
• It does not show that the tag stayed with the item. If somebody opened the carton, the tag's route stopped being the item's route, and nothing in the data flags the moment that happened.
• It does not show who moved anything, or why.
• It does not show condition. A tag that arrives says nothing about the mirror packed beside it.
• It shows nothing from before you connected. Apple keeps no readable location history to fetch afterwards, so that stretch does not exist anywhere.
• Silence is not absence. AirTags are not GPS, so a location exists only when a passing Apple device relays a sighting, so a quiet warehouse produces a gap rather than a fact.

Say the narrow version out loud when you submit. A reader who notices the tag-and-contents gap themselves will discount everything else you sent; one who reads you naming it first tends to treat the rest as honest.

Does the answer change by country and by forum?

Yes, in both directions. Rules on what a decision-maker may consider, how electronic records are treated, and whether someone has to speak to how a record was produced vary between jurisdictions, and within one jurisdiction they vary between a court, a small claims process, an ombudsman, and a company's internal complaints procedure.

We cannot tell you where yours lands. What we can tell you is what the record contains and how it was made, which is the part any of those readers will ask about first.

One thing does not vary: this is for things, not people. Tracking a person with a tag is prohibited by our acceptable-use policy regardless of where you are, and both iOS and Android ship unknown-tracker alerts that we support rather than work around. A record obtained that way is a worse problem than the dispute it was meant to settle.

How do you give a record its best chance?

1. Export the whole window that covers the dispute, from pickup to delivery, rather than cropping to the hours that suit you. Cropping is the first thing a sceptical reader looks for.
2. Keep the original export untouched. If you need to annotate, annotate a copy and say clearly which is which.
3. Send the human-readable PDF evidence report for the person, and the raw CSV underneath it for anyone who wants to check the rows.
4. State the timezone once and use the same one everywhere, including in your covering email.
5. Point at specific rows with times, rather than attaching a file and writing "see attached".
6. Name the gaps in coverage yourself, including the long quiet stretch inside a warehouse.
7. Export while your tracking window is active so you have a standalone copy ready to attach.

None of that makes a record admissible. It makes it legible and hard to dismiss, which is the part you control.