Last updated: 11 September 2026
This Privacy Policy explains what personal data SuriGO collects, why we collect it, who else receives it, how long we keep it, and what you can ask us to do about it.
It applies to the SuriGO customer app (com.surigoapp.customer), the SuriGO driver app (com.surigoapp.driver), the SuriGO store app and store panel, and to our website and API at api.surigoapp.com.
We recommend reading the whole policy, but these are the points people ask about most:
SuriGO is a super-app for Suriname offering rides, deliveries and store orders. The company that decides how your personal data is used — the data controller — is:
For anything about your privacy — questions, complaints, or a request to use one of the rights in section 11 — write to contato@surigoapp.com. That is the channel we monitor for privacy requests, and the one we answer from.
For everyday help with an order or a ride, use the chat inside the order or the ride, or the Help section in the app — that Help chat is run for us by tawk.to, listed in section 8.2. You can also call [PENDENTE: telefone de suporte].
In an emergency in Suriname, call 115. SuriGO is not an emergency service.
Three different kinds of people use SuriGO, and they do not give us the same data. Read the part that describes you. Where a section does not say otherwise, it applies to all three.
If you are not a SuriGO user but your data reaches us anyway — for example, you are the recipient of a parcel a customer sent you — see the note at the end of section 3.
The tables below list what we actually collect, why, and who else sees it. Data described as "SuriGO only" stays on our own servers and is not sent to any outside company, although it may still be shown to the store or the driver handling your order.
| What we collect | Why | Who else receives it |
|---|---|---|
| Name, email address, phone number and country code | To create and secure your account, and so the store and the driver can reach you about your order | Your phone number goes to Google (Firebase Phone Authentication) to send your SMS code. Your email goes to Brevo when we send you a transactional email. Your name and email go to the payment provider if you pay online. |
| Password | To sign you in, and to confirm sensitive actions such as deleting your account | Nobody. We store it as a one-way hash and never see the original. |
| Profile photo | So the driver and the store can recognise you | Stored by us. The photo address is also written to Google Cloud Firestore as part of the order chat. |
| Saved delivery addresses: label, street, city, district, country and map coordinates | To deliver your order, to calculate the delivery fee, and to check whether a store delivers to you | Google Maps Platform, when we turn what you typed into coordinates. The address on an order is passed to the store and the driver. |
| Location from your device | See section 4 | See section 4 |
| Orders and rides: items, prices, tips, discounts, notes, pickup and drop-off points, times, distance and fare | To run, charge for and prove the order or ride | The store sees the order; the driver sees the pickup and drop-off. Ride routing uses Google Maps Platform. |
| Payment records: amount, method, provider reference and status | To take payment and to settle disputes | The payment provider you chose. We never receive or store your card number. |
| Wallet balance and transaction history, loyalty points, referrals | To let you pay from your balance, transfer balance and earn rewards | SuriGO only. |
| Prescription photos, on pharmacy orders | So the pharmacy can fill your medicine order | The pharmacy you ordered from. See the note on health data below. |
| Chat messages with the store and the driver, including photos you send | To let you sort out a problem with an order in progress | Google Cloud Firestore, which stores the messages. The alert that a new message arrived also passes through Google Firebase Cloud Messaging, carrying the message title and body. |
| Ratings and written reviews of stores, drivers and products | To keep quality up and to help other users choose | Published in the app. Your rating is visible to the store or driver you rated. |
| Shopping lists and favourites | To let you reorder quickly | SuriGO only. |
| Push notification token, device identifier, app version and chosen language | To send you order and chat notifications, and to show the app in your language | Google Firebase Cloud Messaging receives the token and the notification text. |
| Sign-in records: your email address, your IP address, and your device type, platform and browser | Account security — so we can spot a suspicious sign-in and tell you about it | SuriGO only. |
| Crash reports: the error, your device model and your operating system version | To find and fix bugs | Google Firebase Crashlytics. |
| Advertising identifier, customer app only | None. We do not advertise. See the note below. | Meta (Facebook). |
Health data. A prescription photo says something about your health, which makes it more sensitive than the rest. We collect it only when you choose to order from a pharmacy and upload it yourself. It is attached to that one order and is visible to the pharmacy filling it and to SuriGO staff handling a problem with it. We do not use it for anything else, and we do not share it with any other store, with the driver, or with any outside company.
Advertising identifier. The customer app currently includes the Meta (Facebook) software kit. It starts together with the app and is able to read your device advertising identifier, even though the Facebook sign-in button is switched off. SuriGO runs no advertising campaigns and makes no use of this identifier. We are removing this component from the customer app. Apart from this, there is no analytics or advertising tracking of any kind in SuriGO — no Google Analytics, no Meta Pixel, no attribution service — on the website or in any of the apps.
People who are not SuriGO users. When you send a parcel, you give us the name, phone number, address and delivery note of the person receiving it, for up to four stops. We use that only to deliver the parcel and to let the driver call the recipient if something goes wrong. We do not create an account for the recipient, we do not market to them, and we do not use their details for anything beyond that delivery. Please give us only recipient details you are allowed to share. If you are a recipient and want your details removed, write to contato@surigoapp.com.
Everything in 3.1 that concerns your account — name, email, phone, password, profile photo, notifications, sign-in records, crash reports, chat — also applies to you. On top of that:
| What we collect | Why | Who else receives it |
|---|---|---|
| Identity document: your ID-Kaart or passport, as a photo or PDF, with its expiry date | To confirm you are who you say you are before you carry passengers or goods. Required for both rides and deliveries. | Reviewed by SuriGO staff. Not sent to any outside company. |
| Driving licence (Rijbewijs), with its expiry date | Legally required before you may accept rides | Reviewed by SuriGO staff. |
| Vehicle documents: Nummerbewijs, Keuringsbewijs and Verzekeringsbewijs | To confirm the vehicle is registered, roadworthy and insured | Reviewed by SuriGO staff. |
| Vehicle details: type, make, model, colour and number plate | So the customer can identify the vehicle arriving, and so we offer you only jobs your vehicle can do | The customer sees the vehicle description for their own ride or delivery. |
| Precise location while you are online, including when the app is not on screen, together with the direction your device is facing | To offer you the nearest job, to show the customer and the store where you are, and to estimate arrival times | Sent live to the customer and the store of the order you are carrying. See section 4. |
| Payout details: account holder name, account number and payment instructions | To pay you | SuriGO only, plus the bank or payment service used to make the transfer. |
| Earnings, commission and cash you owe us from cash orders | To settle accounts with you | SuriGO only. |
| Proof of delivery: a photo you take at the door, or the recipient's signature drawn on your screen | To prove the order was delivered, and to settle a "never arrived" dispute | Attached to the order. This is data about the customer that you collect for us — please photograph the package and the doorstep, not people. |
| Ratings customers give you | Service quality | Shown as an average in the app. |
We keep your identity and vehicle documents so we can show a Surinamese authority, or a customer making a claim, that you were licensed to do the job on the day you did it. If you send us a replacement document, we keep the earlier version too, so that a rejection can be checked against what you actually submitted.
Everything in 3.1 that concerns the account of the person managing the store also applies. On top of that we collect:
We use these to confirm that the business is real and licensed, to pay you, and to meet our own tax and record-keeping duties.
This is the part of the app people worry about most, so we are being specific. The customer app and the driver app do not behave the same way, and we do not want you assuming the wrong one.
Why we need it. To deliver an order we need to know where to take it. To show you stores, we need to know which ones deliver to where you are.
Where it comes from. Either you type the address yourself, or you let the app read your device's location using GPS and nearby mobile and Wi-Fi networks. Either way, you confirm the address before an order is placed.
When we read it. The customer app asks your device for a precise position at specific moments: once when you open the home screen, when you tap "use my location", when you place a pin on the map, at checkout, and when you create a parcel. On the ride-booking screen, the app reads your position when the screen opens, so that the map and the pickup pin start in the right place.
When we stop. When you leave those screens, or close the app, the app stops reading your position.
The customer app does not collect location in the background. The Android permission that would allow it (ACCESS_BACKGROUND_LOCATION) is deliberately stripped out of the customer app when it is built, so the app is not technically capable of it. While you watch a delivery move on the map, you are receiving the driver's position — your own phone is not reporting anything.
You can say no. If you refuse the location permission, the app still works: type the delivery address instead. It is slower, not blocked.
One thing you should know. While you have the app open, it attaches your last known coordinates to the requests it sends to our servers. We do not use those coordinates for any feature, and we are removing this from the app.
If you drive for SuriGO, read this carefully. It is the real difference between the two apps.
What we collect. Your precise position from GPS, and the direction your device is facing.
When it starts. The moment you set yourself Online in the driver app. Not at install, not at sign-in — when you go online.
How often. Your app sends a new position each time you have moved more than a set distance, currently about 2 metres, and at most once every 3 seconds. Moving through traffic, that is up to roughly twenty positions a minute. Both figures are settings rather than fixed rules; the ones written here are the values in force today.
In the background. Yes. While you are online, the driver app keeps reporting with the app behind another app and with the screen off. That is the whole point: a job cannot be offered to you if we cannot tell how far away you are. While the driver app is reporting your position in the background, Android shows a permanent SuriGO notification in your status bar.
If you are standing still. Positions are sent when your position changes, not on a timer. Parked at a traffic light or waiting outside a restaurant, your app sends us little or nothing — though a GPS reading drifts by a few metres even on a phone that is not moving, so the occasional position still goes out.
When it stops. When you set yourself Offline, the app stops sending your position to us and you disappear from the dispatch map. Being straight with you about what happens next: because of a defect we have identified and are fixing, the app keeps reading GPS in the background after you go offline, even though it no longer sends anything to us and we do not record it. It stops completely when you close the app — swipe it away from your recent apps list — or restart your phone. Nothing turns it back on by itself: there is no component in the driver app that restarts location tracking after a reboot.
What we keep. This matters, and it is good news: we do not build a history of your route. Our database holds one row per driver — your last known position — overwritten by each new one. There is no trail of where you drove yesterday. Your live position is also held in our in-memory index so that nearby jobs can be found, and is sent in real time to the customer and the store waiting for the order you are carrying.
What your app sends that we do not keep. The app also transmits your speed, the accuracy of the GPS fix and the time of the fix. Our servers do not store any of the three. We are removing them from what the app sends.
So that you can compare what we say here against what your phone tells you, this is what each app asks for and why.
Customer app: notifications, for order and chat updates; location while using the app, as described in 4.1; camera, through the QR scanner, to sign in by QR code and to check a parcel; and access to your photo gallery, to set a profile photo and to upload a prescription. The customer app also still declares a phone-state permission inherited from the software it was built on. No part of the app uses it, and we are removing it.
Driver app: notifications; precise location, including background location, as described in 4.2; a foreground service, a wake lock and an exemption from battery optimisation, all so that Android does not kill the tracking service while you are working and drop you off the map; camera, for document photos, proof-of-delivery photos and the order QR scanner; and permission to display over other apps, which is what lets a new-job alert appear on top of whatever you are doing.
You can withdraw any of these permissions in your phone's settings at any time. If you refuse the location permission in the driver app you can still set yourself Online, but we cannot see where you are, so jobs near you will not be offered to you.
Suriname does not yet have a general data protection law setting out these grounds, but we think you are entitled to know them anyway, so we hold ourselves to the following:
We do not sell your personal data. We share it in four situations: with the other people in your order, with companies that provide part of the service, when the law requires it, and if the business is ever sold.
These are the outside companies that actually receive data today. Each is bound to use it only to provide its service to us.
One more, and you are the one who starts it: when you tap to navigate, the app hands the pickup or delivery coordinates to the navigation app you pick on your own phone — Google Maps or Waze, for example. To be able to offer you that choice, the app first checks which map applications are installed on your device. The app you choose is not ours and has its own privacy policy.
Payment methods our software supports but which we do not currently use receive nothing at all: Stripe, PayPal, Paystack, RazorPay, Flutterwave, PayTM, PayU and Abitmedia. The same is true of the SMS providers our software supports but which are switched off — your SMS code is sent by Google, not by them.
We will disclose data to the police, a court or another authority when the law requires it, and we may do so on our own initiative where we believe there is a serious risk to someone's safety or evidence of a crime against SuriGO or its users. If SuriGO is ever merged with or sold to another company, your data may transfer with the business, and you will be told before that happens.
Suriname is our market, but our systems are not physically in Suriname. Our servers, database, uploaded files and backups are hosted on a server in the United States. The companies listed in 8.2 process data in the United States, the European Union and Malaysia.
This means that when you use SuriGO, your personal data leaves Suriname. We require every provider we use to protect it to a standard no lower than the one described in this policy.
Inside the app: open Profile, choose Delete account, enter your password and confirm. You can tell us why you are leaving, but that is optional.
From a web browser, without installing anything: go to https://api.surigoapp.com/pages/account/deletion, which explains both routes. If you no longer have the app, you can ask us by email; we confirm your identity before deleting anything.
Before you delete, please note: we do not check any of this for you, and nothing stops the deletion going through. If an order or a ride is still running, deleting your account does not cancel it. If you are a driver, deleting your account does not pay out your wallet balance and does not settle the cash you owe us — withdraw your balance and settle up first, because we cannot recover it for you afterwards.
Immediately: your account is closed and you can no longer sign in. We add a prefix to your email address and phone number, so that they can no longer be used to sign in and so that you — or anyone else — are free to register with them again. The original values stay readable in our records, attached to the closed account, for the reasons in 10.3; your name is not changed either. Your app session is ended and your device stops receiving SuriGO notifications. Your profile disappears from the app. If you are a driver, you stop receiving jobs and you disappear from the map.
We would rather tell you the truth than make a promise our systems do not keep. Closing your account does not erase everything. This is what stays:
| What stays | Why |
|---|---|
| Your orders and rides, with their addresses, coordinates, times and amounts | Accounting and tax records; settling a dispute or a claim that arrives after you leave; and the store and the driver hold their own record of the same transaction |
| Payment records, wallet balance and transaction history, earnings and payouts | Accounting and tax obligations, and proof of what was paid to whom |
| Payout account details | Proof of where money was sent |
| Your saved delivery addresses | They are attached to past orders |
| Ratings and reviews you wrote | Removing them would distort the rating of stores and drivers who did nothing wrong. They stay without your name attached. |
| Driver and store documents — identity, driving licence, vehicle papers, business registration — and proof-of-delivery photos and signatures | Proof that the person doing the job was licensed on the day, and evidence in an accident, insurance or liability claim |
| Your email address and phone number, prefixed as described in 10.2, your name, and the closed account record itself | To link the records above to a single closed account, and to stop a banned account simply registering again |
| Your shopping lists, favourites, loyalty points and referrals | They stay attached to the closed account record. Nobody can see them once the account is closed, and we do not use them for anything. |
| A driver's registered vehicle: type, make, model, colour and number plate | It is attached to the rides and deliveries that vehicle carried, and to the vehicle documents above |
| The record that a device was once registered for notifications — an encrypted device token and the topic it was subscribed to | This record carries no account reference, so we cannot look it up by your name to remove it. It stops being used as soon as the account is closed. |
| Sign-in records, including IP addresses | Security — investigating account takeover and fraud |
| A driver's last known position | It is a single row that gets overwritten, never a route history |
Two things are held by Google rather than by us, and deleting your SuriGO account does not reach them:
If you want those removed as well, tell us at contato@surigoapp.com and we will remove them.
Backups. We take a full backup of our systems every day and keep each backup for 14 days. So for up to 14 days after you delete your account, your data still exists inside those backups. We use backups for nothing except restoring the service after a failure, and each one is destroyed on that 14-day schedule.
Server logs. Our application log is cleared automatically and holds only the last few days.
Anything else. If you want records erased that we are not legally or operationally required to keep, ask us at contato@surigoapp.com. We will erase what we can and tell you plainly what we cannot erase, and why.
You can ask us to:
Several of these you can do yourself, without contacting anyone: change your name, email address, phone number, password and profile photo under Profile; manage saved addresses under Addresses; delete your account under Profile, then Delete account; and turn notifications and location on or off in your phone settings.
For everything else, write to contato@surigoapp.com from the email address on your account, or tell us enough for us to find the account. We answer within 30 days. If we need longer, or have to refuse, we will say so and explain why. We may ask you to prove who you are before we hand over data — that protection is for you.
Some things in SuriGO happen automatically, without a person looking at them. You should know which:
Decisions that actually cost you something — approving or rejecting a document, suspending an account — are made by a person, not by software, and the reason is recorded. If you believe a decision about your account is wrong, write to contato@surigoapp.com and a person will review it.
Traffic between the apps and our servers travels over HTTPS. Passwords are stored as one-way hashes, which means nobody at SuriGO can read them — not even to help you. Access to the admin panel is limited to staff who need it, protected by a password and optional two-factor authentication, and every sign-in is logged. A driver's live position is sent to the customer and the store attached to that order.
No system is perfectly secure, and we will not pretend otherwise. If a breach happens that puts you at real risk, we will tell you, describe what happened, and say what to do about it.
Your part matters too: use a password you use nowhere else, do not share your account, and do not let anyone else use your driver profile — your documents and your earnings are attached to it.
SuriGO is for adults. You must be 18 or older to create an account as a customer, a driver or a store. We do not knowingly collect data from children. If you believe a child has created an account, write to contato@surigoapp.com and we will close it and delete the data we are not required to keep.
The version in force is always the one published on this page, and the date at the top tells you when it last changed. If we make a change that materially affects you — a new category of data, a new company receiving it, a new purpose — we will tell you in the app or by email before it takes effect, not afterwards. Smaller corrections are published here with a new date.
SuriGO is available in English, Dutch, Portuguese and Chinese. This English version is the authoritative one. If a translation of this policy differs from it, the English text applies.