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.