Privacy Policy
Last updated: 26 March 2026
This document describes the current behaviour of Mandate Atlas as implemented. It is provided for transparency purposes only and does not constitute legal advice.
1. Data Sources and Licensing
Mandate Atlas processes parliamentary and institutional data originating from multiple publicly available sources, including:
- HowTheyVote (ODbL) — https://howtheyvote.eu
- European Parliament official data sources
- European Commission public data sources
- Council of the European Union public data sources
- Open-access RSS feeds and publicly available web content
Primary dataset licensing (where applicable):
Open Database License (ODbL) — https://opendatacommons.org/licenses/odbl/
Attribution: Contains data from HowTheyVote (ODbL) and other public institutional and open-access sources.
Use of such data remains subject to the respective terms, licences, and conditions of each source, including attribution and, where applicable, share-alike obligations.
2. Data We Process
The application processes:
- locally stored datasets (e.g. howtheyvote_votes folder),
- user-uploaded CSV files,
- API responses and external data required for selected features,
- publicly accessible RSS feeds and web content where explicitly triggered.
3. Local Storage and Device Data
The application stores technical data in the user’s browser to ensure continuity of service between sessions, including:
- localStorage (application settings, preferences, UI state, presets, configuration),
- IndexedDB (cached vote sessions and related datasets).
Users may clear such data via in-app controls or browser settings.
4. Cookies
Mandate Atlas does not currently use advertising or profiling cookies. Functionality relies on browser storage mechanisms (localStorage and IndexedDB) necessary for core operation.
5. External Services and Network Calls
Depending on enabled features, requests may involve:
- HowTheyVote endpoints (data synchronisation and source referencing),
- European Parliament, Commission, and Council endpoints (data enrichment and validation),
- embedded AI system endpoints for selected analytical features,
- RSS feeds and publicly available web sources accessed via user-triggered requests,
- CDN providers (e.g. jsDelivr, unpkg, Google Fonts), which may receive standard technical connection metadata such as IP address and user agent.
6. Retention
Client-side data persists until removed by the user (via in-app controls or browser settings). Server-side retention, where applicable, depends on the deployment environment and its configuration.
7. Nature of Outputs
The service provides processed outputs (including visualisations, indicators, and analytical results). Access to the service does not, unless explicitly stated, constitute access to or redistribution of a structured database, whether original or derived.
8. User Responsibility
Users who extract, reuse, or otherwise process data obtained through the service are solely responsible for ensuring compliance with applicable licences and terms of use, including the ODbL where relevant.
9. Rights and Contact
Requests concerning access, rectification, or deletion should be addressed to the operator responsible for the specific deployment environment.