SWYFT provides an authenticated in-app deletion request with a trackable receipt and a human-reviewed retention check.
In-app deletion request active · External web request pending
01
Start the authenticated request
In the Customer app, open Account → Privacy and security → Request account deletion. Confirm the request while signed in. The secure backend creates a support receipt beginning with TKT and prevents duplicate open requests.
02
If you cannot sign in
Use password recovery first so the request can be tied to the correct account. The secure external-request backend and abuse controls are installed, but public submission remains locked. Check the external rights-request gate for its verified activation status.
03
What the request covers
The request covers the customer account and associated personal data held for the SWYFT service. It is not an instant destructive action. Authorized operations first verify identity, open deliveries, unsettled payments, disputes, safety events and records that may be subject to a legitimate retention obligation.
04
Deletion and restricted retention
Eligible personal data is deleted or de-identified. A narrowly required legal, tax, accounting, payment, fraud, safety, claim or dispute record may be retained with restricted access and removed or de-identified when the obligation ends. The final category-by-category schedule still requires approval.
05
Pilot limitation
This page documents the working in-app deletion path for internal testers. The external channel cannot accept requests until the legal operator, accountable privacy contact, retention schedule, transactional email, and human review owner are verified.