Privacy Policy

1. Who we are and what this policy covers

NaijaMingle is operated by Munar Africa, a business based in Lagos, Nigeria that is currently completing company registration. Munar Africa is not yet an incorporated company, no registration number is claimed, and nothing on this page should be read as describing a limited liability company. Our full street address is available on written request.

This policy explains how Munar Africa processes personal data when you use NaijaMingle. It covers the website, matchmaking, video and text conversations, safety reporting and our administrative systems. It does not cover other websites or apps, including anything another user sends you a link to.

NaijaMingle has no user accounts, no signup, no email address collection and no profiles. We designed the Service to collect as little as possible, and this policy describes exactly what remains.

2. The short version

• We do not ask for your name, email address, phone number, date of birth or any identity document.
• We do not store your IP address. We do not record video or audio, and we do not keep a chat history.
• We derive a coarse region (country and, where available, state) from your network connection at our edge provider. It can be wrong and it is never treated as verified.
• We keep anonymous technical records about visits, matches and calls so the Service works and so we can measure reliability.
• Browser notifications are optional. If you turn them on, we store the push subscription your browser creates so we can tell you when NaijaMingle gets busy. Turning them off deletes that record.
• Reports and legal acceptance records are stored, because safety and accountability need a durable record.
• We do not use advertising or analytics cookies, and no third-party tracking scripts are loaded.

3. Information we process

The categories below reflect what the current version of the Service actually processes. We do not claim to collect anything outside this list.

• Anonymous identifiers: a random identifier issued to your browser session when you first use the Service, and a separate random identifier for each browser tab (the "visit"). These are not linked to your name or contact details.
• Visit and presence data: when a visit started, when it was last seen, when it ended, and which mode (video or text) was used.
• Matching data: when a match was requested, whether it succeeded, how long it waited and how it ended.
• Call metadata: mode, start and end times, duration, connection type (direct or relayed), and technical quality indicators such as round-trip time, packet loss, jitter and connection state.
• Approximate location: country, ISO region code, region name and a coarse city value derived by our edge provider from the network connection. Current versions of the Service no longer store the city; older records may contain one.
• Device class: a general category (mobile, tablet, desktop) plus a browser and operating-system label derived from the request. The raw user-agent string is not stored.
• Legal acceptance records: the document versions you accepted, when you accepted them, and the anonymous identifier and optional visit identifier.
• Notification subscription: if you enable browser notifications, the push endpoint and public encryption keys your browser generates, the version of the anonymous identifier it belongs to, whether milestone alerts are on, and the date it last succeeded or failed. The endpoint is a capability: it lets our infrastructure ask your browser to show a notification. It does not identify you by name.
• Prompt history: whether the notification or sharing prompt was shown or dismissed, kept in your browser rather than our database. Our servers receive only aggregate counters such as "prompt shown" or "link copied", attached to the same anonymous identifier used for analytics.
• Milestone records: which online-user thresholds were announced, the online count observed at the time, and aggregate delivery counts (accepted, failed). These never include a per-person record of who was notified.
• Reports: the category you select, any description you write, the anonymous identifiers of the reporter and the reported participant, and the identifier of the conversation.
• Operational and security records: rate-limit counters, enforcement records, moderation decisions and administrative audit logs.

4. What we do not collect

• No names, email addresses, phone numbers, postal addresses, dates of birth or government identifiers.
• No GPS, precise coordinates or device sensor location, and no browser fingerprinting.
• No address book, contacts, photo library or files from your device.
• No message content, call transcripts, video or audio recordings. Conversations are relayed in memory and discarded.
• No advertising profiles and no cross-site tracking identifiers.
• No IP addresses in our database. Your IP address is visible to the network providers that carry your traffic, and is passed to our bot-protection provider for verification, as explained below.

5. Why we process it, and our legal bases

We process personal data under the Nigeria Data Protection Act 2023 ("NDPA"). Depending on the activity, we rely on the following legal bases:

• Providing the Service (performance of a contract or steps taken at your request): creating a visit, matching you with another user, relaying messages and media, connecting calls, and giving effect to blocks.
• Legitimate interests: keeping the Service secure and available, preventing abuse and automated attacks, rate limiting, diagnosing failures, measuring aggregate reliability, and maintaining safety and audit records. We only rely on this basis where our interests are not overridden by your rights.
• Legal obligation: retaining records needed to respond to lawful requests, to handle safety incidents, and to meet regulatory or law-enforcement requirements.
• Consent: any optional feature that requires it, such as non-essential tracking if we ever introduce it. We do not bundle consent with acceptance of the Terms.
• Vital interests or protection of a person: where a report suggests a risk to life or of serious harm, including harm to a minor.

6. IP addresses and approximate location

Our edge provider sees the network address your device uses, because that is how any web request reaches a server. We use the location hints it derives at the edge to produce a coarse region. We do not read a location supplied by the browser, and we do not trust a forwarding header as a location source.

We do not write IP addresses to our database and do not keep them in application logs. Our bot-protection provider does receive your IP address, together with a challenge token, when a verification check runs. That provider processes it to decide whether the request is automated.

IP geolocation estimates where a network is likely to be, not where a person is. VPNs, proxies, corporate networks, mobile carrier gateways and errors in geolocation databases can all produce a wrong result. We mark results as resolved, partial or unknown, and we show unknown as unknown rather than guessing.

Other participants never receive your IP address from us. They may be able to infer a network address through the peer-to-peer media connection itself, as explained in the next section.

7. Conversations, media and what other users may see

Text messages, video and audio are transmitted in real time. Our signalling service relays connection information, and media flows directly between participants or through a relay when a direct connection is not possible. Messages and media are held in memory only for as long as they are needed to deliver them, and are not written to our database.

Peer-to-peer media connections normally exchange network candidates so that two devices can find a route to each other. As a result, a participant may be able to learn a network address of the other participant, particularly if they use technical tools. We do not sell or provide that information, but we cannot describe the connection as fully private. A relayed mode that hides participants' network addresses from each other is available as a configuration option; it is not enabled by default because it increases cost and can reduce call quality.

We do not create recordings, screenshots or transcripts. Another participant can still record or screenshot you with their own device, and we cannot prevent that.

When you submit a report, the description you write is stored. If you quote a message or describe what happened, that text becomes part of the safety record and is retained for the period described below.

We do not add chat history or media recording in order to support moderation.

8. Cookies, local storage and similar technologies

The public Service does not set advertising or analytics cookies, and does not load third-party tracking scripts. Fonts are served from our own domain rather than from a third-party font service.

• Browser local storage keeps: your anonymous session credentials, a bot-check pass valid for a short period, your 18+ confirmation, your legal acceptance cache, your block list cache, whether you have seen or dismissed an engagement prompt (`nm_engagement_prompts`), how many calls you completed on this device (`nm_completed_calls`), and preferences such as theme, data saver and video quality.
• Session storage keeps: the per-tab visit identifier and engagement prompts already shown in this tab (`nm_engagement_session`).
• Cookies are used only in the administrative control centre, to keep staff signed in. Those cookies are HttpOnly, secure in production and restricted to the admin area. They are not set for ordinary visitors.
• Bot protection may set a cookie or use similar storage to complete its challenge. It exists for security and is strictly necessary for that purpose.

9. Optional browser notifications

NaijaMingle can tell you when a lot of people are online. This is optional, off by default, and never required to use the Service. We ask once after your first completed call, and again on a later visit only if you dismissed the request; we do not repeatedly trigger your browser's permission dialog after you have refused.

If you turn notifications on, your browser creates a push subscription: a URL provided by your browser's push service and two public encryption keys. We store those values against your anonymous identifier so we can send a notification. Messages are encrypted so that only your browser can read them. We do not store a notification history, and we do not know whether you saw or opened a notification.

To deliver the notification, our servers send an encrypted request to the push service operated by your browser vendor — for example Google, Mozilla, Microsoft or Apple. That provider necessarily sees the request, your subscription endpoint and the network address of your device at that moment. We do not control its retention or its policies. This is the same mechanism every website uses for web push.

Notifications contain a short message and a link to the Service. They never contain conversation content, names, locations or any information about another participant.

You can turn notifications off at any time from the "Notifications" control in the site footer, which unsubscribes the browser and deactivates the stored subscription. You can also revoke permission in your browser or device settings; the next time you visit, we detect that and stop sending.

A milestone notification is sent only when our own presence count for the site reaches a configured threshold. We announce each threshold at most once per re-arm window (by default, once per day). We do not claim a specific number of people is online unless our own count verified it.

10. Sharing and service providers

We do not sell personal data and we do not share it for advertising. We use service providers in the following categories, who process data on our instructions:

• Hosting and content delivery for the website.
• Database, authentication and API services for anonymous identities and stored records.
• Edge networking, serverless compute and real-time coordination for matchmaking and signalling.
• Bot protection, which receives your IP address and challenge token when a check runs.
• Media relay, which forwards encrypted media when a direct connection fails.
• Browser push services, which deliver an encrypted notification to your device only if you have enabled notifications.
• Security and operational logging provided by the infrastructure above.

11. Legal disclosure and business changes

We may disclose information if we are required to by law, a court order or a competent authority, or if we believe in good faith that disclosure is necessary to investigate fraud or a security issue, to protect a person from harm, or to enforce our Terms.

Where a report indicates that a minor may be at risk, or that child sexual abuse material may be involved, we may preserve the related safety record and report it to the appropriate authorities.

If the Service or our business is transferred, merged or reorganised, records may be transferred as part of that transaction, subject to this policy continuing to apply.

12. International transfers

Our providers operate globally, so personal data may be processed outside Nigeria, including in the European Union, the United Kingdom and the United States.

Where data is transferred out of Nigeria, we rely on the transfer mechanisms available under the NDPA and on our providers' contractual commitments, including standard contractual clauses and equivalent safeguards where applicable. Transfers are limited to what is necessary for the purposes described in this policy.

You can ask for more information about the safeguards that apply to a particular transfer by emailing munar.africa@gmail.com.

13. How long we keep information

We apply the retention schedule below. Deletion is carried out through a controlled operational process by authorised administrators, and each run is recorded in our audit log. Records are deleted in batches, and residual copies may persist for a short period in provider backups before they are overwritten.

• Visit and presence records: up to 180 days.
• Analytics events: up to 90 days.
• Call metadata and connection diagnostics: up to 90 days.
• Matching attempt records: up to 180 days.
• Active push subscriptions: until you turn notifications off or the push service reports the subscription is gone. Deactivated subscriptions are deleted after 90 days.
• Milestone event and delivery records: up to 180 days. They contain aggregate counts, not a list of who was notified.
• Safety reports, moderation notes and enforcement records: up to 24 months, and longer where needed to handle an appeal, an open investigation or a legal obligation.
• Legal acceptance records: up to 24 months after the document version is replaced.
• Administrative audit logs: up to 7 years, because they evidence access to restricted records.
• Conversation content and media: not retained at all.
• Preferences, prompt history and identifiers stored in your browser: until you clear them.

14. Security

We protect records with database row-level security, server-side authorisation checks that read administrative roles from a dedicated table rather than trusting a token claim, restricted access to safety records, and audit logging of administrative actions.

Push subscriptions, notification keys and milestone delivery records are never exposed to the public API or to the administrative interface. The VAPID private key used to sign notifications exists only as a server-side secret.

Bot protection, rate limits and session-bound connection tickets reduce automated abuse. Conversations are relayed over encrypted connections, and media is encrypted in transit using the browser's WebRTC encryption.

No system is perfectly secure, and anonymity is not the same as invisibility. We cannot guarantee that our safeguards will prevent every unauthorised access, and we cannot guarantee that another participant will not record or identify you by other means.

If you believe you have found a security issue, please email munar.africa@gmail.com. Please do not test it against other users or against production data.

15. Your rights

Under the NDPA you may have the right to access your personal data, to have inaccurate data corrected, to request deletion, to object to or request restriction of processing, to request portability where applicable, and to withdraw consent where processing is based on consent. You also have the right to lodge a complaint with the Nigeria Data Protection Commission.

To make a request, email munar.africa@gmail.com and describe what you want. We respond within 30 days.

16. Children and under-18s

NaijaMingle is strictly for adults aged 18 and over. We do not knowingly allow anyone under 18 to use the Service, we do not knowingly collect data about children, and we do not market the Service to children.

Age is confirmed by self-declaration at the adults-only gate; we do not verify age documents. If we become aware that a user is under 18, we will restrict the anonymous identifier and delete records associated with it where appropriate, unless we need to keep them to respond to a safety incident or a legal requirement.

If you believe a user is under 18, report the conversation in the app. If you believe a child is at risk, contact the Nigerian Police Force or another appropriate authority, and email munar.africa@gmail.com so we can act on the report as well.

17. Automated processing

Matching is automated: the system pairs visitors who are waiting at the same time. It does not assess your character, health, finances or suitability, and it does not produce a profile about you.

Moderation decisions are made by people. Automated systems may rate-limit requests, block obviously abusive traffic, or flag a pattern for review, but they do not impose enforcement on their own.

18. Changes to this policy

We may update this policy. Each version carries a number and an effective date. Material changes that affect what we process, or why, will be reflected in a new version, and the adults-only gate will be shown again so that acceptance can be recorded against the new version.

We will not apply a change retroactively to data we were not entitled to process at the time.

Contact us

Questions about this document, privacy requests, safety reports and legal notices can all be sent to munar.africa@gmail.com. This is the only official contact channel for NaijaMingle at this time; please treat messages arriving from any other address with suspicion.

We aim to respond to privacy requests within 30 days. Safety reports submitted through the app reach our moderation queue and do not depend on email.