Skip to content
Integrations Global Relay
Global Relay
+
SendSafely
Global Relay integration

Supervise SendSafely communications just like email and messaging.

Automatically archive secure file exchanges in Global Relay. Using SendSafely Actions and the Global Relay Open Connector, encrypted files are exported, decrypted and preserved alongside email and chat in a unified, tamperproof archive. Ready for FINRA, SEC, MiFID II, and electronic communications supervision reviews.

Request Demo See How It Works Compliance overview
17a-4
SEC supervision rule
FINRA
electronic comms ready
OpenPGP
end-to-end encryption
100 GB
max file size
For regulated financial services

Secure file exchange, supervised like the rest of your electronic communications

Your reviewers shouldn't have to chase down attachments in a separate system.

Broker-dealers, registered investment advisors, and asset managers send sensitive files every day — deal documents, statements, KYC paperwork, audit responses. SendSafely encrypts those files end-to-end with OpenPGP. The Global Relay integration exports a copy of every send into your Global Relay archive so the same supervision workflow that covers email, instant messaging, and chat also covers your secure file exchanges.

FINRA Rule 3110 SEC Rule 17a-4 SEC Rule 17a-3 GLBA Safeguards Electronic comms supervision
Compliance archive — Q1 2026
archive.example/sendsafely
Captured SendSafely package 2026-04-12 09:14 UTC
Quarterly statements — institutional account
Sender
Registered Representative
Wealth management desk
Recipient
External counterparty
Verified via SMS passcode
3 files · 18.4 MB total End-to-end encrypted · Expires in 14 days · Identity verification on
Sealed
One pipeline. One archive.

Connect every channel. Secure the data. Archive the record.

Email. Helpdesk. AI chat. Wherever sensitive data moves through your organization, SendSafely is the secure pipeline. Global Relay is the supervised record.

Outlook + GmailSecure email
ZendeskSalesforce
Zendesk · SalesforceHelpdesk + Service Cloud
Intercom
Intercom · FreshworksConversation platforms
HALO for AI agentsAda · Forethought · Fin
Jira
Jira · SlackTicketing + workflow
REST API + DropzoneYour own apps
SendSafely
Encrypted infrastructure
end-to-end split-key data sovereignty
Global Relay
Supervised record
SEC 17a-4 FINRA 3110 MiFID II electronic comms
Sensitive data moves through one encrypted pipeline. The supervision record of every send lands in one archive. Your reviewers stop chasing attachments across systems.
What supervisors see

A SendSafely package, captured the way Global Relay captures email

SendSafely Workspace uploads, outbound sends, inbound file collection, file metadata and recipient details - all archived. Reviewers query and search  the same way they handle any other archived message.

Compliance archive — package detail
archive.example/sendsafely/pkg/REDACTED
Channels
Email182k
Chat94k
SMS7.2k
SendSafely1.4k
Filters
Last 30 days
Registered reps
Flagged for review
Captured SendSafely package 2026-04-12 09:14:08 UTC pkg_id · REDACTED
Signed onboarding documents — institutional account opening
Sender
Registered Representative
Authenticated via SAML SSO
Recipient
External counterparty
Verified via SMS one-time passcode
4 files · 28.6 MB total End-to-end encrypted · OpenPGP · Expires in 14 days · SMS verification on
Sealed
Event timeline
09:14:08 Package finalized — 4 files encrypted on sender's device PACKAGE_EVENT
09:14:09 Notification sent — secure link delivered to recipient PACKAGE_EVENT
09:22:41 Identity verified — recipient passed SMS one-time passcode USER_EVENT
09:23:02 File downloaded — Account_Agreement.pdf (4.2 MB) PACKAGE_EVENT
09:23:18 File downloaded — W9_signed.pdf, KYC_supporting.zip PACKAGE_EVENT
09:24:55 Access closed — all files retrieved, link sealed for archive PACKAGE_EVENT

Illustrative archive view. Field names and counts shown are stylized for clarity.

How it works

Encrypted on SendSafely. Decrypted in your environment. Archived in Global Relay.

A connector deployed in your environment — not SendSafely’s — retrieves each encrypted package, decrypts it using a key only your connector holds, and forwards the plaintext to Global Relay for archive ingestion. SendSafely never sees the unencrypted file.

1
User sends
Sender encrypts a file on their device with OpenPGP via SendSafely's web app, Outlook plug-in, Gmail extension, or a connected helpdesk.
2
Your connector pulls the encrypted file
A connector that runs in your environment — not SendSafely’s infrastructure — retrieves the encrypted package from SendSafely. The connector holds a decryption key that SendSafely does not have access to.
3
Connector decrypts locally and archives
Decryption happens entirely within your environment. The connector decrypts the file locally and forwards the plaintext to Global Relay for archive ingestion. SendSafely never sees the unencrypted content.
4
Supervisors review
Compliance teams search, sample, flag, and produce on SendSafely records from inside Global Relay — same workflow they already use for the rest of their electronic communications.

Supervision copy delivery is configured by SendSafely Customer Success and your Global Relay administrator. See SendSafely support for current connector options.

Split-key architecture

Files are encrypted end-to-end. Decryption happens in your environment — not SendSafely’s.

Every file is encrypted on the sender's device with OpenPGP before it reaches SendSafely. Nobody, not even SendSafely, can read the contents. Decryption only happens inside the connector you deploy in your own environment, using a key you control. SendSafely never handles the plaintext.

SendSafely is audited annually and maintains the certifications regulated industries require. BAAs are available on Enterprise plans. Compliance support for FINRA and SEC workflows is part of the Enterprise plan.

Certifications
SOC 2 Type 2 HIPAA PCI DSS GDPR CCPA FINRA / SEC
Architecture
Client-side OpenPGP
Files are encrypted in the browser or plug-in before they ever leave the sender's device.
Split-key architecture
The decryption key is split so no single party—including SendSafely—can decrypt file contents on its own.
Decrypted in your environment, not ours
The connector runs in your infrastructure and holds a decryption key SendSafely never has. Files are decrypted there, then forwarded to Global Relay. SendSafely handles only the encrypted version.
Get started

Bring secure file exchange into your electronic communications supervision program.

Forward a supervision copy of every SendSafely send into Global Relay and give your reviewers one place to search, sample, and produce on every regulated channel — including end-to-end encrypted file transfer. It is the archival half of the financial services stack; the security overview covers what the encryption itself guarantees.