Last Updated: June 8, 2026

1. Introduction to Cookie Usage

When you interact with the Ojahmi platform—including our primary administration portal (ojahmi.com), our merchant management dashboards, and any independent storefronts hosted via our infrastructure—small text files known as "Cookies" or tracking pixels are automatically placed onto your computer, tablet, or mobile device browser.

This policy details exactly why Ojahmi uses these technologies, what types of cookies we deploy, and how you can manage or restrict their usage.

2. Why Does Ojahmi Use Cookies?

We utilize cookies and unique device identifiers strictly to enhance system security, deliver a high-performance e-commerce experience, and keep your business operational. These tracking tokens allow our servers to:

• Recognize your identity as an authorized Merchant so you do not have to input your password every time you click a different dashboard menu.

• Persistently save your storefront configuration edits, multi-theme layouts, and custom dashboard preferences.

• Protect your account from Cross-Site Request Forgery (CSRF) scripts and session hijacking attempts.

• Ensure that when an end-buyer visits a merchant storefront, their chosen items remain securely saved inside their digital shopping cart as they browse different product pages.

3. Categories of Cookies We Deploy

Ojahmi separates its tracking infrastructure into three distinct operational classifications:

3.1 Essential & Strictly Necessary Cookies

These tokens are non-negotiable for the basic technical operations of your e-commerce site. Without these, our application framework cannot load, and basic actions (like logging into your store or accessing OjahmiPay) will break.

• Purpose: Session validation, authentication defense, user-load balancing, and secure multi-store routing.

• Lifespan: Mostly "Session Cookies," which delete themselves automatically the moment you close your web browser.

3.2 Performance & Functional Cookies

These cookies remember choices you make to provide an optimized, localized dashboard experience.

• Purpose: Remembering your currency choice (e.g., NGN, KES, GHS, USD), tracking language parameters, and saving your active workspace configurations.

• Lifespan: "Persistent Cookies," which remain on your device for a set period (e.g., 30 days to 1 year) unless cleared manually.

3.3 Infrastructure Analytics Cookies

We use anonymized telemetry tracking tokens to measure how our servers and backend scripts perform across various geographical nodes in Africa and internationally.

• Purpose: Spotting broken database links, measuring dashboard loading times, monitoring mobile application crash frequencies, and optimizing server performance.

• Data Collected: Anonymized technical metadata, device screen resolutions, and page loading speeds. No personal financial or identity information is stored here.

4. Third-Party Tracking Controls

Because Ojahmi serves as an infrastructure provider, we do not inject third-party ad-tracking pixels or commercial behavioral remarketing scripts into your admin panel.

However, if a Merchant chooses to independently integrate external third-party software tools (such as Google Analytics, Meta Pixels, or custom marketing plugins) directly into their own Ojahmi storefront code settings, the Merchant is exclusively responsible for disclosing those specific third-party cookies to their customers. Ojahmi exercises no operational control over cookies dropped by plugins activated by the store owner.

5. How Users Can Manage and Delete Cookies

You have the complete legal right to control, block, or completely wipe cookies from your devices at any time.

• Browser Level Settings: You can configure your web browser (Google Chrome, Safari, Mozilla Firefox, Microsoft Edge, Brave) to block all cookies or to you when a cookie is being sent.

• The Effect of Blocking: If you choose to completely block or disable Ojahmi’s essential and functional cookies, you will be instantly logged out of your merchant panel, and your storefront builder dashboard will fail to save active updates or process administrative requests.