WEBSITE PRIVACY
Your website privacy choices.
Status: Production
Optional first-party website analytics help RFile understand return visits and download interest. Local desktop file browsing does not send usage analytics.
- Visitor analytics require your choice
- No advertising trackers or fingerprinting
- Only the verified RFile owner can view administration
Choose whether to share website activity
Choose Allow in the website privacy notice to enable a signed, first-party visitor cookie for up to 180 days. Choose No thanks to browse without visitor analytics. Open Privacy choices in the website footer to change your decision. Do Not Track and Global Privacy Control signals keep visitor tracking disabled.
With permission, RFile records normalized website pages, visit times, an approximate country code when available, and installer download handoffs. Query strings, URL fragments, private file paths, raw IP addresses and user-agent fingerprints are not stored in visitor analytics. A visit restarts after 30 minutes of inactivity.
When you sign in, consented visitor activity is associated with your account. The administrator can then see your account name/email, visit counts and download handoffs. Signed-out visitors appear as anonymous browser IDs; these are not an exact count of people. Signing out or switching accounts separates subsequent activity on a shared browser.
What download and update counts mean
Website download counts measure the handoff to the official GitHub installer, including anonymous requests. Reading release information, checking for an update and HEAD requests do not count as installer downloads. An installer handoff does not prove that the download completed or the app was installed.
The admin dashboard also reads GitHub's public installer download counters. These include direct downloads, updater downloads, repeat downloads and release verification; they cannot identify a person or prove installation.
A paired PC already reports its running app version when it connects. RFile records a version change when that reported version changes, allowing the administrator to see account-associated updates or downgrades. Offline or unpaired PCs cannot be identified this way. Local browsing, file contents and file paths are not reported.
Access and retention
Administration at /admin requires an active authenticated session for the verified haskbasirat@gmail.com account. The API enforces this restriction on every request. Ordinary accounts cannot read other visitors or accounts.
Visitor events, visitor records and reported device version changes are retained for up to 180 days with hourly expiry maintenance. Withdrawing website analytics consent removes this browser's retained visitor record and associated detailed events. Anonymous daily totals are retained without a visitor ID, account ID, IP address or user agent. Request status totals cover up to 30 days and distinguish authentication retries from visits.
Account signup, account status and paired-device records are operational account data, available independently of optional website analytics. Historical visits cannot be reconstructed: the dashboard displays when collection began. For questions or data requests, contact haskbasirat@gmail.com.