Shield provides a communications compliance platform for financial institutions. It brings captured messages and calls into an environment for retention, search, review and investigation. For a brokerage, the practical use is oversight of employee and client communications, with tools that connect the underlying records to potential conduct issues and supervisory actions.[1]
Its energy and commodities offering explicitly covers conversations involving traders, brokers, schedulers and operational teams across physical and financial markets. This illustrates its role alongside transaction records: communications supply context for investigations into manipulation, collusion or inappropriate information sharing. The advertised functions support compliance teams’ analysis and workflows; they do not make every detected concern a proven violation.[10]
Services and product scope
Sections ↑Core products
| Product | Operational role |
|---|---|
| Shield Archive | Retain and retrieve communications under configured records policies.Source 3 |
| Shield Discover | Search, collect and organise evidence for cases.Source 4 |
| Shield Surveillance | Identify potential communications risks for investigation.Source 5 |
| Shield Supervision | Manage first-line review and escalation.Source 6 |
| Voice | Make recorded conversations searchable and reviewable.Source 7 |
| AmplifAI | Assist investigations and alert handling with governed AI agents.Source 8 |
Data Engine ingestion controls
| Stage | Published capability |
|---|---|
| Capture | Native connectors and APIs across more than 100 sources.Source 2 |
| Normalisation | Content and metadata brought into a common model.Source 2 |
| Reconciliation | Ingested records checked against the source.Source 2 |
| Exceptions | Gaps and anomalies made visible for follow-up.Source 2 |
Archive retention and discovery
| Function | Published capability |
|---|---|
| Preservation | Original and enriched communications retained.Source 3 |
| Storage | Encrypted, immutable storage.Source 3 |
| Governance | Retention policies and legal holds.Source 3 |
| Investigation | Traceability, search and retrieval.Source 3 |
| Migration | Historical archives can join live records.Source 3 |
Surveillance and first-line supervision
| Area | Published role |
|---|---|
| Surveillance | Risk scenarios, custom lexicons and multiple AI methods.Source 5 |
| Review coverage | Multilingual and voice content with sampling and analysis.Source 5 |
| Supervision | First-line review groups and business-specific workflows.Source 6 |
| Escalation | Links supervisory review with investigation/surveillance.Source 6 |
| Organisation changes | Reviewer groups and permissions can follow changes in hierarchy.Source 6 |
Control Room dependencies
| Input or workflow | Purpose |
|---|---|
| Personnel data | Identify employees and organisational relationships.Source 9 |
| Restricted lists | Identify the relevant instruments and information constraints.Source 9 |
| Wall-crossing data | Support monitoring of information barriers.Source 9 |
| Communications access | Give control-room teams relevant conversation evidence.Source 9 |
Voice investigation
| Capability | Published function |
|---|---|
| Transcription | Convert recorded speech into searchable text.Source 7 |
| Synchronized playback | Inspect the recording alongside its transcript.Source 7 |
| Speaker separation | Distinguish speakers in the investigation view.Source 7 |
| Accuracy context | Language, audio quality and financial terminology affect results; clean-test figures are not a guarantee for difficult calls.Source 7 |
AmplifAI and human oversight
| Capability | Published role |
|---|---|
| Noise reduction | Agent-assisted reduction of irrelevant alerts.Source 8 |
| Language and explanation | Support interpreting communications and risk context.Source 8 |
| Shiela | Natural-language investigation assistance.Source 8 |
| Alert Closure Agent | Can close alerts where it establishes no risk, under configurable governance.Source 8 |
| Human review | Thresholds, overrides and review responsibility remain part of the operating design.Source 8 |
Capture, integrations and data access
Sections ↑API Hub: dated release status
| API/function | March 2025 announcement |
|---|---|
| Legal hold and case management | Existing API suite described.Source 11 |
| Alert/hit extraction | New structured data access described.Source 11 |
| JWT | Access-control mechanism.Source 11 |
| Audit log and communications metadata | Described as forthcoming; not assumed live from that announcement.Source 11 |
| Consumers | Business intelligence, analytics and case-management systems.Source 11 |
Pricing and commercial terms
Sections ↑The reviewed public pages direct prospective customers to a tailored discussion and demo, without a standard subscription price list. Request a quote that separates the selected products, communication sources, monitored population, retention volumes, migration, AI functions and support. Contract length, renewal terms and any minimum commitment need to come from the proposal.[17]
Archive and cloud cost boundaries
| Item | Published position |
|---|---|
| Export and exit fees | Archive advertises none.Source 3 |
| Data ownership | Customer ownership of communications data advertised.Source 3 |
| Subscription/storage/migration | No-export-fee wording does not make these services free.Source 3 |
| AWS contract | Some arrangements let customers own/manage their Amazon hosting contract and use existing commitments.Source 14 |
Deployment, migration and security
Sections ↑Archive tiering introduced in March 2026
| Tier or control | Published behaviour |
|---|---|
| Hot records | Frequently accessed material stays readily searchable.Source 12 |
| Cold records | Metadata remains visible.Source 12 |
| Restore | Cold material can be temporarily restored for review.Source 12 |
| Migration control | Retention and legal holds must be preserved across storage/migration workflows.Source 12 |
Deployment and security model
| Control | Provider disclosure |
|---|---|
| Infrastructure | AWS SaaS, one or more regions depending on deployment.Source 14 |
| Customer environment | Isolated AWS environment and region controls.Source 15 |
| Privileged access | Temporary access subject to approval and audit trail.Source 15 |
| Assurance | Annual SOC 2 Type II audits and independent penetration tests.Source 15 |
Support and operating relationships
Sections ↑Official contact routes
Scope Knowledge-base route linked from Shield’s official website; access may depend on customer credentials.
Scope Official route requesting further security and privacy documentation.
For energy and commodities clients, Shield also describes hands-on onboarding, focused go-live support and a global team working across time zones. Those statements indicate an operating model, not a published round-the-clock incident SLA. Establish the support obligations that apply to the specific rollout and critical communications channels.[10]
Service and implementation relationships
| Relationship | Published scope |
|---|---|
| Customer success | Dedicated manager, tailored plan and quarterly business reviews.Source 16 |
| Go-live | Hands-on onboarding and focused launch support described for energy/commodities.Source 10 |
| PwC UK | September 2025 collaboration covers strategy, operating model, data sourcing, tuning, testing and governance.Source 13 |
| Commercial boundary | Professional services and incident SLAs need the applicable agreement.Source 13Source 16 |
Permissions and compliance responsibilities
Sections ↑Shield’s January 2026 privacy policy names Shield Financial Compliance Ltd and covers website, platform and customer-contact information. It describes intra-group processing arrangements and contractual protections for certain international transfers. Employee communications create a separate implementation question: the institution should establish its authority to capture, retain and review each channel and document the applicable notices, restrictions and access controls.[19]
Archive is marketed to support records obligations across jurisdictions, including US securities and derivatives frameworks and MiFID II. Product alignment is not a regulator’s approval of a firm’s implementation. The institution must determine the applicable retention periods, evidence requirements, legal holds and supervisory processes, then validate that its configuration implements them.[3]
Security statements about SOC 2, ISO alignment, GDPR and DORA should be assessed within their actual scope. Audit evidence and contractual commitments can inform vendor diligence; a marketing statement is not a financial-services permission or a guarantee that a customer satisfies every obligation.[15]
Company and investment background
Sections ↑Legal and operating identity
| Item | Published evidence |
|---|---|
| Policy entity | Shield Financial Compliance Ltd.Source 19 |
| Co-founders | Shiran Weitzman, Ofir Shabtai and Eran Noam.Source 18 |
| Published offices | Tel Aviv area, London, New York and Lisbon.Source 17 |
| Contract | Relevant affiliate and service scope belong in the signed agreement.Source 19 |
- Operator
- Shield Financial Compliance Ltd; contractual affiliate to be confirmed
- Service scope
- Communications archiving, surveillance, supervision and investigation support.
- Customer types
- Financial institutions; Brokerage and trading firms; Energy and commodities businesses
- Delivery
- SaaS; API
- Pricing publication
- Quote only
- Platforms
- Shield Archive; Shield Discover; Shield Surveillance; Shield Supervision; Voice; AmplifAI
- Integrations
- Native communications connectors; API Hub; HR and restricted-list data; AWS
- Pricing scope
- Tailored commercial discussion; no public standard tariff in the reviewed pages.
- Implementation
- AWS deployment with source integration, historical migration and customer-specific controls.
- Support
- Dedicated customer success and linked support portal; incident terms are contractual.
- Permissions and regulatory scope
- Technology supporting communications and records obligations; institutional compliance remains implementation-specific.
Provider metadata checked 26 Oct 2026Source 11Source 3Source 14Source 17Source 9Source 10Source 2Source 1Source 19Source 16
Sources & further reading
- Platform overview Shield · Accessed 21 Oct 2026
- Data Engine Shield · Accessed 21 Oct 2026
- Shield Archive Shield · Accessed 21 Oct 2026
- Shield Discover Shield · Accessed 21 Oct 2026
- Communications Surveillance Shield · Accessed 21 Oct 2026
- Communication Supervision Shield · Accessed 21 Oct 2026
- Voice Shield · Accessed 21 Oct 2026
- AmplifAI Shield · Accessed 21 Oct 2026
- Control Room Shield · Accessed 21 Oct 2026
- Energy and commodities trading Shield · Accessed 21 Oct 2026
- API Hub expansion Shield · 12 Mar 2025 · Accessed 21 Oct 2026
- Archive modernization release Shield · 26 Mar 2026 · Accessed 21 Oct 2026
- PwC UK collaboration Shield · 18 Sep 2025 · Accessed 21 Oct 2026
- Shield on AWS Shield · Accessed 21 Oct 2026
- Security Shield · Accessed 21 Oct 2026
- Customer success Shield · Accessed 21 Oct 2026
- Contact and offices Shield · Accessed 21 Oct 2026
- Company and leadership Shield · Accessed 21 Oct 2026
- Privacy Policy Shield · 13 Jan 2026 · Accessed 21 Oct 2026
This profile reports dated public information, including provider-published services and terms. It does not independently test or guarantee service delivery, integrations or performance. Inclusion is not an endorsement. Permissions and protections apply only to the named legal entity, service and client category; check the current official records and your contract.