Visitor and installation records · updated 10 October 2026
Optional visitor analytics are off until you choose Allow analytics. With that choice, CudiChat assigns a random first-party browser or installation ID and records visits, first/last visit times, device type, operating system, browser/app version, available model information, observed public IP and approximate network city, region and country. The main website uses a restricted CudiChat connection to the same app collection service, so a visitor record can be linked when you later sign in. A visit is a 30-minute visit session, not every click. The Visitors register represents unregistered browsers/installations, not verified people, and cannot count a download that has never opened and connected. Clearing storage, reinstalling or using another browser can create another ID. We do not use hardware serial numbers, IMEI, MAC addresses, advertising IDs, hidden device fingerprinting or GPS for this feature.
Referral tags and search terms
With optional visitor analytics enabled, we record the external referring website's hostname and supplied campaign fields (source, medium, campaign and term). Supported Android builds can read those same campaign fields from Google Play's install referrer after consent. We do not store a full referring URL, unrelated query parameters, advertising click IDs, browsing history or an inferred search query. Search engines and stores often do not provide a keyword. Our acquisition labels classify available evidence; they are not AI claims about a person's interests or identity. No visitor data is sent to an AI provider for this feature.
Account linking and necessary security history
After a verified sign-in or registration, the current visitor record can be associated with that account and no longer appears in the unregistered Visitors list. Necessary account-security records are separate from optional analytics. They record an app/browser device reference, login and session references, timestamps, observed IP and approximate network location to help protect accounts and investigate abuse. Encryption-key device records remain separate. Shared IP addresses do not establish that two accounts belong to one person. We use contract and legitimate security interests where applicable, subject to applicable law; optional visitor/acquisition analytics rely on consent.
Location and VPN limitations
IP-derived locations are estimates of a network connection, not proof of where a person lives or is physically present. A VPN or proxy may show its exit location. CudiChat does not uncover a hidden original IP or label a VPN exit as a person's real location. VPN status is Unknown unless a supported detection source actually supplies a result. Network or location changes alone do not establish wrongdoing and are not used as a sole basis for an adverse account decision.
Privacy choices and access controls
Choose Essential only on cudichat.com to use the service without optional visitor analytics. You can reopen these choices using Usage settings on that website, withdraw optional consent and request removal of that browser's visitor history. App screens do not display the website notice, and registration does not enable optional analytics. Recognised Global Privacy Control and Do Not Track signals keep optional analytics off. Necessary authentication/security records continue independently. Only authorised administrators can access the protected register; IPs are masked in ordinary lists and access to full network details is restricted and audited. Authentication passwords, live access/refresh tokens and private-message encryption keys are not displayed in these records.
Security and visitor retention
Optional visitor events are retained for up to 30 days; the visitor summary and cookie expire at a fixed 30 days from the first visit. Repeat visits do not extend that expiry. Account security observations, network history and session-history details expire after 90 days. Expired records are excluded from the interface immediately and are queued for physical deletion; database expiry deletion can take additional days. Minimal token-revocation controls, without IP/location/device-model history, may remain until the relevant authentication token expires (the current maximum refresh lifetime is ten years), so a revoked token cannot become valid again when history expires. Backups follow the hosting service's recovery lifecycle and are not used as the active visitor register. Account deletion also removes linked visitor/security data, subject to specific lawful preservation obligations. We do not reconstruct missing historical visits or locations.
What we collect
Account details such as first name, last name, date of birth, phone number, email, user ID and profile information; verification submissions; payment, balance and transaction records; device identifiers, operating system, browser, app version, IP history and approximate location; login, linked-device, security and support events; contacts you approve inside CudiChat; status audience, interest channel, viewing, interaction and advertising records. Your exact date of birth remains private and is used for age eligibility and account administration. Your device address book is not uploaded unless a future feature clearly asks for separate permission.
Status visibility and insights
When you view a Private or Public status, the author can see your display name, profile photo, verification state, contact/public relationship and viewing time. A status view is not anonymous. Authors may also receive aggregated age-band, audience, country, Nigerian state or region, completion and views-over-time analytics. We do not expose a viewer's phone number, exact birth date, IP address or precise location through status insights.
Chat display protection
Private chat does not require an always-on front camera and does not inspect the camera for external recording devices. The chat can be hidden manually and is covered when the app goes into the background; playback is paused. A compatible Android app enables native secure-window protection for private chat and reports when it is active. Older app builds and browsers cannot claim this protection. Native iOS capture handling is not implemented in this build. An optional pseudonymous session watermark is a deterrent, not a guarantee against copying, recording or screenshots.
Screenshot event notices
Where a supported operating-system screenshot callback is available, CudiChat may send a notice to conversation participants using the authenticated account/device reference, conversation reference, event ID, event type and time. No screenshot image, camera feed or chat content is automatically submitted with that event. Notices are reports from the app on a device, not independent proof of who physically used it, and some captures cannot be detected. Android secure-window blocking does not supply screenshot-attempt notifications. Detection can occur after an image has already been saved.
Message permissions and saved recordings
In-app sharing and forwarding actions use approval for the selected message version and destination. Permission requests and decisions use metadata; quoted replies and forwarded message contents are encrypted for their recipients. For a recipient, the first authorized play of a paid audio or video message is charged. Further plays require the message to be saved in CudiChat and a new sender approval; approved replays are free. Saving retains the encrypted message in CudiChat and does not export a plaintext recording. Decrypted playback buffers are temporary on the device, not plaintext media uploads. These controls are not digital-rights management and cannot recall copies a participant has made outside the app.
Encrypted communications
Private chat messages and voice notes are designed to be end-to-end encrypted. CudiChat administrators must not possess the keys needed to decrypt them. We may receive unencrypted content only when a participant deliberately reports and submits that specific content, or where limited technical metadata is necessary to operate the service.
Why we process data
To create and secure accounts; deliver private statuses to accepted contacts and public statuses to all CudiChat users; provide messaging, connections, advertising and payment functions; verify identity; process account funding, paid responses and withdrawals; detect account takeover, fraud and abuse; provide support; comply with financial, tax, legal and regulatory duties; improve reliability; and send service or security notices. Where required, processing relies on contract, legal obligation, legitimate interests or consent.
Sharing
We may share only necessary information with hosting, identity, communications, security, analytics and payment providers acting under contract; payment counterparties; professional advisers; regulators, courts or law enforcement where legally required; and a successor in a lawful business transaction. We do not sell private chat content or phone numbers.
Other retention
The visitor and security-specific periods above apply to the new identity history feature. Separate account, payment, verification and audit records are kept only as needed for the service, disputes, fraud prevention and applicable law. New status content expires from view after the selected duration of 1 to 12 hours (12 hours by default) and is scheduled for deletion within 7 days. Existing statuses keep their original expiry. Deleted accounts are erased or anonymized except records retained for a specific lawful payment, security or dispute purpose. Country-specific financial and legal retention schedules require compliance review before commercial launch; they are not permission to retain visitor history indefinitely.
Your choices and rights
Subject to applicable law, you may request access, correction, deletion, restriction, objection, portability or withdrawal of consent. You may remove linked devices, manage notification choices, block connections and request account deletion in the app or through the public deletion page. You may complain to the Nigeria Data Protection Commission or another competent regulator.
International transfers and security
Service providers may process data outside Nigeria. We will use appropriate contractual and technical safeguards. Security measures include encryption, least-privilege administration, MFA, device linking, risk monitoring, session revocation and audit trails. No system is perfectly secure; confirmed breaches will be handled and notified as required by law.
Children and contact
CudiChat is not intended for anyone under 18. Privacy questions, rights requests, data-deletion requests and complaints may be submitted through CudiChat Support or by email to reports@cudichat.com.