User Roles

Account Closure — Self-Deletion

How users request account deletion, the 30-day grace period, and what data is removed.

Users can request permanent deletion of their Influenzic account from their dashboard settings. The request is not immediate — it enters a 30-day cooling-off period during which the admin can reject it and the user can cancel it themselves.

Requesting Account Closure

  1. Go to Settings → Account → Close Account.
  2. Read the consequences listed and confirm.
  3. The request is submitted. inzc_deletion_requested_at is stamped on the user record.

Blocking Conditions

The platform blocks a closure request if the user has any of the following at the time of submission:

  • Active projects (status = active)
  • Open disputes (status not resolved or closed)
  • Positive wallet balance
  • Pending payout requests

The user must resolve these before the request is accepted.

Grace Period (30 Days)

After submission, the account enters a 30-day grace period. The daily inzc_process_pending_closures cron processes any request that has aged past 30 days. During the grace period:

  • The account continues to function normally.
  • The admin can reject the request from Influenzic → Pending Closures.
  • The user can cancel the request from their settings.

What Happens on Processing

When the grace period expires and the cron processes the request:

  • The WordPress user is tombstoned (not hard-deleted): the display name is replaced with a generic label, the email address is changed to closed-{id}@account.invalid, and the password is randomised. The user row is retained to preserve foreign key integrity in transaction and project history.
  • Social accounts, social account history, portfolio items, and portfolio media library attachments are permanently deleted.
  • All inzc_* user_meta except the closure markers (inzc_account_closed, inzc_account_closed_at) is purged.
  • The user is barred from logging in.
Account closure is irreversible once processed. The tombstoning approach preserves historical project and transaction records for audit and legal compliance; it does not delete the underlying WordPress user row.

Was this article helpful?