Privacy — Radar

The short version

You can browse Radar without creating an account. We do not build profiles of readers or keep page-view histories in the application database.
There is no advertising, analytics, or third-party tracking script on this site. Your browser does request the Inter typeface from Google Fonts, which can receive connection data such as your IP address.
We do not sell, rent or trade personal information.
The Radar application database does not store raw IP addresses. Where needed for abuse prevention, it stores a salted hash instead; the hosting provider may separately process connection metadata.
General feedback and community reports require an account. Opportunity and tool suggestions can be sent without an account while accounts are disabled; they go to human review and are not published automatically. Correction and dispute requests can also be sent without an account. Community reports use your account’s optional display name, or appear as Anonymous.
When accounts are enabled, signed-in users can flag a public report for human review. A flag is not public and does not automatically hide the report.
If the separate helpful-votes feature is enabled, verified accounts at least 24 hours old can mark another approved report useful. Public pages show only an aggregate count from at least three eligible accounts, never voter identities; votes do not verify a claim.

1. Browsing Radar

Reading pages, searching, filtering and opening a listing creates no record tied to you. We do not keep visitor logs in the application database and we do not build profiles of readers.

2. What we hold, and why

When	What is kept	Why
You run a URL check	The URL, the result, and the time. No IP address, no identifier.	To show how a result was produced and to avoid repeating expensive lookups.
You post a community report	The report text, a link to your account, the display-name snapshot (if set), a salted hash of your IP, your browser's user-agent string, and the time.	To review and publish the report, attribute it to your account, and detect spam, flooding and repeat abuse. A chosen display name may appear publicly; Radar does not display your account email unless you include it in the report text.
You flag a public report (when accounts are enabled)	The report ID, your selected reason and optional context, a link to your account, a salted IP hash, your browser's user-agent string, and the time. A separate audit event records the flag and any later review reason, actor, and time.	To send an approved report for human review, limit repeat abuse, and preserve a record of the review. Flag details are not published; a flag does not automatically hide or remove a report.
You mark an approved community report useful (only when helpful votes are enabled)	The account ID, report ID, and time. No IP address or user-agent is stored with the vote. A separate admin suppression record and reasoned audit events may be kept if an account's votes are excluded.	To provide a limited usefulness signal. Voter identities are never public; counts are hidden until at least three currently eligible accounts have voted. Votes do not verify reports or affect moderation, opportunity ratings, or risk signals.
You suggest a tool	The suggestion fields, an account link for signed-in submissions when accounts are enabled (no account link when accounts are disabled), any optional reply email you provide, a salted IP hash, your browser’s user-agent string, and the time.	To send the idea for admin review, reply if you provided an email, link it to your account when signed in, and limit repeat submissions. A review status does not add a tool to the catalog automatically.
You send general feedback or an opportunity suggestion	Your message, an account link if you are signed in, any optional reply email you provide, the opportunity link if supplied, a salted IP hash, your user-agent, and the time.	To review it, reply if you asked us to, link it to your account, and keep a record of the review. Nothing you send is published automatically.
You send a correction or dispute request	Your request, its linked listing and (if selected) community report, an optional account link if you are signed in, any optional reply email, a salted IP hash, your user-agent, and the time. A separate audit event records the request text and target IDs, then each review status, reason, actor, and time.	To review the claim and preserve a record of each decision. Requests may be anonymous, are not verified by receipt, and do not automatically change a listing or hide a report.
You create or use a Radar account	Your email address, a bcrypt password hash, optional display name, account status, verification time, and sign-in timestamps. A signed session cookie is stored in your browser.	To provide sign-in, account recovery and account settings. Email verification is not required to contribute; a verified link is used for recovery and email changes. The display name may appear beside a community report; Radar does not display the account email publicly unless you include it in contribution text.
You sign in to the admin console	Username, a bcrypt password hash, and the time of the last sign-in. A session cookie is set in your browser.	To keep the console secure. This applies to Radar administrators, not to visitors.
Some sign-in, account, Checker, and admin requests	Short-lived per-IP counters, plus submitted-email or account-ID counters for sign-in and account actions, are held in process memory. Helpful-vote limits also use in-memory account and salted-IP-hash counters; no vote IP key is written to the database. Contribution limits also use the account link and the salted IP hash already stored with each contribution.	To limit automated or excessive requests. In-memory counters disappear when the service restarts; contribution-linked data follows the retention periods below.

Your account email is used for sign-in and account messages. Radar does not automatically copy it into the optional reply-email fields on contributions.

The IP hash is a one-way salted SHA-256 digest. It is not the address itself and cannot be turned back into one, but we treat it as personal information because it can still distinguish one visitor from another.

3. Cookies

Ordinary-account sign-in uses radar_user_session; administrator sign-in uses the separate radar_console_session. They can exist independently in the same browser. Each lasts 12 hours by default (the configured lifetime may differ), is marked HttpOnly and SameSite=Lax, and is Secure over HTTPS. Radar also sets radar_csrf_session, a signed, HttpOnly, SameSite=Lax cookie that binds form-protection tokens to this browser; it is used only for form security, is Secure over HTTPS, and expires after 12 hours.

There are no advertising, analytics or preference cookies, which is why you are not asked to accept any. If that ever changes, this page will say so first.

4. When you ask us to check a URL

The Checker works by having our server fetch the address you give it. The website being checked sees Radar's server, not you. We do not send your identity, your browser details, or your address along with that request.

We deliberately refuse to check addresses that point inside our own network or at private infrastructure, so the Checker cannot be used to reach systems it should not.

5. Services that see your browser

Radar's styling is compiled and served from this site; no Tailwind runtime script is loaded from a CDN. Your browser does request the Inter typeface from Google Fonts (fonts.googleapis.com and fonts.gstatic.com).

Google Fonts can see your IP address and the page origin requesting the font. The Community page links to our X account, but nothing is embedded, so visiting Radar does not load anything from X.

When account email is enabled for production, the SMTP provider selected by Radar will process your address and the account message to deliver recovery or email-change links. We will name that provider here before production email is enabled.

6. How long we keep things

Rate-limit counters: minutes, in memory, discarded on restart.
URL check records: kept for now as an audit trail of how results were produced. There is no automatic expiry yet; when we add one, this page will state the period.
Feedback, corrections and opportunity suggestions: kept while useful as a review record. On an account-removal request, account links may be removed where practical; contribution text may be retained in de-identified form for review history, abuse prevention, or legal requirements.
Community reports, report flags, and tool suggestions: kept while the report or suggestion is part of the site. Removed reports and their review/audit records may be retained in moderated form for abuse and decision-history records; account links may be unlinked where practical.
Helpful votes (only if enabled): vote rows are deleted when the linked account is deleted. A separate account-level suppression record is removed with that account; its reasoned audit entries may remain as a decision-history record with the account ID, admin actor, reason, and time, but no email address or public voter identity.
Ordinary account records: retained while the account is active. You can request removal by email; some contribution records may be retained separately for review history, abuse prevention, or legal requirements and unlinked from the account where practical.
Account-action token records: raw links are not stored; token hashes expire after 45 minutes and cannot be reused. A requested new email address is also stored with an email-change token. Expired or consumed token records, including that address, are not yet automatically purged.
Admin sign-in records: kept for the life of the account.

We would rather tell you honestly that a retention period is not yet in place than print a number we do not enforce.

7. Your choices and rights

You can ask what we hold about you, ask for it to be corrected, or ask for it to be deleted. Write to radar.complaints@gmail.com and say what you are asking about.

A community report can appear as “Anonymous” when your profile has no display name, but it is still linked to your account internally. A public pseudonym is not anonymous to Radar. Contact us from your account email if you need help locating or removing account data.

8. Security

Passwords are stored as bcrypt hashes and are never recoverable. Ordinary-user and administrator sessions use separate signed, HttpOnly cookies. Account recovery and email change links are stored as hashes, expire after 45 minutes, and can be used once. Forms are protected against cross-site request forgery, sign-in attempts are rate-limited, and raw IP addresses are not stored in the database.

No service can promise perfect security. If you believe you have found a vulnerability, please tell us at the address above before doing anything else with it.

9. Children

Radar is intended for adults. It is not directed at anyone under 18, and we do not knowingly collect information from them.

10. Changes to this policy

When our practices change, this page changes with them and the date at the top moves. We aim to handle personal information in line with the Nigeria Data Protection Act 2023 and with the principle that we should hold as little of it as possible.