Last updated: October 2, 2026 · Applies to the Android app "Vendor Center" (package com.vendorapp.jumia)
Vendor Center is a companion app for people who run a shop on Jumia's marketplace. It lets you view and manage your own orders, products, account statements, and sales analytics from your phone, by calling Jumia's Vendor Center API directly using credentials you register with Jumia and enter into the app yourself.
The app does not have its own servers or backend. There is no developer-run database, and the developer does not receive, store, or have visibility into your Jumia data, credentials, or orders. Every API call the app makes goes directly from your device to Jumia's servers.
Everything below is stored only on your device, inside Android's EncryptedSharedPreferences (AES-256, keyed to the Android Keystore). None of it is transmitted to the developer.
| Item | What it is | Why it's stored |
|---|---|---|
| Client ID & Client Secret | The OAuth2 app credentials you generate yourself in Jumia's Vendor Center dashboard | Required to authenticate your app registration with Jumia |
| Access & refresh tokens | OAuth2 tokens issued by Jumia after you log in | Lets the app call the Vendor Center API on your behalf without asking you to log in every time |
| Shop ID & country/market code | Identifies which of your Jumia shop(s) to fetch data for | Required by the API to scope requests to your shop |
| API/auth base URLs | Which regional Jumia Vendor Center environment to call | Jumia operates market-specific endpoints |
| Cached orders, products, statements, analytics | Data fetched from Jumia's API for display and offline viewing | Lets screens load instantly and work briefly offline |
| App preferences | Theme choice, last-selected tab/filter, notification toggle | Convenience — remembers how you left the app |
None of this is linked to a developer-side account, because there is no developer-side account — the app has no sign-up or login system of its own beyond the Jumia OAuth flow described above.
Every screen in the app (Orders, Products, Account Statement, Analytics) works by calling Jumia's publicly documented Vendor Center REST API over HTTPS, directly from your device, using your own access token. Jumia's handling of that data is governed by Jumia's own privacy policy and terms, not this one — please refer to Jumia's official privacy policy at jumia.com for how Jumia itself processes vendor and order data on its platform.
The app is monetized with Google AdMob banner, interstitial, and app-open ads, and uses Firebase Analytics (also a Google product) to understand overall app usage - things like which screens are opened and whether an update (order action, price change) succeeded, so the developer can tell what's actually used and where something is breaking. To serve and measure ads, and to record analytics events, these Google SDKs may collect and process:
This data is collected and processed by Google, under Google's Privacy Policy, not by the app's developer. For ads, the developer receives only aggregated revenue and performance reports from AdMob; for analytics, the developer receives only aggregated usage reports from Firebase - neither ever identifies you individually.
Analytics collection is held off by default and only switches on once your consent choice (Section 6) resolves - the same choice governs both ads and analytics, rather than asking twice.
You can control ad personalization for your Google account at adssettings.google.com, and reset or opt out of your device's advertising ID in your Android system settings (Settings → Privacy → Ads or similar, depending on your Android version).
If you're located in the European Economic Area, the UK, or Switzerland, the app shows a consent form — built with Google's User Messaging Platform (UMP) — the first time you open it, before any ad request is made. Your choice (personalized ads, non-personalized ads, or no ads where required) is respected for every ad shown afterward.
You can review or change that choice at any time from inside the app: open the navigation menu → Privacy Policy → Ad privacy options.
If you're a California resident, Google's role as an ad-technology provider and your choices around the sale/sharing of information for advertising are described in Google's own privacy policy and Ad Center.
If you grant notification permission, the app periodically checks Jumia's API in the background (using Android's WorkManager) for new orders and shows a local notification when one arrives. This check runs entirely on your device using your existing session token — no separate push-notification server is involved, and no data leaves your device to make this work beyond the same direct calls to Jumia's API described in Section 4.
| Permission | Used for |
|---|---|
INTERNET | Calling Jumia's API and loading ads |
ACCESS_NETWORK_STATE | Detecting connectivity to retry failed requests sensibly |
POST_NOTIFICATIONS | Showing the "new order" notification described in Section 7 (Android 13+) |
RECEIVE_BOOT_COMPLETED | Re-scheduling the background order check after your device restarts |
com.google.android.gms.permission.AD_ID | Lets the Google Mobile Ads SDK read the resettable advertising ID described in Section 5, subject to your consent choice |
EncryptedSharedPreferences/Keystore, not stored in plain text.Aside from Jumia (Section 4) and Google/AdMob/Firebase Analytics (Section 5), your data is not sold, rented, or shared with any other third party. The app has no advertising networks, data brokers, or analytics vendors beyond the ones disclosed above.
Vendor Center is a business tool for people who operate a Jumia seller account, and Jumia requires vendors to be of legal age to enter into a commercial agreement in their country. The app is not directed at children, and the developer does not knowingly collect data from children.
Depending on where you live, you may have rights to access, correct, export, or delete your personal data, and to object to or restrict certain processing. Because:
there is no separate developer-held dataset for the developer to action a rights request against — but you're welcome to reach out (Section 15) with any question about how the app itself handles data, and it will be answered directly.
If this policy changes, the "Last updated" date at the top of this page will change accordingly, and material changes will be reflected here before they take effect. Since this page is the single source of truth referenced from inside the app, checking here is the way to see the current version at any time.
Questions about this policy or how the app works can be sent to: krystalgraphix@gmail.com