Cookie Preferences

Cookie Policy Updated: 14 April 2026

This Cookie Policy explains how Pcific Marketplaces Limited, trading as PCIFIC ("PCIFIC", "we", "us", or "our"), uses cookies and similar technologies on https://www.pcific.co.uk and related PCIFIC marketplace pages that link to this policy.

It should be read with our Privacy Policy, which explains how we process personal data more broadly.

What we mean by cookies and similar technologies A cookie is a small text file stored on your device by a website or service.

Similar technologies are other tools that store information on your device or access information from your device. On PCIFIC, this may include:

local storage; session storage; browser cache; service-worker cache; scripts, tags, and pixels; third-party SDKs; and embedded third-party tools used for payments, maps, analytics, or security. These technologies may be first-party, meaning they are set by PCIFIC, or third-party, meaning they are set or controlled by another provider whose service we use.

Our consent tool PCIFIC uses a consent tool to record whether you choose:

Accept all; or Essential only. The current tool is binary. It does not provide separate sliders for every category of technology.

Your choice is stored by PCIFIC in local storage under pcific_cookie_consent. This record is set by PCIFIC, stores your cookie/similar-technology choice and timestamp, and is kept for up to 12 months.

We do not treat browsing, account registration, or purchase as consent for non-essential cookies or similar technologies.

Essential technologies needed for security, fraud prevention, login, checkout integrity, consent recording, or service continuity may still operate where they are needed to provide the service you request.

Categories we use

Essential and security technologies These technologies help PCIFIC load, stay secure, remember your consent choice, support login, preserve checkout state, and protect against abuse or fraud.

If you block these technologies, parts of PCIFIC may not work correctly.

Examples include:

__cf_bm - set by Cloudflare for bot management and protection against malicious or automated traffic. Typical duration: about 30 minutes. pcific_cookie_consent - set by PCIFIC to record your consent choice and timestamp. Typical duration: up to 12 months. st--token and similar Sharetribe token cookies - set by PCIFIC / Sharetribe for login, session continuity, and authenticated marketplace requests. Typical duration: varies by flow; some token stores may last up to 180 days. st-authinfo, st-autherror, st--idp-oauth-state, st--idp-oauth-context, and st--idp-pending-auth - set by PCIFIC / Sharetribe for social login, sign-up, and authentication error handling. Typical duration: short-lived, usually up to 10 to 15 minutes. st--oauth2State, st--pkceCodeVerifier, and st--targetPath - set by PCIFIC / Sharetribe for secure support or admin login-as flows, including OAuth state and PKCE checks. Typical duration: short-lived, usually about 30 seconds. support_session - set by PCIFIC for authenticated support/admin session handling. Typical duration: up to 24 hours. CheckoutPage - PCIFIC session storage used to preserve checkout order, listing, and transaction state during checkout. Typical duration: browser session, with checkout data treated as fresh for up to 1 day. pcific_cart - PCIFIC local storage used to preserve a guest cart before login or checkout. Typical duration: until cleared, replaced, merged into an account, or browser storage is cleared. pcific-static-v1 - PCIFIC service-worker Cache Storage for the app shell, static assets, and some same-origin GET responses. Typical duration: until replaced by a newer cache version or cleared by browser/site-data controls. 2. Functional technologies These technologies remember choices, in-progress actions, and interface state so that features you use can continue to work smoothly. Some are stored only for the current browser session; others remain until cleared, replaced, or overwritten.

Examples include:

pcific_search_history - set by PCIFIC to store recent search history for marketplace and AI search convenience. Typical duration: up to 20 items, until cleared or browser storage is cleared. pcific_recently_viewed - set by PCIFIC to store recently viewed listings and category signals for convenience. Typical duration: up to 10 listings, until cleared or browser storage is cleared. pcific_saved_searches - set by PCIFIC to store saved searches in the browser. Typical duration: up to 20 saved searches, until cleared or browser storage is cleared. pcific_viewMode, pcific_ai_overview_mode, pcific-ai-mode, pcific-ai-experience-mode, pcific_smart_features, and pcific-sound-muted - set by PCIFIC to remember display, AI, dashboard, and sound preferences. Typical duration: until changed or browser storage is cleared. pcific_accountSetupAssistant:v1: - set by PCIFIC to remember account setup assistant progress and whether the proactive prompt has been shown. Typical duration: until replaced or browser storage is cleared. pcific_accountSetupBannerDismissed, verification_nudge_dismissed_, pcific_exit_intent_shown, assistant-fly-shown-dashboard, and assistant-fly-shown- - set by PCIFIC as session flags to avoid repeatedly showing banners, nudges, or animations. Typical duration: usually the current browser session. bulkUpload_activeSession and pcific.bulkUpload.activeSession - set by PCIFIC to preserve bulk-upload or CSV-import progress and reconnection state. Typical duration: session storage plus a local recovery copy, typically about 23 to 24 hours. pcific.bulkUpload.mappingProfiles.v1 and bulkUpload_listingTypeChoice - set by PCIFIC to store CSV mapping profiles and draft/published import choices. Typical duration: until cleared or browser storage is cleared. pcific_ai_listing_draft:v1:: - set by PCIFIC to preserve AI listing-draft wizard state and uploaded-image draft continuity. Typical duration: about 24 hours. pcific-buyer-listing-conversations, pcific_ai_listing_transactions, pcific_ai_seller_replies, and pcific_ai_tx_ids - set by PCIFIC to maintain AI assistant, listing, seller-reply, and transaction continuity. Typical duration: varies by item; pcific_ai_tx_ids is session storage. pcific-unread-notifications, pcific_unread_notification_state, and pcific_message_read_status - set by PCIFIC to remember read/unread state for support tickets, notifications, and messages. Typical duration: until overwritten, cleared, or browser storage is cleared. pcific-milestones-shown and pcific_advisor_last_visit - set by PCIFIC to remember seller dashboard milestone and advisor visit state. Typical duration: until overwritten or browser storage is cleared. Some functional storage is also used to support requested marketplace features such as cart continuity, listing creation, bulk upload, messages, support, and account setup. Where a feature cannot work properly without the storage, we treat it as necessary for that feature.

Analytics and measurement technologies PCIFIC uses analytics to understand how people use the marketplace and to improve the service. Analytics technologies are not described here as advertising or social-media tracking technologies.

Examples include:

Google Analytics 4, measurement ID G-486230WHE0 - provided by Google to measure site traffic and page views after the user chooses Accept all in the PCIFIC consent tool. Typical duration: controlled by Google and browser settings; PCIFIC only loads the GA4 script after full consent in the current frontend implementation. pcific-listing-engagement-session-id - set by PCIFIC as a first-party local storage identifier for listing engagement, view counts, rate limiting, and anti-abuse/marketplace measurement. Typical duration: until browser storage is cleared. PCIFIC's current code can support Plausible analytics if it is configured. We do not describe Plausible as active in this policy. If PCIFIC enables Plausible in the future, we will review and update this policy and our consent controls where required before using it.

Payment and fraud-prevention technologies PCIFIC uses Stripe on checkout, saved-card, payment-method, and seller payout/onboarding flows. Stripe may use cookies and similar technologies to provide payments, authenticate payment sessions, recognise devices, and prevent fraud.

Examples that may appear on relevant payment or account routes include:

__stripe_mid - set by Stripe for fraud prevention and device recognition. Typical duration: about 12 months. __stripe_sid - set by Stripe for fraud prevention and session correlation. Typical duration: about 30 minutes. m - set by Stripe for Stripe service, session, or fraud-prevention support. Typical duration: varies. These Stripe technologies should be understood as payment and fraud-prevention technologies. They are not described here as being set on every anonymous public page.

Map, address, and location technologies PCIFIC uses map and address tools to support search, listing location, shipping, checkout, payment-address, and account-address flows.

Examples include:

Mapbox scripts, SDKs, map tiles, geocoding, and address autofill - provided by Mapbox for maps, address suggestions, geocoding, and address-related functionality. Note: Mapbox is the default map/address provider in the current codebase. Google Maps scripts and APIs - provided by Google for map or place functionality if the configured map provider is switched to Google Maps. Note: this is conditional and is not the default map provider in the current codebase. Browser geolocation - provided by your browser or device and used by PCIFIC only if selected. Purpose: lets you use current-location search or location-related features. Note: used only if you choose the feature and grant browser/device permission. Map and address providers may receive technical information such as IP address, browser/device details, search/address queries, map interactions, and approximate or precise location information depending on the feature used.

Embedded content, fonts, and delivery technologies PCIFIC may load embedded or delivery-related technologies where needed for content or site presentation.

Examples include:

YouTube no-cookie embeds - provided by YouTube / Google to display listing video content where a listing includes a video. Note: only relevant where video content is embedded or played. Google font delivery and related asset requests - provided by Google to load fonts or assets used by the site interface. Purpose: functional site presentation. Sharetribe asset/font CDN requests - provided by Sharetribe to load marketplace assets, fonts, and hosted configuration. Purpose: functional marketplace delivery. When you interact with embedded third-party content, the third party may use its own cookies or similar technologies under its own policies.

Technologies not described as active site cookies Some providers help PCIFIC outside the browser. They are relevant to wider privacy information, but they are not presented in this Cookie Policy as active website cookie providers:

SendCloud is used for shipping, labels, carrier services, and tracking in server-side marketplace flows. It is covered by wider privacy/vendor information, but we have not identified it as a browser cookie provider on the PCIFIC website. MailerLite is used for waitlist, newsletter, or important-updates membership where configured. It is a server-side communications processing point, not a PCIFIC website cookie provider in the current implementation. Separate advertising, behavioural advertising, or social-media tracking technologies are not described here as active unless PCIFIC enables and discloses them. How to manage cookies and similar technologies You can manage cookies and site data through your browser settings. Most browsers allow you to:

view stored cookies; delete cookies; block cookies for all or selected websites; clear local storage and session storage; clear cached site data; and manage site permissions such as location access. If you want to reset your PCIFIC consent choice, you can clear PCIFIC site data in your browser. If PCIFIC provides an on-site cookie-preferences control, you can also use that control.

Please note that clearing or blocking essential technologies may prevent sign-in, checkout, payment, support, cart, security, or other requested marketplace features from working correctly.

Deleting browser data does not automatically delete server-side account records, orders, messages, support records, shipping records, payment records, or marketing preferences handled outside your browser. Those are covered by our Privacy Policy and applicable account or support processes.

Changes to this policy We may update this Cookie Policy from time to time to reflect:

changes to the technologies we use; changes to our marketplace features; changes in law or regulatory guidance; or changes to our third-party providers. When we update this policy, we will change the "Updated" date above. Where required by law, we will take additional steps to notify you or ask for your consent.

Email: support@pcific.co.uk Post: Pcific Marketplaces Limited, 71-75 Shelton Street, Covent Garden, London, United Kingdom, WC2H 9JQ