外掛標籤
開發者團隊
② 後台搜尋「Bear Essentials: Account Manager」→ 直接安裝（推薦）
原文外掛簡介
Add a Delete My Account option to WordPress or WooCommerce so eligible
customers can permanently delete their own accounts after confirming their
password. Bear Essentials: Account Manager checks for outstanding obligations
before proceeding and explains when a customer needs help instead.
WooCommerce customers use My Account. On other WordPress sites, add the form
to a page with a shortcode. Ordinary customer/subscriber accounts are supported.
Delete My Account > Confirm Password > Check > Delete or Explain.
Customer self-service: Password confirmation and permanent-deletion consent.
WooCommerce safeguards: Completed orders need not block deletion. Orders survive; supported privacy settings control personal-data handling.
Clear help route: Blocked customers can use Request Help; administrators review and reply under Users > Account Deletion.
Simple administrator control: One immediately saved ON/OFF switch. Deletion is OFF by default, including after version upgrades.
Supported competition integrations: Protects detected entries and prize-related records for integrations such as Flintop Giveaways.
On-screen results: Confirms verified completion, without sending customer emails.
By Bear Branding Co. Part of Bear Essentials: straightforward solutions
to everyday WordPress problems. Simple tools without unnecessary complications.
Security and data handling
Deletion requires the saved administrator toggle to be ON. Version upgrades
reset it to OFF. BEAAM_ENABLE_SELF_SERVICE_DELETION=false in trusted site
configuration overrides the toggle; the plugin never changes that configuration.
A legacy true constant alone does not enable deletion. Staging and production
use the same process without a development allowlist or test helper.
Signed-in customers/subscribers confirm their password and permanent deletion.
Checks include POST, user/session-bound nonces, HTTPS (except explicit local
environments), throttling, per-user locking and repeated safety checks.
Privileged roles and multisite are unsupported. Successful deletion revokes
sessions. Passwords are checked with WordPress, not stored by this plugin.
Supported WooCommerce privacy settings control anonymisation or invoice
preservation. Orders and financial totals/currency are verified and retained;
unnecessary standard contact, shipping, tracking and customer-note fields are
minimised when invoice identity remains. Previously used integrations that
become unavailable fail safely rather than treating their records as absent.
All detected Flintop ticket, winner and instant-win ownership records cause a
hold, regardless of status, including historical, archived, trashed or
unregistered-status records. Stored ownership is checked even when Flintop is
inactive. A closed draw is not proof that prize obligations are settled.
Request Help does not settle prizes, transfer entitlements or remove records.
Safe historical hold resolution is not automated or verified. The plugin never
suppresses Flintop’s deleted_user hooks or starts its queue.
Privacy
No telemetry, remote service, license server or customer-email transport is
included. Requests, statuses, timestamps, original numeric customer IDs, help
messages/replies, processing receipts and pseudonymous signed audit events are
stored in the site’s WordPress database. Existing notes and approvals survive.
Necessary orders, requests and audit evidence may survive account deletion and
plugin uninstall. Free text can contain personal information. Site owners must
justify retention, explain it in their privacy policy and minimise unnecessary
identifying text. WordPress privacy exporter and eraser callbacks disclose
retained request evidence; they do not promise erasure of external services,
independent app tokens or backups.
Audit identifiers and signatures use separate random installation keys in a
non-autoloaded option, independent of WordPress authentication secrets and salt
rotation. Preserve these keys with secured database backups. Missing/invalid
keys stop signing/deletion rather than replacing keys for existing evidence.
Old salt-derived signatures remain unchanged and explicitly unverified.
See AUDIT-SECURITY.md for key-loss, legacy and threat-boundary limitations.
Compatibility and limitations
Installed testing used WordPress 7.1.3, PHP 8.2, MySQL 8.4, WooCommerce 11.2.1/HPOS
and Flintop Giveaway 13.5.0. Standalone/absent integrations have isolated API
contract coverage, not universal version/theme/extension testing.
Staging tests covered empty-account deletion, completed-order preservation and
unresolved prizes; RC.2 covered status-independent ownership. Anonymisation
contract tests do not imply all installed combinations were destructively tested.
Completion is reported only after verified account removal and saved evidence.
Erasure is not one atomic transaction: a later failure can leave some data erased
and require recovery. Do not blindly retry an incomplete operation. Plugin-file
rollback cannot restore deleted users or personal data.
Custom stores, external processors, app tokens and backups are not universally
erased. Mobile-app/public-page/store checks remain each site’s responsibility.
