Privacy Notice

Status: Pre-launch notice. This notice is not yet effective because the website operator, production domain, service providers, data practices, and privacy contact have not been verified.

Effective date

Not yet assigned

Last updated

Not yet assigned

This page is intended to describe privacy practices for a proposed professional website concerning Fred Katz, the NBA journalist. It does not represent that Fred Katz owns, operates, endorses, or has authorized the website.

No production domain is currently covered by this notice. In particular, fredkatz.com must not be identified as the NBA journalist’s website: research found that the domain currently presents material about jazz cellist and composer Fred Katz, and its ownership and authorization for this project have not been established.

Once completed, this notice will apply only to information processed by the verified production website and its contracted service providers. Independent publishers, membership platforms, retailers, media outlets, and other external destinations have their own privacy practices.

Website operator and privacy contact

The legal identity of the website operator or data controller has not been verified. Fred Katz must not be named as the operator, controller, or privacy contact without documented authorization.

No authorized privacy email address, telephone number, postal address, agent, or representative was established by the available research. Private, guessed, scraped, or unverified contact details will not be published.

A verified privacy contact method must be added before the website launches or enables any feature that collects information requiring an accessible request channel. Until then, visitors cannot submit privacy requests through this website.

Accessibility concerns are addressed separately in the Accessibility Statement. That reporting route must also remain unavailable until an authorized recipient has been established.

Information that may be collected

The planned core website can operate as static informational pages with lightweight browser-based archive filtering. No inquiry form, newsletter signup, advertising system, analytics provider, or production host has been confirmed.

The table below records the current implementation status. It does not claim that unverified categories are collected or absent.

The production notice must be revised to describe only the information the completed website actually processes.

Why visitor information would be used

The website is intended primarily as an informational gateway to reporting, podcast, book, and media resources hosted by their original publishers or platforms.

If production systems collect information, each category must be connected to a documented purpose. Those purposes may include:

• delivering requested pages and files;
• maintaining website security and investigating technical misuse;
• supporting accessibility and correcting technical barriers;
• responding to an authorized inquiry or privacy request; or
• measuring aggregate website performance, if a reviewed analytics service is enabled.

No legal basis is stated at this stage. Consent, contractual necessity, legitimate interests, or another basis must not be claimed until the operator, relevant jurisdictions, processing activity, and supporting procedure have been reviewed.

No verified implementation currently uses visitor information for advertising, behavioral profiling, affiliate attribution, or marketing. If any such practice is introduced, this notice and any required controls or commercial disclosures must be updated first.

Cookies, local storage, and analytics

No analytics provider, nonessential cookie, or cookie-preference system has been identified for the production website. This is not a guarantee about a future implementation.

Archive filters may operate entirely within a visitor’s browser. Whether filter preferences will be saved in local storage has not been determined. If browser storage is used, the final notice must identify the stored record, its purpose, and how a visitor can remove it.

A production cookie and storage inventory must include, for every technology used:

• its name and provider;
• its operational purpose;
• how long it remains active;
• whether it is essential; and
• how consent can be given or withdrawn where required.

A cookie banner or preference control should be deployed only if the final technology and applicable rules require it. Any preference control must be keyboard accessible, show its current state, and avoid preselecting optional consent where affirmative consent is required.

Form submissions and communications

No inquiry, correction, accessibility, privacy-request, or newsletter form is authorized on this page or confirmed for the website’s launch.

A professional inquiry route must not be activated until it has an authorized recipient, defined submission fields, spam controls, retention and deletion rules, a secure service provider, and an approved privacy workflow. Submissions must not be described as reaching Fred Katz unless that recipient and authorization are verified.

The current availability of professional contact options is explained on the Professional Inquiries page.

If a form or newsletter is introduced later, the notice shown before submission must identify:

• the form’s purpose and all required and optional fields;
• the authorized recipient and any service provider;
• where submissions are stored, including email systems, hosted platforms, or backups;
• the retention period or deletion criterion;
• the expected follow-up; and
• separate consent choices for optional marketing communications.

External services and links

The website is expected to use ordinary outbound links to original publication pages, Patreon, Simon & Schuster, approved retailers, verified media outlets, and confirmed professional profiles. Activating one of these links takes the visitor to an independently operated service with its own privacy notice and terms.

External publishers may require a subscription. Patreon controls its memberships, prices, benefits, and access rules. Publishers and retailers control book availability, transactions, and ordering terms. This website does not control how those services collect or use information after a visitor leaves the site.

Ordinary links do not normally transmit the same range of information as embedded players, videos, social posts, or retailer widgets loaded within a page. The planned site should prefer privacy-preserving links over unnecessary third-party embeds. Any embed added later must be reviewed for data transmission that occurs before visitor activation.

No affiliate tracking has been documented. If commercial or affiliate links are introduced, their tracking practices and the commercial relationship must be disclosed clearly.

Visitors should review a destination service’s privacy notice before providing information there. For more about canonical article links and possible subscription requirements, see the Article Access and External Link Guide.

Service providers, disclosures, and data transfers

No production hosting, content-delivery, security, analytics, form, email, mailing, or spam-prevention provider has been identified. The final notice must name each provider that processes website visitor information and explain its limited purpose.

No verified conclusion can yet be stated about:

• sale or sharing of personal information;
• behavioral advertising disclosures;
• storage or processing locations;
• international data transfers or safeguards;
• provider access to logs or submissions; or
• procedures for responding to lawful requests from public authorities.

These statements must be completed from actual contracts, vendor settings, and technical configuration rather than generic assumptions. Independent external websites are not service providers to this website merely because a visitor follows an ordinary outbound link to them.

Retention and security

No retention periods can be stated until the production data inventory and vendors are confirmed. Before launch, the operator must establish a retention period or specific deletion criterion for each category, including server logs, security records, analytics data, submissions, email records, and backups.

Expired records should be deleted or anonymized according to the documented schedule. The final notice must explain how deletion applies to active systems and when records age out of backups.

The static site architecture can reduce privacy risk by minimizing collection. Any enabled service should use proportionate organizational and technical protections, such as restricted access, secure transmission, maintained software, account safeguards, and documented incident procedures where appropriate.

No website or storage system can guarantee complete security. The final notice must describe actual safeguards without making absolute promises.

Privacy rights and choices

Privacy rights vary according to the operator, the visitor’s location, and the processing involved. Because the operator, jurisdictions, and privacy-request recipient have not been confirmed, this page does not promise universal rights or fixed response periods.

Where applicable, visitors may have rights concerning access, correction, deletion, restriction, portability, objection, or withdrawal of consent. The effective notice must explain which rights apply, how to exercise them, how identity will be verified proportionately, and whether authorized agents may submit requests.

No verified privacy-request channel is currently available. One must be established before launch, along with an authorized recipient and a documented response process. Information about complaints to a regulator will be added only after the relevant jurisdiction is confirmed.

Requests to correct public site metadata or report a broken link are editorial matters rather than privacy requests. Those matters are covered by the Corrections and Update Policy.

Children’s privacy

The documented audiences for the proposed website include NBA readers, New York Knicks fans, podcast listeners, book readers, journalists, producers, event organizers, researchers, and professional peers. No planned feature is intentionally directed to children.

No specific age threshold is stated because the operator’s applicable jurisdictions have not been confirmed. Before launch, the operator must determine the appropriate threshold and procedure with qualified counsel.

The effective notice must explain how the operator will respond if it learns that a child’s information was collected contrary to the website’s policy, including appropriate review and deletion steps.

Updates to this notice

This notice must receive a production privacy review before it becomes effective. The verified effective date and last-updated date will appear near the top of the page once the operator, domain, contact route, vendors, and data practices are confirmed.

A further review is required before enabling or materially changing:

• analytics or nonessential cookies;
• forms, newsletters, or mailing tools;
• embedded third-party content;
• affiliate or advertising tracking;
• spam-prevention or security services that process visitor data; or
• hosting, content-delivery, or other production vendors.

When the effective notice is revised, its last-updated date will change. Any additional method for communicating material changes must reflect the operator’s documented governance process. Archived versions should be retained if that process or applicable law requires them.

Return to this page to review the current notice before using any newly enabled data-collection feature.