No. SleekView Feedback reads directly from whatever table or option key CleanTalk Pro is using. You point it at the source, pick the columns for votes, status, category, author, and title, and the board renders. No ETL job, no sync, no duplicated data. Anything CleanTalk Pro writes shows up on the next page load.

Yes. SleekView ships with anonymous voting backed by cookies, so public visitors can upvote feedback items without an account. You can also require login if you want the board restricted to editors or paying members, and the same view handles both modes with a single toggle in the block settings panel.

Each visitor gets a cookie scoped vote token per item. Logged in users are tracked by user ID. The plugin also exposes a rate limit so a single IP cannot spam the board, which is enough to keep a public spam feedback queue honest without forcing a signup wall in front of every regular reader.

Yes. SleekView accepts a WHERE clause when you wire up the data source, so you can scope the board to comment events, registration events, checkout events, or any combination of fields CleanTalk Pro already stores. Different boards on different pages can use different filters at once.

False positive is just a category value on the row. You can write it into a meta key CleanTalk Pro already understands or a dedicated column. Either way it shows up in the WordPress admin alongside the original event, so the admin tuning the filter can see the flag without leaving WordPress or chasing email.

They write back to the source column, which means CleanTalk Pro and any of your own queries can sort future rule reviews and exemptions by that score. Several teams use the score to gate which filter changes get rolled out, which makes the board operational and not just a vanity dashboard for the security lead.

Both. SleekView ships as a Gutenberg block, an Elementor widget, a Bricks element, and a classic shortcode. Theme developers can also call the render function from PHP and pass a configuration array, so you can mount the board on any template without touching the page editor or training the editors.

The view paginates server side and only loads the rows it needs to render the current page. Indexed columns stay fast even on long tables. For very busy sites, scoping the board by reason or recent date range keeps both the query and the audience focused, so the page feels snappy even at heavy scale.