No. All the data the bot quotes comes from the local WordPress database, specifically the ast_sites_imported_data option and the _astra_sites_imported_post and _astra_sites_imported_term postmeta. The Starter Templates plugin populates these during import, so SleekAI reads them without any outbound API call.

The Wizard exposes the ast_sites_imported_data option, the imported_post and imported_term postmeta, and the list of plugins recorded by the import. You can map any other option or meta in two clicks, including custom flags written by a Premium Starter Templates plan or a White Label import.

Yes. The Starter Templates import stores the page builder choice in the import data, so the bot can quote whether the site was set up with Elementor, Beaver Builder, Brizy, Spectra, or the block editor. That matters because the cleanup path is different per builder, especially for custom template parts.

Some optimization plugins prune unknown options. If ast_sites_imported_data is missing, the bot still works by reading the _astra_sites_imported_post postmeta, which lives on each imported page and is harder to remove. It just cannot quote the source template name or the import date in that case.

Yes. Display conditions support user role, logged-in state, and URL pattern. A typical setup limits the bot to administrators on /wp-admin/themes.php?page=starter-templates and the related admin URLs. Visitors never see the audit bot, and a separate public bot can run under multibot.

No. By default SleekAI only reads data. Action toolcalls are opt-in and disabled. The bot identifies imported posts, but the actual delete or trash step is still a manual click by an admin, which keeps cleanup safely auditable, especially on sites with multiple editors.

Yes. The import data records the plugin slugs installed during template setup. The bot lists those, checks whether each plugin is still active, and can suggest deactivating or removing ones that have no posts, no entries, or no settings configured. That helps shrink the security surface.

Most teams keep this one admin only. The Starter Templates audit is internal cleanup. Clients usually do not need to know which demo pages still exist. You can spin up a separate public bot for actual client questions and limit this audit bot to administrators inside wp-admin via display conditions.