Multisite

Wynko is fully multisite-aware. Every setting, log, and alert is per-site — each site in your network connects to its own Laposta account, keeps its own activity log, and mails its own alerts on its own hourly cap. Transients are per-site for the same reason.

Per-site API keys via constants or environment variables

If you’re deploying the API key as a wp-config.php constant (or an environment variable, including one supplied through a .env file your host loads) across a network, give one site its own key by suffixing that site’s own blog ID — every site has one, visible under Sites → All Sites — not literally the number 3:

define( 'WYNKO_API_KEY_3', 'a-different-laposta-api-key' );  // only for the site whose blog ID is 3

The same suffix pattern works for every other deployable setting.

Uninstall

Deactivating and deleting Wynko walks every site in the network and clears that site’s options and transients individually — nothing is left behind network-wide, and nothing from one site leaks into another during cleanup. A key defined as a constant is never written to the database and is therefore not removed; delete the constant yourself.