Shield Connectors

DCI Internal Chat Connector

Back To Connectors Page

Internal Messaging | Connector for DCI Internal Chat

Request a Demo

What Is the Shield Connector for DCI Internal Chat?

DCI Internal Chat refers to the internal messaging and collaboration communication layer within DCI — a financial technology and trading infrastructure platform used across regulated financial institutions. DCI’s internal chat functionality enables trading desk staff, operations teams, and compliance functions to communicate in real time within the DCI platform environment, coordinating trading activity, discussing positions, managing workflows, and sharing information relevant to the firm’s regulated operations — all within the same system that supports their broader trading and financial operations activity.

Shield’s connector for DCI Internal Chat ingests chat messages and associated metadata directly from the DCI platform into Shield’s compliance platform, making every captured communication immediately available for AI-powered surveillance, investigation, and eDiscovery alongside every other channel the firm uses. From the moment data enters Shield, it is available within a single unified platform — without manual exports, without siloed review workflows, and without the blind spots that arise when trading platform internal chat is managed separately from other regulated communications.

DCI Internal Chat data does not exist in isolation. Shield understands the full context of trading platform communications, enabling compliance teams to detect genuine risk rather than chasing false positives.

Why DCI Internal Chat Compliance Is Complex

DCI Internal Chat presents compliance challenges that reflect both the specific characteristics of trading platform-embedded messaging and the broader compliance considerations of internal communications within regulated financial operations. Several issues arise consistently across regulated firms:

  • Trading platform messaging as a regulated channel. DCI Internal Chat is generated within a trading and financial operations platform — meaning communications are directly adjacent to regulated trading activity. Messages exchanged within DCI about orders, positions, pricing decisions, and trading desk coordination carry a higher compliance risk profile than general enterprise messaging, because they may directly relate to or accompany regulated transactions. Surveillance models for DCI Internal Chat must be calibrated for trading-context language and risk typologies, not generic enterprise messaging patterns.
  • Internal communications oversight within regulated operations. Internal communications between trading desk staff are subject to the same recordkeeping and supervision obligations as external communications — a point that is sometimes overlooked when compliance teams focus on client-facing or counterparty communications. FINRA Rules 3110 and 4511 and equivalent frameworks require firms to supervise and retain internal as well as external communications relating to regulated business. DCI Internal Chat between traders about positions, orders, and trading strategy is firmly within this scope.
  • Platform-specific data delivery and metadata. DCI Internal Chat data is generated within DCI’s own platform architecture — with data delivery mechanisms, metadata structures, and export formats specific to the DCI environment. Compliance connectors designed for general enterprise messaging platforms do not automatically extend to DCI, and firms that have deployed comprehensive eComms archiving for Bloomberg IB, email, and Teams may nonetheless have a gap in their DCI Internal Chat coverage.
  • Cross-platform trading workflow communications. Trading activity at firms using DCI typically involves communications across multiple platforms — DCI Internal Chat for in-platform coordination, Bloomberg IB for counterparty communication, email for formal correspondence, and voice for real-time execution coordination. Compliance architectures that treat DCI Internal Chat separately from these other channels produce fragmented trading communication records that cannot support complete trade reconstruction or cross-channel misconduct detection.
  • Volume and surveillance prioritisation. DCI Internal Chat within active trading operations generates high message volumes across the trading day. Without AI-assisted prioritisation, manual review at this scale is operationally impractical, and compliance teams cannot focus review resources on the communications that carry genuine risk.

Key Features of the Shield DCI Internal Chat Connector

Complete DCI Internal Chat Capture. Shield captures all DCI Internal Chat messages within scope — including one-to-one conversations, group chats, and desk-level channel communications — alongside the full metadata layer generated by the DCI platform. All data is ingested in full, with zero data loss.

Full Metadata Preservation. Shield retains and enriches the complete DCI Internal Chat metadata layer — including sender and recipient identifiers, channel and workspace identifiers, timestamps, message IDs, and thread context. This metadata is preserved in its original form, made fully searchable, and stored as part of the immutable compliance record — ensuring that investigations, regulatory examination responses, and eDiscovery productions are accurate and legally defensible.

Immutable, Audit-Ready Archive. All DCI Internal Chat data captured by Shield is stored in a tamper-evident, WORM-compliant archive with a complete audit trail of every access and action taken on the record. Data is indexed for rapid search and retrieval, supporting regulatory examination responses, eDiscovery requests, and internal investigations. Retention periods are fully configurable to meet jurisdiction-specific requirements — including the six-year standard under SEC Rules 17a-3 and 17a-4, the five-to-seven-year requirements under MiFID II and MAR, and the five-year requirements under CFTC Regulation 1.35.

Out-of-the-Box AI Surveillance Models. Shield ships with pre-configured AI surveillance models for DCI Internal Chat, targeting behaviours including market manipulation, information leakage, MNPI sharing, front-running, coordinated trading, and personal misconduct — calibrated to the specific language patterns and risk typologies of internal trading platform communications. Models can be customised to reflect a firm’s specific risk appetite, restricted lists, and internal policy requirements.

Unified Cross-Channel Surveillance. DCI Internal Chat does not exist in isolation. The same traders and operations staff communicating within DCI are also using Bloomberg IB, email, Microsoft Teams, and other channels — often about the same trades and positions. Shield ingests DCI Internal Chat data into the same unified compliance platform as every other channel, enabling compliance teams to correlate in-platform messaging with communications from all other sources. This cross-channel context is essential for accurate misconduct detection and complete trade reconstruction.

Data Governance and Chain of Custody. Shield’s DCI Internal Chat connector preserves a complete, verifiable chain of custody from ingestion through archiving and retrieval. Every stage of data handling is logged, auditable, and reportable — giving compliance officers and legal teams the confidence that DCI Internal Chat records are admissible, complete, and unaltered throughout their lifecycle.

Regulatory Coverage

DCI Internal Chat communications are classified as business records subject to capture, retention, and surveillance requirements across multiple regulatory frameworks. The Shield DCI Internal Chat connector supports compliance with:

  • SEC Rules 17a-3 and 17a-4 — requiring broker-dealers to capture, preserve, and produce records of all communications related to their business, stored in WORM-compliant, non-rewriteable format with an audit trail, for a minimum of six years — applicable to DCI Internal Chat communications generated in connection with regulated trading activity.
  • FINRA Rules 4511 and 3110 — requiring member firms to archive all communications relating to their business as such — including internal communications between trading desk staff — with written supervisory procedures, supervision requirements, and full audit trail capability in place.
  • MiFID II Article 16(7) and Market Abuse Regulation (MAR) — requiring investment firms to record and retain electronic communications related to orders and transactions for a minimum of five years, with trade reconstruction capability within three days, and to monitor communications for indicators of insider trading, front-running, and market manipulation — applicable to DCI Internal Chat communications in connection with trading activity.
  • CFTC Regulation 1.35 and 17 CFR § 23.202 — requiring swap dealers, major swap participants, and futures commission merchants to retain records of all communications relating to commodity interests and swap transactions as part of a complete audit trail for trade reconstruction, including internal platform communications.
  • FCA Rules (SYSC 10A and MAR) — requiring FCA-regulated firms to record and retain relevant electronic communications for a minimum of five years, and to implement effective surveillance arrangements to detect and prevent market abuse — applicable to DCI Internal Chat communications by regulated trading desk staff.
  • GDPR and applicable data privacy regulations — Shield’s architecture supports data residency requirements and privacy-compliant data handling across jurisdictions, enabling firms to meet GDPR obligations alongside their financial services recordkeeping requirements.

Other Related Connectors

Shield’s connector portfolio spans the full range of eComms channels and trading platforms used across regulated financial institutions. All connectors feed into a single unified compliance platform — so DCI Internal Chat data is always reviewed in the context of every other channel your trading desks use.

Frequently Asked Questions

Are internal trading platform communications in scope for regulatory recordkeeping?

Yes. The SEC, FINRA, MiFID II, FCA, and CFTC require firms to retain all communications relating to their business — including internal communications between trading desk staff, not only external client or counterparty communications. DCI Internal Chat messages between traders about orders, positions, pricing decisions, and trading strategy are within the scope of these recordkeeping obligations. Firms that capture Bloomberg IB and email while leaving internal trading platform chat unarchived have a compliance gap that regulators increasingly expect to be addressed.

Does Shield capture all DCI Internal Chat communication types?

Shield captures one-to-one DCI Internal Chat conversations, group chats, and desk-level channel communications — alongside the full metadata layer. The specific communication types captured are configurable to match the firm’s compliance scope definition and the DCI deployment in use.

Which regulations does the Shield DCI Internal Chat connector help firms comply with?

The Shield DCI Internal Chat connector supports compliance with SEC Rules 17a-3 and 17a-4, FINRA Rules 4511 and 3110, MiFID II, Market Abuse Regulation (MAR), CFTC Regulation 1.35 and 17 CFR § 23.202, FCA SYSC 10A, and applicable data privacy regulations including GDPR.

Can DCI Internal Chat data be reviewed alongside Bloomberg IB and other channels during an investigation?

Yes, and this is central to the compliance value of the Shield DCI Internal Chat connector. Trading misconduct and coordinated activity rarely stay within a single platform — a position discussion may begin in DCI Internal Chat, continue over Bloomberg IB, and be confirmed via email or voice. Shield ingests DCI Internal Chat into the same unified compliance archive as every other channel, enabling compliance teams to reconstruct the complete trading communication sequence in a single workflow.

How does Shield handle the high volume of DCI Internal Chat messages generated by active trading desks?

Shield’s AI-powered surveillance engine is built for enterprise-scale financial communications data. Rather than surfacing every message for manual review, Shield applies multi-layered AI models to prioritise the messages that carry genuine compliance risk — dramatically reducing the volume of alerts that reach compliance teams while ensuring that genuine risk signals are identified accurately.

How should firms handle GDPR and privacy obligations for DCI Internal Chat data?

DCI Internal Chat data captured for compliance purposes is subject to GDPR obligations — including requirements around lawful basis for capture, employee notification, data subject access rights, and retention limitation. Shield’s architecture supports privacy-compliant handling of DCI Internal Chat data, including configurable retention periods and data residency controls.

Related Terms