Swift legal
Privacy Policy
- Effective
- Version
- 2026-11-17.2
When this version takes effect. If you accepted an earlier version, that version keeps applying to you until 5 December 2026; from that day, the app asks you to accept this version to keep using Swift. If you accept this version before then, for example when you sign up, it applies to you from when you accept it.
This policy explains what personal data Swift collects, why, on what legal basis, who it is shared with, how long it is kept, and the rights you have. Guyana's Data Protection Act 2023 has been passed but, as of 17 November 2026, has not been brought into force. Swift follows it now and will update this policy when it starts. We collect the minimum needed to run a delivery, ride and marketplace platform, and we never sell your data.
Who is responsible (data controller)
Westbridge Inc. (trading as Swift), registration no. 17703, Lot 165 New Trafalgar Building, Waterloo Street, Georgetown, Demerara, Guyana, is the data controller. Our data protection officer is the Data Protection Officer, Westbridge Inc., privacy@swiftgy.com. For anything about your privacy — access, correction, deletion or a complaint — email privacy@swiftgy.com. This inbox reaches us even if you can no longer sign in to the app, so you are never locked out of your rights. This policy covers customers, Partners (businesses and movers), advertiser contacts, and visitors to our websites.
1. What we collect
- Account: your phone number (verified by SMS code), name, and optional email.
- A registration selfie (riders, drivers, hair, beauty and personal-care providers, and service providers and businesses that visit customers): riders and drivers take one when they sign up; a hair, beauty or personal-care provider (barber, hairdresser, salon, nail technician or makeup artist) takes one before customers can find them, wherever they work, and a person at Swift compares it with their ID, and again after a new photo or a renewed ID; any other individual service provider takes one before their first home job; and a service business takes one when it offers to go to customers (home or mobile visits), to deter account fraud; it becomes their in-app photo. A store owner, store staff, a service business (a store) that serves customers only at its own place, an advertiser, and a customer never need one. Customers see whether a hair, beauty or personal-care provider goes to their home. A selfie taken before this change stays your in-app photo and is protected as described in this policy.
- Orders, rides and bookings: what you ordered, addresses you save or enter, delivery instructions, and the trip/delivery history tied to your account. If you pay by MMG, your order also keeps the payment references section 2 describes.
- Location: your device location while you use the app to set pickup/delivery points. For movers, live location while online or on a job — that is what powers dispatch and customer tracking. Background collection for movers happens only after a separate, explicit in-app consent, and stops when you go offline. We do not keep a lasting record of where a mover has been. We keep only: your latest position on your mover profile; a short trail of your recent positions, used to work out a job's distance and to check for false positions, and deleted 3 hours after your last position; a job's distance, never its route; a single position with the order's record at certain steps of a job, or when a problem is recorded on it, such as arrival, pickup, handover or a failed delivery; positions that look false, kept for up to 400 days so a person can review them; and, while an SOS is open on a trip, the positions added to that safety record.
- Verification documents (partners only): government ID (a national ID, Digital ID card or passport) and, for movers, licence, insurance and related documents; for a business, its registration papers and, where someone other than the owner manages its Swift account (a company's account holder, or a manager), a letter of authority. These are stored privately; in the app they are viewable only by our verification team through short-lived signed links, each access logged. Identity verification is done by people: our verification team checks each partner document and, for a partner who takes a selfie, compares that partner's identity document with their selfie. Swift does not ask a customer for an ID and does not keep one. No outside identity-verification provider receives them. If a store asks us to, Swift staff may upload its papers, menu and item photos for it. We record who at the store agreed, how and when, and every upload is logged under the staff member's name. A person's own ID is uploaded only when that person agrees.
- Messages, ratings and reports: order-scoped chat messages, the ratings and review tags you give and receive, reports you file, and your block list.
- Emergency contacts: if you add one, their name and phone number. We text them a verification code immediately, use the number only for your safety alerts, and never for marketing. If someone added you and you want the number removed, email privacy@swiftgy.com.
- People named in a business's letter of authority: a letter of authority names the director or owner who signs it and the person they authorise, and carries the signer's signature. If the business asks Swift to send the letter for signing, we also collect the signer's name and phone number, text them a one-time link and code to sign it, and keep the signed letter and their signature as drawn, with their phone number, the times they opened the link, confirmed the code and signed, a keyed digest of the network address they signed from, and the device and browser they signed on, as evidence of the signature. We use these only to check that the person managing the account is authorised, keep them with the business's other verification documents (while the business is on Swift and for 90 days after), and never use them for marketing. A letter sent for signing that was not signed is deleted 30 days after its link expired or was withdrawn. If you were named in one and want to ask about it, email privacy@swiftgy.com.
- Support and consent records: your Help & Support tickets, and the consent ledger — a tamper-evident record of each policy version you agreed to, when, and on what surface. At consent we may also store a keyed cryptographic digest of your network address as evidence of the event; the address itself cannot be read back from it.
- When you sign in we keep your network address and the browser or app you used, for up to 30 days after your 7-day session ends. We also keep handover and parcel photos, and photos you send in chat.
- Device and diagnostics: a push-notification token, app version, and crash and error reports from the app and from Swift's servers (section 5 says what they contain).
- In-app calls: when Swift's in-app calls are switched on and you place or answer a call inside the Swift app, the app uses your phone's microphone for that call only, and only once you have allowed it. What you say is carried live to the other person and is never recorded, by Swift or by Twilio. Section 5 says what Twilio receives, and section 6 what Swift keeps.
- Partner records (partners only): subscription and payment-confirmation history for the weekly fee (if you pay in person, how you paid, the reference and the receipt; if you pay by card, our card processor's reference for the payment, the amount and currency, the result of the bank's security check, and whether the payment was approved, refused or refunded, never your card number), earnings summaries, and operational quality metrics.
- How you found Swift: some Swift links and QR codes carry a short tag saying where they were shared (for example a Facebook post, a flyer, or a store's QR code). If you open Swift from one, your browser or phone keeps that tag on your device for up to 30 days, then deletes it, and also deletes it once you have signed up. While it is kept, it is sent when you create an account, join as a partner (a rider, driver or business) or set up a service-provider profile. Swift does not store it with your account: it only adds one to a daily count for that tag and kind of account, and keeps no record of who signed up through which link.
2. What we do NOT collect
Swift never holds your order money, so we do not collect card numbers or mobile-money credentials. If you are a partner and pay Swift's weekly fee by card, you type your card details on our card processor's secure payment page, shown inside the Swift app or website; they go to the card processor, never to Swift. If you pay a business through MMG, that payment happens in MMG's own flow under MMG's terms. Your order keeps the record of it: what you tell us about the payment, including any MMG reference you enter; the reference and amount the business records when it confirms your payment, and who recorded it; and the reference of any refund the business records. Our websites and app carry no third-party advertising or cross-site tracking pixels.
3. Why we use it — and the legal bases
Under the Data Protection Act 2023, each use of your data rests on a legal basis:
- To perform our contract with you: running your account; transmitting orders; matching deliveries and rides; live tracking; receipts; order-scoped chat; calls between the people on an order; Partner subscription administration; checking partners' identity and licence documents, for safety and fraud prevention.
- To meet legal obligations: keeping tax and accounting records, and responding to lawful demands from authorities.
- For legitimate interests, balanced against your rights: preventing fraud and abuse (strikes, collusion checks, GPS-plausibility and account-security signals), keeping the platform safe and available, and producing aggregated, de-identified statistics (e.g. orders per day, or how many sign-ups came through each link) that carry no personal data. You may object — see section 9.
- With your consent, separately asked and freely refusable: marketing messages; background location for movers; the optional email on your profile. Consent can be withdrawn at any time without affecting the service.
- With your explicit consent: police clearance certificates (optional for taxi drivers; required for service providers who visit homes).
4. Automated systems and human review
Swift uses automated systems to match orders to movers, estimate times, and flag possible fraud or account-takeover risk. Flags lead to review, not to automatic punishment: no decision that produces a legal or similarly significant effect on you — losing your account, a penalty, a withheld payment confirmation — is taken by a machine alone; a human reviews the record first, and security holds (such as a staged change to where a Partner is paid) are announced to the account owner with a way to cancel them. You can contest any such decision through Help & Support.
5. Sharing
A business handling your order sees the items, your first name and delivery address, and your phone number, only so it can reach you about that order. A mover handling your order sees the pickup and drop-off details, your first name and your phone number, only so they can reach you about that order; a taxi driver also sees the passenger's rating. A mover or business is never shown your last name or a photo of you. Customers see the name, photo, rating and phone number of the mover handling their order, and for a taxi the car details. When Swift's call service is switched on, the current Swift app and website stop showing these phone numbers between the people on an order, and you call each other through Swift instead: Swift rings your phone from Swift's own number and you press 1, then Swift rings the person you are calling, who must also press 1 to be connected, and neither of you sees the other's number. Older versions of the app may keep showing the number until they are retired. When Swift's in-app calls are switched on, the current Swift app can also call the other people on an order inside the app, over the internet: their phone rings with a line such as "Swift: your rider is calling about your order", which names your role on the order, never your name or your number. If the call cannot reach them in the app and they did not decline it, Swift rings their phone instead, as above, when Swift's call service is on. If you do not allow the microphone, you can still call through Swift's phone line where it is on, or message them in the order chat. Calls through Swift, in the app or by phone, are never recorded. For each call Swift keeps a record with no phone number in it: who asked for the call (their account, and their role on the order, such as customer, rider or store), the role they called, when, and whether it connected and for how long. If a business takes MMG, the MMG payment details it gives Swift (its MMG number or pay link, and the name on that MMG account) are shown to you on your order, so you can pay the business directly. Your verified emergency contacts receive your live location if you raise an SOS. We share data with authorities only where the law requires it, and we document every such demand.
Technical service providers (processors): to run Swift we use a small number of providers, each bound to process only what its function needs, on our instructions: DigitalOcean (hosts Swift's servers and databases, and the encrypted storage for verification documents and images, in the United States), Cloudflare (runs the domain-name service (DNS) that points Swift's web addresses to its servers), Twilio, a company in the United States (delivers your SMS verification codes — your phone number — and, when Swift's call service is switched on, connects calls between the people on an order: both phone numbers and the call's time and length; when Swift's in-app calls are switched on, it also carries calls made inside the Swift app: your phone's push token for calls, which the app gives Twilio when you have a live order (on Android, only once you have allowed the microphone), so that Twilio can ring your phone through Apple's or Google's push service, and asks Twilio to remove when you sign out; a code for your signed-in phone that is not your name, phone number or account number; the line shown on the call screen and Swift's reference for the call; the sound of the call, live, while you talk; the call's times; and the technical details of the connection that the calling software in the app reports, such as your phone's network (IP) address, its operating system, the software's version and the call's sound quality; Twilio keeps its own records of these calls, in the United States, and the calls themselves are never recorded), Expo (delivers push notifications through Apple's and Google's push services — a device token), Resend (delivers our emails — your email address, if you gave one, and the email itself; it sends them from Brazil and keeps its records in the United States), GoDaddy (hosts Swift's own mailbox, which receives the emails you send us), MMG — Mobile Money Guyana — (processes a Partner's weekly-fee payment — the paying phone number and the amount), PowerTranz, our card processor, outside Guyana (processes a Partner's weekly-fee payment by card: its secure payment page, shown inside the Swift app or website, receives the card details typed there, the cardholder details the page asks for, such as your name and your email address or phone number, and your device's network (IP) address and browser details, for the payment and the bank's security check (3-D Secure); Swift sends it the amount and Swift's reference for the payment and receives back the payment's reference and result, never your card number; as PowerTranz serves that page, it also asks ipapi.co, an IP-location service, from your browser where your network address is located), WhatsApp, run by Meta (carries the support chats you start with us on WhatsApp — your phone number and what you write), Google Places (address search, from our servers: the text you type, an approximate area to rank results, and a map pin when you look up an address; Google does not receive your network address from these searches), and the map built into your phone — Google Maps on Android, Apple Maps on iPhone — which receives the map area you are viewing in order to draw it. Routes and travel estimates run on Swift's own servers using OpenStreetMap data. On Swift's website, maps are drawn with map images from MapTiler, a map provider that uses OpenStreetMap data: to show a map, the viewer's browser requests those images from MapTiler, which receives the viewer's network (IP) address, the address of Swift's website (never the address of the page itself, so never a tracking link's code) and which map squares are shown — on a shared trip or parcel-tracking page the location is rounded before the map is drawn, and when you place a pin (a delivery address, a parcel's pickup or drop-off, or a store entrance) it is the streets around that pin. Swift sends MapTiler no name, phone number, account or order details. MapTiler's own servers may set cookies; Swift does not. Crash and error reports go to an error-tracking service (GlitchTip) that Swift runs on its own servers: for our servers' reports we attach route templates rather than full URLs, drop request query strings, headers, cookies and bodies, and run an automated filter that removes tokens and signed links from the report — a report is diagnostic context, not your account records. If the Swift phone app crashes or hits an error, it sends a crash report to the same error-tracking service (GlitchTip) on Swift's own servers: the phone model and operating system, the app version, the error and where in the app it happened, the phone's language and time zone, and a random identifier for that app install that is not linked to your account or phone number. A crash report never includes your name, phone number, messages, location or a screenshot. No outside company receives Swift's crash or error reports, except the short error description Expo receives as described below. Our servers are with DigitalOcean in Atlanta, United States, and several providers process data in the United States. We use each provider's written data-protection terms and send only what each needs.
Notifications go through Expo, Apple and Google. They carry the notification text, for example a short chat preview or your delivery code. When the app downloads an update, Expo receives your network address and an install ID, and after a crash, a short error description. Twilio carries our texts and calls: sign-in codes, SOS alerts to your emergency contacts (your first name and a map link) and trip-share messages (car and plate).
AI processing: Swift sends nothing you write to an artificial-intelligence service. Search terms, store menus and your messages are handled by our own software and by people; no model reads them, and none is used to decide anything about you. Identity verification is done by our verification team: Swift uses no automated document-reading or face-matching service, and no identity-verification provider receives your documents or selfie. When you upload a document, automated security and file-format checks run on it first; they can accept the file, or reject it if it is unsafe or not a supported format. A person on our verification team then reviews each partner document and decides whether to accept it. If a document is rejected you are told and can submit it again, or raise it through Help & Support. Swift sends no other document, message or account record to any automated-analysis service.
Business changes: if Swift's business is transferred to a successor, your data moves with it under this policy's protections, and you are told before any materially different use begins.
6. Retention and deletion
We keep personal data only as long as its purpose or a legal duty requires. Verification documents are purged on a schedule after they stop being needed, with the purge itself logged; purged documents are irrecoverable. A police clearance is kept only as whether it was clear and the date it was issued: its image is deleted soon after our check (the app shows how many days before you upload it), and you can withdraw it at any time on its card in the app (Withdraw my police clearance); Swift then deletes it and keeps only a note that it was withdrawn, unless the law requires us to keep more. Swift no longer keeps customers' IDs: any a customer added before 1 November 2026 is withdrawn and deleted, unless a legal or safety hold keeps it until the hold ends. Order, ride and settlement history is retained for the period required for disputes, payments Swift has decided to make, tax and legal obligations. Order and job chat is deleted one year after the order or job ended, unless it is still needed for a dispute, a refund, a safety case, a report or a legal hold. Resolved Help & Support tickets are deleted 3 years after they are resolved, and closed safety records 7 years after they close, unless a legal hold keeps them. The record of a call made through Swift, by phone or in the app (no phone number, never what was said), is kept with its order's record, and the record of a call you asked for is deleted when your account is deleted. For in-app calls, Swift also keeps a note that your signed-in phone can be rung in the app (the code for that phone and when it last registered, no phone number); it is deleted 30 days after your phone last registered, and the app asks for it to be deleted when you sign out. If a Business records that a customer did not come to an appointment, Swift keeps that record (which booking it was, when the Business recorded it, and who at the Business recorded it) with its order's record, for as long as that order's record is kept, so that a person at Swift can review repeated missed appointments; it carries no fee or strike. The consent ledger is retained as legal evidence of what was agreed — it is append-only by design and is kept even after account deletion, holding only what it must. Crash and error reports are kept for 90 days, then deleted. You can delete your account from inside the app — Profile → Personal data → Delete my account — or on swiftgy.com, which closes your account, revokes signed-in access, and deletes or de-identifies personal data not subject to a legal retention duty. Customers, riders and drivers can start deletion from their profile in the app or on swiftgy.com. Active jobs and unsettled cash must be resolved first; historical earnings records do not prevent deletion. If a rider still holds a customer's cash from an order, the rider's account deletion waits until our operations team records it resolved, or for at most 90 days; the cash record is kept as part of the order record. A customer's own deletion is never blocked by this. If we cannot act on a deletion request straight away, we tell you why and when, in writing, within one month. Documents under a legal or safety hold remain protected until the hold ends, and incomplete erasure is retried automatically. Encrypted backups are kept for a limited time and are used only to restore Swift after a failure; a restore applies deletions again before the data is used. Business and advertiser profiles offer an account closure request, tracked in Help & Support, so outstanding listings, campaigns and confirmation records are handled correctly first.
7. Security
Data in transit is encrypted (the app pins Swift's certificates), access to production data is restricted and audit-logged, verification documents are encrypted at rest and readable only through short-lived signed links, security-sensitive account changes require step-up confirmation, and administrative actions on your account leave a permanent trail. If a breach is likely to put you at risk, we will tell you without undue delay and, once the Data Protection Act is in force, notify the Data Protection Commissioner within 72 hours. Businesses and Movers are bound by their agreements with Swift to use your details only for the order or job they are handling. If you think your account or phone has been compromised, tell us straight away through Help & Support or at the privacy email address above.
8. Children
Swift is for adults: you must be 18 to hold an account, and we do not knowingly process children's data. Our published Child Safety Standards state our zero-tolerance rules and the dedicated reporting channel; anything reported there is prioritised, removed, and reported to the authorities as the law requires.
9. Your rights under, and before the start of, the Data Protection Act 2023
You have the right to: access the personal data we hold about you; have it corrected; request its deletion; restrict processing; object to processing based on legitimate interests and to any direct marketing; withdraw a consent at any time; receive a copy of your data in a portable form (the app's "Download my data" does this instantly); and not be subject to a solely automated decision with legal or similarly significant effect — section 4 describes how we already work that way. Exercise any of these by email to privacy@swiftgy.com or through Help & Support; we respond within one month (up to two more months for complex requests, and we will tell you why), and identity is verified before data is released. Each right is subject to the legal retention duties described above, and exercising them never costs you the service. If you believe we have mishandled your data, you have the right to complain to the Data Protection Commissioner of Guyana.
10. Changes to this policy
Material changes are announced in the app before they take effect, and where the law requires fresh consent we ask for it. Every version of this policy is recorded with its date and an integrity hash, so the exact words that applied to you at any time are provable.