The fastest way to reach us is email: support@byldcode.com. Include your account email and a short description of what you saw. Screenshots help. We typically respond within 72 hours.

Two ways, same result — all your data is permanently removed.

From the App (recommended)

1. Open Nutrition Assist.
2. Tap the Profile tab.
3. Scroll to the Legal section and tap Delete Account.
4. Type DELETE to confirm.
5. Your account and all associated data — profile, meals, water logs — are deleted from our DynamoDB tables within 30 days. Your Clerk user record is deleted immediately. Backups age out of the 35-day retention window on their own.

The in-app Delete Account flow ships in the next App Store release. If you're on an earlier build, use the email method below.

By email

1. Email support@byldcode.com from the address on your account.
2. Subject: “Delete my account.”
3. We'll confirm receipt and complete the deletion within 72 hours.

Why are the macros off?

AI estimation from text or photo is imprecise by nature — on average 30–50% off, and worst on large portions or mixed plates. If you have the packaging, trust that. Use the App's estimates to see weekly trends, not to hit exact daily numbers.

Does the App store my meal photos?

No. Photos are sent to Anthropic Claude for analysis and discarded immediately after — they never land in a database or on an S3 bucket. See the Privacy Policy for details.

Can I edit a meal entry after logging?

Not yet. For now, tap the entry on the Today tab and use Delete entry to remove it, then re-log. Inline editing is on the roadmap.

Why did the App show a “Welcome” screen when I signed back in?

A returning user whose session has expired used to see Clerk's default sign-up screen for a moment before the App recognized their existing account. Recent versions replace that with a “Welcome back” screen that routes you directly to sign-in. Your data is always safe on our backend — the screen never reflected anything being deleted or reset.

I tapped the water + button but nothing happened.

If you're on an old build, upgrade to the latest App Store version — this was a server-side bug we fixed in the build that launched on the App Store. If it's still happening on the latest version, email us with the time and your account email and we'll investigate.

See the Privacy Policy for what we collect and how we use it, and the Terms of Use for the rules of the road.