Your information
Dial privacy notice.
How Dial handles information across the app, account services, and optional features.
Dial Privacy Notice
Updated October 24, 2026
Who operates Dial
MacroMatic LLC operates Dial. This notice covers Dial for iOS and Android and their shared account services. Features and permissions can differ by platform. Contact sam@macromatic.space for questions, access or deletion requests. Our mailing address is 1309 Coffeen Avenue STE 1200, Sheridan, Wyoming 82801, USA.
Accounts and saved content
Dial uses Google Firebase to authenticate your account and store your account ID, name and email when provided, profile settings, food logs, portions, nutrition values, recipes, goals, progress and feedback. Guest accounts also have an account ID. Foods and recipes you create for the shared catalog may be searchable by other users; the catalog is separate from your account food log. Profile information and follower relationships are used by available social features.
Health and fitness information
You can provide age, sex, height, weight, activity level, training experience, body measurements and nutrition or fitness goals. Dial uses these values to calculate targets, show progress and provide personalized features. With your permission, Apple Health can supply age, sex, height and weight to prefill your profile; the profile values you save are stored with your Dial account. Authorized activity, steps and sleep information is also read for on-device displays. If you enable weight sync and allow Weight access, Dial reads the last 90 days of Apple Health weigh-ins and new measurements, including their dates and sample identifiers, and saves them to your Dial account on Firebase. Pending imports are stored on your device so they can retry when you reconnect. This sync is one-way from Apple Health to Dial; Dial does not request permission to write to Apple Health. Turning weight sync off stops future imports and does not remove weights already saved in Dial. Deleting a measurement in Apple Health does not automatically delete its Dial copy. You can manage Apple Health access in system settings and request deletion of saved Dial data as described below.
iOS photos and AI features
Profile and body photos can be uploaded to Google Firebase Storage. With your explicit permission, food and nutrition-label photos are sent through Firebase to OpenAI to estimate foods and nutrients. Body scans share the selected photo plus available age, sex, height, weight, activity level, training experience and previous scan or weight context. Goal suggestions share profile values, goal type and an available body-fat estimate. Check-in feedback shares goal type, macro targets, scan dates and estimates, and up to 180 days of nutrition and weight logs. Micronutrient estimates share the selected day’s food names, brands, portions and nutrients. AI food search sends your food search query through the Dial backend on Firebase to OpenAI to generate nutrition estimates. Coaching features share your messages and recent conversation, name, profile, goals, phase dates, pace, weight and body-fat measurements, and up to 10 recent daily progress records, including foods, calories, macros and weight, with OpenAI after permission. These AI requests include a pseudonymous account identifier for abuse prevention. In iOS 4.50 build 3 and later, Dial records your account, the feature, disclosure version and permission time for these optional photo, goal, check-in, micronutrient and coach features, and checks their permission before each request. You can decline these features and use manual entry, or turn their permissions off in Profile → AI Privacy. Older app versions may not offer these controls; update Dial on each device to use them. Turning permission off does not recall requests already in progress or data already sent. AI results are estimates and saved results can become part of your account. OpenAI processes API inputs to provide these results and does not train on API data by default. Requests disable API response storage; separate abuse-monitoring or legally required retention can still apply. We require service providers handling personal data on our behalf to protect it consistently with this notice and applicable requirements, restrict processing to authorized purposes, and use appropriate security safeguards. We send data over encrypted connections and limit access to the service functions needed for the feature. Provider processing and retention depend on the service and its settings; this notice does not promise immediate provider deletion or that every AI request is excluded from provider retention.
Android features and permissions
Android supports email/password and guest accounts. Sign in with Apple is not available in the Android app. Creating a separate account does not automatically transfer history or subscriptions.
Health Connect
With your permission, Dial for Android reads steps, sleep, active energy and weight from Health Connect while the app is open. This access is optional and read-only. In the current Android version, imported values are used for on-device displays and are not uploaded by this import path. Health information you enter and save manually is a separate account-data flow stored on Firebase. You can revoke access in Health Connect settings. Deleting your Dial account does not delete Health Connect records held by other apps.
Selected photos and AI analysis
Choosing or capturing a photo for an Android food, nutrition-label or body scan starts its upload for analysis. The selected image goes through Firebase to OpenAI with the feature instructions, a pseudonymous account identifier for abuse prevention and relevant body-profile context when supplied. These optional scans can be avoided by using manual entry. The iOS AI Privacy controls and permission receipts described above are specific to the stated iOS versions; they are not Android controls. AI results are estimates; review them before use.
Uploads, retries and saved scan results are not memory-only processing. Food-scan completion attempts to remove the uploaded image. Interrupted or failed cleanup can leave uploads for retry. New unattached uploads become eligible for cleanup after 24 hours, and scan-retry media have a 30-day expiry window. Saved body photos remain until scan or account deletion. Cleanup is asynchronous; expiry eligibility does not promise an exact removal time or immediate erasure of provider or recovery copies. Requests disable OpenAI response storage, but separate abuse-monitoring or legally required retention can still apply.
AI food search
With your permission, Android AI food search sends your search text and a pseudonymous account identifier through Firebase to OpenAI to generate nutrition estimates and help prevent abuse. Avoid including personal details in searches. You can use library search without AI. Review suggested portions and nutrition before logging; logging a suggestion saves it only to your account. Firebase stores request results and records used for retries and request limits; this is not memory-only processing. Requests disable OpenAI response storage, but separate abuse-monitoring or legally required provider retention can still apply.
Android services, subscriptions and notifications
Android uses Firebase Authentication, backend services, Messaging and Installations, and App Check with Google Play Integrity. These services process account or installation identifiers and relevant app, device, network and integrity information for their functions and security. Messaging-token initialization can occur independently of permission to display notifications. Bundled Google ML Kit processes barcode camera frames on the device and separately collects its documented diagnostics and usage metadata. Barcode lookup can send the recognized barcode through the Dial backend to Open Food Facts; this lookup does not send the scan photo or your meal log to Open Food Facts.
Google Play and RevenueCat process Android purchase and subscription state, your Dial account identifier and relevant purchase, app and SDK information. RevenueCat Paywalls also record impressions. Deleting Dial or its account does not cancel a Google Play subscription or automatically erase provider-held transaction records. Manage a subscription in the store where you bought it, and contact support for retained-data requests.
Shared catalog and reports
The Android catalog workflow stores new food and recipe definitions privately before you explicitly request sharing for moderation. Approved definitions can be public. Sharing a definition does not publish your personal food log or private scan photos. Reports include your account, the selected content and reason, and text you submit. Limited safety and moderation records, deletion markers and receipts can remain for moderation and safe retries. Older clients and shared catalog records can follow the legacy paths described in this notice.
Optional assistant connections
Connecting Claude (Anthropic) or ChatGPT (OpenAI) lets that named provider access only the Dial permissions you explicitly approve. The promotion shown in Dial does not itself authorize access to your food or weight data. Food permissions can share requested food logs, portions, totals, targets and remembered estimates; separate weight permissions share or save requested weights, units and dates. Dial receives the structured values sent to its tools, rather than your full assistant conversation or original meal photos. The assistant provider processes your chat and uploads under its own privacy controls. Each assistant requires separate authorization. Disconnecting prevents future authorized access when the Dial grant is revoked; it does not erase saved food or weight records, previous assistant messages or retained records. A provider-side disconnect may not immediately update the connection badge in Dial.
Subscriptions and notifications
Apple and RevenueCat process subscriptions and purchases. RevenueCat receives your Dial account ID and purchase or subscription information so Dial can provide purchased features and restore access. Dial does not receive your payment-card number. Referral-related purchase records may include the purchaser account, the profile that led to the purchase and the product. If you allow notifications, Firebase Messaging and Apple process a device notification token; Dial stores it with your account to deliver notifications.
Subscription-event notifications
An existing production billing integration sends subscription events through Firebase to Slack for subscription monitoring. These messages can include your Dial or RevenueCat account ID, transaction ID, product, store, price and currency, purchase and expiry dates, and entitlements. The older callback also records incoming billing-event data in Google Cloud Logging. The separate protected subscription verification route does not send Slack notifications. Copies held by these services follow their configured retention and may require separate review when you request deletion.
iOS product analytics and earlier app versions
Dial uses PostHog and server logs to measure product use, connection setup, request results and performance. These records can be linked to your Dial account ID and include app and device details, event timestamps, session identifiers, coarse feature actions and subscription activity. Starting with version 4.46, native PostHog analytics are limited to operational fields and exclude name, email, profile answers, food names, nutrition values, weight values, free-form error descriptions and transaction IDs. Version 4.50 also removes the Meta and Firebase Analytics SDKs from the app. Branch remains available for explicit deterministic links with attribution disabled. RevenueCat can continue to send subscription events to our Firebase and Google Analytics services for subscription reporting; removing a native analytics SDK does not turn off this server-side reporting. Earlier versions, including 4.45, can send identifying and profile or onboarding values to PostHog and initialize Firebase Analytics, Meta and Branch analytics or attribution. Updating the app does not automatically remove records those versions already sent. We have not established a single retention period covering every analytics or provider record.
Other services and website visits
Barcode lookup sends the scanned barcode through the Dial backend on Firebase to Nutritionix. Nutritionix requests can include your Dial account ID. Other food lookup features can send a barcode or search request to Open Food Facts. Providers also receive network information needed for requests. Our website uses the existing Google Analytics web stream for page visits, App Store link activity and assistant-connection link activity, with coarse referral-source categories. Our explicit website events use public page paths rather than full query strings or fragments, and do not include Dial account IDs, food logs or health values. The website honors Global Privacy Control and Do Not Track for this measurement, and serves assets through external hosting or content providers. Contacting support shares the information you choose to send. Third-party services operate under their own terms and privacy notices.
Retention and account deletion
Account data is generally retained while your account exists, unless you remove entries or request deletion. Use Delete Your Account in Dial to request backend account cleanup. Deletion does not cancel an App Store subscription; manage that subscription through Apple. Shared catalog entries can remain after author attribution is removed. Minimal deletion receipts and hashed deletion markers are retained to prevent data from being recreated and to support safe retries. Some older photos use storage paths whose ownership cannot be established automatically and may require manual review; account deletion is not a guarantee that every historical photo has already been erased. Request records with expiry fields and expired connection records are eligible for asynchronous cleanup, rather than deletion at an exact promised time. Account deletion does not automatically erase every analytics, billing, AI-provider, support, backup or previously exported record. Contact us for a request covering retained records; applicable retention obligations and each provider’s controls may affect the response.
Current Google Cloud recovery settings can retain deleted Storage objects and Firestore data versions for seven days. Ordinary operational log retention is configured for 30 days; required Cloud Audit Logs are configured for 400 days. These records are separate from active account data. Historical exports and records held by other providers can follow separate retention and may require review through support. See account deletion instructions for app and external requests.
Your choices and requests
You can choose which optional photos, AI features, Apple Health and Health Connect permissions and assistant connections to use, correct or remove saved food, decline an assistant draft and request account deletion. To request access, correction or deletion of retained information, contact sam@macromatic.space. We may need to verify that the request concerns your account. Applicable law may provide additional privacy rights. Do not include passwords, sign-in codes or unrelated medical records in a support request.
Changes to this notice
We update this notice as Dial’s features and data practices change. The revision date identifies this update. The general app notice and the separate assistant-connection notice describe different parts of the service; neither a policy update nor an App Store privacy label changes existing access controls or guarantees complete historical erasure.