JADYS VISUAL RADAR

Privacy

What Visual Radar collects, what it avoids, and how public browsing stays lightweight

Last updated: September 10, 2026

01

Public browsing

You can browse public rankings, creator pages, visual pages and information pages without creating an account. Public browsing does not ask for a password or payment information.

02

Member accounts

When you register, Visual Radar stores your display name, normalized email address, acceptance time for the Terms and Privacy Policy, and a one-way password hash. The original password is never stored. Account requests can be submitted through the Feedback page.

03

Analytics

Visual Radar records lightweight page-view events to understand site usage. Events can include path, locale, country or region from edge headers, referrer, device type, an optional signed-in user id and a hashed visitor identifier for UV estimates. Admin routes, static assets and healthcheck routes are excluded, and full raw IP addresses are not stored.

04

Cookies and security

The site may store a language preference cookie and local theme preference. Member login uses a separate HttpOnly, SameSite session cookie containing a random token; only its hash is stored in the database and it expires after 30 days. Rate-limit counters use a salted network-identifier hash and expiry time to prevent abuse. Full raw IP addresses, passwords and raw session tokens are not logged. Admin access uses a different HttpOnly cookie.

05

Feedback and forms

Feedback forms collect the fields you submit, such as category, subject, details, related page, creator username, optional name and optional reply email. Reply email is stored through the existing encrypted contact field when encryption is configured.

06

Source data

Visual Radar uses public X profile and post information for discovery and ranking. It does not request X passwords, private messages or non-public account data. Apify may be used to collect public profile or post information, and source failures are recorded as operational status rather than hidden.

07

Secrets

Public pages and public APIs must not expose database URLs, admin passwords, access tokens, Apify secrets, R2 credentials or other private environment values.