How the streak counts

The streak number on your TrakMac dashboard is the count of consecutive days where you've logged at least 1,000 calories of food. The current day counts as long as your daily total is over 1,000 calories at the time you check. Yesterday counts if it ended over 1,000.

A few specifics:

  • The cutoff is midnight in your device's local time zone. A day that ends at 11:58 PM with 950 calories logged does not count, even if you eat something after midnight that would have pushed the previous day over the line.
  • Logging a meal counts on the day you ate it, not the day you logged it. If you forget to log lunch and remember at 9 PM, the lunch goes on the right day.
  • The streak number on your dashboard updates in real time as you log throughout the day. You don't have to wait until tomorrow for today's contribution.

Why 1,000 calories

The threshold exists for a specific reason: it stops the streak from being a participation trophy. Most adults' resting metabolic rate is around 1,400-1,800 calories. Eating less than 1,000 calories in a day is either a fast, an illness, an extreme deficit you should not be sustaining, or a day you forgot to log meals.

None of those are days where the streak should keep ticking. A streak that counts "opened the app" instead of "actually tracked your day" stops meaning anything within a week. The 1,000-calorie floor is the lowest reasonable bar for "this was a real tracked day."

It also catches a real failure mode: people who track breakfast and lunch but skip dinner. The streak quietly drops them to a sub-1,000 day, the day doesn't count, and the trend is preserved honestly.

When the streak resets

The streak resets to zero when:

  • You go a full day without logging anything (any 24-hour period from midnight to midnight in your local time zone with zero meals).
  • You log meals but the daily total comes in under 1,000 calories.

The reset happens at the next midnight after the qualifying-day failure. If you have a 28-day streak and miss Tuesday, your dashboard will show 28 through Tuesday night. On Wednesday, the streak shows 0. If Wednesday ends over 1,000 calories logged, Thursday starts a new streak at 1.

There is no streak freeze, no streak recovery purchase, no "I was traveling, give me back my streak" support ticket. The streak is the number it is. Reviving it would defeat the point of having one.

Why we don't offer streak freezes

A few reasons the obvious add-on isn't built:

  • Streaks that can be paused are vanity counters. The whole psychological function of a streak is the asymmetric stakes — building takes work, losing it stings. Removing the sting flattens the motivation curve.
  • Streak protection becomes a paid product trap. Apps that monetize streak preservation end up training users to value the number more than the underlying behavior. We'd rather you skip a day, restart the streak, and stay focused on the actual goal (consistent tracking) than pay us to lie to you about your consistency.
  • The reset isn't a punishment. Restarting at zero isn't the app calling you a failure. It's the app saying yesterday wasn't a tracked day, which is true.

What the streak actually predicts

Long-term tracking data shows that users with streaks above 30 days log meals roughly 4-5x as often as users without active streaks. Streak length is the single best predictor of whether someone will still be using the app in 6 months.

The behavior loop runs both directions: people who care about the streak log more, and people who log more care more about the streak. Both halves are useful. The streak is mostly a way to externalize the daily decision to log so it doesn't have to be a fresh act of willpower every morning.

If you're new and finding it hard to log every day, the goal isn't a 1,000-day streak. It's getting to a 7-day streak, then a 14, then a 30. After about 30 days, daily logging stops feeling like a decision and starts feeling like a habit.

Edge cases worth knowing

International travel and time zones. The streak uses your device's current time zone for the midnight cutoff. If you fly across time zones, the day boundaries shift accordingly. This usually works fine. Occasionally a long-haul flight with multiple time zone changes can give you a 23-hour or 25-hour day, which works in your favor or against you depending on direction.

Daylight saving time. Same logic — the cutoff is whatever midnight your device says. The hour shift is invisible to the streak.

Devices and accounts. The streak lives on your account, not on a specific device. Logging on a new iPhone preserves the streak. Logging on a friend's phone while signed into your account counts. The streak tracks you, not the device.

Subscription gaps. If you let your subscription lapse and come back later, the streak resets when you stop logging — not when the subscription expires. The subscription doesn't gate the streak; logging does.

How to actually keep one going

A few practical things that help streaks survive:

  • Log breakfast as soon as you finish eating, not later. The single largest cause of streak failure is forgetting to log earlier meals and running out of mental energy to do it at the end of the day.
  • Use voice logging for low-effort days. Tapping through a database is high-friction. Saying "yogurt with berries and granola" is 3 seconds.
  • Default to logging a placeholder when in doubt. Even a rough estimate counts. A 950-calorie day that should have been 1,200 because you forgot a snack still counts as a sub-1,000 fail. A logged 1,200 with imperfect numbers counts as a streak day.
  • Don't try to chase the streak by overlogging. If you didn't eat 1,000 calories, log what you ate. Inventing food to clear the threshold corrupts your own data and makes the dashboard useless to you. The streak resetting is fine. Lying to your tracker is not.

The streak is a tool, not the goal. The goal is the body composition outcome the tracking is producing. The streak just helps the tracking actually happen.