PORTO MARKETPLACE
Cookie Policy
Last updated: 18 September 2026
This Cookie Policy explains how Porto Marketplace Ltd (“PORTO”, “we”, “us”, or “our”), operating as PORTO Marketplace, uses cookies and similar storage and access technologies when you use the PORTO website and related services (the “Platform”).
This document describes only the technologies that PORTO actually uses at the date above. It is not a generic list of cookies that might be used in the future.
UK law regulating cookies and similar technologies includes the Privacy and Electronic Communications Regulations (PECR), read together with the UK GDPR. This Policy is intended to be consistent with the Information Commissioner’s Office (ICO) guidance on Storage and Access Technologies, finalised on 29 April 2026.
1. Cookies and similar technologies
A cookie is a small text file that a website can store on your device. Similar storage and access technologies include local storage and session storage in your browser. These are not cookies, but they can store information on your device and are covered by the same UK rules when they are used to store or access information.
PORTO currently uses:
- one first-party cookie, in a limited OAuth account-linking flow
- local storage, including for session persistence and preferences
- session storage, to avoid counting the same listing or profile view more than once in the same browser tab
- limited third-party browser technologies where a feature you use loads a third-party resource (for example Cloudflare Turnstile on login and register, Google Fonts, and media hosted on Cloudinary)
PORTO does not currently use IndexedDB, Cache Storage, or a service worker on the Platform.
2. How PORTO groups these technologies
PORTO does not treat every stored item as strictly necessary. For the launch described in this Policy, the groupings are as follows.
Strictly necessary / functionality
Technologies used to provide a service you have requested, such as keeping you signed in after you log in, linking a Google or Facebook account from Settings, or remembering favourites you save.
Functional preferences
Technologies used to remember language and display-currency choices.
Statistical / measurement
First-party technologies used to count listing and seller-profile views. These are described in section 6. PORTO does not present them as strictly necessary for using the marketplace.
3. The cookie PORTO sets
PORTO currently creates only one cookie on its own domain:
porto_oauth_link
- First-party cookie set by PORTO
- Purpose: to complete the “connect Google / connect Facebook” flow from account Settings while you are already signed in
- It does not keep you logged in and is not used for ordinary email-and-password sign-in
- Maximum duration: 10 minutes
- HttpOnly: yes
- Secure: yes in production
- SameSite: Lax
- Path: /auth
Ordinary authentication does not use a session cookie. After you sign in, PORTO stores session information in local storage, as described below, not in a login cookie.
4. Local storage
Local storage remains on your device until it is cleared (for example when you sign out, where PORTO deletes the session entry, or when you delete site data in your browser). PORTO does not assign a single fixed expiry date to these entries.
porto_auth
This entry holds your PORTO session after you sign in. It includes the tokens needed to keep you authenticated and basic account details used by the Platform (such as your name, email address, and account role). It is not a cookie. PORTO removes it when you sign out or when the session is otherwise invalidated.
porto_lang
Stores your language preference so the Platform can display the interface in the language you selected. This is a functional preference. It may be stored whether or not you are signed in.
porto_currency
Stores your display-currency preference. This is a functional preference. It may be stored whether or not you are signed in.
porto_favorite_listing_ids:guest
Stores listing identifiers that a visitor who is not signed in has saved as favourites, so those favourites can be shown on the device.
porto_favorite_listing_ids:{userId}
Local cache of listing identifiers saved as favourites by a signed-in user. The key includes that user’s account identifier. Favourites are also stored on PORTO’s servers for signed-in users.
porto_analytics_visitor_key
A random identifier generated by PORTO and stored in local storage. It is sent with first-party listing-view and seller-profile-view records so that PORTO can measure views of listings and public seller profiles. It is not a name, email address, or password. It is not a cookie. PORTO does not treat this identifier as strictly necessary to browse or use the marketplace.
5. Session storage
Session storage lasts only for the current browser tab or session and is cleared when that tab is closed.
porto_listing_view:{listingId}
A flag (the value “1”) used to avoid counting the same listing view more than once in the same tab. It does not store messages, passwords, or payment details.
porto_profile_view:{sellerId}
A flag (the value “1”) used to avoid counting the same seller-profile view more than once in the same tab. It does not store messages, passwords, or payment details.
6. First-party view measurement
PORTO does not use third-party analytics products on the Platform. There is no Google Analytics, Google Tag Manager, Meta Pixel, Hotjar, PostHog, Plausible, Sentry, or similar third-party analytics or error-monitoring script running in the PORTO browser application.
PORTO does operate its own first-party view measurement. When you open a listing or a public seller profile, PORTO may record that view on PORTO’s own systems, using the random local-storage identifier described above and a short-lived session-storage flag so the same tab is not counted twice.
This is statistical / measurement use of storage. The ICO’s Storage and Access Technologies guidance recognises a limited exception for certain statistical purposes, but only where the specific conditions of that exception are met. PORTO does not, in this Policy, assert that the exception automatically applies. PORTO does not currently provide a cookie banner, preference centre, or an in-product control to object to or refuse this first-party measurement identifier.
7. Advertising
PORTO does not currently use advertising, remarketing, or third-party advertising cookies or similar tracking technologies.
8. Third-party technologies in the browser
Some features load resources from organisations other than PORTO. PORTO does not set those organisations’ cookies from PORTO’s own code, and PORTO does not invent or control cookie names on those third-party domains. Where you leave PORTO for another website, that website’s own terms and privacy information apply.
Stripe
When you start or manage a PORTO membership, PORTO redirects you to Stripe Checkout or the Stripe Customer Portal. PORTO does not load Stripe’s payment script on portomarketplace.com and does not state that Stripe places cookies on the PORTO domain. Any cookies Stripe uses are set on Stripe’s own sites after that redirect.
Google and Facebook
You may sign in or connect an account using Google or Facebook. PORTO does this by redirecting you to that provider and then returning you to PORTO. PORTO does not embed Google or Facebook advertising or social SDKs for tracking. Cookies those providers use during sign-in are set on their own domains, not by PORTO as first-party cookies on the PORTO origin.
Cloudflare Turnstile
On the login and register pages, PORTO loads Cloudflare Turnstile to help distinguish genuine users from automated abuse. Cloudflare may use storage and access technologies in connection with that widget. PORTO does not create, name, or control Turnstile cookies in PORTO’s own code.
Google Fonts
The Platform loads font files from fonts.googleapis.com and fonts.gstatic.com. These are third-party resources. PORTO does not define its own cookies for Google Fonts.
Flag images
The country selector loads flag images from flagcdn.com. These are third-party image resources. PORTO does not define cookies for that service.
Cloudinary
Listing and profile images and videos are stored by PORTO using Cloudinary and then displayed from Cloudinary’s content network. There is no Cloudinary upload widget in the PORTO browser application. PORTO does not set Cloudinary cookies from its own code.
Mapbox
Address lookup used by PORTO is performed on PORTO’s servers. PORTO does not load Mapbox’s mapping library in the browser and does not state that Mapbox places cookies on the PORTO domain.
Resend
PORTO uses Resend only on its servers to send email. Resend is not loaded in the browser and does not store information in your browser through the Platform.
9. Consent
PORTO does not currently display a cookie banner, consent management platform, or cookie preference centre.
Continuing to browse the Platform is not treated as consent. Where UK law requires consent before a storage or access technology is used, and no PECR exception applies, consent must be obtained in advance by a valid mechanism. PORTO does not currently operate such a mechanism.
10. How to manage or delete stored information
You can delete or block cookies and site storage using your browser or device settings. PORTO does not provide a separate in-product preference centre for these technologies.
Clearing PORTO site data may:
- sign you out (by removing porto_auth)
- reset language or currency preferences
- remove locally stored guest favourites
- remove the first-party view-measurement identifier until a new one is created if you view a listing or profile again
- affect other functions that rely on the stored items listed in this Policy
11. Security
PORTO uses browser storage to operate signed-in sessions and to remember the preferences described above. Session tokens are stored in local storage rather than in a session cookie. You should avoid using a shared device without signing out. PORTO uses HTTPS in production. No internet-based system can be guaranteed to be completely secure.
12. What PORTO does not currently use
- Third-party analytics products: not used
- Advertising or remarketing cookies or similar advertising tracking: not used
- A cookie banner or consent management platform: not provided
- IndexedDB: not used
- Cache Storage: not used
- Service worker: not used
13. Changes
PORTO may update this Cookie Policy when the Platform, the law, or the technologies described here change. The current version will be published on the Platform with its update date. Where UK law requires additional notice of a material change, PORTO will provide that notice.
14. Contact
For questions about this Cookie Policy or PORTO’s use of cookies and similar technologies, contact:
Porto Marketplace Ltd
Company number: SC895950
Registered in: Scotland
Registered office:
67/8 Iona Street, Edinburgh, Scotland, EH6 8SR
United Kingdom