Miami and Latin America corridor

Cross-Border Evidence Handling in the Miami Corridor

Preservation, collection, and transfer for matters where records sit across the Miami and Latin America corridor. The technical workflow is designed against the transfer mechanism counsel selects and against the local rules the records are subject to.

Bagged hard drive beside a forensic write blocker.

The engagement

What the Cross-Border Evidence Handling engagement covers

Miami is the working hub for a large volume of matters that cross into Latin America. Records at issue may sit with affiliated entities in Mexico, Central America, the Andean region, Brazil, or the Southern Cone. Custodians travel between the region and Miami. Vendors, correspondent banks, and shipping counterparties add another layer of records that live under a different legal regime than the matter itself. Getting evidence handled correctly on both sides is a technical and procedural task, not a shipping task.

GDF coordinates preservation, collection, and transfer with local counsel and the client's own affiliates. The engagement runs against the transfer mechanism counsel selects (party consent under a documented protocol, letters rogatory, Hague Evidence Convention requests, mutual legal assistance treaty requests, or voluntary production by the foreign entity). GDF does not provide legal advice on the transfer mechanism; the technical workflow is designed to support the mechanism counsel chooses.

For active incidents that cross the corridor, remote preservation of the Miami-side tenant, endpoint telemetry, and identity records starts on the intake call. Coordination with local counsel and the affiliate's IT team on the foreign side is arranged in parallel so that short-retention sources on both sides are captured before rotation.

Scope

  • Corridor evidence map

    A written map of the record sources on both sides of the corridor: US-side tenants and systems, foreign-side tenants and systems, shared services and vendors, custodian device populations, and the entities and individuals that hold access. The map identifies which records sit under which entity and jurisdiction so counsel can decide the transfer mechanism for each.

  • US-side preservation and collection

    Preservation and collection of Miami-side and other US-side records under standard forensic protocols: cloud tenant holds, endpoint imaging, mobile device collection, SaaS platform export, and structured-data extraction. Chain of custody is documented from the source system to secure storage.

  • Foreign-side coordination

    Coordination with local counsel and the foreign affiliate's IT team on preservation and collection under the mechanism counsel selects. Where GDF is authorized to perform the collection abroad, work is scheduled around local operations. Where a local vendor or the affiliate's own team performs the collection, GDF sets the protocol, checklist, and quality-control review so the collection is defensible under both regimes.

  • Transfer, storage, and access

    Evidence transfer is scheduled against the mechanism counsel selects. Physical media transfer, encrypted electronic transfer, and secure storage on the US side or the foreign side are configured against the requirements the transfer mechanism carries. Access logs to the evidence are maintained so counsel can show who touched what.

  • Language and processing

    Processing accommodates Spanish and Portuguese language populations. Field-level metadata is normalized so a review population from the corridor sits alongside the US-side population without a separate workflow. Reviewer support for Spanish- and Portuguese-language populations is available.

  • Reporting for counsel and the court

    Reports document the evidence map, the transfer mechanism used for each source, the collection and processing record on both sides, and the chain of custody. Where the matter reaches a court that will assess the collection, the record is prepared so counsel can walk the court from the source system to the exhibit.

Evidence commonly reviewed

Evidence reviewed

  • Corridor evidence map with entities, systems, and jurisdictions
  • US-side collection and cloud tenant preservation records
  • Foreign-side collection records and quality-control review
  • Transfer records tied to the mechanism counsel selected
  • Chain-of-custody records for the life of the matter
  • Processing and review-platform loading records for merged populations

What you receive

Deliverables

  • Written corridor evidence map with counsel-facing options
  • Collection reports for US-side and foreign-side sources
  • Transfer record aligned to the selected mechanism
  • Merged review population loaded to the platform of choice
  • Chain-of-custody record for the life of the matter
  • Expert report where the matter requires testimony on the workflow

Engagement workflow

How the engagement runs

  1. Scoping and evidence map

    The engagement opens with a written map of the record sources on both sides of the corridor: US-side tenants and systems, foreign-side tenants and systems, shared services and vendors, custodian device populations, and the entities and individuals that hold access. The map identifies which records sit under which entity and jurisdiction so counsel can decide the transfer mechanism that fits each source and the matter's schedule. The evidence map is a working document that is updated as new sources are identified during the engagement.

  2. US-side preservation and collection

    US-side preservation and collection runs under standard forensic protocols. Cloud tenants are placed on hold at the platform level where the environment supports it. Endpoint imaging, mobile device collection, SaaS export, and structured-data extraction are scheduled against custodian availability. Short-retention sources are prioritized because retention on some of them is measured in days. Chain of custody is documented from the source system to secure storage on the US side.

  3. Foreign-side coordination

    Foreign-side preservation and collection is coordinated with local counsel and the foreign affiliate's IT team under the mechanism counsel selects. Where GDF is authorized to perform the collection abroad, work is scheduled around local operations and travel logistics. Where a local vendor or the affiliate's own team performs the collection, GDF sets the written protocol, the checklist, and the quality-control review that keeps the collection defensible under both regimes. The record documents which party performed each step and under what authority.

  4. Transfer, storage, and access

    Evidence transfer is scheduled against the selected mechanism. Physical media transfer, encrypted electronic transfer, and secure storage on the US side or the foreign side are configured against the mechanism's requirements. Access logs to the evidence are maintained so counsel can show who touched what during the life of the matter. Where a data protection authority notification or a local privacy assessment is needed, the technical record is prepared so counsel can support the assessment without additional collection work.

  5. Processing, review, and reporting

    Processing accommodates Spanish and Portuguese language populations. Field-level metadata is normalized so a review population from the corridor sits alongside the US-side population without a separate workflow. Reviewer support for Spanish- and Portuguese-language populations is available. Reports document the evidence map, the transfer mechanism used for each source, the collection and processing record on both sides, and the chain of custody, so the technical record travels with the matter for the life of the case.

Frequently asked

Common questions on Cross-Border Evidence Handling

Do you decide the transfer mechanism for foreign records?

No. GDF does not provide legal advice on the transfer mechanism. The technical workflow is designed to support the mechanism counsel selects (party consent, letters rogatory, Hague Evidence Convention requests, mutual legal assistance treaty requests, or voluntary production by the foreign entity).

Can GDF perform the collection on the foreign side?

Where GDF is authorized to perform the collection abroad, work is scheduled around local operations. Where a local vendor or the affiliate's own team performs the collection, GDF sets the protocol, the checklist, and the quality-control review that keeps the collection defensible.

How is local data protection law considered?

Local data protection law shapes the transfer mechanism, the notification requirements, and the handling of personal data during the collection and transfer. Counsel and local counsel determine the applicable law and the required steps. The technical workflow is designed to fit those steps and to produce a record counsel can use to support any assessment.

Can Spanish and Portuguese review populations be staffed?

Yes. Foreign-language identification runs during processing, and review workflows can be staffed for Spanish- and Portuguese-language populations common in corridor matters.

How is the technical record prepared for court?

The record documents the evidence map, the transfer mechanism used for each source, the collection and processing record on both sides, and the chain of custody. Where the matter reaches a court that will assess the collection, the record is prepared so counsel can walk the court from the source system to the exhibit.

Talk with an examiner

Discuss the matter and the next step.

Call to discuss timing, scope and the safest way to share information. Do not send evidence or credentials by email.

24/7 hotline: 1-800-868-8189

Privacy center

Choose your site settings

Optional technology stays off until you choose otherwise. You can change these browser settings at any time. Access to the core site does not depend on optional technologies.

Technology preferences
Sale or cross-context sharing: not used GDF does not sell or share website personal information for cross-context behavioral advertising.