> 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/writebackextreme/prologue/architecture/data-handling-and-security-in-writebackextreme-saas.md).

# Data handling and security in WriteBackExtreme (SaaS)

WriteBackExtreme is designed with data integrity and operational transparency in mind. Here's how data is handled during the writeback process in our **SaaS deployment**:

* **Data Transmission**: Entered data is passed directly to the configured target database during the writeback operation.
* **Audit Trail**: A copy of the submitted data is stored in an **audit table** within the WriteBackExtreme repository database, providing traceability and accountability.
* **Linked Mark Data**: When interacting with marks in Tableau (e.g., adding a comment), the extension stores references to these marks to preserve context.
* **No Data Inspection**: WriteBackExtreme **does not inspect, log, or process** the content of user-entered data beyond storage for audit and linking purposes.
* **System Logs**: Operational logs are collected (e.g., for error reporting), but **they do not include any user-entered data**.

We understand the importance of keeping architecture secure and transparent. On our roadmap for this year, we plan to introduce a feature that allows both audit data and linked data to be stored **directly on the target connection database instead of our repository**. Once this is released, this will provide full control and transparency over where and how your data is stored.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.infotopics.com/writebackextreme/prologue/architecture/data-handling-and-security-in-writebackextreme-saas.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.