SAC Database Inspector

SAC Database Inspector helps administrators understand what is using the WordPress database before deciding whether maintenance is appropriate.

It is inspection-first: no background cleanup, “clean everything” action, telemetry, paid feature, or automatic external request is included.

Database diagnostics

• Runtime, storage, and maintenance health categories
• Deterministic and explainable health penalty score
• Database and table sizes when the host permits access
• Graceful fallback when information_schema is restricted
• Object-cache status and bounded maintenance counts

Ownership and footprints

• Conservative plugin option, metadata, transient, and custom-table estimates
• Active, inactive, not-installed, WordPress core, theme, and unknown owner states
• Explicit ownership confidence and evidence
• Inactive installed plugins are never treated as missing

Autoload and ghost data

• Paginated, searchable, size-sorted autoload inspector
• Serialized, protected, owner, status, confidence, and size indicators
• Capped option previews with centralized sensitive-name redaction
• Orphan metadata, expired transient, missing-plugin option/table, and stale cron findings
• Heuristic findings are read-only and never automatically deleted

Controlled maintenance and rollback

• Capability, nonce, target, read-only-mode, and explicit-confirmation checks
• At most 100 records changed per request
• Lightweight local safety snapshots before supported changes
• Restoration for options, autoload state, and orphan metadata
• Protected WordPress options cannot have autoload changed

Reports and optional AI

• Redacted JSON, CSV, and HTML exports from one normalized report
• Optional WordPress 7.0 AI Client explanations when a text provider is configured
• Provider-neutral integration with no SAC API-key settings
• AI receives capped metadata, not raw option values or database credentials
• AI cannot run SQL, clean data, change options, or restore snapshots
• All deterministic features work without AI

Privacy and external services

SAC has no telemetry or tracking. Database inspection and exports are local.

If an administrator explicitly requests an AI explanation, SAC passes a capped and redacted metadata-only diagnostic context to the provider selected through WordPress Settings → Connectors. The external service, data handling, and terms depend on the connector/provider configured by the site owner. SAC does not store provider credentials and does not send raw option values, database credentials, WordPress salts, private keys, or authentication tokens.