Fargo, West Fargo & Cass CountyCriminal defense informationCall 701-929-4886
Fargo and North Dakota criminal defense guide

Metadata and File History in North Dakota Criminal Cases

Metadata is information about a file, record, communication, or system event. It can help answer when an item was created, modified, transmitted…

ElementsPenaltiesEvidenceNext steps

File dates, EXIF, GPS tags, document properties, application databases, server logs, cloud versions, hashes, time zones, copying effects, forensic extraction, authentication, experts, and trial exhibits

Metadata and File History in North Dakota Criminal Cases

Metadata is information about a file, record, communication, or system event. It can help answer when an item was created, modified, transmitted, uploaded, opened, or copied—but only if the lawyer understands which system generated the field and what that field actually means. A “created” date may record a later copy. A photo’s location may be user supplied or stripped by a platform. A document author field may be inherited from a template. Metadata can be powerful evidence, but it is not self-interpreting and rarely identifies a human actor without corroboration.

A timestamp needs a source, clock, event definition, and time zone. Demand the native file or database, acquisition logs, field definitions, clock settings, conversion rules, software versions, hash values, and complete event history before accepting a forensic timeline.

“Metadata” describes many different records, not one kind of proof

File-system metadata describes storage events

A file system may record creation, modification, access, status-change, allocation, deletion, ownership, permissions, and directory information. The available fields depend on the operating system and storage format. A file-system creation time often means the time that particular file instance was created on that volume, not when its intellectual content was first authored. Copying an old file onto a new device can produce a new creation time while preserving or changing other dates.

EXIF and media metadata can describe capture equipment and settings

Images may contain camera make, model, lens, exposure, orientation, capture time, software, thumbnails, and GPS coordinates. Video and audio containers can hold duration, codecs, creation labels, tracks, and location. Applications, editing tools, exports, and platforms may modify or remove these values. A field inside a media file is evidence to interpret, not a guarantee that the camera was at the stated place or that the displayed date is correct.

Document properties may be inherited or user controlled

Word-processing, spreadsheet, presentation, and PDF files may store author, company, title, creation and revision dates, editing time, comments, tracked changes, prior directory locations, printer information, templates, and application versions. Author fields can come from the software registration or template rather than the person typing. “Total editing time” may accumulate while a file is open or change during conversion. Native revision data is far more informative than a printed page.

Application metadata lives in databases and logs

Messaging, social, payment, navigation, photo, browser, and cloud applications store account identifiers, message IDs, database row numbers, status codes, upload records, synchronization tokens, cache entries, and event times. A forensic report translates those fields. Reliable interpretation may require the application version, database schema, log documentation, and testing, particularly when an automated parser assigns labels such as “sent,” “deleted,” or “location.”

Server and provider metadata reflects remote systems

A provider can record login times, IP addresses, device sessions, account changes, message routing, upload events, and access logs. Server clocks may be more stable than a user device, but the record still requires an event definition. A login event may reflect a saved session or background refresh. An IP address identifies a connection at a time and generally does not, by itself, identify the human who acted.

Cloud history may preserve versions and collaboration events

Cloud platforms may track file versions, uploads, downloads, shares, comments, account access, restore operations, and collaborator changes. A “modified by” label can mean the account credited with a system event, not necessarily the person who authored every change. Synchronization can propagate a local timestamp or create a new server timestamp. The provider’s field guide and audit-log scope should accompany the export.

Embedded and external metadata must be distinguished

Some metadata resides inside the file; other metadata belongs to a file-system entry, database, server, evidence platform, or forensic tool. Sending a file by email may preserve embedded EXIF while changing local file-system dates. Taking a screenshot preserves displayed content in a new image but usually does not carry the source page’s metadata. Counsel should identify exactly where each asserted fact resides.

A timestamp is meaningful only after its clock and event are identified

“Created,” “modified,” and “accessed” are system-specific labels

A creation field might record camera capture, document initialization, file copy, database insertion, server receipt, or extraction export. Modification may reflect content editing, metadata change, synchronization, conversion, or application cleanup. Access time may be disabled, delayed, rounded, or updated by antivirus and indexing. A witness should define the event rather than recite a report heading.

Device clocks can be wrong

Phones and computers commonly synchronize time, but users can change settings, devices can remain offline, batteries fail, virtual machines use different clocks, and embedded equipment may drift. A reliable analysis compares system time with trusted events such as network logs, photographs of a known clock, messages received by another device, or acquisition time. The examiner should document clock offset at seizure when possible.

UTC, local time, and daylight saving time can shift a chronology

Databases often store Coordinated Universal Time while interfaces display local time. Some fields store an offset; others rely on the viewing system. Daylight-saving transitions can create repeated or apparently missing hours. Travel across time zones adds another layer. Reports should state the original stored value, unit, conversion, applicable zone, and whether the software applied historical daylight-saving rules.

Epoch and unit errors can produce plausible but false dates

Systems count seconds, milliseconds, microseconds, or other intervals from different epoch dates. Using the wrong unit can yield nonsense; a smaller conversion error can yield a plausible wrong day. Some applications use proprietary or platform-specific formats. An examiner should validate decoded times against known records and disclose the conversion method rather than relying solely on a tool’s displayed column.

Precision does not equal accuracy

A timestamp displayed to six decimal places may come from a clock that was minutes wrong or an event recorded in batches. A rounded minute may still be accurate for its purpose. The witness should distinguish stored precision, clock accuracy, logging delay, synchronization delay, and uncertainty. A timeline graphic should not imply second-by-second certainty the data cannot support.

Later processing can overwrite time fields

Downloading, unzipping, restoring, scanning, converting, exporting, or opening a file can change file-system dates. Evidence collection should preserve original attributes where possible and document the acquisition method. If dates changed, native archives, server logs, database records, and forensic container metadata may preserve earlier values. The change itself does not prove tampering, but unexplained processing weakens confidence.

Timestamp conflicts should be investigated, not averaged

A file may contain EXIF capture time, file-system creation, document creation, server upload, message transmission, and evidence-acquisition dates. They may legitimately differ. The correct approach identifies what each event represents and reconstructs the sequence. Selecting the one date that fits a theory while ignoring contrary fields creates a completeness and reliability problem.

File history can reveal copying, editing, synchronization, and deletion

A hash shows file identity, not origin

A cryptographic hash can demonstrate that two files are byte-for-byte identical or that an evidence file has not changed since hashing. It does not establish who created the file, whether its content is true, where it existed earlier, or whether metadata was altered before the reference hash. The record should identify the algorithm, exact item hashed, time, and person or system performing the calculation.

Different hashes do not always mean different visible content

Two images can look identical yet have different hashes because metadata, compression, thumbnails, color profiles, or container structure differ. A platform may recompress a photo or video. Conversely, an edited image can be saved to mimic some visible features while differing elsewhere. Hash comparison should be combined with file structure, metadata, perceptual comparison, and provenance.

Version history may preserve earlier content

Documents and cloud files can retain revisions, tracked changes, autosaves, temporary files, or earlier synchronized copies. Version records can show when content changed and which account performed an event. They may not capture every keystroke or prove the person behind the account. Retention settings, manual history deletion, plan level, and provider export scope affect completeness.

Thumbnail and cache artifacts are secondary records

Operating systems and applications generate previews and cached copies. They can show that a device displayed or processed an image, even when the original is missing. A thumbnail may be resized, cropped, rotated, or stale and may lack the original name and time. Its presence does not necessarily establish intentional viewing, knowledge of content, or possession at the charged time.

Database journals can preserve superseded states

SQLite write-ahead logs, journals, freelist pages, and carved records may retain prior or deleted values. These artifacts can be important, but relational context may be incomplete. A recovered timestamp without a reliable row association should not be assigned to a message or user by assumption. The examiner should identify the artifact source and reconstruction method.

Deletion metadata does not always show a human deletion

A status may reflect user action, application cleanup, retention policy, synchronization, account removal, database migration, or parser interpretation. The alleged deletion time may be the time a row changed or the time a server processed a request. Proof of concealment requires evidence about mechanism, actor, knowledge, and timing—not merely a “deleted” label in a report.

Provenance is stronger when independent sources converge

A file’s history becomes more reliable when native metadata aligns with a device log, message attachment, cloud version, provider upload, recipient copy, and witness observation. Conflicts may expose clock errors, copying, editing, or incomplete collection. Corroboration should remain independent; several reports generated from one database are not several sources.

Forensic collection must preserve both content and context

A copy made for ordinary use may not preserve source attributes

Dragging files, emailing them, uploading them, or copying them through a phone interface can change names, times, metadata, and folder relationships. A forensic acquisition attempts to preserve source data and document integrity, but access limitations can restrict what is captured. The examiner should state whether the source was a physical device, file-system image, logical backup, cloud export, provider return, or user-supplied file.

Acquisition logs define the boundaries of the evidence

Logs should identify device, account, date, time, tool, version, connection method, credentials, errors, excluded areas, encryption, filters, and hash results. A successful status does not mean every application or remote account was collected. Failed and partial attempts matter because later reports may silently omit unsupported data.

Native files and databases should accompany reports

A PDF or spreadsheet report is a transformation. It may normalize dates, translate codes, calculate fields, deduplicate items, or omit metadata. Meaningful review requires the native file or database, forensic image or lawful working copy, extraction log, schema information, parser version, and report settings. Sensitive unrelated material can be managed through protective procedures rather than withholding the source needed to test an opinion.

Write protection and hashing document post-seizure integrity

Forensic practice may use write blockers or other controls to reduce changes during acquisition, followed by hash verification. Phones and live cloud accounts present different challenges because some systems must run and can change. The examiner should disclose unavoidable changes, isolation steps, and later access. Integrity controls begin at collection; they cannot establish what occurred before seizure.

Tool output should be validated against known data

Automated tools are useful but can misinterpret a new application schema, time format, or status code. Validation may include manual database review, a second tool, controlled testing on a comparable version, comparison with known messages, or provider documentation. Disagreement between tools should be explained rather than resolved by choosing the preferred result without analysis.

Extraction itself can create new metadata

Exported attachments, decoded databases, thumbnails, reports, and analyst spreadsheets receive new file-system dates and sometimes new names. Those are evidence-processing records, not source events. Trial exhibits should not display an export creation time as though it were the original file’s creation. An exhibit lineage should link each derivative back to its source.

Metadata requires authentication, purpose, and an admissible interpretation

Rule 901(b)(9) addresses processes and systems

A witness may authenticate metadata by describing the system that generated it and showing an accurate result. The needed detail depends on the dispute. Routine photo properties may require modest foundation; a contested database carve or proprietary timeline may require technical evidence about collection, decoding, testing, and error. The court’s threshold determination does not prevent the defense from challenging weight.

Electronic certifications have defined limits

N.D.R.Ev. 902(13) allows qualifying certified records generated by an electronic process or system, and Rule 902(14) addresses qualifying data copied from an electronic device, storage medium, or file through a digital-identification process. Notice and inspection requirements apply. Certification can establish process or copy integrity; it does not prove the prosecution’s inference about identity or intent.

Henderson requires foundation beyond custody after receipt

In State v. Henderson, 2024 ND 42, ¶¶ 9–27, the North Dakota Supreme Court reversed where central documents, images, receipts, and video lacked adequate authentication or business-record support. An investigator can explain receiving a metadata report, but a source witness, certification, or qualified examiner may be needed to establish how the relevant system created and maintained the fields.

Machine-generated fields and user-entered statements differ

A server timestamp or hash may be generated automatically. An image description, document author, profile location, or file name may be entered by a user. A business-record foundation does not make every user assertion true. Hearsay analysis should identify the declarant and purpose for each human-supplied field while separately evaluating the system’s reliability.

Original-evidence rules apply to metadata too

N.D.R.Ev. 1001 recognizes accurate readable outputs of electronically stored information as originals. N.D.R.Ev. 1003 generally permits duplicates unless a genuine authenticity question or unfairness exists. A spreadsheet of selected fields can be admissible, but the native source and transformation should remain available when selection or conversion is disputed.

Completeness can require conflicting metadata

A party should not display only the timestamp that supports its narrative when the same file contains a conflicting date or version record. N.D.R.Ev. 106 may apply to completing parts of a statement, while Rules 401 and 403 address the relevance and misleading effect of selective metadata. The defense should request the entire record needed to interpret the field fairly.

Metadata opinions must fit the expert’s actual work

Extraction, interpretation, and attribution are different opinions

An examiner may competently preserve a device image without expertise in a particular application schema. A document specialist may interpret revision history without identifying who used the computer. An image examiner may analyze EXIF without establishing that the accused held the camera. The court should evaluate qualifications and methodology for each opinion rather than treat “digital forensics” as one unlimited specialty.

Rule 702 requires sufficient facts and reliable application

Under N.D.R.Ev. 702, expert knowledge must help the factfinder, and the opinion must rest on sufficient facts, reliable principles and methods, and reliable application. Disclosure should identify tools, versions, source data, conversions, tests, assumptions, conflicts, and limitations. A report label is not a method.

Timeline software can conceal inferential choices

Analysts often combine device, provider, surveillance, and witness events into a chart. Selection, deduplication, time-zone normalization, clock correction, and event wording involve judgment. The defense should obtain the source table, formulas, scripts, excluded rows, original times, and revision history. A polished chronological graphic may contain more analyst opinion than the jury can see.

Maps require source and uncertainty disclosure

GPS EXIF, application location, IP estimates, cell sites, and user-entered place tags have different precision. Plotting each as an identical dot falsely equalizes them. A map should disclose source, coordinate system, claimed accuracy, whether location was automatic or chosen, and any transformation. A device coordinate does not by itself identify its user.

Negative evidence needs a completeness foundation

An expert may say no metadata showed editing, location, access, or transfer. That statement is meaningful only if the relevant source would ordinarily record the event and the collection included it. Platforms strip metadata, logs rotate, settings disable fields, and tools omit unsupported data. “Not found” should not become “did not happen” without a validated basis.

Demonstratives must not overstate precision

A second-by-second animation, exact map pin, or single “file created” label can mislead when the underlying evidence is uncertain. N.D.R.Ev. 107 governs illustrative aids, while N.D.R.Ev. 1006 governs summaries admitted to prove voluminous content. The court and jury should know which is being used and what assumptions it contains.

Defense counsel should reconstruct metadata from source to courtroom claim

Demand native evidence and every transformation

Request forensic images or reviewable working copies, native files, archives, application databases, server returns, cloud exports, logs, hashes, certifications, schemas, field guides, extraction records, tool versions, parser warnings, examiner notes, spreadsheets, formulas, scripts, filters, maps, timelines, and trial exhibits. A screenshot of a property panel is not a substitute for the file whose properties are disputed.

Create a field dictionary

For every important field, record the source system, table or file, stored name, displayed label, data type, epoch, unit, time zone, event definition, whether machine or user generated, extraction method, and known limitations. This exercise often reveals that two witnesses use the same word—“created”—for different events.

Preserve alternate sources promptly and lawfully

Old devices, original memory cards, email attachments, recipient copies, cloud versions, web accounts, and backups may clarify provenance. Collection should avoid opening or resaving files in ways that change metadata. Qualified imaging, read-only review, contemporaneous documentation, and hashes protect integrity. Counsel should not access accounts without authority.

Test the prosecution timeline with independent anchors

Compare disputed dates with phone calls, surveillance, receipts, access-control logs, known photographs, device clock offset, provider events, witness observations, and external server records. Identify whether sources are truly independent. Several fields copied from one original timestamp do not corroborate one another.

Retain the original numeric values

Discovery and expert work should preserve a timestamp’s raw integer or text value alongside every human-readable conversion. The raw value permits independent review of epoch, unit, offset, rounding, and software assumptions. A spreadsheet containing only converted local dates can conceal an erroneous setting and make correction impossible without returning to the source. The same principle applies to coordinates, status codes, account identifiers, and calculated fields: retain the source value, document the formula, and label every derived result.

Separate device, account, and human attribution

Metadata may show that a file existed on a device, an account uploaded it, or a connection accessed it. Those facts do not automatically prove who held the device, controlled the account, knew the content, or intended the act. Shared devices, synchronization, automated processes, remote access, malware, and account compromise require fact-specific consideration.

Use focused motions and specific trial objections

A motion may seek native discovery, a foundation hearing, expert disclosure, exclusion of an unreliable conversion, Rule 106 completion, correction of a misleading map, or limits on unsupported attribution. Under N.D.R.Ev. 103, state the exact defect: source, collection, field meaning, clock, conversion, hearsay, completeness, expert fit, or unfair presentation.

Explain why the metadata limitation matters to an element

Technical uncertainty becomes legally important when it affects identity, time, location, knowledge, possession, intent, or alteration. A copy-created date may not prove document authorship; stripped EXIF may not disprove location; a cloud-account event may not identify the user; an inherited author field may not prove preparation. The defense should translate the technical record into the reasonable doubt it creates.

Frequently asked questions about metadata in criminal cases

What is metadata?

It is information about a file, communication, account, or system event, including dates, identifiers, locations, device properties, versions, status codes, and processing history.

Does a file creation date show when the content was first made?

Not necessarily. It may show when that file instance was created on a particular storage volume, including after a copy, download, extraction, or restore.

Can metadata be changed?

Yes. Users, software, copying, editing, synchronization, exports, and platform processing can alter or remove fields. The significance depends on the field and mechanism.

Does EXIF GPS prove where a photo was taken?

It can support location when properly authenticated and corroborated, but coordinates may be absent, altered, inherited, user supplied, or affected by device settings and accuracy.

Does an author field prove who wrote a document?

No. It may come from a template, software profile, prior author, shared computer, or default setting. Revision history and independent evidence may be more informative.

What does a hash value prove?

A matching cryptographic hash shows byte-level identity for the compared items. It does not prove origin, truth, authorship, or what happened before hashing.

Why can two identical-looking files have different hashes?

Metadata, compression, container structure, thumbnails, or encoding may differ even when visible content looks the same.

Why do timestamps conflict?

They may record different events, clocks, time zones, copies, uploads, edits, or conversions. Each field must be defined before the sequence is reconstructed.

What is UTC?

Coordinated Universal Time is a common reference used by databases and servers. Software may convert it to local time using an offset and daylight-saving rules.

Can opening a file change metadata?

It can, depending on the system and application. Access times, previews, indexes, autosave data, and application history may update.

Are forensic reports the native evidence?

Usually not. They are transformed views of acquired files and databases. Native sources, logs, hashes, parser versions, and report settings are important for review.

Can metadata be authenticated without live testimony?

Qualifying electronic-process records or copied data may be certified under Rule 902(13) or (14), subject to notice and inspection. Interpretation and attribution may still require testimony.

Is machine-generated metadata hearsay?

Purely automated system output may not be a human statement, while user-entered fields can be. The source and purpose of each field require separate analysis.

Can metadata show that a file was deleted?

Sometimes, through database status, logs, directory records, or remnants. The evidence must distinguish human action from automatic cleanup, synchronization, and parser labels.

Can absence of metadata prove an event did not occur?

Only with a foundation that the relevant system ordinarily recorded the event and that collection was complete. Stripping, rotation, settings, and unsupported data can explain absence.

When is a metadata expert useful?

Complex timestamps, databases, deleted artifacts, cloud logs, file provenance, editing claims, or combined timelines may require expert interpretation and validation.

What should the defense request in discovery?

Native files and databases, forensic images, provider returns, logs, hashes, certifications, field guides, schemas, tool versions, parser warnings, notes, formulas, and all derivative exhibits.

Does metadata identify the person who used a device?

Usually not by itself. It may identify a device, account, session, or file event. Human attribution requires evidence of control, possession, knowledge, and surrounding circumstances.

Official authorities cited

Legal information, not legal advice. Metadata analysis depends on the native source, field definition, event, clock, time zone, device settings, software version, copying and synchronization, acquisition method, parser, validation, completeness, attribution, expert foundation, and current law.


Call nowChoose a time