Types of Information We Collect
Technical data arrives automatically when a page loads. IP address. Browser type. Operating system. Device category β phone, tablet, laptop. Which page was opened. How long the visit lasted. Where the visitor came from β a search engine, a direct URL, a link from another site.
This is standard server logging. Every site with analytics collects the same kind of data. None of it includes names, email addresses, or anything the visitor typed in voluntarily.
The contact form is the exception. A visitor who sends a message provides a name, an email, and whatever they wrote. That data is voluntary. Nobody has to use the form. Those who do choose what to include.
Personal Information We Do Not Collect
The site does not ask for and does not store:
Passwords to any platform. One-time codes or OTPs. Bank account numbers. Card details. Crypto wallet keys or seed phrases. Identity documents. KYC materials. Aadhaar numbers, PAN numbers, NIN, BVN, or any national ID format. Phone PINs. Security answers.
If a contact form message arrives with any of these included, the team deletes the message and notifies the sender. Nobody from the editorial team will ever ask for login credentials, payment information, or identity documents. Any message claiming to come from this site and requesting such data is fraudulent.
How Cookies Are Used
Cookies handle two jobs on this site.
Functional cookies keep things working. Language preferences. Session state. The cookie consent choice itself, so the banner doesn’t reappear on every page.
Analytics cookies count visitors without identifying anyone by name. One anonymous browser is distinguished from another anonymous browser. The data feeds into aggregate statistics β total visits, popular pages, device breakdown β without connecting those numbers to specific people.
No advertising cookies. No retargeting pixels. No cross-site tracking. No data shared with ad networks.
Browser settings control cookies. Blocking them won’t break the site. Some preferences may not persist between visits, but the content loads the same way either way.
Data Processing by Service Providers
A small number of external services keep the site running.
- Hosting. The site sits on infrastructure managed by a hosting provider. Server logs are generated as part of standard operations. The provider’s own privacy terms govern their handling.
- Analytics. A traffic analysis tool processes visitor data in aggregate. No individual profiles are built. The tool sees numbers and trends, not people.
- Anti-spam. The contact form runs spam filtering that checks submission patterns and IP data to separate real messages from automated junk.
- Each service has its own data practices. The site selects providers that align with minimal data collection. But “minimal” is defined by each provider’s standards, not by this site’s preferences.
- Data is not sold. Not shared with marketing partners. Not handed to advertisers. Not used for profiling or retargeting.
User Requests for Data
A visitor who submitted information through the contact form can ask what’s stored. The request goes through the same form. The team checks that the request comes from the person whose data is in question, then provides the information or confirms deletion.
Visitors who never used the contact form have no individual-level data stored by the site. Their visits show up only in aggregate analytics, which can’t be traced back to a specific person.
Deletion requests are handled on a case-by-case basis. The team confirms when the data has been removed.
Questions about data handling go through the contact form. Including “privacy” in the message helps with routing.