Skip to main content

Learn How Swym Uses Cookies and Local Storage and How Our Apps are GDPR Compliant

User privacy is an important issue in today’s increasingly digital world. The EU’s General Data Protection Regulation (GDPR) sets the tone for privacy regulations that are becoming more stringent around the world. At Swym, user privacy has always been a top priority. To protect merchants and shoppers, our platforms are fully GDPR compliant. You can read more about this in our blog post on the topic here.

This document covers what you need to know about how Swym uses cookies and local storage, and why those cookies and local storage are necessary.

How does Swym use browser cookies and local storage?

Swym uses cookies and local storage properties on the shopper’s browser to allow our apps to work correctly. These cookies and local storage also let shoppers save their preferences to create a better shopping experience. The cookies and local storage Swym uses can be classified into two main categories, which we’ll discuss below.

Necessary Cookies

Necessary cookies are required for the application to function. They may contain personally identifiable information.

Without necessary cookies, Swym apps will not be able to function. By default, these cookies are not set until the shopper has responded to your store's cookie consent banner and Shopify's Customer Privacy API has confirmed that consent has been given. Only once consent is confirmed does the application load and these cookies become active.

Note: What a shopper sees while consent is undecided depends on which wishlist button your theme uses. The classic (non-Advanced) Add to Wishlist button stays hidden until consent is confirmed, and is removed from the page entirely if the shopper explicitly declines. The Advanced Product Detail Page button, Advanced Collections button, and the header wishlist icon behave differently — they remain visible either way, and prompt the shopper for consent at the moment they click, rather than hiding.

Below is a list of the necessary cookies utilized by our apps:

Cookie Name

Description

Duration

swym-pid

Unique identifier to track merchants and their wishlist settings.

1 year

swym-swymRegid

This cookie is used to store an encrypted version of the user's device ID and information on the user's session. The ID links the user's Swym app-specific content to their device. It also retrieves those contents from our cloud storage whenever the user attempts to access Swym apps.

1 year

swym-session-id

This is a general-purpose platform session cookie used to maintain an anonymous user session.

30 minutes

swym-o_s

Related to swym app versioning systems.

30 mins

swym-isCheckedForMisauth

An internal record used to avoid repeating a one-time account-authentication cleanup step.

1 year

Preference Cookies and Local Storage

Unlike necessary cookies, preference cookies and local storage properties aren’t required for Swym apps to function. However, they support additional functionalities that enhance the user’s experience and make the apps perform better. Preference cookies and local storage properties support caching, authentication, instrumentation, and system preferences. They also store customer preferences and may include third-party cookies from analytics or email service providers.

Information stored in preference cookies and local storage properties is anonymized. This means these cookies and local storage properties cannot be used to identify an end user. However, the information can be used to help optimize the shopper’s journey by tailoring their app experience based on their preferences.

Below is a list of the preference cookies and local storage properties that help bring additional functionality to Swym’s apps:

Preference Cookies table:

Cookie

Description

Duration

swym-email

This stores the email address when the shopper logs into the store or when the shopper authenticates their wishlist or subscribes for a back-in-stock alert.

1 year, unless the shopper is logged out or manually disconnects.

swym-ol_ct

Tracks the last-synced shopping cart token, used only if the optional cart-attribute-sync feature is enabled.

30 mins

swym-tpermts

Related to asking user permission for marketing.

1 year

swym-u_pref

Related to user's marketing preference.

1 year

swym-weml

Related to user's email address for Swym apps.

1 year

swym-clctmap

Internal record avoiding duplicate identity-detection calls to the same source.

1 year

swym-mkt-denied

Related to 'wishlist' accept marketing pop-up cancellation.

1 year

swym-_oid

Internal record preventing an order confirmation from being reported more than once.

30 mins

swym-remoteAuth

Tracks whether a passwordless login request is pending, completed, or should be cleared.

1 year

swym-rvn

Related to 'recently viewed' notification pop-up display history.

1 year

swym-watchlist-mailing-list-subscribed

Related to showing mailing list checkbox in back-in-stock popup.

1 year

swym-wn

Related to wishlist nudge history data.

1 year

swym-sflPopupShownCount

Related to 'save for later' pop-up display count.

30 minutes

swym-pauseSFLPopup

Related to pausing 'save for later' pop-up display according to the user's choice.

30 minutes

swym-v-ckd

An internal record ensuring a software version check only runs once per session.

30 mins

swym-nf_svd

Records that the shopper added an item to their wishlist during the current browsing session.

30 mins

swym-pstlgnrd

Remembers which page to return the shopper to after they are required to log in.

30 mins

swym-ignach

A short-lived internal marker used immediately after a passwordless login request.

30 mins

swym-t_m

An internal record ensuring a technical mismatch is only reported once per session.

30 mins

swym-badrid

Counts repeated technical errors related to a visitor's identifier, used to decide when that identifier should be reset.

30 mins

Local Storage table:

Local Storage

Description

Duration

swym-instrumentMap

Buffer of shopper interaction events, flushed to Swym's servers for on-site personalization triggers.

No fixed expiry; cleared once its contents are flushed

swym-devices

Caches device information tied to the shopper's session.

About 5 minutes

swym-devices_timestamp

Staleness marker for swym-devices.

About 5 minutes

swym-products

Caches wishlist product details for faster rendering.

About 5 minutes

swym-products_timestamp

Staleness marker for swym-products.

About 5 minutes

swym-rconfig_cache

Related to retailer configuration.

No expiry

swym-rapps_cache

Related to retailer configuration.

No expiry

swym-thmver

Related to wishlist launcher in the header and stores theme config versions.

No expiry, overwritten each time it's checked

swym-rfrshthmprst

Related to wishlist launcher in the header and determines whether to refresh the theme preset or not.

Transient, removed once used

swym-wshlstcnt

Related to wishlist launcher in the header and stores a count of wishlisted items.

No expiry, cleared if the shopper changes

swym-scheduledSFLAsk

Related to save for later pop-up display.

About 15 seconds

swym-ab-test-config

Related to controlled feature display.

No expiry

swym-thmprst

Related to wishlist launcher in the header and stores theme preset for ideal rendering.

No expiry

swym-wishlisthkey

Related to sharing wishlist.

About 5 minutes

swym-wishlisthkey_timestamp

Related to sharing wishlist.

About 5 minutes

swym-authn

Related to Swym authentication for a user.

About 5 minutes

swym-authn_timestamp

Related to Swym authentication for a user.

About 5 minutes

swym-uprefcheckmeta

Related to user's preference about marketing permissions.

About 5 minutes

swym-uprefcheckmeta_timestamp

Related to user's preference about marketing permissions.

About 5 minutes

swym-sms-config

Related to Swym app config for back in stock.

No expiry

swym-rvd

Related to 'recently viewed' products history of user.

Self-clears after 365 days of inactivity

swym-rvua

Related to 'recently viewed' last viewed product timestamp.

Drives the 365-day check above

swym-userSettings

Related to saving user settings for HTC app.

No expiry, persists until overwritten

If you’d like to know more about Swym’s cookies and local storage properties, or are looking for specific details about the cookies we use, contact us to ensure you have the right information based on your plan.

Both the necessary and preference cookies and local storage properties noted above are dynamic and subject to change based on our applications installed in your store and updates we make to those applications.

For more information on any of the above, please contact our support team via email at [email protected].

Swym reserves the right to change the information available on this document as required to match our product updates.

Did this answer your question?