SMS and text marketing

The text message that proves your phone number left the site

SMS plugins can use a phone number from a checkout form, an existing order, or a subscribe form. Some send through a gateway the shop chooses; others use a named SMS or marketing service. Saving a number in WordPress does not mean it stays there: sending a text through an outside gateway passes the recipient number to that service. This table describes the setups below; your settings can change what is saved and sent. Abandoned-cart email capture and newsletter email plugins have separate pages.

Based on plugin documentation, not tests of your site. Your settings can change what is saved. This is not legal advice or a compliance rating.

Scan your site for third-party requests

How we group SMS plugins

We compare the phone-number sources and SMS services in the named setups. Some plugins use a gateway the shop chooses; others connect to a specific service. Both can send the recipient number outside WordPress. Outside browser hosts are listed separately from server transfers. Consent timing has not been tested, and vendor data retention has not been assessed.

How phone numbers reach an SMS service

A gateway the shop chooses

WSMS saves subscribe-form numbers in WordPress. WC APG and Texty use the billing phone already on a WooCommerce order. They send texts through a gateway the shop configures. An outside gateway receives the recipient number in a server request, even when the number is stored in WordPress first. The host column covers browser requests only.

A named SMS or marketing service

Omnisend, SMS Alert, and BulkGate connect to their named services. The setups below can send phone numbers from the store to those services. Omnisend also loads a visitor script from omnisnippet1.com; that script host alone does not show where a phone number is submitted. A server transfer is different from a visitor browser request.

Before consent

Consent timing is not tested here. An agreement checkbox in a plugin is not a test of your site. The Before consent column is not a scan finding. The site scan linked below checks for third-party requests on your pages; it does not access your WordPress database.

SMS plugins

No paid placement. Plugins with a shop-selected gateway appear first, then plugins connected to a named service, then plugins not yet reviewed. Names are alphabetical within each group.

PluginDocumented behaviorDocumented outside browser hostsHow long data is keptBefore consentLinksSource
Texty

This row covers Texty WooCommerce order texts. The plugin uses the billing phone already on the order and sends through a gateway the shop set up, such as Twilio. A pause switch and a company-name footer can be on. Consent timing is not tested here.

Stored in WordPress; sent via a chosen gatewayNo outside browser host documented for this setup. Server sends to SMS services are separate.Not assessedNot tested
  • None
WC APG SMS Notifications

This row covers WC APG SMS Notifications for WooCommerce order texts. The plugin uses the billing phone already on the order and sends through a gateway the shop selected. That send is a server request, so this row does not list a visitor host. Consent timing is not tested here.

Stored in WordPress; sent via a chosen gatewayNo outside browser host documented for this setup. Server sends to SMS services are separate.Not assessedNot tested
  • None
WSMS

This row covers the WSMS subscribe form. Name and phone number are saved in WordPress. Texts later go through a gateway the shop set up. An unsubscribe link can run on the site. An agreement checkbox can be on. Consent timing is not tested here.

Stored in WordPress; sent via a chosen gatewayNo outside browser host documented for this setup. Server sends to SMS services are separate.Not assessedNot tested
  • None
BulkGate SMS Plugin for WooCommerce

This row covers BulkGate SMS Plugin for WooCommerce when a BulkGate account is connected. The store sends texts through BulkGate. Visitor scripts load from the store, so this row does not list a visitor host. Consent timing is not tested here.

Connected to a named SMS or marketing serviceOutside browser hosts not verifiedNot assessedNot tested
  • None
Omnisend

This row covers the Omnisend plugin when it is connected. Visitor pages load a launcher from omnisnippet1.com. Omnisend can collect phone numbers for texts. Newsletter email capture is a different page. Consent timing is not tested here.

Connected to a named SMS or marketing serviceomnisnippet1.comNot assessedNot tested
  • None
SMS Alert

This row covers SMS Alert checkout phone capture. Checkout phone, email, and name can be saved to WordPress as those fields change, then texts are sent through SMS Alert. Abandoned-cart email recovery is a different page. Consent timing is not tested here.

Connected to a named SMS or marketing serviceOutside browser hosts not verifiedNot assessedNot tested
  • None

What this table does and does not prove

This table describes the named SMS setups, not requests measured on your site. Numbers stored in WordPress can still be sent to an outside SMS gateway. The host column covers documented visitor browser requests, not server API destinations, and a script host does not by itself establish a phone-number submission endpoint. Other page requests are not covered. Abandoned-cart email capture and newsletter email plugins have separate pages. Plugins marked Not reviewed have not been assessed. Consent timing has not been tested, and vendor data retention has not been assessed. The linked site scan checks for third-party browser requests; it does not access your WordPress database or verify server-to-server SMS transfers.

Documentation snapshot: Oct 6, 2026. Sources are linked in each reviewed row.

Related pages

Scan your site for third-party requests

/wp-sms-plugin-privacy