Authentication of Digital Records in North Dakota Criminal Cases
Digital evidence is not authenticated merely because it appeared on a phone, arrived in a provider return, or looks familiar on a courtroom screen. The…
Rule 901, Rule 902 electronic certifications, conditional relevance, native files, hashes, metadata, screenshots, texts, email, social media, audio, video, jail calls, provider records, system output, authorship, attribution, timestamps, completeness, alteration, synthetic media, chain of custody, hearsay, original-record proof, objections, and trial presentation
Authentication of Digital Records in North Dakota Criminal Cases
Digital evidence is not authenticated merely because it appeared on a phone, arrived in a provider return, or looks familiar on a courtroom screen. The proponent must identify what the exhibit claims to be and produce evidence sufficient for a reasonable juror to find that claim true. A genuine screenshot may still have an unknown author. A correctly copied file may still be incomplete. An authentic record may still contain hearsay, misleading timestamps, or inadmissible conclusions.
Authentication is a preliminary question, not a seal of truth
Rule 901 treats authentication as conditional relevance. The judge asks whether enough evidence exists for a reasonable juror to find that the item is what the proponent claims. If that threshold is met, the jury may still reject the claim or give the exhibit little weight. The defense can attack authenticity both at the admissibility stage and before the jury.
The Rule 901 explanatory note is explicit: “A determination that evidence is authentic does not render it admissible.” A message can be genuine yet hearsay. A video can accurately depict a scene yet be unfairly edited. A provider log can be authentic yet require expert testimony before it supports a location inference. Authentication is one gate among several.
Start by forcing the proponent to state what the item is
A digital exhibit can support multiple propositions. A screenshot may be offered as proof that certain words appeared on a display, that a platform account contained them, that a named person wrote them, that the exchange is complete, or that it occurred at the displayed time. Evidence sufficient for the first proposition may be inadequate for the others.
Ask the court to require a precise claim. “A Facebook message from the defendant” includes platform origin, account association, authorship, message integrity, and speaker identity. “A screenshot found on a witness’s phone” is narrower. The foundation should match the claim communicated to the jury, not a carefully limited description used only when the exhibit is admitted.
File identity, account identity, device identity, and human authorship are different
A forensic examiner may prove that a file came from a particular phone. That does not prove who created the file or controlled the phone at the relevant moment. A platform custodian may associate an account with an email address. That does not prove who typed a specific message. An account holder, device possessor, subscriber, logged-in user, and author can be different people.
Attribution ordinarily depends on a combination of facts: possession, credentials, distinctive knowledge, conversational context, response timing, known contacts, photographs, admissions, device artifacts, IP logs, location, payment records, and the absence or presence of compromise evidence. No single fact invariably proves authorship. The inference should be stated at the level the evidence supports.
Integrity and completeness are separate from authorship
A witness may recognize the participants and still have captured only selected messages. A provider may authenticate a complete export while an investigator later crops it. A hash may establish that the offered file matches the acquired file but say nothing about what occurred before acquisition. Ask which stage the integrity proof covers.
Completeness matters because digital content is easily filtered, threaded, quoted, forwarded, edited, or displayed without adjacent context. An exhibit can be authentic as far as it goes and misleading because it omits earlier messages, later corrections, attachments, reactions, timestamps, deleted items, or the identity of the quoted speaker.
A timestamp must be tied to its clock and event
Digital records may contain creation, modification, access, upload, server-receipt, send, delivery, display, export, and download times. Some are stored in Coordinated Universal Time and displayed in local time. Others use a device clock that the user can change. A screenshot may show only a formatted display time while metadata preserves a different source value.
Authentication of the file does not prove that the displayed time is accurate or means what the proponent argues. Foundation should identify the clock, timezone, synchronization method, daylight-saving treatment, event represented, and whether conversion occurred. A minute-level timeline can fail when records from different systems are compared without normalizing their clocks.
Rule 901 permits multiple methods of authentication
Rule 901(b) gives examples, not an exclusive checklist. Digital evidence may be authenticated through a witness with knowledge, distinctive characteristics, voice identification, telephone circumstances, process-or-system evidence, statutory methods, or a combination. Circumstantial evidence can be enough, but it must connect the offered item to the claim actually made.
Witness with knowledge
A participant can testify that a text thread accurately reflects an exchange. A photographer can identify an image and explain when it was captured. A recipient can recognize an email and its surrounding conversation. A technician can explain an export. The useful foundation addresses how the witness knows, not merely a conclusion that the exhibit is “fair and accurate.”
Witness knowledge has boundaries. A recipient can identify what appeared on a screen without knowing whether a hidden account administrator altered the data. A detective can testify about extraction and custody without knowing who authored a message. A custodian can explain a platform’s records without identifying the human user. Cross-examination should preserve those boundaries.
Distinctive characteristics and surrounding circumstances
Rule 901(b)(4) permits reliance on appearance, content, substance, internal patterns, and other distinctive characteristics considered with all circumstances. A message may reference private facts, use a familiar nickname, continue an earlier exchange, contain a known writing style, or prompt conduct consistent with the conversation. These facts can support identity without direct eyewitness testimony.
Distinctiveness must be evaluated, not assumed. Names, profile photographs, signatures, and writing habits can be copied. Shared knowledge may be known to several people. Automated suggestions can mimic style. The defense should identify plausible alternative users or sources supported by evidence rather than rely on abstract possibilities alone.
Voice identification and recorded conversations
Rule 901(b)(5) permits a witness to identify a voice based on familiarity acquired at any time under circumstances connecting it with the alleged speaker. The witness should explain the basis and duration of familiarity, recording quality, language, distortion, and whether the identification occurred before suggestive case information was supplied.
In Hendricks, an officer had listened to jail calls, recognized the recordings, identified the defendant’s voice, and testified that they fairly and accurately represented the calls. 2025 ND 143, ¶¶ 18–19. The Court held that the evidence as a whole permitted a reasonable juror to find the recordings authentic, while noting that the State could have developed more foundation. Id. ¶ 19.
Telephone and 911 recordings
Rule 901(b)(6) identifies circumstances that can authenticate telephone conversations. Self-identification alone may not establish the speaker, but surrounding events can. Address, contemporaneous police response, injuries matching the report, admissions, known voices, call-back information, and system records may combine to support the finding.
State v. Burton, 2025 ND 83, ¶¶ 20–26, upheld authentication of a 911 recording based on circumstantial evidence plus officer testimony and a custodian’s certificate. The Court emphasized that the State need not conclusively eliminate every inconsistent possibility. Id. ¶¶ 21, 25.
Evidence about a process or system
Rule 901(b)(9) permits evidence describing a process or system and showing that it produces an accurate result. This method matters for automated logs, forensic tools, body-camera systems, access controls, license-plate readers, breath instruments, cloud exports, and machine-generated reports. The witness should know the relevant process rather than merely receive its output.
Foundation can include system design, configuration, validation, input sources, error detection, maintenance, user permissions, version, time synchronization, export method, and known limitations. The amount of proof should reflect the claim. Showing that a system reliably saves video is different from proving that an analytics model correctly identified a person.
Self-authentication under Rules 902(13) and 902(14)
N.D.R.Ev. 902(13) allows a qualified person to certify that an electronic process or system generated a record and produces an accurate result. Rule 902(14) permits certification of data copied from an electronic device, storage medium, or file through a digital-identification process. Both incorporate the notice requirements of Rule 902(11).
The certification must be made by a qualified person and supplied with reasonable written notice, the record, and the certificate at least fourteen days before trial or hearing. Inspect whether the certificate identifies the exact exhibit, tool, version, process, hash algorithm, source, acquisition date, and result. A certificate covering an archive may not cover a later analyst-created chart.
Self-authentication does not prove authorship, truth, completeness, or technical interpretation. A Rule 902(14) hash can establish that copied data matches a source. It cannot prove that the source data was accurate when created or that the accused generated it. A Rule 902(13) certificate can support system output while leaving hearsay and expert-fit objections intact.
Authentication should be tailored to the type of digital record
Text messages and messaging applications
For a text conversation, identify the source device or provider, application, account, participants, extraction method, message identifiers, timestamps, attachments, reactions, quoted replies, edits, and deletions. A photograph of a screen may accurately show what the photographer saw while omitting metadata and surrounding messages. Native extraction usually offers stronger context.
Authorship may be shown through possession, prior authenticated messages, distinctive content, reply behavior, known events, account access, and corroboration. A saved contact name proves how a phone owner labeled a number, not who used the number. A profile photograph proves what the account displayed, not who controlled it.
Modern messaging platforms allow message editing, deletion, disappearing content, multiple logged-in devices, linked desktops, forwarded material, and account recovery. Foundation should address functions relevant to the dispute. The defense need not prove hypothetical manipulation, but concrete evidence of shared access, compromise, or inconsistent exports can make the authentication claim materially weaker.
Email authentication can draw from headers, server records, domain information, message identifiers, reply chains, attachments, account access, distinctive content, and witness testimony. A printed email body may omit routing headers and metadata. The “From” field can be spoofed, while a provider export or server log may provide stronger evidence about transmission.
Separate the identity of the account from the author of the message. Assistants, shared mailboxes, delegated access, compromised credentials, and automated systems can send from an account. Examine authentication logs, device information, recovery events, forwarding rules, and contemporaneous responses when authorship is disputed.
Social-media posts and direct messages
A public profile can be copied or impersonated. Authentication may rely on platform records, account-creation data, recovery contacts, linked devices, payment data, IP logs, photographs unavailable elsewhere, distinctive content, admissions, or a witness who observed posting. A username and profile picture alone are weak proof of authorship.
Determine whether the exhibit is a live page, archived page, screenshot, provider return, or investigator recreation. Platforms change interfaces and time displays. Posts can be edited; comments can be deleted; handles can change; shared posts may attribute words to the wrong person. Preserve the URL, account identifier, capture time, full context, and native records where available.
Photographs
A witness familiar with the scene may testify that a photograph accurately depicts it, even if the witness did not take the picture. When the claim depends on capture time, device, geolocation, originality, or absence of editing, visual recognition alone may be insufficient. Obtain the original file, metadata, source device, cloud copy, and editing history.
Image metadata can be useful but is editable and may be stripped during messaging or social-media upload. A thumbnail, screenshot, or recompressed copy differs from a native image. Compare dimensions, encoding, filename, embedded preview, and hash. If enhancement is used, preserve the unenhanced source and document every operation.
Video, body-camera, doorbell, and surveillance recordings
Video foundation should identify the camera, location, field of view, recording mode, clock, trigger, frame rate, retention, export process, and whether audio is synchronized. A witness can authenticate an accurate depiction, while a system witness may authenticate automatically recorded footage. Gaps, pre-roll, motion triggers, and dropped frames affect completeness and interpretation.
Body-camera footage may be automatically segmented, uploaded, redacted, or transcoded. Doorbell systems may store clips rather than continuous video. Store surveillance may cycle among cameras or use variable frame rates. The trial version should be compared with the original export, and the jury should not be told that missing footage depicts inactivity unless the system actually recorded continuously.
Audio recordings
Authenticate the device or system, speakers, continuity, recording process, editing, and any enhancement. A participant can identify a conversation; a familiar listener can identify a voice; system logs can corroborate time and source. Transcripts require separate accuracy proof and should not replace the recording when tone, overlap, or ambiguity matters.
Noise reduction, compression, speed changes, and channel mixing can alter perception. Preserve the first-generation file and processing settings. If a disputed word drives the case, the court should hear the relevant original segment and understand any transcript convention rather than treat an analyst’s interpretation as the audio itself.
Provider records and cloud exports
A provider custodian can authenticate records maintained by the service, and Rules 902(11), (13), or (14) may permit certification. Provider authenticity does not establish the human author of user content. It also does not prove that an investigator’s selected spreadsheet or screenshot faithfully represents the entire production.
Preserve the return exactly as received, including cover letters, load files, folder structure, metadata, field definitions, and hashes. Record transformations into review software and trial exhibits. Ask whether timestamps are stored or displayed, whether deleted content is included, and whether records reflect server events, user actions, or inferred attributes.
Device extractions and forensic reports
A forensic image can be authenticated by acquisition testimony, device identification, write protection, hash values, tool logs, and chain of custody. A parsed report is not identical to the forensic image. Software interprets databases, assigns labels, converts timestamps, and may omit unsupported or deleted records. Tool version and parsing behavior can matter.
Demand the extraction type, acquisition log, source identifiers, hash reports, tool and version, warnings, failed steps, time settings, and native artifacts supporting important rows. A report labeled “message” or “location” reflects software interpretation. The examiner should explain how the source artifact supports the label and whether another tool reproduces the result.
Machine-generated logs and sensor data
Pure machine output may not be a human assertion and therefore may fall outside hearsay, but it still requires authentication. Establish the process, input, configuration, calibration where applicable, clock, error conditions, maintenance, and accurate export. Human-entered labels inside the same record need separate analysis.
Do not let “automated” substitute for reliable. Systems can ingest incorrect inputs, operate under changed settings, duplicate events, round values, or display calculated estimates. The appropriate foundation depends on whether the State offers a basic log entry or a specialized conclusion derived from it.
AI-generated, altered, or synthetic media
Digital media can be genuine as a file while false as a depiction. Authentication should address source provenance, capture or generation records, editing history, content credentials where available, project files, model or application, prompts, account history, and independent corroboration. Visual inspection alone may not resolve sophisticated alteration.
Detector scores are not self-proving. The proponent should disclose the tool, version, training and validation information, error rates, population fit, inputs, thresholds, and reproducibility. The defense should avoid unsupported accusations of fabrication; instead, identify missing provenance, inconsistent metadata, editing artifacts, or an expert basis for the challenge.
Hashes, metadata, and chain of custody answer limited questions
A hash is a comparison tool, not a truth certificate
A cryptographic hash creates a digital fingerprint of a specific byte sequence. Matching hashes strongly support that two files are identical. Different hashes show that the bytes differ, but the reason may be editing, metadata change, recompression, export, or format conversion. Document the algorithm, source, time, operator, and compared values.
A hash begins protecting integrity when calculated. If a file was altered before acquisition, a later hash faithfully preserves the altered file. If an investigator converts video for playback, the converted file will have a different hash from the native source. Both should be retained and the transformation explained.
Metadata must be interpreted in context
Metadata can identify dates, devices, software, dimensions, accounts, message identifiers, or geolocation. Some fields are automatically created; others are user-controlled, inherited, or rewritten during copying. A metadata field should be tied to its specification and event before counsel assigns evidentiary meaning.
Conflicting metadata does not always prove tampering. Cloud synchronization, file-system copying, export, time conversion, and application processing can produce different dates. The relevant question is why the values differ and which event each records. An expert should distinguish expected transformation from unexplained inconsistency.
Chain of custody is strongest when it documents transformations
For digital evidence, chain of custody should show seizure or receipt, source identification, acquisition, hashing, storage, access, processing, export, and courtroom preparation. Every person need not testify if the evidence as a whole supports identity and integrity, but material gaps or unexplained changes can undermine the foundation or weight.
A custody log that records only who possessed a drive may miss the most important events: database parsing, screenshot creation, clip trimming, transcript preparation, enhancement, or spreadsheet filtering. Preserve audit logs and work-product exports that show what changed between source and exhibit.
Native files matter when the dispute concerns more than appearance
A screenshot is often useful and sometimes sufficient. Native evidence becomes important when authorship, time, editing, deletion, threading, account identity, or completeness is disputed. Native data may contain identifiers and context invisible in a screenshot. Discovery should include both the human-readable exhibit and the underlying source.
If the native material no longer exists, determine why, when preservation began, whether backups remain, and whether a secondary version accurately reflects the source. The absence does not automatically require exclusion, but it may affect authentication, original-record proof, cross-examination, and the fairness of allowing a confident inference.
Authentication does not resolve hearsay, completeness, or unfair prejudice
Hearsay and authorship require separate rulings
An authenticated message is an out-of-court statement if a person made an assertion. The proponent must identify a nontruth purpose, an exclusion such as an opposing-party statement, or an exception. Embedded quoted messages may add layers under Rule 805. Machine output and human labels should be separated.
In Hendricks, the defense objected on authentication grounds but not hearsay grounds. The Court treated them separately and declined to find error from the unmade hearsay objection. 2025 ND 143, ¶¶ 20–23. State each ground at trial; one does not preserve another.
Business-record certification does not prove user-generated content
A provider may regularly maintain logs and messages. Rule 803(6) can support the provider’s recordkeeping, but an outsider’s assertion inside the record needs its own basis. A platform’s duty to store a user’s words does not give the user a business duty to speak accurately. Certification likewise does not prove authorship.
State v. Henderson, 2024 ND 42, ¶¶ 18–24, reinforces that authenticity and business-record foundation must be proved rather than assumed. A detective’s receipt of financial documents and general familiarity did not explain the creator’s system or authenticate condensed exhibits.
Original-record rules focus on proof of content
N.D.R.Ev. 1001 treats an accurate printout or other readable output of electronically stored information as an original. Rule 1003 generally permits duplicates unless a genuine authenticity question or unfairness exists. Accuracy and fairness remain central.
A screenshot may be an admissible representation, but when the dispute concerns omitted context, edits, or hidden metadata, the court should consider whether the available source better proves content. If the original is lost, Rule 1004 may permit other evidence unless the proponent lost or destroyed it in bad faith or another condition applies.
Rule 106 can prevent a misleading excerpt
N.D.R.Ev. 106 permits an adverse party to require introduction of another part of a writing or recorded statement that fairness requires at the same time. For digital conversations, the necessary context may include preceding questions, quoted replies, reactions, later corrections, attachments, or a continuation on another device.
The requested completion should be targeted. Explain how the omitted material changes meaning, speaker identity, timing, or inference. A full device dump is not automatically required, but a prosecutor should not present a fragment that converts sarcasm into admission or separates a response from the accusation it denies.
Rule 403 applies to polished but overstated exhibits
Digital exhibits can appear unusually authoritative. Maps, timelines, message bubbles, transcripts, enlarged frames, and analytics labels may conceal uncertainty or editorial choice. Under Rule 403, the court can exclude or limit presentations whose unfair prejudice, confusion, or misleading effect substantially outweighs probative value.
Request neutral labels, visible uncertainty, original context, accurate scale, and limiting instructions. Distinguish evidence admitted under Rule 1006 from an illustrative aid governed by the current Rule 107. The jury should know which portions came from the source and which were created for litigation.
A disciplined authentication challenge is exhibit-specific
Preserve first, then compare every version
Send preservation requests when appropriate and seek source devices, provider returns, native files, extraction reports, audit logs, hashes, and all processed versions. Create a version table listing filename, size, hash, source, creator, date received, transformation, and intended use. Unexplained divergence often reveals the real evidentiary issue.
Compare the proposed exhibit with the source before the hearing. Check row counts, page counts, message counts, clip length, resolution, metadata, timezone, and omissions. A demonstrative may be accurate yet should not be confused with a source record. The court needs to know which version the witness is authenticating.
Use a claim-by-claim foundation chart
For each exhibit, list the State’s claim, foundation witness, Rule 901 method, supporting facts, gaps, separate hearsay basis, original-record issue, completeness concern, and requested remedy. This prevents a general objection from obscuring the precise missing connection and helps counsel renew the correct ground if testimony changes.
The chart may show that some claims are adequately supported while others are not. Counsel can concede that a screenshot was found on a phone while contesting authorship; concede file identity while contesting timestamp meaning; or concede account ownership while contesting event-time use. Narrow concessions increase credibility.
Voir dire the foundational witness
Ask how the witness obtained the item; whether the witness saw the original event; what system created it; whether the witness used that system; which version is offered; what transformations occurred; whether the exhibit is complete; how time is recorded; and what supports authorship. Keep questions tied to the claim communicated to the jury.
If the witness cannot answer, request a hearing outside the jury’s presence or a different witness. The answer may justify exclusion, a narrower description, redaction, a limiting instruction, or admission with cross-examination. Do not allow counsel’s unsworn explanation to fill the foundation.
Make specific, timely objections
Identify Rule 901 and the missing link. Separately identify Rule 902 notice or certificate defects, hearsay, Rule 805, Rule 1002 or 1003, Rule 106, Rule 403, expert reliability, privilege, or confrontation. Hendricks illustrates the cost of preserving authentication but not hearsay. 2025 ND 143, ¶¶ 20–23.
If the court admits the exhibit conditionally, track whether the promised connecting evidence arrives. Move to strike if it does not. If a later witness broadens the claim beyond the original ruling, renew the objection. Request findings that identify the authenticated proposition and supporting evidence.
Offer the court a focused remedy
Authentication disputes need not be all or nothing. The court can allow proof that a screenshot existed while prohibiting an unsupported authorship claim; admit a complete native conversation instead of a crop; require testimony about a system; redact unverified labels; exclude a litigation-created summary; or give a limiting instruction about what the evidence does not establish.
At trial, return to the difference between threshold and weight. Authentication means only that a reasonable juror could find the item genuine in the claimed respect. It does not shift the burden, create a presumption of authorship, or establish an element beyond a reasonable doubt. The State retains the burden on identity, intent, and every charged element.
Frequently asked questions about authenticating digital records in North Dakota
Does a screenshot authenticate itself?
No. A witness or other evidence must connect it to what the proponent claims. A screenshot may accurately show a display while leaving source, authorship, time, completeness, and alteration unresolved.
Must the State prove digital evidence beyond all possibility of alteration?
No. Rule 901 requires evidence sufficient for a reasonable juror to find the item is what the State claims. Concrete alteration evidence still may defeat or narrow that claim or reduce weight.
Does possession of a phone prove authorship of every message?
No. Possession is relevant but does not exclude shared use, linked devices, compromise, automation, or another user. Authorship should be supported by all surrounding evidence.
Is a contact name proof of who used a number?
No. A contact name shows how someone labeled the number. Subscriber records, voice, content, possession, responses, and corroborating events may provide stronger identification.
What does a matching hash prove?
It strongly supports that two compared byte sequences are identical. It does not prove who created the file, whether it was altered before hashing, or whether its contents are true.
Can metadata authenticate a photograph?
Metadata can support device, time, location, or software inferences, but fields can be stripped, rewritten, user-controlled, or misinterpreted. Corroboration and source context matter.
Can circumstantial evidence authenticate an account or recording?
Yes. Burton used surrounding facts to authenticate a 911 call, and Hendricks relied on voice recognition and recording familiarity for jail calls.
Are provider records enough to prove who wrote a message?
Not automatically. Provider records can establish account and system facts. Human authorship usually requires additional evidence connecting the person to the specific content.
What is Rule 902(13)?
It permits self-authentication of a record generated by an electronic process or system through a qualified person’s certification that the system produces an accurate result, with required notice.
What is Rule 902(14)?
It permits self-authentication of data copied from an electronic device, storage medium, or file through a certified digital-identification process, commonly using hash values.
How much notice is required for electronic certification?
Rules 902(13) and (14) use Rule 902(11)’s procedure: written notice and access to the record and certification at least fourteen days before trial or hearing.
Does authentication eliminate a hearsay objection?
No. The North Dakota rules expressly separate the issues. A genuine message can contain inadmissible hearsay, and each embedded statement may need its own basis.
Can an officer authenticate a recording without the records custodian?
Sometimes. In Hendricks, an officer’s familiarity with the calls and voices supplied enough evidence. The required foundation depends on the claim and all circumstances.
Can an edited clip be admitted?
Possibly, if accurately authenticated and not misleading. The original should be preserved, all edits disclosed, omitted context evaluated, and the clip accurately described.
What if the device clock was wrong?
The file may still be authentic, but its displayed time may not prove the event time. The proponent should explain clock settings, synchronization, timezone, and corroboration.
Are AI detector results self-authenticating?
No. The output, system, version, inputs, validation, limits, and expert interpretation require foundation. A score does not independently prove that media is genuine or synthetic.
Should the defense obtain native files?
Yes when integrity, metadata, authorship, time, deletion, threading, or completeness matters. A screenshot or PDF may omit evidence necessary to test the State’s claim.
What is the strongest authentication objection?
One that identifies the precise claim, the missing connection, and a focused remedy. “Lack of foundation” alone is less useful than explaining why the evidence does not connect the item to the asserted author, source, time, or completeness.