Privacy Policy

Last updated: August 1, 2026. Applies to every McMizzle app, including AmbientCast and Calorie Burndown.

The short version: your data stays on your own devices. None of it passes through any server McMizzle operates, because there isn't one — every McMizzle app talks directly to the services you've chosen to connect it to (like Bambu Lab or YouTube), or to Apple's own on-device frameworks (like HealthKit), and nowhere else.

What McMizzle apps store, and where

Specifics vary by app, but the pattern is the same everywhere:

• Account credentials and access tokens (e.g. AmbientCast's Bambu Lab sign-in) are stored in your device's Keychain, on-device only. Passwords are sent directly to the relevant third-party service to authenticate — never stored by the app itself.
• Health & fitness data (e.g. Calorie Burndown's use of HealthKit) is read directly from Apple's HealthKit on your device and never leaves it, governed by Apple's own HealthKit privacy rules.
• App settings and cached status (e.g. printer connection details, daily calorie goals) are stored locally, and where an app has a companion widget or watch app, shared only via an on-device App Group container — never sent anywhere off-device.

What McMizzle apps don't do

• No analytics, crash reporting, advertising, or tracking SDKs of any kind are included in any McMizzle app.
• No account credentials, health data, or usage data are ever sent to any server McMizzle operates.
• Nothing is sold or shared with third parties beyond the services you've directly chosen to connect to.

Third-party services

Where a McMizzle app connects to a service on your behalf (e.g. AmbientCast to Bambu Lab's cloud or YouTube for optional live streaming), that portion of your data is governed by that service's own privacy policy — not this one.

Contact

Questions about this policy: see the support page for the right place to ask, per app.