What this site does not collect
Happy Clarinet’s current V1 application does not provide user accounts, login, payments, a newsletter signup, a contact form, comments or file uploads. There is no application database used to store a visitor profile. The fingering chart does not ask for access to your microphone or camera. Pressing Hear note creates a synthetic reference tone in the browser; it does not record you, analyze your playing or send microphone audio to the site.
The current application source does not include an advertising network, behavioral-advertising tag or visitor analytics script. It also does not use a third-party font service: the interface uses system fonts and its application assets are served with the site. This description is about the current Happy Clarinet application and should be updated if those features change.
“Does not have an application database” is not the same as “no technical data is ever processed.” Loading any public website requires network requests. Infrastructure providers can receive request information needed to route, secure and deliver those requests. The next section explains the current hosting setup without inventing a promise about logs or retention that has not been verified.
Hosting and technical information
Happy Clarinet is currently deployed as static Next.js output on Cloudflare Workers Static Assets and served through the happyclarinet.com domain. When your browser requests a page, stylesheet, script, font or other asset, Cloudflare necessarily participates in delivering that request. Technical request information can include items such as the requested URL, IP address, user-agent/browser information, timing and security-related request metadata.
Happy Clarinet does not currently run its own server-side application code for the fingering chart, create an account record from those requests or write request data into an application database. Static hosting is one reason the site can perform its core lookup and print tasks without asking you to sign in.
The exact infrastructure-log products, retention periods and processing locations that may apply at the Cloudflare account/platform level have not been stated here as fixed facts because they have not been independently verified for this deployment configuration. Cloudflare’s own policies govern data it processes as a service provider or network operator. If Happy Clarinet enables additional Cloudflare analytics, security logging or another infrastructure service later, this notice should be reviewed and updated to describe the actual configuration rather than relying on this V1 description.
Preferences on your device
The interactive chart keeps a small amount of UI state while the page is open. Examples include the selected written note, whether accidentals are displayed as flats or sharps, and the paper size selected for printing. In the current implementation those choices are held in the page’s in-memory React state. Reloading the page resets them. The application does not currently write those preferences to cookies, localStorage or sessionStorage.
The report helper on the Contact page can write a prepared text outline to your clipboard, but only after you press the copy button. That clipboard operation happens on your device. Happy Clarinet does not receive the copied text merely because you pressed Copy. If clipboard permission is unavailable, the interface selects the text so you can copy it manually.
Printing is also initiated on your device. When you choose Print / Save PDF, your browser and operating system open their own print interface. The website does not receive the printer name, local file path or PDF you save. If you choose a cloud printer or another operating-system destination, that destination’s own privacy practices apply outside Happy Clarinet’s application.
Email enquiries
Happy Clarinet publishes hello@yangweiwei.dev as its current contact address. The website does not contain a form that silently sends data to this mailbox. If you click the address, your device opens its configured mail application; if you copy it, you can use any email service you choose. Sending an email discloses your email address and everything you put in the message to the email systems involved in delivering and receiving it.
Please send only information needed to answer the question or investigate the report. For a fingering correction, a written note, instrument system, chart version and relevant source are normally more useful than personal details. For a print or browser problem, device/browser information and a cropped screenshot may help. Remove unrelated names, account information or sensitive content before sending an attachment.
The public site does not currently state a specific mailbox provider, fixed deletion schedule or legal-operator identity because those operational facts have not been confirmed for publication. Until they are confirmed, Happy Clarinet should not claim that email is automatically deleted after a particular number of days. Privacy questions can use the same public contact address.
Third-party services and changes
The Methodology and Fingering Chart pages link to external references such as Yamaha, the Woodwind Fingering Guide and the International Clarinet Association. Those are ordinary outbound links. Happy Clarinet does not embed their full fingering charts as third-party widgets. When you follow an external link, you leave happyclarinet.com and the destination website can process your request under its own privacy practices.
Cloudflare is the current hosting and network-delivery platform for the site. GitHub is used for the project source and deployment workflow, but ordinary visitors do not need a GitHub account to use Happy Clarinet. The site does not currently embed social-media pixels, advertising SDKs, third-party comment widgets or remote font loaders in the public pages.
This notice is configuration-dependent. Adding analytics, a feedback database, a newsletter, user accounts, payments, microphone-based tuning, advertising or a different email/contact workflow would change the data flows and require a review before the feature is treated as covered by this text. The “updated” date on this page should change when the privacy-relevant behavior or the notice itself changes, not simply every time code is rebuilt.
Contact
Privacy questions can be sent using the public email address on the contact page. A public operator identity is not stated in this preview.