Jiji

Kiungo Privacy Policy

Last updated: 14 October 2026

Kiungo is maintained by the Jiji team for Jiji and Bikroy. This policy explains how information is handled when you visit Kiungo pages, open a short link or use the administration area at admin.jiji.to. For privacy questions, contact vs@jiji.ng.

Information from short-link visits

When you open a Kiungo short link, the service processes the request to choose and open its destination. The visit record may contain:

The daily code is derived from the request's IP address, browser information, date and a service secret. It helps estimate repeat visits within a day. It is not a name or an account ID, but it is still pseudonymous information rather than fully anonymous data.

Kiungo's application visit table does not store the raw IP address or the full user-agent. Cloudflare still processes connection information to deliver and protect the service and may retain infrastructure or security logs under its own policies. Approximate network location is not precise GPS location.

Event invitations and check-in

Some Kiungo pages invite sellers to Jiji or Bikroy events. For these events Kiungo keeps a guest list: the seller or shop name and phone number that the event team added or that you typed on the page, who invited you, your answer (coming or not), the time you checked in at the door, and whether the team has turned on the offer for people who came. Personal invitation links contain a short code that tells us which invitation was answered.

The event team uses this list to save seats, remind guests, turn on the offer in your Jiji or Bikroy account and review the event. Ratings on visit pages are counted without your name or phone number. To have your details removed from a guest list, contact vs@jiji.ng.

Google sign-in and team accounts

Only the administration area requires sign-in. Google authenticates team members through Cloudflare Access using the basic identity scopes openid, email and profile. These scopes can provide an account identifier, email address and basic profile information, such as a name or profile image, to the authentication service.

Kiungo uses the verified email address and the name supplied by the sign-in service, when available, to identify team members. It stores account permissions, account status and access timestamps. It also records the email address of the person who creates or changes links, permissions and related settings in an activity log.

Kiungo does not request access to Gmail messages, Google Drive files, contacts or calendars. It does not receive your Google password. Google sign-in information is used for authentication, access management, support, security and accountability within Kiungo; it is not used for advertising or sold.

Kiungo's use of information received through Google sign-in will comply with the Google API Services User Data Policy, including applicable Limited Use requirements.

How we use and share information

We use this information to route links, measure campaign traffic, maintain the service, troubleshoot problems, protect access and keep a record of changes. Authorised team members can see the information their role permits, including campaign summaries and relevant activity records. Technical administrators may access underlying records for operation, support and security.

Cloudflare processes information as part of hosting, database storage, security and access management. Google processes information when you use Google sign-in. These services may process information outside the country where you are located. We do not sell Kiungo visit records or Google sign-in information.

A link may send you to Jiji, Bikroy, an app store, an Adjust app link, a social platform or another selected destination. The destination receives the information normally included in a browser or app request. Kiungo may include campaign tags and forward permitted query parameters with the link. Those services handle the resulting visit under their own privacy policies. Do not place passwords, authentication tokens or other confidential information in a short link or campaign tag.

Cookies and other connections

Kiungo's public short-link redirect code does not set a visitor-tracking cookie. The staff sign-in process uses authentication cookies through Cloudflare Access and Google. Cloudflare may also use security mechanisms when protecting the service. Sites and apps opened from a link may set their own cookies.

Kiungo pages currently load the Roboto font from Google Fonts. This makes a request from your browser to Google to retrieve the font, which includes ordinary connection information such as your IP address and browser details.

Retention

Link settings and their change history may remain useful for as long as printed materials or published links are in circulation. Visit records are retained for campaign reporting, troubleshooting and security. Team account and activity records are retained to administer access and explain changes, including changes made by former team members.

Retention depends on these purposes, active support or security investigations and applicable obligations. The current service does not apply an automatic fixed deletion deadline to these application records. You can contact us to ask about a record or request its removal. We will assess what can be removed and whether any information must be retained for security, accountability or applicable obligations. Infrastructure providers have their own retention arrangements.

Your choices and requests

You can visit a destination directly instead of using a Kiungo short link. For team accounts, you can ask a Kiungo administrator to correct your information or disable access. You can also remove Kiungo's Google connection in your Google Account connections settings; this does not automatically erase records already held by Kiungo or immediately end an existing Cloudflare session.

To request access to, correction of or deletion of information, contact vs@jiji.ng. We may ask for information needed to verify the request. Because short-link visit records use pseudonymous codes, we may not be able to identify a particular visit from your name or email alone.

Changes to this policy

We will update this page when our data practices change and revise the date above. Material changes affecting team accounts will also be communicated through the service or the team administrator.