> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/deployment-and-licensing/security-and-data-protection/data-processing-and-gdpr-compliance.md). # Data processing & GDPR compliance Infotopics operates from the Netherlands (European Union) and complies with the **General Data Protection Regulation (GDPR)**. Data protection principles are embedded into both product design and operational processes. *** ### GDPR compliance Infotopics ensures that: * Personal data is processed lawfully and transparently * Data is processed only for defined and legitimate purposes * Data processing is limited to what is strictly necessary * Appropriate technical and organisational safeguards are in place *** ### Roles and responsibilities Under GDPR: * **Customers** act as the **Data Controller** * **Infotopics** acts as the **Data Processor** Customers retain ownership and control of their data at all times. *** ### Data Processing Agreement (DPA) The **Data Processing Agreement (DPA)** forms part of the contractual agreement between Infotopics and its customers. The DPA defines: * Scope and purpose of data processing * Types of data processed * Security measures applied * Use of sub-processors * Data breach notification procedures * Data retention and deletion policies The DPA applies primarily to **solutions that store or process data outside Tableau**, such as: * WriteBackExtreme * MailScheduler * DashboardUsage Extensions that operate entirely within Tableau dashboards and do not store data externally do not require persistent data processing agreements. *** ### Data retention and deletion Upon termination of services: * Customer-specific environments are removed * Application data (such as audit logs or mappings) is deleted * Only legally required contractual or financial records are retained --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.infotopics.com/deployment-and-licensing/security-and-data-protection/data-processing-and-gdpr-compliance.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.