Summary
- Browsing is anonymous. There are no analytics scripts, advertising, tracking pixels or third-party embeds on public pages.
- An account holds your email address, a password hash managed by the identity provider, an optional display name, and a website access status.
- When you download a file, a minimal event is recorded: which account, which file, when, and whether the request was authorized. No IP address or URL is stored with it.
- Account email is transactional only (verification, password reset, email change confirmation). There is no marketing list and no way to be added to one.
- You can delete your account from the account page at any time.
What is collected and why
Public browsing
Public pages are static files served by Cloudflare. Cloudflare processes connection data (such as IP address and request headers) to deliver the site and protect it from abuse, under Cloudflare's own terms. The website does not set cookies on public pages except a short-lived, content-free CSRF token when you open a form.
Accounts
Accounts exist only to gate installer downloads. The identity service (Supabase Auth, in a project dedicated to this website) stores your email address, the time it was verified, a salted password hash, and session records. The website stores a profile row with your optional display name, an access status (active, suspended or deleted) controlled by the site operator, and the time of your last download.
Passwords are checked against a minimum length and known-breach lists at the provider; the website never sees or stores them.
Download events
Each request to the download gateway records: an anonymous request identifier, your account identifier (when signed in), the artifact identifier, the HTTP method, whether it was a resumed range request, the outcome (authorized, denied for a stated reason, or upstream error) and a short diagnostic code. These records let a withdrawn build be traced to the accounts that received it and let abuse be investigated. They contain no IP address, no confirmation token and no signed URL.
Abuse limits
To limit email flooding and password guessing, the website keeps short-lived counters keyed by a daily-salted hash of your network address and, for email actions, a hash of the address. Counters expire within an hour of the window they cover.
Support form
Messages sent from the support page are delivered by email (via Resend) to the developer. They contain what you typed, the address you gave for replies, and a request reference. Do not include passwords, keys or private note content.
Services used
| Service | Purpose | Data |
|---|---|---|
| Cloudflare (Workers, DNS) | Hosting, TLS, abuse protection | Connection metadata in Cloudflare logs |
| Supabase (Auth, Postgres) | Accounts, sessions, release metadata, download events | Email, password hash, profile, events |
| Resend | Sending account and support email | Recipient address, message metadata |
| GitHub | Private release storage for installer files | None about you; files are fetched server-side |
Cookies
Signed-in sessions use HttpOnly, Secure cookies named nx_session (set by the identity library). A CSRF token cookie (nx_csrf) protects forms. A short-lived nx_return cookie remembers which download you selected while you verify your email. None of these are used for tracking, and no consent banner is shown because no non-essential cookies exist.
Retention and deletion
- Account data is kept until you delete the account. Deleting removes the identity record and profile; download events keep the artifact and time but lose the account reference.
- Download events are retained for 24 months for security-notice purposes, then deleted.
- Rate-limit counters expire automatically within about an hour.
- Support emails are kept in the developer's mailbox until the matter is resolved.
- Unverified accounts that never confirm their email may be removed after 30 days.
Your choices
- Read everything without an account.
- Change your email, change your password, sign out of all sessions, or delete the account from the account page.
- Ask questions through the support page.
Applications
The desktop applications are separate from the website account. CLITiles, Tuner and InfiniteNotes run locally and make network requests only for features that need them (for example, InfiniteNotes sends selected content to an AI provider you configured with your own key; Tuner queries radio directories). Each product page has a "Data and privacy" section describing the current release; those descriptions, and the applications' own documentation, are the authoritative statements for the applications.
Changes
Material changes to this page are noted with a new "last updated" date. The website repository keeps the history of this text.