LEGAL · PRIVACY · RETENTION

Evidence before activation.

SWYFT now has a private, auditable approval pack for the public-launch facts that cannot be guessed. The records exist; the real evidence and accountable approvals are still pending.

01REVIEW REQUIRED

Legal operator

Pending verified documents

The pilot does not infer SWYFT’s legal operator from a customer, business workspace, domain owner, or app-store account. The real operator and public business address require documentary and legal review.

02REVIEW REQUIRED

Privacy contact

Pending named owners and tests

A public privacy contact needs a primary owner, a different backup owner, a monitored mailbox, domain authentication, inbound and outbound delivery tests, and legal approval.

03REVIEW REQUIRED

Retention schedule

0 of 11 categories approved

Eleven operational data categories are registered for review. No retention period, legal basis, disposal method, exception, or public promise has been invented or activated.

CATEGORY REGISTER

A schedule without made-up dates.

Every category must receive its actual purpose, lawful basis, retention trigger, approved duration, exceptions, disposal method, public summary, human approval and legal review.

  1. Account identityPending approval
  2. Driver onboarding and KYCPending approval
  3. Vehicle and compliancePending approval
  4. Delivery transactionsPending approval
  5. Location and trackingPending approval
  6. Payments and ledgerPending approval
  7. Delivery proof and mediaPending approval
  8. Support, disputes and safetyPending approval
  9. Notifications and device tokensPending approval
  10. AI inputs, outputs and logsPending approval
  11. External rights requestsPending approval

FAIL-CLOSED RELEASE

Completing the pack still does not launch the form.

After every item is verified, SWYFT must separately test the transactional-email and support channels, name the human review and escalation owners, obtain the final release decision, and keep the public request gate locked until that decision is recorded.

See the protected request boundary.

The external rights-request gate remains disabled. Pilot customers who can sign in may continue using the authenticated in-app account-deletion request.