Standard wp_posts rows for Elementor's page and template post types, the _elementor_data meta on each row and any _elementor_ai_* meta the plugin uses to flag AI-touched widgets, plus relevant wp_options rows for global AI settings.

No. SleekView never calls Elementor's AI service or any model vendor. It reads what Elementor has already written to your database when the editor saved the page or template.

Yes, where the plugin stamps a flag in postmeta. SleekView surfaces that flag as a sortable, filterable column. If a particular widget was edited by hand afterwards, the flag stays consistent with whatever Elementor wrote.

Yes. They are standard WordPress post types under the hood, so SleekView lists them next to pages with their type as a column. One combined view, or one view per type, your choice.

Yes. Select rows, pick a new status and SleekView writes through wp_update_post, so Elementor save hooks and any listening plugins still fire as expected.

No. SleekView is an additional admin surface. The editor stays where it is. SleekView gives a row-level audit and triage view across hundreds of pages, which the editor was never designed to provide.

Yes. Any filtered set exports as CSV with the same columns the view shows. Useful for disclosure audits and for archiving a snapshot before a redesign sprint.

No. SleekView only renders inside WP Admin and only queries the database when a view is opened. The front end of an Elementor site is untouched.