Cookie Policy
Please read this cookie policy carefully as it contains important information on who we are and how we use cookies on our website. This policy should be read together with our Privacy Policy which sets out how and why we collect, store, use and share personal information generally, as well as your rights in relation to your personal information and details of how to contact us and supervisory authorities if you have a complaint.
Who we are
This Libraro.com website and platform (hereinafter “website”) is operated by Libro Publishing Limited trading as Libraro. We are a company incorporated in England and Wales with company number 14602616; registered address at C/O Solid Ltd, Eagle House, 163 City Road, London EC1V 1NR, United Kingdom; and ICO Registration ZB861769. The website is operated in the United Kingdom but available to users globally.
Our website
Throughout our website and the Libraro Platform we may link to other websites owned and operated by certain trusted third parties to provide other products and services to you. These other third party websites may also use cookies or similar technologies in accordance with their own separate policies. For privacy information relating to these other third party websites, please consult their policies as appropriate.
What are cookies
A cookie is a small text file which is placed onto your device (e.g. computer, smartphone or other electronic device) when you use our website. Similar technologies include SDKs, pixels, tags, local storage, device identifiers, and other technologies that store or access information on your device or browser.
These help us recognise your device so that you remain logged into the service and help us to ensure the website and platform services are functioning correctly.
For example, we may monitor how many times you visit the website. This information helps us to understand our users and optimise our services for them. Some of this data will be aggregated or statistical, which means that we will not be able to identify you individually.
Why we use cookies
We use cookies for the following purposes:
- Strictly necessary: To make the website and platform work, enable core features such as page navigation, security, user authentication (including email login), and to allow you to comment, like, share and access your account. These are essential and do not require consent.
- Preferences (functional): To remember your settings and choices (such as language, cookie preferences, and display options).
- Analytics and performance: To understand how our website and platform are used, measure performance, and improve our services (for example, page views, feature usage, error diagnostics).
- Advertising and marketing: To deliver and measure advertising, including interest‑based or cross‑site advertising where enabled, and to understand the effectiveness of marketing campaigns.
- Security and fraud prevention: To help detect and prevent fraud, abuse, or security incidents, and to protect the integrity of our platform and blockchain‑connected functionality.
Your consent is the legal basis for our use of non‑essential cookies (such as preferences, analytics and advertising cookies) under the UK GDPR and EU GDPR.
Where these cookies or similar technologies involve the processing of personal data, such processing is carried out in accordance with our Privacy Policy and applicable data protection laws.
For further information on cookies generally, including how to control and manage them, visit the guidance on cookies published by the UK Information Commissioner’s Office, or www.allaboutcookies.org.
You also have the right to lodge a complaint with your local data protection authority (for example, the Information Commissioner’s Office in the UK or the competent authority in your EU Member State) if you believe your rights have been infringed.
California (CCPA / CPRA) and other US privacy laws
If you are a resident of California, the California Consumer Privacy Act (as amended by the CPRA) gives you additional rights in relation to personal information collected via cookies and similar technologies.
Where cookies or similar technologies involve “personal information” and this information is “sold” or “shared” under the CCPA/CPRA (for example, in connection with certain advertising technologies), we will:
We may also apply similar opt‑out mechanisms to residents of other US states that have comparable privacy laws, where appropriate.
Consent to use cookies and changing settings
Generally we will ask for your consent to place cookies or other similar technologies on your device, except where they are essential for us to provide you with a service that you have requested (e.g. allowing you to login and use the service).
You can withdraw any consent to the use of cookies or manage any other cookie preferences by clicking on the cookie link at the bottom of the landing page or through your browser. You can then update your consents. It may be necessary to refresh the page for the updated settings to take effect.
Our use of cookies
The table below provides more information about the cookies we use and why, indicating specific retention periods for individual cookies::
Service
Cookie name
Cookie type
Description
Essential
Libraro
libraro-user-session (LIBRARO_REFRESH_TOKEN, LIBRARO_TOKEN, SESSION_ID, USER_ID)
Strictly necessary
Manages user authentication and secure access to the platform
Duration: session
Libraro
app-cookies-accepted
Strictly necessary (Consent storage)
Stores user cookie consent preferences
Duration: Persistent
Stripe
__stripe_mid
Strictly necessary / Third-party (payments)
Set for fraud prevention purposes and helps us assess the risk associated with an attempted transaction. Duration: up to 1 year
Google Analytics 4
_ga*
Analytics
Distinguishes users by assigning a randomly generated identifier and collects aggregated usage data.
Duration: 2 years
Google Analytics 4
ga
Analytics
Stores session-related information for analytics tracking.
Duration: up to 1 year
Google Ads
gac_gb
This cookie contains compaign-related information for the user.
Google Ads
_gcl_au
Stores conversion information to measure advertising effectiveness.
Duration: 3 months
Meta Pixel
_fbp
Stores a unique browser identifier to help measure and attribute conversions and support ad targeting/retargeting.
Duration: ~3 months
Meta Pixel
_fbc
Stores the Facebook Click ID value when a user lands with a fbclid parameter, supporting ad conversion attribution.
Duration: ~3 months
TikTok Pixel
_ttp
Measures and improves ad performance and personalizes ad experience on TikTok
Duration: ~13 months
TikTok Pixel
ttcsid_, ttcsid_
Supports advertising measurement/attribution for TikTok campaigns.
Duration: ~13 months
TikTok Pixel
ttclid
Supports click-based attribution for TikTok ads and campaign performance measurement.
Duration: ~13 months
HubSpot
__hstc
Main tracking cookie used by HubSpot to keep track of visitors. It stores the domain, initial timestamp, last visit timestamp, current session timestamp, and session number.
Duration: ~3 months
HubSpot
hubspotutk
Stores a unique visitor identifier to track a visitor across sessions and associate form submissions and interactions with the same user.
Duration: ~3 months
HubSpot
__hssrc
Analytics
Indicates whether the visitor has restarted their browser. Used to determine if a new session should be created.
Duration: Session
HubSpot
__hssc
Analytics
Tracks sessions and is used to determine session count and timestamps for HubSpot analytics.
Duration: 1 hour
Viral Loops
g_state
Stores information related to authentication or consent state to ensure secure sessions.
Duration: 6 months
Viral Loops
stg_externalReferrer
Analytics (behaviour tracking)
Stores the external referrer that directed the user to the website.
Duration: session
Viral Loops
stg_last_interaction
Analytics (behaviour tracking)
Determines whether the last visitor’s session is still in progress or a new session has started.
Duration: 1 year
Viral Loops
stg_returning_visitor
Analytics (behaviour tracking)
Indicates whether a visitor is returning to the website.
Duration: 1 year
Viral Loops
wooTracker
Tracks user interactions and attribution data for analytics or marketing purposes.
Duration: up to 13 months
VWO
_vwo_uuid_v2
Analytics / A/B testing (VWO)
Assigns a unique ID to track participation in experiments and A/B tests.
Duration: persistent
Microsoft Clarity
_clck
Analytics (Microsoft Clarity)
Persists the Clarity User ID and preferences, unique to that site is attributed to the same user ID.
Duration: 1 year
Intercom
intercom-device-id-*
Identifies a device to enable customer support chat functionality.
Duration: 9 months?
Intercom
intercom-session-*
Used by Intercom Messenger to store identifier for each unique browser session and is used to keep track of sessions.
Duration: 1 week
Matomo / Piwik
_pk_id.bc0b6894-5f…
Analytics (Matomo / Piwik)
Stores a unique visitor ID to recognize returning visitors and collect anonymous analytics data.
Duration: up to 13 months
How to turn off all cookies and the consequences of doing so
If you do not want to accept any cookies, you may be able to change your browser settings so that cookies (including those which are essential to the services requested) are not accepted. If you do this, please be aware that you may lose some of the functionality of our website.
For further information about cookies and how to disable them please go to the guidance on cookies published by the UK Information Commissioner’s Office, or www.allaboutcookies.org.
Cookies and blockchain‑related features
The Libraro platform connects to blockchain technology for certain features (for example, recording specific transactions or interactions on‑chain, verifying ownership or activity, or enabling blockchain‑based rewards or functionality).
In doing so, we may use cookies or similar technologies to:
- Link your web account (created with your email address) to a blockchain identifier or wallet address.
- Maintain sessions or security tokens required for blockchain interactions executed via the Libraro platform.
- Measure usage of blockchain‑related features and improve their performance.
While blockchain records are outside of your device, the technologies used to interact with those features (such as wallet integrations, SDKs or session tokens) may rely on cookies or similar storage on your device, which are handled in accordance with this Cookies Policy and our Privacy Policy.
How to contact us
Please contact us if you have any questions about this cookie policy or the information we hold about you.
If you wish to contact us please send an email to [email protected].
Changes to this policy
We may change this policy from time to time to reflect usage, new third parties or changes in applicable law and regulation. When we do we will inform you via email or placing a notice on the website.
This policy was published on 14.11.2023 and last updated on 1 January 2026 (version 2.0).