Does your website use third-party services? Get GDPR compliant in minutes.
Try FlowConsentFree plan · 10-min setup
Marionette.js is an open-source application framework built on top of Backbone.js that provides structure and best practices for building large-scale JavaScript applications. It is a developer tool, not a data processor or tracking service. GDPR obligations arise from the application built with Marionette.js and the data it processes, not from the framework itself.
Marionette.js is a JavaScript application framework that extends Backbone.js with additional structure, patterns, and conventions for building large-scale web applications. It provides composite views, application architecture patterns, event aggregation, and module management that make complex Backbone applications easier to organise and maintain. Marionette.js was widely used in the early-to-mid 2010s for building single-page applications before modern frameworks like React and Vue became dominant. It is open-source and does not itself process data.
GDPR obligations arise from the application built with Marionette.js and the personal data it processes, not from the framework itself. A Marionette.js application that displays user profiles, processes form submissions with personal data, or communicates with APIs that return personal data is subject to GDPR. The developer is responsible for implementing appropriate data handling, consent management, and privacy practices within the application.
Marionette.js applications built on Backbone.js may cache model data (potentially containing personal data) in client-side memory and localStorage. If Backbone models contain personal data, this data must be cleared appropriately: on logout, on consent withdrawal, and after defined session periods. Applications using localStorage for offline data persistence must manage personal data retention within that storage.
Get GDPR compliant in 10 minutes
Free plan available · No credit card required
Bundle Marionette.js rather than loading from CDNs. Clear Backbone model caches containing personal data on logout. Manage localStorage data retention. Implement cookie consent management in the application. Build data subject rights handlers. Sign DPAs with backend APIs and services the application integrates.
Websites using Marionette.js must obtain user consent under GDPR regulations.
DPIA considerations
A DPIA is not required for Marionette.js itself. It may be required for applications built with Marionette.js that process personal data at large scale or perform automated decision-making.
Sample consent text
This application is built using Marionette.js. Data collection and processing within this application are described in our privacy policy.
Third-party domains contacted
marionettejs.comgithub.comCookies placed
| Name | Type | Duration | Purpose |
|---|---|---|---|
| backbone_sid | session | Session | Session identifier used by Backbone.js authentication in Marionette.js applications — set by developer |
This service may collect user data. Ensure GDPR compliance with FlowConsent.
No. Marionette.js is an open-source JavaScript framework. GDPR applies to the application built with it and the personal data it processes, not to the framework code itself.
No. Marionette.js does not set any cookies by default. Cookies in Marionette.js applications are set by the developer's code or by third-party services integrated into the application.
Backbone.js models used with Marionette.js may cache personal data in browser memory or localStorage. Applications must ensure this cached data is cleared on logout, on consent withdrawal, and after appropriate retention periods.
Marionette.js itself does not transfer data. Transfer obligations depend on where the application is deployed and which backend APIs and services it integrates.
Not for Marionette.js itself. DPIAs may be required for applications that process personal data at large scale or perform automated decision-making.
Marionette.js is in maintenance mode. Active development has slowed significantly as modern frameworks (React, Vue, Angular) have replaced Backbone-based architectures. New projects should use modern alternatives. Existing Marionette.js applications should be assessed for migration planning.
Build data subject rights functionality at the application layer: export endpoints for access requests, deletion flows for erasure requests, and update flows for rectification. Clear Backbone model caches and localStorage data as part of erasure flows.
No, the framework does not need to be disclosed. The data processing within your Marionette.js application needs to be described, including what data is collected, the legal basis, retention periods, and any third-party processors.