Learn how Swym uses cookies and local storage, and how Wishlist Plus is GDPR compliant — including in cookie-declined states.
Overview
To align with our commitment to data privacy, Wishlist Plus supports Shopify's Customer Privacy API for EU/EEA and UK regions in line with GDPR and UK-GDPR guidelines. For more on how Swym uses cookies and local storage, see our cookies and local storage guide . You can also review Shopify's approach to customer privacy in their help article.
If you are using a separate cookie consent management application, ensure that the cookies required for Swym are categorised as necessary. As an alternative, you may consider using Shopify's default cookie banner to gather customer consent — instructions can be found here.
Privacy-First Wishlist — A Cookie-less Option for Stores with Cookie Consent Banners
For any store displaying a cookie consent banner, Wishlist Plus offers a Privacy-First Wishlist mode — regardless of where the store is based. When enabled, the wishlist continues to work for shoppers who decline your cookie consent banner — saving items to the shopper's own device rather than to Swym's servers. No cookies are set. No personal data is collected or transmitted.
This means that for EU/EEA stores with Privacy-First Wishlist enabled, the standard behaviour described in this article — where the app remains inactive until cookies are accepted — no longer applies. The two modes work as follows:
Shopper Action | Standard Mode (Cookies Accepted) | Privacy-First Mode (Cookies Declined) |
Accepts cookie banner | Full wishlist functionality. Items saved to Swym cloud. All features active. | Not applicable — shopper accepted cookies. |
Declines cookie banner | Wishlist inactive. No features available. | Wishlist active in device-only mode. Items saved to shopper's browser. No cookies set. |
Note: Privacy-First Wishlist is available to all Wishlist Plus merchants globally. It activates wherever your store is showing a cookie consent banner to shoppers — the geographic location of your store is not a factor. Merchants can opt out at any time from their Configurations panel. |
For full details on how Privacy-First Wishlist works — including merchant configuration and the shopper experience — see the related articles below.
Cookies Used in Standard Mode
The following cookies are required for standard Wishlist Plus features to operate correctly. Each is marked below as Necessary or Functional, using the common categories used in cookie banners and consent management tools. If you are using a third-party cookie consent management app, mark these accordingly so the app loads correctly for shoppers who accept cookies.
Note: These cookies apply to the standard consent-accepted flow only. When a shopper is using Privacy-First Wishlist in device-only mode, none of these cookies are involved.
Cookie Name | Description | Duration | Category |
swym-pid | Unique identifier used to track merchants and their wishlist settings. | 1 year | Necessary |
swym-swymRegid | Stores an encrypted version of the user's device ID and session information. This ID links the user's Swym app content to their device and retrieves it from cloud storage when they access Swym apps. | 1 year | Necessary |
swym-session-id | General-purpose session cookie used to maintain an anonymous user session. | 30 minutes | Necessary |
swym-o_s | Related to Swym app versioning systems. | 30 minutes | Necessary |
swym-isCheckedForMisauth | An internal record used to avoid repeating a one-time account-authentication cleanup step. | 1 year | Necessary |
swym-pstlgnrd | Remembers which page to return the shopper to after they are required to log in. | 30 minutes | Functional |
swym-ignach | A short-lived internal marker used immediately after a passwordless login request. | 30 minutes | Functional |
swym-nf_svd | Records that the shopper added an item to their wishlist during the current browsing session. | 30 minutes | Functional |
swym-t_m | An internal record ensuring a technical mismatch is only reported once per session. | 30 minutes | Functional |
swym-v-ckd | An internal record ensuring a software version check only runs once per session. | 30 minutes | Functional |
swym-badrid | Counts repeated technical errors related to a visitor's identifier, used to decide when that identifier should be reset. | 30 minutes | Functional |
swym-remoteAuth | Tracks whether a passwordless login request is pending, completed, or should be cleared. | 1 year | Functional |
swym-clctmap | Internal record avoiding duplicate identity-detection calls to the same source. | 1 year | Functional |
swym-ol_ct | Tracks the last-synced shopping cart token, used only if the optional cart-attribute-sync feature is enabled. | 30 minutes | Functional |
swym-_oid | Internal record preventing an order confirmation from being reported more than once. | 30 minutes | Functional |
swym-email | Stores the shopper's email address when they log into the store, authenticate their wishlist, or subscribe for a back-in-stock alert. | 1 year (unless the shopper logs out or manually disconnects) | Functional |
swym-weml | Stores an email address specifically tied to watchlist alerts. | 1 year | Functional |
swym-productCartAction | Records the state of a cart action for a specific product. | 1 year | Functional |
swym-validatedUserContactNo | Stores a phone number the shopper has confirmed, for back-in-stock text message alerts. | 1 year | Functional |
swym-tpermts | Records when it is next appropriate to show the shopper a permission prompt again, so they are not asked repeatedly. | 1 year | Functional |
swym-u_pref | Stores a shopper's saved wishlist and notification preferences. | 1 year | Functional |
swym-shutm | Records marketing campaign attribution information (which campaign brought the shopper to your store). | 1 year | Marketing |
Frequently Asked Questions:
What happens if a shopper doesn't consent to cookies?
This depends on whether your store has Privacy-First Wishlist enabled.
If Privacy-First Wishlist is enabled (available to all stores globally): the wishlist remains active for the shopper in device-only mode. Items are saved to their browser only. No cookies are set and no personal data is collected. The shopper can save up to 5 items locally, and is invited to log in and sync their list for cross-device access.
If Privacy-First Wishlist is not enabled: the Wishlist Plus features will remain inactive for shoppers who decline cookies. The app depends on cookies to operate in standard mode, so features are only available after consent is given.
My store has Privacy-First Wishlist enabled. Does the app still require cookie consent? [NEW]
No — not for the device-only flow. When a shopper declines cookies and Privacy-First Wishlist is active, the wishlist operates entirely without cookies, using the shopper's own browser storage. Your cookie consent banner still governs all other tracking on your store. Swym's Privacy-First Wishlist simply does not require consent to function in device-only mode because no cookies or personal data are involved.
I'm using a separate cookie consent management app (e.g. Consentmo, OneTrust). What do I need to do?
For standard wishlist functionality, ensure that the functional cookies listed above are categorised as necessary within your CMP settings.
If you have Privacy-First Wishlist enabled, your CMP continues to control whether Swym's scripts load at all. If a shopper accepts cookies, the standard cloud wishlist activates as normal. If they decline, Privacy-First Wishlist activates instead — using device storage rather than cookies. The two layers work together. No additional CMP configuration is required for Privacy-First Wishlist.
What if I want a simpler setup for managing customer consent?
You may consider using Shopify's default cookie banner, which is a built-in feature of the platform and works seamlessly with Swym's Customer Privacy API integration. Instructions can be found in Shopify's help documentation.
The wishlist icon or functionality isn't showing up on my store, but I can see it in the customiser. What should I do?
If Privacy-First Wishlist is enabled: the wishlist icon should be visible and functional for all shoppers regardless of their cookie choice. If the icon is not appearing, please check that the Privacy-First Wishlist setting is enabled in your Configurations panel under Compliance & Accessibility.
If Privacy-First Wishlist is not enabled and your store operates in EU/EEA regions: the wishlist icon and features will only appear after the shopper has accepted cookies. This is expected behaviour in standard mode.
I see a console warning that says "No customer consent to load Swym," and the wishlist isn't present on my store. What does this mean?
This warning means that Wishlist Plus has correctly detected that a shopper has not yet provided cookie consent, and the standard app has not loaded as a result.
If Privacy-First Wishlist is enabled and you are still seeing this warning alongside a missing wishlist icon, please contact Swym support — this may indicate a configuration issue.
If Privacy-First Wishlist is not enabled: this warning is expected and not an error. The app will become visible and functional once the shopper accepts cookies.
Need further assistance?
You can always reach out to us at [email protected].
If you're already on our Messenger, simply say "talk to an agent," and Fin will connect you with a member of our team who can provide further assistance.