Bear Essentials: Account Manager Wordpress Plugin - Rating, Reviews, Demo & Download
Plugin Description
Simple, secure account deletion for WordPress. Let users permanently delete their accounts with password confirmation. No fuss, no complicated settings. Just install, enable and you’re ready.
By Bear Branding Co. A lightweight self-service account-deletion plugin for
ordinary WordPress customer/subscriber accounts. Works without WooCommerce or
Flintop; both are optional integrations. No administrator approval workflow,
retention wizard, email transport or Action Scheduler dependency.
Customers confirm their password and permanent-deletion checkbox. The plugin
checks their records before processing. A blocked customer sees an explanation
and one Request Help button. Administrators read and reply under Users > Account
Deletion; there is no administrator deletion button. Replies and completion
confirmations appear on-screen, not by email.
Deletion is OFF by default, including after a version upgrade. Administrators
use the immediately saved ON/OFF switch at the top of Users > Account Deletion.
Security and data handling
Deletion requires the saved administrator toggle to be ON. Existing installs
are reset to OFF when upgraded, even if a legacy server switch was true.
BEAAM_ENABLE_SELF_SERVICE_DELETION=false in trusted site configuration always
overrides the toggle and prevents enabling it. The plugin never changes that
configuration. A legacy true value alone does not enable deletion. Staging and
production use the same guarded process; no allowlist or test helper is required.
Password confirmation, a user/session-bound nonce, POST-only processing, HTTPS
(except explicit local environments), throttling, per-user locking and repeated
safety checks protect the operation. Privileged roles and multisite are not
supported. The ordinary customer/subscriber must be signed in.
Completed WooCommerce orders do not automatically prevent deletion. Supported
WooCommerce privacy APIs and the site’s existing order-erasure choice determine
anonymisation or invoice preservation. Orders are detached, not deleted, and
financial totals/currency are verified. When invoice identity remains, standard
unnecessary contact/shipping/tracking and customer-note fields are minimised.
The site owner remains responsible for justifying retained information.
Outstanding/unknown orders, download rights, unresolved subscriptions and
customer-authored content can require help. Previously used integrations that
become unavailable fail safely rather than assuming their records disappeared.
Flintop historical-record limitation
Every detected Flintop ticket, winner or instant-win ownership record causes a
hold, regardless of status, including archived, trashed or unregistered-status
records. Stored ownership is checked even when Flintop is inactive. A closed
draw alone is not proof that prize obligations are settled.
Request Help preserves the account and opens an administrator resolution request.
It does not transfer entitlements, settle prizes, remove historical records or
bypass checks. Safe historical hold resolution is not automated or verified.
The plugin never suppresses Flintop’s deleted_user hooks or starts its queue.
Privacy
This plugin has no telemetry, remote service, license server or customer-email
transport. It stores request status, timestamps, original numeric customer ID,
help messages/replies, processing receipts and pseudonymous signed audit events
in the site’s WordPress database. Existing administrator notes and approvals
are preserved. Passwords are checked with WordPress and are not stored by this
plugin. Necessary order records, request evidence and audit records may survive
account deletion and plugin uninstall; free-text messages may contain personal
information. Site owners must explain and justify retention in their privacy
policy and minimise unnecessary identifying text. WordPress privacy exporter
and eraser callbacks disclose retained request evidence; this is not a guarantee
that external services, independent app tokens or backups have been erased.
Audit identifiers and signatures use separate, randomly generated installation
keys stored in a non-autoloaded WordPress option. They do not use WordPress
authentication keys, cookies or salts and survive authentication-salt rotation.
Preserve these keys with your secured database backups. Missing or invalid keys
stop new signing/deletion rather than silently replacing keys for existing
evidence. Old salt-derived records remain unchanged and are labelled as legacy
signatures, not cryptographically verified. See AUDIT-SECURITY.md.
Compatibility and limitations
Version 1.2.6 separates audit and order-comparison cryptography from WordPress
authentication secrets. Existing interface and deletion protections are retained.
Password, identity, order, competition, audit and completion checks are unchanged.
Installed testing used WordPress 7.1.3, PHP 8.2, MySQL 8.4, WooCommerce 11.2.1
with HPOS and Flintop Giveaway 13.5.0. Standalone/absent-integration behaviour
passed isolated WordPress API contract tests. This is not a claim that every
WordPress/PHP version, theme or third-party extension has been tested.
Controlled staging tests verified empty-account deletion, deletion with a
preserved completed order, and protection of an unresolved prize. Later RC.2
tests verified status-independent ownership detection without deleting accounts.
The order-anonymisation branch has isolated contract coverage; equivalent
installed destructive testing was not repeated.
Successful completion is shown only after verified account removal and saved
completion evidence. WordPress sessions are revoked. Erasers are not one atomic
transaction: a later failure can leave some data erased and require recovery.
Do not blindly retry an incomplete operation.
Existing requests and signed audit evidence are preserved, including on
uninstall, and may contain personal data requiring the site’s normal review.
External processors, custom stores, separate app tokens and backup copies are
not universally erased. Mobile-app and public-page/store-declaration checks
belong to each site’s deployment, not a bundled app-store certification.
Screenshots
No screenshots provided
