Your Mac’s thermals stay on your Mac

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 and the hardware-testing program. 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. 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 beta 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.

After a genuinely new hardware-beta application is encrypted and stored, Smart Breeze makes a best-effort attempt to send a second server-side custom event named “Hardware beta application received.” It is not attempted for a honeypot submission, validation failure, or duplicate, and it has no custom properties. It is not proof of a verified email address, an Accepted Tester, or a completed cohort.

For either 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, encrypted-application pathname, request ID, or other persistent identifier with either event. Analytics delivery can fail without changing the download or application 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 either event to decrypted hardware-beta application contents, the submitted email address, 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, hardware-beta application, 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. Paid checkout is disabled, and no payment information is collected by Smart Breeze at this stage.

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.

When a valid hardware-beta application is submitted, Smart Breeze reads Vercel’s trusted public-IP header only in memory to enforce a five-submission, ten-minute fixed-window limit. Smart Breeze does not log or persist the raw address. It stores a bucket-scoped, keyed pseudonymous reservation token in private storage; the token 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.

Hardware testing applications

If you apply for exact-model fan-control qualification or fanless sensor-compatibility testing, Smart Breeze collects the email address, exact model identifier, optional model name, chip, macOS version, fan count, whether this is a primary or secondary Mac, testing availability, optional time zone, optional notes, and the versions of the acknowledgements you submit. Do not send a serial number, Apple ID, password, administrator credential, personal file, or diagnostic report through the application form.

Applications are encrypted before they are written to private storage. They are used only to group exact-model cohorts, coordinate testing, provide safety support, investigate reports, and administer the tester-license benefit. They are not sold, used for advertising, or connected to the installed app’s fan-control state. A submitted application and its checkbox acknowledgements remain unverified until the Smart Breeze team receives a reply from the submitted email address; no test assignment or model-specific build is issued before that confirmation. The app still sends no automatic telemetry.

Unselected applications are reviewed monthly and deleted after 180 days from submission. If you join an active cohort, the application and restricted contact record may be kept while testing or a related safety issue remains active, then are deleted within 180 days after the last program contact. For a tester who earns the complimentary license, Smart Breeze keeps a separate restricted entitlement record containing only the verified email, cohort and model, completion status and date, and delivery status and date until the benefit is delivered or the program is formally cancelled; that record is deleted within 180 days afterward. You may withdraw or request deletion by replying to a verification or cohort email, or by emailing support@smartbreeze.app.

Paid purchases

PixelSunset LLC currently operates the free Smart Breeze beta. Smart Breeze does not offer paid checkout today and collects no payment information. Before Smart Breeze offers any paid purchase, the checkout and then-current terms and privacy notice will identify the seller, paid-license scope, price, taxes, refund terms, payment processor or merchant of record, applicable retention periods, and privacy rights.