How Timezones Affect Your Streaks (And How to Handle Travel)
The timezone problem
You live in Zurich. You fly to New York. Suddenly "today" is 6 hours longer — or did you just skip a day? Timezone-aware habit tracking is harder than it sounds.
How EmberTrack handles timezones
EmberTrack uses your configured timezone as the source of truth for when a day starts and ends. This means:
- Midnight is always midnight in your timezone, regardless of where your phone thinks you are
- Changing your timezone in settings shifts the boundary for "today" — it doesn't retroactively change past check-ins
- All check-ins are stored with timestamps, so the system always knows the real order of events
Traveling? Here's what to do
Short trips (a few days): Don't change anything. Check in based on your home timezone. If you're in New York and it's 11 PM there but 5 AM in Zurich, you might need to check in for "yesterday" — that's fine.
Long stays (weeks+): Update your timezone in Account → Timezone. Your future check-ins will follow the new timezone. Past history stays intact.
Crossing the date line: The trickiest case. If you fly from LA to Tokyo, you might "skip" a day. Use a freeze or check in for the missed day retroactively.
Weekly and monthly habits with timezones
For weekly habits, the week boundary follows your week-start setting — Sunday, Monday, or Saturday, either chosen explicitly or auto-detected from your timezone. For monthly, it's the 1st of the month in your timezone. Changing timezone mid-week won't retroactively change which week a check-in belongs to.
Pro tip: set reminders around your routine, not the clock
Instead of "remind me at 8 PM," think "remind me after dinner" and set the time accordingly. When you travel, adjust the reminder time to match the local equivalent of your routine.
Configure your timezone and reminders in EmberTrack settings.