This policy is provided by JMB Assets LLC, doing business as StackForge Studios. It is separate from the general StackForge Studios Privacy Policy and applies to "consumer health data" processed through PlateStack or another StackForge feature that expressly links to this policy. It provides the disclosures required by consumer-health privacy laws, including Washington's My Health My Data Act.

PlateStack processes this data for user-requested logging, display, sync, storage, summaries, general coaching, editable planning, reminders, security, export, and deletion. PlateStack is not a medical device or health monitor, and its automated output is not professional medical, nutrition, dietary, fitness, recovery, readiness, or safety advice.

1. Consumer health data we collect and why

Health-linked account and profile information: account identifier, age or age range, height, weight, activity level, dietary preferences, fitness preferences, goals, units, settings, and legal-consent records. We use this data to create and secure the account, apply the user's choices, and provide requested self-tracking features.
Nutrition and routine information: foods, meals, recipes, calories, macros, micros, nutrients, water, fasting, habits, reminders, shopping lists (including any supplement items you add to them), food images, labels, barcodes, voice transcripts, and corrections. We use it to create requested logs, estimates, summaries, trends, reminders, and user-requested AI results.
Fitness and activity information: workouts, exercises, sets, repetitions, loads, RIR, cardio, steps, active energy, activity, user-created templates, personal records, and progress. We use it to create requested logs, history, record comparisons, social features, editable templates, summaries, and general coaching.
Body and connected-record information: body weight, measurements, body-fat entries, progress photos, sleep, resting heart rate, HRV, blood oxygen / SpO2, respiratory rate, blood pressure, VO2 max, and mindful minutes. We use it to display user-requested history and trends and to provide connected features. Progress photos are stored privately and are not included in Coach requests.
Connected-health information: the data types the user authorizes PlateStack to read from or write to Apple Health / HealthKit or Android Health Connect. We use it to perform the sync and display functions the user requests.
User-requested AI inputs, outputs, and inferences: selected food or label photos; voice or natural-language food entries and transcripts; Coach prompts and responses; and generated logging estimates, workout or progress summaries, and editable meal or workout plan drafts. Depending on the feature selected, a request may include limited age, biological sex, goal, preference, nutrition-log, hydration, fasting, workout and RIR, cardio, body-progress, saved-plan, habit, recipe, reminder, Coach-memory, the screen the request was started from, and separately authorized connected-health context. The connected-health snapshot may include steps, active energy, sleep, resting heart rate, HRV, VO2 max, blood oxygen, and respiratory rate when available, together with a recovery figure calculated from those values against the user's own earlier readings. That figure is an inference drawn from the user's records, not a medical, readiness, or safety assessment. We exclude full name, email address, and full date of birth from these AI requests.
Health-feature usage and security records: timestamps, permission status, sync state, quota or entitlement records, and technical events associated with health features. We use them to deliver the feature, prevent abuse, diagnose failures, protect data, and comply with law.

2. Android Health Connect

On Android, PlateStack integrates with Health Connect only after the consumer opens Devices & Integrations, or the optional setup step, and explicitly taps Connect. Health Connect grants permission per record type in its own system sheet. PlateStack requests twelve permissions — seven reads and five writes — and each one supports a specific feature.

Read access (7 record types):

Weight — imported into the consumer's PlateStack body-metrics history and plotted on the Progress weight trend, so a weigh-in already recorded by a connected scale does not have to be entered a second time.
Body fat percentage — imported into the same body-metrics history and charted directly beside weight, so the consumer can distinguish fat loss from weight loss, which the weight trend alone cannot show.
Exercise sessions, distance, and total and active calories burned — imports workouts recorded by another app, such as a watch or running app, into the consumer's cardio and workout history, with distance and energy matched to the same session. These four reads arrive with the next Android update and are disclosed here in advance; the current Android release reads only weight, body fat percentage, and sleep.
Sleep duration — last night's total is displayed beside the food and training the consumer logged for that day, so the two can be seen together without switching apps.

Write access (5 record types): exercise sessions, active calories, and distance for workouts and cardio the consumer completes in PlateStack; body weight the consumer enters in PlateStack; and nutrition for the food the consumer logs in PlateStack. These writes exist so that records the consumer creates in PlateStack are available in the other apps they use, rather than being confined to one app.

PlateStack does not read steps through Health Connect. Health Connect data is used only for the features described above. It is never used for advertising, never sold, and never shared with a data broker. The consumer can disconnect inside PlateStack at any time, and can fully revoke access from Health Connect → Apps → PlateStack. PlateStack re-checks its granted permissions every time it returns to the foreground, so a revocation takes effect in the app immediately.

Apple Health / HealthKit on iOS is a separate integration with its own permission prompts, and may include additional record types — such as steps, active energy, and heart-rate measures — where the consumer authorizes them. References to steps elsewhere in this policy describe that iOS integration and manual entry, not Health Connect.

3. Sources of consumer health data

the consumer, through entries, uploads, prompts, photos, audio, settings, corrections, and permissions;
the consumer's device and operating system;
Apple Health / HealthKit and Android Health Connect, after platform permission;
food, nutrient, barcode, and public-recipe sources used at the consumer's request;
other users, when the consumer intentionally participates in a social or shared-workout feature; and
processors that return a transcription, food result, AI output, delivery result, purchase entitlement, or security signal for a consumer-requested feature.

4. Consumer health data we share

We do not sell consumer health data. We do not share it for advertising, data brokerage, credit, insurance, employment, housing, lending, or eligibility decisions.

We disclose the following categories only as needed to provide a consumer-requested product or service, operate or secure that product, or comply with law:

health-linked account, profile, nutrition, fitness, activity, body, recovery, photo, social, and feature records to hosting, database, storage, authentication, and security processors;
the selected AI input and the limited context described in Section 1 to OpenAI or Anthropic when the consumer invokes AI logging, PlateStack Coach, a generated summary, or editable meal or workout plan drafting;
food search terms, barcodes, recipe URLs, and related request information to food, barcode, nutrition, and recipe sources used for the requested lookup;
health-feature notification content and delivery identifiers to push or email providers when the consumer enables or requests the communication;
purchase or entitlement information associated with a health feature to app-store and subscription processors; and
user-selected profile, workout, activity, score, or message information to another user when the consumer intentionally uses a sharing or social feature.

5. Processors, third parties, and affiliates

Categories of processors or third parties that may receive the consumer health data described above are:

Cloud, database, authentication, storage, and security: Supabase, Amazon Web Services, and Cloudflare.
User-requested AI processing: OpenAI and Anthropic for food and label analysis, transcription, natural-language logging, PlateStack Coach, grounded workout or progress summaries, and editable meal or workout plan drafting. The provider receives only the selected input and bounded context described in Section 1 for the result the consumer requests.
Food, barcode, nutrient, and recipe retrieval: FatSecret, USDA FoodData Central, Open Food Facts, the public recipe website selected by the consumer, and a functionally equivalent replacement disclosed before materially new processing.
Subscriptions, purchases, and platform services: RevenueCat, Apple, and Google.
Notifications and email: Expo and Resend or a functionally equivalent delivery provider.
Consumer-selected recipients: another StackForge user with whom the consumer intentionally shares data.
Legal or transaction recipients: a government authority or other recipient when required by valid law, or a successor in a qualifying business transaction that assumes the obligations of this policy.

StackForge Studios currently has no affiliates with which it shares consumer health data.

6. Your consumer health data rights

Subject to applicable law, a consumer may:

confirm whether we collect, share, or sell consumer health data;
access that data and obtain a list of the third parties or affiliates with which it was shared;
withdraw consent from future collection or sharing;
request deletion from our network, including notice to processors and other recipients; and
appeal a refusal to act on a request.

Submit a request at any time to hello@stackforgestudios.com with the subject "Consumer Health Data Request." You may also use an existing in-app account-deletion control. We will use commercially reasonable methods to authenticate the request and may ask only for information reasonably needed to do so. You do not need to create a new account.

We respond without undue delay and, where Washington law applies, within 45 days. We may extend once by 45 days when reasonably necessary and will explain the extension. Qualifying requests are free up to twice each year. Health data in archived or backup systems will be deleted within the period required by law and, under Washington law, no later than six months after authentication.

If we refuse a request, reply with the subject "Consumer Health Data Appeal." We will respond to a qualifying appeal in writing within 45 days. If the appeal is denied, Washington consumers may submit a complaint to the Washington State Attorney General.