Let's Talk Macros

Privacy Policy

Effective October 25, 2026


In short

  • Let's Talk Macros stores the food, exercise, and weight data you log so it can show you your own history and totals. Nothing more.
  • You sign in with Apple or Google to use the app. Your data is tied to your account and kept separate from every other user's. We don't see your password either way.
  • Talking to the app happens on your device: "Let's Talk" turns your speech into text on the phone itself, and no audio leaves it. One smaller microphone, used to fill in an amount on the manual log screens, still sends a short clip to OpenAI for transcription and then discards it.
  • Barcode scanning happens entirely on your device. No photo or camera image is ever captured, stored, or sent anywhere. Only the barcode number is used.
  • The text of what you log is sent to an AI service so the app can understand and act on it. Currently that's Google's Gemini and Z.ai's GLM models, reached through OpenRouter, with Anthropic's Claude as the backup. Nutrition lookups for a specific branded or restaurant food go to Edamam. Section 8 lists every service and what it receives.
  • If you turn on the optional Apple Health connection, some health data is read directly from your device and shown in the app. Section 7 explains exactly what's read, what's written, and what is never sent to our servers.
  • We don't sell your data, run ads, or use tracking or analytics services.
  • This app is still in early testing with a small group of people. Section 10 explains what that means today.
  1. 1About this app
  2. 2Information you provide
  3. 3Account & sign-in
  4. 4Information collected automatically
  5. 5Voice recordings
  6. 6Camera & barcode scanning
  7. 7Apple Health
  8. 8Third-party services
  9. 9How we use your information
  10. 10Data storage & security
  11. 11Retention & deletion
  12. 12Children's privacy
  13. 13Your choices
  14. 14Changes to this policy
  15. 15Contact

1About this app

Let's Talk Macros is a food and workout tracking app built and operated by Peach Haze Studio LLC, an independent developer. This policy explains what information the app collects when you use it, why, and what happens to it. It applies to the Let's Talk Macros mobile app and its backend service.

2Information you provide

Using the app means logging things about yourself, by design. That includes:

3Account & sign-in

You need to sign in to use Let's Talk Macros, using either Sign in with Apple or Sign in with Google. We use Clerk, a third-party authentication provider, to handle this. We never see or store a password, and we don't offer our own email/password sign-in.

Depending on which method you choose, Clerk may receive your name and email address from Apple or Google to set up your session. On our side, we store only the account identifier Clerk gives us, and every piece of data described in Section 2 is tied to that identifier. This is what keeps your logs, foods, weight, and conversations separate from every other person using the app. Governed by Clerk's privacy policy.

4Information collected automatically

We don't use analytics, advertising, or tracking services of any kind. Our hosting provider (Railway) automatically logs standard technical information common to any web service, such as IP address, request timestamps, and error logs, as part of running the server. This is used only to operate and troubleshoot the service, never to build a profile of you.

5Voice recordings

There are two separate places you can speak to the app, and they work differently:

This changed in September 2026. The main voice feature used to send its audio to OpenAI too. It no longer does, and now runs entirely on your device.

6Camera & barcode scanning

The app's barcode scanner uses your device's camera to read a barcode on your device. No photo, video, or camera image is ever captured, stored, or transmitted. The app only reads the barcode number itself, which is then looked up against our food database and, if needed, the public Open Food Facts database (see Section 8).

7Apple Health

If you turn on the optional Apple Health connection (Settings → Apple Health), the app can read your step count, floors climbed, walking and running distance, active energy burned, heart rate, and body weight from Apple's Health app on your device, and can write your logged body weight back to Health. A dedicated screen explains exactly what's read and written before iOS's own permission prompt ever appears, and you can turn access off at any time in iOS Settings → Privacy & Security → Health.

Steps, floors climbed, distance, active energy, and heart rate are read live from your device each time the app shows them. They are never sent to or stored on our servers. Body weight works differently. If you choose to import a weight you already have in Health (for example, from a smart scale), it's saved to our backend the same way as any weight you type in yourself (Section 2). Any weight you log in the app is, in turn, written to your device's Health app. Weight is the only Health data type this app ever writes.

8Third-party services

To provide its features, the app sends specific, limited information to these services:

OpenRouter, and through it, Google and Z.ai

Receives the text of your conversational logging requests so an AI model can understand and act on them, for example matching "my usual eggs" to a food already in your library. OpenRouter is a routing service: it passes the request on to the model actually handling it, which today is Google's Gemini for the first message of a conversation and Z.ai's GLM for follow-up messages. Where a model is open-weight and several companies host it, our routing preferences deliberately steer away from the model developer's own servers. Which model handles a given message can change as the app is tuned, and this section will be updated when it does. Governed by OpenRouter's privacy policy, together with the privacy policy of whichever provider serves the request.

Anthropic (Claude API)

The backup for the above. If the OpenRouter request fails, the same text is sent to Anthropic's Claude instead, so a logging attempt never simply fails. Claude also handles the short "work out the amount" parse behind the microphone on the manual Log Food / Log Recipe screens. Governed by Anthropic's privacy policy.

OpenAI (Whisper API)

Receives a short voice recording only from the microphone on the manual Log Food / Log Recipe screens, and only to transcribe it to text, as described in Section 5. The main "Let's Talk" voice feature does not use it. That feature runs on your device. Governed by OpenAI's privacy policy.

Edamam

When you ask to log a specific branded or restaurant food we don't already have (like "a slice of Pizza Hut pepperoni pizza"), the food's name is sent to Edamam's food database to find a nutrition match. The result is saved to our shared food library so the same lookup isn't repeated. Governed by Edamam's privacy policy.

Open Food Facts

When a scanned barcode isn't already in our own food library, we look it up against this free, open product database by barcode number only. Governed by Open Food Facts' privacy policy.

Clerk

Handles Sign in with Apple/Google and issues your account session, as described in Section 3. Governed by Clerk's privacy policy.

Railway

Our hosting provider. It stores the app's database and runs its backend server. Governed by Railway's privacy policy.

We don't share your information with anyone else, and we don't sell it to anyone, ever.

9How we use your information

We do not use your information for advertising, and we do not build any profile of you beyond what the app itself shows you.

10Data storage & security

Your data is stored in a database on our hosting provider's infrastructure (Railway) and transmitted using HTTPS encryption in transit. Every request to our backend must come from a signed-in account (Section 3), and every query is scoped to that account. Another person using this app cannot see your logs, foods, weight, or conversations, and you cannot see theirs.

Let's Talk Macros is still in early testing with a small group of people and is operated by a single independent developer. Treat it as a beta: back up anything you can't afford to lose, and expect bugs to get found and fixed as testing continues.

11Retention & deletion

We keep your data for as long as your use of the app is active. Deleting a food, log entry, or recipe within the app removes it permanently. Logged history is never silently altered when you edit the underlying food later (that's how the app's snapshot accuracy works). To request deletion of your account and data entirely, contact us at the email below and we'll remove it.

12Children's privacy

Let's Talk Macros is not directed at children, and we do not knowingly collect information from anyone under 13. If you believe a child has provided us information, contact us and we'll delete it.

13Your choices

14Changes to this policy

If this policy changes in a meaningful way, we'll update the effective date above. We'd encourage checking back here occasionally, especially while the app is in active early development.

15Contact

Questions about this policy, or a request to see or delete your data? Reach Peach Haze Studio LLC at support@peachhazestudio.com.