Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
Live Story is a no-code creative digital experience platform that lets brand and commerce teams build and publish rich content layouts without development, embedded on the brand site through a lightweight script.
Live Story is a no-code creative digital experience platform used mainly by fashion, retail and commerce brands. It lets marketing and e-commerce teams design rich, responsive content layouts with a drag and drop editor and publish them onto their websites and storefronts without relying on developers. The content is delivered to the brand site through a lightweight embedded script that loads layouts and assets from the Live Story platform.
In its basic content delivery role, Live Story renders layouts and does not need to profile visitors, so the cookie footprint can be very small. However, when teams enable engagement analytics, A B testing or personalisation, the platform can begin to process visitor behaviour, device data and identifiers, and may set first party cookies or use local storage. The exact data depends on which features a brand switches on, so each deployment should be assessed individually.
Where Live Story only serves content, strictly necessary delivery does not require consent and can rest on legitimate interest. Once personalisation or analytics cookies are used, the ePrivacy Directive requires prior consent before they are placed, and the GDPR governs any behavioural data and identifiers collected. The brand is the controller deciding why and how data is processed, while Live Story typically acts as a processor under a data processing agreement.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
Because Live Story is a US based company, content and any engagement data may be processed in the United States. EEA controllers should confirm whether Live Story is certified under the EU US Data Privacy Framework or relies on standard contractual clauses, and whether European hosting is available. Non essential personalisation and analytics features must be gated behind consent in your cookie banner so they only load when the visitor agrees.
Sign a data processing agreement, map which Live Story features you enable and what each collects, and connect any non essential cookies to your consent management platform. Confirm the hosting region and transfer mechanism, document the processing in your records, and keep your privacy and cookie notices in step with the features in use. Where you only need content rendering, keeping personalisation off is the simplest privacy posture.
Websites using Live Story must obtain user consent under GDPR regulations.
DPIA considerations
Live Story is a medium risk content layer. A DPIA is advisable where you enable personalisation, engagement analytics or user generated content, because these can process visitor behaviour and identifiers. Assess what the embedded script loads, whether any cookies or local storage are set, the volume of personal data flowing to the platform, the US hosting and transfer mechanism, and the role split between you as controller and Live Story as processor.
Sample consent text
This site uses Live Story to display interactive content experiences. Where Live Story sets non essential personalisation or analytics cookies, they will only load after you accept them. By accepting, you also consent to related data being processed by Live Story, including on infrastructure in the United States.
Third-party domains contacted
livestory.ioassets.livestory.iolivestory.nycCookies placed
| Name | Type | Duration | Purpose |
|---|---|---|---|
| ls_session | Necessary | Session | Maintains the rendering session for the embedded Live Story content experience. |
| ls_uid | Analytics | 1 year | Optional first party identifier used for engagement analytics when the brand enables it. |
| ls_perso | Functional | 6 months | Optional cookie used to remember personalisation choices when personalisation features are turned on. |
This service may collect user data. Ensure GDPR compliance with FlowConsent.
In its basic content delivery mode Live Story may set only a strictly necessary rendering session cookie. When a brand enables engagement analytics or personalisation, it can also set a first party analytics identifier and a personalisation cookie, so the exact set depends on the features in use.
Consent is not required for the strictly necessary cookies that render the content. It is required before any non essential analytics or personalisation cookies are placed, so those features should be gated behind your consent banner.
Serving and rendering content can rely on legitimate interest. Personalisation, A B testing and engagement analytics that process visitor behaviour need consent under ePrivacy, and that consent is the GDPR basis for the related personal data.
Likely yes. Live Story is a US based company, so content and engagement data may be processed in the United States. Confirm whether it is certified under the EU US Data Privacy Framework or uses standard contractual clauses, and whether EU hosting is offered.
A DPIA is advisable when you switch on personalisation, engagement analytics or user generated content, since these process visitor identifiers and behaviour. If you use Live Story purely to render static content, a lighter screening may be enough.
Sign a data processing agreement, enable only the features you need, and connect any non essential cookies to your consent management platform. Confirm the hosting region and transfer mechanism, and describe Live Story accurately in your privacy and cookie notices.
EU based or self hosted headless CMS and content platforms such as Storyblok, Contentful with EU hosting, or a self managed visual editor reduce US transfer exposure. Disabling personalisation in any of these keeps the privacy footprint minimal.
Document the necessary rendering cookie and any analytics or personalisation cookies you have enabled, with their purpose and duration. Note that Live Story is a US based content platform and disclose the transfer, keeping the entry aligned with your consent banner.