WPCompliance bundles cookie consent, policy generation and subject-request handling into a single WordPress plugin. Each module writes its own data: the cookie banner records consent decisions per visitor, the policy generator stores which policies were generated and last reviewed, and the request handler keeps a log of access and erasure requests with their status.

The plugin's admin uses tabs per module, which is appropriate per site but does not give a posture view. Which requests are still open, which consent decisions came from the marketing module, when the policy was last refreshed, all live behind separate tabs. Answering across them today means clicking through and exporting CSVs.

SleekView reads the WPCompliance consent table, policy metadata and request log directly. Sort by decision_date to see the latest consent. Filter by request_status to drain the open queue, by active_module to see which modules write what, by site to compare installs. The plugin still owns the modules and the workflow. SleekView only adds the sortable triage surface.

WPCompliance bundles three jobs into one plugin: consent banner, policy generator and request handler. Each module produces its own data, and each has its own tab in the admin. The questions privacy officers and agency leads ask cross those tabs.

How many decisions did the banner capture, how many requests are still open, which modules are actually active, did the latest policy review complete. SleekView reads the same stores and renders them as one sortable workspace. Same plugin, same modules, but a posture surface that matches how DPIA evidence and queue management actually get done.