Storyblok

Overview

Storyblok is a headless content management system distinguished by its visual editing interface, Storyblok Studio. Unlike traditional CMSs that serve rendered pages, Storyblok delivers content via API to frontend frameworks (Next.js, Nuxt, Astro, etc.) while providing content editors with a real-time visual preview of their changes. On production websites, Storyblok's script footprint is minimal — the editing bridge scripts only load for authenticated editors in preview mode. End users visiting the published site typically receive no Storyblok scripts or cookies.

What This Script Does

Storyblok's JavaScript bridge (storyblok-js-client or the @storyblok/js SDK) loads in two distinct contexts:

Editor/preview mode (authenticated editors only):

• Loads the Storyblok Bridge script from app.storyblok.com to enable real-time visual editing
• Establishes a postMessage communication channel between the editor iframe and the preview site
• Enables click-to-edit functionality, drag-and-drop component reordering, and live content updates
• Sets authentication cookies for the editor's Storyblok session

Production mode (public visitors):

• No Storyblok scripts are loaded on production builds in most implementations
• Content is fetched at build time (SSG) or server-side (SSR) and delivered as static HTML
• No cookies are set on the visitor's browser

Cookies set (editor mode only):

• Session authentication cookies scoped to app.storyblok.com
• Preview token cookies for authenticating draft content API requests
• No cookies are set for public visitors in production

Consent & Compliance

Storyblok falls under the functional consent category. Under GDPR and the ePrivacy Directive, the editor bridge scripts and authentication cookies serve the functional purpose of content management — a tool used by authenticated team members, not public visitors. Since production visitors typically receive no Storyblok scripts or cookies, there is no consent obligation for the public-facing site.

If your implementation loads the Storyblok Bridge on production (for example, to enable in-context editing on the live site for logged-in editors), the authentication cookies are scoped to the editor's session and serve a functional purpose.

Under CCPA/CPRA, Storyblok's data processing is limited to content delivery and editor authentication, neither of which involves collecting visitor personal information.

Should You Block This Without Consent?

No. Storyblok's scripts are functional editing tools that only load for authenticated content editors, not public visitors. In production, no scripts or cookies are served to visitors. There is no tracking, analytics, or marketing data collection to block. If the Storyblok Bridge loads on production for editor preview purposes, the authentication cookies are functional and exempt from consent requirements.