Your data should move with boundaries.

SWYFT NEXUS AI Technologies OPC, doing business as SWYFT NEXUS, is the legal operator responsible for the controlled SWYFT pilot data flow. Its registered office is in Muntinlupa City, Philippines. A monitored public privacy contact and named privacy representative must still be approved before public registration opens.

SWYFT may process account identifiers, name, email, mobile number, saved and delivery addresses, selected map points, booking and route details, cargo descriptions and photos, payment status and references, delivery evidence, notification identifiers, support messages, ratings, security events, and AI conversations you choose to submit. SWYFT never asks for your GCash PIN or OTP.

Necessary data is used to secure accounts, prepare quotes, perform deliveries, verify payments, match approved drivers, provide tracking and support, prevent fraud, resolve claims, maintain financial records, and comply with applicable obligations. Optional AI or marketing use requires an approved basis and user control where required.

Assigned drivers and authorized business users receive only what is needed for a delivery. Current service providers support hosting and authentication (Supabase), maps and routing (Google), payment processing (Xendit), notifications (Firebase), and approved AI testing (OpenAI or another configured provider). Provider processing and transfer safeguards remain part of the final legal review.

Customers select delivery points rather than sharing continuous device location. Approved drivers share foreground location while on duty or completing an active trip. Private proof photos, timestamps and bounded location evidence may be used to complete the service, settle earnings, investigate a legitimate dispute, or protect users.

Rules and AI may assist cargo classification, vehicle suggestions, dispatch ranking, fraud signals, proof checks and coaching. Public AI decisions are currently disabled. Penalties, disputes, account restrictions and safety-critical outcomes require deterministic controls and human review.

Data should be kept only as long as needed for its purpose and applicable legal, tax, accounting, payment, safety, fraud, claims and dispute obligations. The final category-by-category retention schedule is not yet approved. Customers can start an authenticated deletion request in the app; records that must remain are restricted and later deleted or de-identified when the obligation ends.

Subject to applicable law, a person may ask to be informed, access personal data, correct inaccuracies, object or withdraw consent, request erasure or blocking, obtain portable data where applicable, and raise a complaint. The verified public privacy representative and external request channel must be published before public registration opens.

This notice describes the current controlled pilot and is not represented as the final public Privacy Policy. The final version must publish the approved privacy representative and contact channels, processing locations, category-by-category retention periods, complaint process, effective date and prior versions.