SenseBridge by WooSense for WooCommerce is the secure bridge between your store and the WooSense iOS app. It gives store administrators a focused WordPress control panel and access to everyday WooCommerce operations away from the desk.<\/p>\n\n
Connect WooSense to:<\/p>\n\n
The responsive admin interface covers onboarding, pairing, settings, diagnostics, privacy controls, and guided configuration.<\/p>\n\n
Download WooSense for iOS:\nhttps:\/\/apps.apple.com\/us\/app\/woosense\/id6765742419<\/p>\n\n
Android support is planned for a future release.<\/p>\n\n
This plugin connects to the services listed below. It does not send data to them merely because the plugin is activated: WooSense requests start only after an administrator initiates pairing or connects the store, Firebase requests occur when push delivery is configured and triggered, and security diagnostics are optional and disabled by default. Pairing QR images are generated locally in the administrator's browser and do not use an external QR service.<\/p>\n\n
Service provider: WooSense.pl, https:\/\/woosense.pl<\/p>\n\n
What it is used for:\n* pairing a WooCommerce store with a WooSense account and the WooSense mobile app;\n* synchronizing store data with the WooSense SaaS service after pairing, including order and customer summaries needed by the mobile app;\n* optionally receiving security diagnostics, only when the site owner enables this setting in WooSense settings.<\/p>\n\n
Data sent and when:\n* during magic-link pairing: claim token, public store URL, store name, WordPress site ID, plugin version, and a generated plugin API key;\n* during authenticated synchronization after pairing: WooSense store ID and sync token; order ID, order number, customer ID, status, currency, and total; customer ID, name, and email address. The initial snapshot contains up to the 25 most recent orders, then changed orders and customers are sent when relevant WooCommerce events occur;\n* for store push delivery after pairing: WooSense store ID and sync token, event type, notification title and body, public store URL, and event-specific metadata. Depending on the event this can include order\/customer\/cart\/conversation identifiers, customer display name and email address, cart total\/currency\/item count and recovery URL, or chat sender name and message preview;\n* only when the site owner explicitly enables security alerts: alert type, affected plugin file path or a hashed suspicious identifier, public store URL, timestamp, and requesting IP address.<\/p>\n\n
Security diagnostics are disabled by default and must be enabled by the site owner.<\/p>\n\n
The WooSense service is a required SaaS component for pairing, synchronized mobile data, and backend-routed push delivery. Local WooCommerce features can load without pairing, but the mobile connection cannot work without this service.<\/p>\n\n
The plugin contains no locally locked code. WooSense is a separate SaaS service that may offer free and paid plans: https:\/\/woosense.pl\/#pricing.<\/p>\n\n
Terms of Service: https:\/\/woosense.pl\/regulamin\/\nPrivacy Policy and Data Processing Terms: https:\/\/woosense.pl\/en\/regulamin<\/p>\n\n
Service provider: Google Firebase, https:\/\/firebase.google.com<\/p>\n\n
What it is used for:\n* delivering push notifications to mobile devices connected to the store.<\/p>\n\n
Data sent and when:\n* only when a push notification is sent through the direct Firebase integration: the configured Firebase server key in the authorization header, target device token, notification title and body, sound\/priority settings, and supplied event metadata. Depending on the event, metadata can contain WooCommerce object IDs, customer name\/email, cart value\/currency\/item count\/recovery URL, chat sender name\/message preview, and public store URL.<\/p>\n\n
Firebase is optional. If no Firebase server key and device token are configured, this direct integration does not send requests.<\/p>\n\n
Terms of Service: https:\/\/firebase.google.com\/terms\nPrivacy and Security: https:\/\/firebase.google.com\/support\/privacy<\/p>\n\n
The plugin stores some data locally in WordPress\/WooCommerce:<\/p>\n\n
Visitor analytics and abandoned-cart tracking are disabled by default and require separate administrator opt-ins. When visitor analytics is enabled, the plugin checks the WordPress consent API for WordPress administrators can export and erase locally stored plugin data through Tools > Export Personal Data and Tools > Erase Personal Data. Site owners should adapt the suggested text under Settings > Privacy to their legal basis, retention policy, and consent solution.<\/p>\n\n QR Code Generator for JavaScript by Kazuhiko Arase is bundled in uncompressed form for local pairing-code generation.<\/p>\n\n License: MIT\nUpstream source: https:\/\/github.com\/kazuhikoarase\/qrcode-generator\/tree\/83b7e8fe3fddd3b0368dbafd6ce56995bd25e3c8\/js<\/p>\n\n\n Yes. Store pairing and mobile management features require the WooSense iOS app. Android support will return soon.<\/p><\/dd>\n You can use WooSense with this plugin to work with orders, products, customers, notifications, analytics, and connected store data.<\/p><\/dd>\n Yes. WooSense uses its external service for store pairing, authenticated sync, mobile delivery, and selected notification flows. Details are listed below in the External services section.<\/p><\/dd>\n Not yet. The current public release is focused on the WooSense iOS app. Android support is planned for a future release.<\/p><\/dd>\n The WordPress.org Plugin Directory delivers public updates through the standard WordPress update flow.<\/p><\/dd>\n No. Visitor analytics, abandoned-cart tracking, and security diagnostics are disabled by default and must be enabled separately by the site owner.<\/p><\/dd>\n No. The plugin does not load Google Analytics and does not record wp-admin usage analytics.<\/p><\/dd>\n No. It does not send plugin-usage analytics to WooSense. Requests to the WooSense API are limited to the mobile service described below and begin only after an administrator explicitly starts pairing or connects the store.<\/p><\/dd>\n\n<\/dl>\n\n\nstatistics<\/code> consent where that API is available. It then uses sensebridge_visitor_id<\/code> for up to 90 days and sensebridge_session_id<\/code> for up to 24 hours. Plugin visitor-session, abandoned-cart, and customer-chat database rows are removed after 180 days; developers can change this interval with the sensebridge_personal_data_retention_days<\/code> filter.<\/p>\n\nBundled libraries<\/h3>\n\n
\n
\n
Do I need the mobile app?<\/h3><\/dt>\n
What can I manage from the app?<\/h3><\/dt>\n
Does the plugin use an external service?<\/h3><\/dt>\n
Does the plugin work with Android?<\/h3><\/dt>\n
How are plugin updates delivered?<\/h3><\/dt>\n
Are analytics and security diagnostics enabled automatically?<\/h3><\/dt>\n
Does the plugin use Google Analytics or track wp-admin usage?<\/h3><\/dt>\n
Does the plugin send usage telemetry to WooSense?<\/h3><\/dt>\n
3.1.0<\/h4>\n\n
\n
3.0.8<\/h4>\n\n
\n
3.0.7<\/h4>\n\n
\n
2.0.4<\/h4>\n\n
\n