MacroSphere Privacy Policy

Effective date: October 5, 2026

About MacroSphere

MacroSphere is operated by Owen Chambers, doing business as MacroSphere. This policy explains how we handle information when you use our app and website. The app is intended for adults 18 and older. Contact privacy@macrosphere.app about privacy or support@macrosphere.app for support.

The short version: MacroSphere stores information on your device and uses cloud services for accounts, selected records, social features, AI features, subscriptions, analytics and other functions described below. Local-first does not mean that all data stays on your device. We do not sell personal or health data, and we do not use your health data to select advertisements.

Information we handle

Accounts and preferences. Our backend provider, Supabase, handles authentication and stores your email, account identifier, profile, username, display name, settings, nutrition targets and policy-acceptance records. Passwords are handled by the authentication service; we do not receive a readable copy of your password.

Health and fitness records. The app stores food and nutrition logs, weight entries, workouts, activities, goals and related preferences on your device. When you are signed in, supported records such as food logs and weight entries are also sent to our backend. Progress photos you save can be uploaded with their date, angle, associated weight and note. They are stored in private cloud storage and are visible only to you. Other information you deliberately share is handled as described below. Do not assume that every locally stored record has an online backup.

Social features. Profiles, friendships, group memberships, messages, reactions, comments, shared workouts and posts use our cloud backend. Content you share is available according to the feature and audience you select.

Images are handled in three different ways, and the difference matters. Profile images are stored in public cloud storage, so anyone who has the image address can open it, including someone who is not signed in to MacroSphere. Progress photos are stored in private cloud storage with access rules that permit only your own account to read them; they are not visible to other users and no feature shares them. Images and content you send to a person or a group are available to that audience; limiting an audience does not prevent someone who receives a copy from saving or sharing it. Avoid sharing information you want to keep private.

Photos and AI features. When you request Photo Scan or meal-description analysis, the photo or description and any accompanying note are sent through our backend to Anthropic to generate food estimates. Voice logging uses Apple's speech-recognition service on iOS. The app does not request recognition that is restricted to your device, so your speech audio may be sent to Apple to be transcribed, under Apple's terms. MacroSphere does not receive or store that audio. The text Apple returns stays on your device unless you then ask for meal analysis, at which point the text, and not the audio, is sent to Anthropic as described above. AI workout generation sends your questionnaire answers and exercise options. AI weekly check-ins send the summary needed to generate the check-in, which can include goals, calorie and protein intake and targets, workout counts and weight changes. These features process the information you submit to produce the requested result.

Food databases. Food searches and barcode lookups use providers such as FatSecret, USDA FoodData Central and Open Food Facts. Search text or barcode numbers and normal network information may be processed to return results. These lookups are separate from the food records saved to your account.

Location and device permissions. If you enable outdoor activity tracking, the app uses precise location to record your route and activity statistics, including background location during a tracking session where supported and permitted. Completed activity statistics and route points are stored on your device and are also uploaded to our backend when you are signed in. Map services may receive network and map-view information. Camera, photo-library, microphone, speech-recognition and notification permissions are used for the features you choose. You can change permissions in your device settings.

Analytics, diagnostics and advertising

Product analytics. PostHog receives app lifecycle events and named actions such as onboarding, food logging, workout completion and subscription-screen views. Events use a random installation identifier before sign-in and an account identifier after sign-in. They may include app/build version, operating system, device type, session information, subscription context and limited categorical properties. Our app filters custom event properties to exclude detailed food entries, calorie and macro values, weight, measurements, workout loads, messages, photos and other user-authored content. Product events are also stored in our backend. PostHog session replay and automatic touch and screen capture are disabled in the app integration.

Crash diagnostics. When enabled, Sentry receives error reports, stack traces and app/device diagnostic context so we can investigate failures. Reports also record which screen you were on when the error happened. In app versions up to and including build 119, that screen value could contain part of the screen's address, such as a username or a record identifier. From the next build it records only the screen template, for example /profile/[username], so those values are no longer included. We do not send your name, email or account identifier to Sentry, and the app does not deliberately attach your food diary, weight history, photos or messages to crash reports.

Advertising. Free-tier users may see non-personalized Google AdMob banner ads. Google may process IP address, device or advertising identifiers, ad interactions and diagnostic information for ad delivery, reporting, frequency controls and fraud prevention. Non-personalized ads do not mean no data is processed. We do not send your health records to AdMob. Paid tiers do not request banner ads. Advertising consent and privacy controls are provided where applicable.

Subscriptions, notifications and the website

Apple handles iOS payments. RevenueCat receives your app account identifier and purchase, trial, renewal, cancellation and entitlement information to manage subscriptions. Subscription events may also be sent to PostHog. MacroSphere does not receive your full payment-card details.

Device notifications include locally scheduled reminders. Supported remote notifications use device push tokens and providers such as Expo and Apple or Google. Your device settings control notification permission.

Our website is hosted by Squarespace. If you subscribe to our newsletter, your email and signup information are processed to manage the subscription and send updates. You can unsubscribe using the link in an email. Website hosting and email services may process standard browser, network and delivery information.

How we use and share information

We use information to provide the functions you request, manage accounts and subscriptions, deliver selected communications, understand product use, diagnose problems, protect the service and meet legal obligations. Our service providers include Supabase, Anthropic, PostHog, Sentry, RevenueCat, Apple, Google AdMob, Expo, food-data providers and Squarespace. Providers receive information relevant to their functions above. We may disclose information where legally required, to protect rights or safety, or as part of a business transfer with appropriate notice.

Retention and deletion

Local records remain until you remove them or clear app data. Account-linked records are retained while needed to provide the service and handle your requests. Deleted database information may remain in encrypted rolling backups for up to 7 days. Support correspondence is retained for up to 12 months after resolution unless longer retention is legally required. Purchase records and records held by service providers may have separate retention requirements. Deleting an account does not automatically cancel an Apple subscription or remove copies that other people have saved.

You can initiate account deletion in Settings → Account or contact us from the email address associated with your account. The updated app removes your uploaded profile, post and progress images before deleting your account-linked database records; if cleanup fails, it keeps the account available for a retry. Some files may already have been removed when a retry is needed. Shared food-catalog records may remain with their creator identifier removed. See Delete Your MacroSphere Account for the process and limitations. Contact us for requests involving uploaded files or records held by external providers. We verify requests before acting to protect your account.

Your choices and rights

You can edit supported account information, choose what to share, change device permissions, use available advertising privacy controls, export supported local data and request account deletion. Depending on where you live, you may have rights to access, correct, delete or obtain a copy of your information, and to appeal a decision. Send requests or appeals to privacy@macrosphere.app. We do not discriminate against you for exercising applicable privacy rights.

Health and fitness information may be consumer health data under applicable laws. The Consumer Health Data Privacy Policy in the app provides additional information. We do not sell consumer health data or use it for targeted advertising.

Security, children and changes

We use measures such as encrypted network connections, access controls and database security rules. No system is perfectly secure. The service operates from the United States, and service providers may process information in the United States or other locations where they operate.

The app is not directed to children under 18. Contact us if you believe a child has provided information. We will investigate and take appropriate action. We will update this policy as our practices change and provide notice or request consent where required.