Surge

Subprocessors

Last updated

When Surge Communications Inc processes personal data on behalf of its customers, it engages the subprocessors listed below to help deliver the Surge service. The table describes each vendor's purpose and processing locations.

Surge requires vendors that handle customer data to follow contractual security requirements. For details on how Surge vets and monitors these vendors, see the Security Overview.

Telecommunications providers act on their own behalf, independently of Surge and its customers, when they transmit and deliver communications over their networks. The table below covers only vendors acting as subprocessors.

VendorPurposeProcessing location
Amazon Web ServicesApplication hosting, databases, caching, storage for message attachments and call recordings, and attachment delivery.Amazon S3 origins are in Northern Virginia, United States. CloudFront may deliver attachments through U.S. and international edge locations.
CloudflareDNS and reverse proxy for Surge’s public service endpoints.Global edge network.
ResendTransactional email delivery and receipt.United States for primary processing and storage. Outbound email routing depends on the sending configuration.
PylonCustomer support via chat and email, plus registration follow-up.United States for hosting.
PostHogProduct analytics and session replay.Northern Virginia, United States, for analytics ingestion and storage. Proxy traffic may pass through global edge locations.
SentryError reporting and performance monitoring.United States for browser data ingestion. Server data ingestion depends on deployment configuration.
Slack (Salesforce)Internal support and operational alerts.United States for storage by default. Workspace data residency settings apply to certain data at rest.
TypeSafe AISMS content moderation and review of carrier registration submissions.United States.
OpenAIPhone number transfer support and review of carrier registration submissions.United States.