NewsletterPlatform.com database review notes

The plugin stores campaigns, consent, delivery state and private audience jobs in
its own prefixed tables. These are not posts or user metadata. Identifiers use
fixed table allowlists and prepared %i placeholders; dynamic values use prepared
placeholders or wpdb insert/update/delete methods. WordPress post, option and
user APIs are used where their semantics match the operation.

A small number of option operations require atomic compare-and-swap, exact lease
ownership, or an authoritative read immediately before transport. They invalidate
WordPress option caches when changing those options. Replacing those operations
with independent get_option/update_option calls would weaken concurrency safety.

Current consent, suppression, privacy erasure, queue ownership, sending limits,
review revisions and recovery outcomes must not be read from stale caches.
Database transactions, locks, writes, physical schema verification and explicit
uninstall are also not cacheable read operations. Interactive private reports
show presently retained records and must reflect erasure and retention on reload.

Exact line-specific Plugin Check database annotations explain these reviewed
exceptions. They do not disable SQL preparation, input validation, output
escaping, authorization or nonce checks. No whole-file or whole-plugin database
sniff exclusion is used. Such annotations document why a recommendation does not
fit a particular operation; a clean automated scan is not security certification
or WordPress.org approval.
