Cookie Policy
This policy explains what the public Payment Gateway Africa website stores in your browser, which today is no cookies at all. It also explains why the separately provided merchant portal is not covered here.
This Policy in Brief
The public Payment Gateway Africa website does not place cookies in your browser.
No third-party analytics scripts and no advertising pixels run on the public website.
Interactive elements, such as the country map, keep their state only in page memory. That state disappears when you close or reload the page.
The merchant portal is provided separately from this website and is outside the scope of this policy.
If our approach changes, we will update this page before any new cookie or tracking technology goes live on the public website.
1. Which Website This Policy Applies To
This policy covers the public Payment Gateway Africa website. That includes the pages that describe our payment gateway, our country and method pages, the documentation pages, the blog and the legal pages.
It does not cover the merchant portal. Merchants receive access to the portal separately as part of onboarding, and it works independently of this website. Any storage the portal uses is described to merchants through the portal and their onboarding materials, not on this page.
How we handle personal data more generally, including details you enter into a form, is described in our privacy policy. Use of our services is governed by our terms of service.
2. Cookies and Similar Technologies Explained
A cookie is a small text file that a website asks your browser to save. The site can read the file on a later visit, for example to recognise a returning browser or to remember a setting.
Similar technologies include browser local storage, session storage, tracking pixels and scripts that collect browsing behaviour for analytics or advertising.
Throughout this policy, "cookies" refers to all of these technologies unless we name a specific one.
3. What the Public Website Stores Today
The current public website is a static front end. It does not set cookies, and it does not write identifiers to local storage or session storage.
We do not load third-party analytics tools on the public website. Your page views are not sent to an analytics provider through scripts on our pages.
We do not use advertising pixels or retargeting tags. Your visit is not shared with advertising networks through the public website.
4. How Interactive Elements Keep Their State
Some pages include interactive features, such as the map that lets you move between the markets we serve. When you select a country on that map, your choice is held in the memory of the open page only.
Nothing from that interaction is written to your device as a cookie or saved storage entry. When you reload the page, open it in another tab or close the browser, the map returns to its default view.
This approach lets you use the map without us keeping any record in your browser of which markets you looked at.
5. The Merchant Portal Is Separate
Merchants who complete onboarding receive access to a merchant portal. The portal is provided separately from the public website and has its own sign-in and session handling.
Because the portal is a different service, the statements in sections 3 and 4 apply only to the public website. They should not be read as describing the portal.
If you are a merchant and want to know how the portal handles sessions or browser storage, ask your Payment Gateway Africa contact or send a request through our contact page.
6. Forms on the Public Website
The contact and onboarding request forms send the details you type in when you press submit. Submitting a form does not, in itself, cause the public website to place a cookie.
The information you provide through a form is personal data handled under our privacy policy, not under this cookie policy.
7. Controlling Storage in Your Browser
Most browsers let you view, block and delete cookies and other site data through their settings. You can use these controls for any website, including ours.
Because the public website does not rely on cookies, blocking them should not stop pages, documentation or interactive elements from working.
8. When This Policy Changes
If we decide to add cookies, analytics or any other storage technology to the public website, we will revise this page first. The revision will name the technology, explain its purpose and describe any choices available to you.
Where a change requires your consent, we will ask for it before the technology is activated. The date shown at the top of this page shows when the policy was last revised.
9. Raising a Question About Cookies
If you have a question about this policy or about storage on the public website, send it through our contact form and mention "cookie policy" in your message.
You can also return to the Payment Gateway Africa home page to continue browsing.
Frequently Asked Questions
Does the Payment Gateway Africa website set any cookies?
No. The public website is a static front end and does not set cookies or write identifiers to local or session storage.
Do you track my visits with analytics or ad pixels?
No third-party analytics scripts or advertising pixels run on the public website.
Why does the country map reset when I reload the page?
The map keeps your selection only in page memory. Nothing is saved to your browser, so a reload returns it to the default view.
Does this policy describe the merchant portal?
No. The merchant portal is provided separately and is not covered here. Merchants can ask their Payment Gateway Africa contact or use the contact page for details about the portal.
Will I be told if cookies are introduced later?
Yes. We will update this policy before any new storage or tracking technology goes live on the public website. Where consent is required, we will ask for it first.