Directus

Overview

Directus is an open-source headless CMS and data platform that exposes structured content through REST and GraphQL APIs. It is primarily a backend service, meaning its presence in a technology stack does not typically result in client-side script execution on end-user browsers. When Directus does appear in a browser context, it is usually because developers have integrated the Directus JavaScript SDK into a frontend application to query content directly from the API.

What This Script Does

Because Directus operates as an API server rather than a tag-injected script, its browser footprint is minimal. When developers use the Directus JS SDK (@directus/sdk), the library makes authenticated fetch requests to the Directus API endpoint—typically a subdomain operated by the site owner, not a third-party domain. No persistent tracking cookies are set by the SDK itself. Session authentication may use short-lived tokens stored in memory or localStorage, but these are scoped to the application and are not shared with external parties. No fingerprinting, behavioral tracking, or advertising identifiers are collected.

Consent & Compliance

Under GDPR and ePrivacy, Directus SDK requests are analogous to first-party API calls—they retrieve content from a server operated by or on behalf of the data controller. No third-party personal data processing occurs. Under CCPA/CPRA, there is no sale or sharing of personal information with Experian or other third parties. Because Directus does not set cookies or collect behavioral data for tracking purposes, it falls into the essential or functional consent category. Consent is not legally required under ePrivacy for first-party technical requests of this nature.

Should You Block This Without Consent?

No. Directus serves as a content delivery mechanism rather than a tracking or advertising tool. Blocking it would typically break content rendering on pages that depend on the Directus API. No user profiling or cross-site tracking is involved.