Privacy and data handling

Recommendation and reporting data stays in your store

The GoScript Smart Cart Recommendations WordPress plugin processes and stores recommendation calculations, cache data, click statistics, attribution records, and reporting data locally in your WordPress and WooCommerce installation.

This gives your store a focused way to power Cart discovery and review performance without sending recommendation or reporting data to GoScript or another external analytics service.

What the local recommendation system uses

To deliver Cart recommendations and their local reports, the plugin works with your WooCommerce product, Cart, and qualifying order-history data. It can store the recommendation result cache, valid click records, temporary attribution records, and the statistics used by the Reports page and Dashboard widget.

Recommendation contextCart products, catalogue conditions, and qualifying WooCommerce history help shape useful suggestions.

Local performance insightClick, attribution, and report data stays close to the store where your team can review it.

These local records support the specific Cart recommendation and reporting features described in the plugin-not a separate external analytics platform.

How click-to-purchase attribution handles visitor context

For attribution, the plugin uses a temporary one-way HMAC visitor identifier derived locally from the visitor IP address and user agent. It does not store raw IP addresses or raw browser user-agent strings for this feature.

The plugin also does not create a dedicated analytics cookie for recommendation attribution. Attribution records expire, and a daily scheduled cleanup removes expired records.

What is not sent for recommendation analytics

The plugin does not send recommendation calculations, recommendation clicks, attributed orders, attributed revenue, or reporting data to GoScript. It also does not send that data to another analytics service as part of its recommendation and reporting features.

This keeps your Cart recommendation reporting grounded in the WordPress and WooCommerce environment where the activity takes place.

Licensing is a separate, limited service interaction

Licensing is distinct from recommendation analytics. Activating, checking, or deactivating a license communicates the product key, site URL, installation identifier, and license credentials with the GoScript licensing service so the plugin can activate and validate its license state.

The actual license key is sent when you activate or replace a license and is not retained after activation. The local entitlement state is integrity-protected with an HMAC.

Data lifecycle and runtime changes

Recommendation cache data follows the duration you configure. Attribution records are short-lived and removed after expiry. Stored settings and reporting data remain available if a trial expires, a license is revoked, or a paid license reaches expiry, so you do not need to rebuild your Cart strategy from scratch when runtime access changes.

A valid license restores the plugin runtime according to its license state while preserving the work you have already done in WordPress.

Use local insight with confidence

Keeping recommendation and reporting data local helps you focus on the Cart experience and performance signals that matter to your store. You can refine product discovery, review attributable activity, and maintain direct control over the settings and data that support the plugin.