Print this page (attorney exhibit format)
Scope of Services
Data365 Evidence provides preservation-first evidence handling and, where authorized, forensic data acquisition aligned to the matter objective.
This page shows what is typically included, what falls outside the standard engagement, and what is confirmed in writing.
Professional Boundaries
- Services are not structured to support predetermined outcomes.
- No legal advice, legal analysis, or representation is provided.
- Records and outputs reflect the confirmed scope, the materials made available, and the handling steps performed.
Service scope overview
Within Scope
Within-scope services center on preservation, authorized acquisition where appropriate, custody continuity, and close-out records.
- Preservation planning and intake definition
- Authorized device, media, and account acquisition appropriate to the source and confirmed handling plan
- Custody continuity, transfer records, and source-identification records
- Verification records for provided images, exports, or transferred files when used
- Cloud exports and account-data preservation using authorized provider pathways where available
- Preservation of authentication, access, and administrative records when they fall within the preservation plan
- Secure storage or return coordination where included in the engagement terms
- Limited technical coordination directly tied to authorized preservation, acquisition, transfer, or custody continuity
- Mobile-device preservation and acquisition under confirmed authority and approved access conditions, including messages, media, application data, and backups where within scope
Outside Standard Scope
The items below require separate written retention or sit outside the standard preservation-first engagement.
- Expert analysis, opinions, testimony, or broad forensic consulting unless separately retained in writing under a clearly defined separate scope
- Admissibility opinions, merits conclusions, or advocacy-directed interpretations
- Password bypass, device unlocking, or covert acquisition techniques
- Destructive testing or alteration of original evidence without explicit approval
- Consumer data-recovery or other non-evidentiary retrieval services
- Cybersecurity remediation, threat hunting, or incident-response services
What keeps scope clear
- Sources, objectives, and expected deliverables are aligned before technical handling begins.
- Access authority, transfer path, and any credential-based handling steps are confirmed before receipt, release, or system access.
- Storage, return, staged handoff, and delivery assumptions are addressed where they affect close-out.
- Added sources or changed objectives are addressed before handling proceeds beyond the approved baseline.
What is confirmed in writing
- Matter definition: sources, preservation objectives, deliverables, and boundaries
- Authority: the responsible contact, access authority, and preservation plan
- Handling terms: transfer method, storage or return instructions, and any retention limits
- Fee terms: project basis, approved external costs, and any priority scheduling assumptions
Where useful, a concise engagement letter or statement of services may be used to keep scope and handling terms aligned.
Scope Notes
Later analysis, expert services, and specialized deliverables sit under separate terms rather than the preservation engagement.
Client-directed disposition decisions may appear in close-out records where relevant. Data365 Evidence does not provide media destruction, data sanitization, or remediation services.
Added sources, travel, logistics, and priority handling are addressed in Fees & Billing so scope and pricing stay aligned.
Next Steps
- Review fees and close-out expectations. Review Fees & Billing and Deliverables next to confirm pricing, deliverables, and close-out expectations.
- Move to written intake. Review Contact before Start Intake, once scope, authority, timing, and logistics are clear enough to confirm handling. Initial intake does not accept file uploads.
- Include deadlines, transfer constraints, authorization details, source type, and any added-source questions so intake opens with the right scope and handling path.