Privacy
Privacy Policy
Draft for product launch preparation. This policy must receive legal review before broad public launch or paid subscriptions.
Draft policy: This page reflects the current FATChat product architecture and intended data practices. It is not a substitute for legal review.
1. What FATChat is
FATChat is a personal GLP-1 journey companion designed to help users organize medication history, weight, symptoms, hydration, activity, body changes, goals and related personal context.
2. Information you provide
Depending on the features you use, FATChat may process account information, profile preferences, medication and dose history, weight and body measurements, symptoms and check-ins, goals, notes, progress photos, photos you choose to submit to Future You, Family Circle permissions and support requests.
3. Connected health data
If you choose to connect a supported health source, FATChat may receive only the categories you authorize. Connected-source records should retain source provenance so imported data can be identified, reconciled and deleted appropriately. Integrations should not be represented as active until they are actually available.
4. How information is used
Information is used to provide the product, maintain your history, calculate trends, generate user-facing observations, operate sharing controls, protect the service, provide support and improve reliability. FATChat is not designed around selling identifiable personal health data.
5. Analytics
The public marketing website should not send medication, weight, symptoms, health notes or other health values to general marketing analytics. If product analytics are added, their scope and processors should be disclosed here before launch.
6. Authentication and service providers
The application uses third-party service providers for specific functions. The processors currently used in production are:
- Clerk — account authentication and session management.
- Google (Gemini API) — image generation for the optional Future You feature only. See section 7.
No payment processor is in use, because FATChat does not currently charge users. Any additional processor will be listed here with an accurate description before it receives production data.
7. AI features and what leaves FATChat
Insights are not AI-generated. Every insight in FATChat is produced by a fixed, inspectable calculation over your own stored data. No health record is sent to any AI provider to generate them.
Future You is the one feature that sends data outside FATChat. If you choose to use it, the photo you select is transmitted to Google’s Gemini API to generate the illustration. This is the only place in the product where your data leaves FATChat’s own infrastructure, and it never happens automatically:
- It runs only when you actively request an illustration, and only on a photo you have chosen and cropped yourself.
- You must give explicit consent before the first time it is used, and that consent is recorded.
- Image metadata, including EXIF and any location data, is stripped before the photo is transmitted.
- Only the photo and a text instruction describing your goal weight are sent. No name, email, account identifier, medication, symptom or other health record is included.
- The resulting illustration is stored privately in your account and is never published or shared by FATChat.
- Both the source photo and the illustration can be deleted from within the app.
If you never use Future You, no data is sent to any AI provider at any point.
8. Sharing
Health records are intended to be private by default. Family Circles are permission-based. A user’s participation in a family plan or circle does not transfer ownership of that person’s health record to another account holder.
9. Retention, export and deletion
FATChat is being designed with export, archive/soft-delete and permanent-purge paths. Exact retention periods and request procedures must be finalized and documented before general availability.
10. Security
FATChat uses technical and organizational measures appropriate to the stage of the service, but no system can be guaranteed completely secure. See the Security page for the current architecture-level approach.
11. Children
Age eligibility must be finalized in the Terms and onboarding flow before launch. FATChat should not knowingly collect data from users below the approved minimum age.
12. Changes
Material changes to this policy should be versioned and dated. Where appropriate, FATChat should record consent to material new uses rather than treating continued use as blanket consent.
13. Contact
Privacy questions can be submitted through the FATChat contact page. A dedicated privacy email address should be published before broad launch.
Last updated: August 15, 2026.
