Who operates Smart Breeze
PixelSunset LLC operates Smart Breeze and smartbreeze.app and is the controller of personal information Smart Breeze collects through this website. For privacy questions or requests, email support@smartbreeze.app.
Inside the desktop app
Temperatures, fan readings, power source, preferences, custom curves, and the 15-minute history stay on the Mac. History exists only in memory. Preferences use the current user’s local UserDefaults.
Smart Breeze stores one device-only authorization token in the user’s Keychain and one independently verified root-owned copy under the legacy-compatible path /Library/Application Support/Breeze. Your license key is also stored in the user’s Keychain after you enter it; the app verifies it offline and never transmits it. Diagnostics leave Smart Breeze only when you explicitly copy them to the clipboard.
Network access used to timestamp and notarize a release occurs during the developer’s release-build process, not while the installed app is running.
This website
This site uses Vercel Web Analytics to count page views and visitors and report aggregate route, referrer when available, approximate location, device, operating-system, and browser statistics. Smart Breeze removes query strings and URL fragments before page-view events are sent. Vercel Web Analytics does not use cookies, and Smart Breeze sets no analytics or advertising cookies. No app account or access code is required.
After the private DMG passes Smart Breeze’s byte-count and SHA-256 checks and the server prepares a successful attachment response, Smart Breeze makes a best-effort attempt to send one server-side custom Web Analytics event. Its only custom properties are the public release version and build. No custom property contains an email address, IP-derived value, Mac model, request ID, referrer, form field, or persistent identifier. The event measures a verified download-response attempt, not whether a browser finishes saving the file, Smart Breeze is installed, or the app is opened. Analytics delivery can fail, so its count may be lower than the number of responses prepared.
For this event, Smart Breeze forwards only the user-agent and Vercel-provided public-IP headers that Vercel uses for aggregate daily-visitor, browser, device, and approximate-location reporting. Vercel may associate those aggregate signals within its daily visitor model. Those headers are not custom event properties. Smart Breeze does not send a cookie, referrer, form value, request ID, or other persistent identifier with the event. Analytics delivery can fail without changing the download response.
Vercel states that Web Analytics stores anonymized data that is not tied to an individual or IP address. A visitor is represented by a hash derived from the incoming request; that hash resets after 24 hours and cannot track someone between websites or across different days. Smart Breeze does not join the download event to support messages, diagnostics, or app state. Vercel separately processes ordinary connection metadata under its service policies for hosting, security, and abuse prevention.
The homepage loads the required Nick Launches badge image directly from nicklaunches.com. The request sends no Smart Breeze account, diagnostics, or app-state data and uses a no-referrer policy, but Nick Launches receives ordinary connection metadata such as the visitor’s IP address, browser headers, and request time under its own policies. The badge is not loaded inside the desktop app.
The privately stored DMG is delivered through Smart Breeze’s integrity-checking server route, which verifies its byte count and SHA-256 before every download. Support emails and diagnostics are received only when you choose to send them. License-key emails are sent only after a completed purchase.
When a valid download form is accepted, Smart Breeze reads Vercel’s trusted public-IP header only in memory to enforce a limit of ten download requests during each fixed ten-minute window. Smart Breeze does not log or persist the raw address. It stores one constant-size, bucket-scoped, keyed pseudonymous reservation token for each accepted request in private storage. A reservation is created before Smart Breeze reads and verifies the private DMG and remains counted if later integrity or delivery work fails, because the limit protects that server work. The token contains no address, browser detail, acknowledgement value, or persistent identifier and is not anonymous data. Reservations are scheduled for deletion after a 72-hour grace period by a daily cleanup job and are removed on the next successful run.
Paid purchases
When you buy a Smart Breeze license on this site, Stripe processes your payment as the payment processor. Stripe tells Smart Breeze that the purchase completed so it can email your license key from hello@smartbreeze.app. Smart Breeze keeps the license record needed to deliver your key, handle re-sends, and process refunds.
Smart Breeze does not see or store your card number. Payment details go directly to Stripe under its own privacy policy.