🕐 App Security Part 1 of 2

How Your Work Apps
Quietly Reveal Where You Are

Slack, Teams, Zoom, and others are collecting timezone data in ways most people don't realize — and some of it you can control, some of it you can't. Here's the honest breakdown.

⏱ 8 min read
🎯 No technical background needed
📱 Covers 6 major apps
Series:
Part 1 — How apps leak your timezone Part 2 — The location bubble
Most people think about their IP address when they think about hiding their location. But your work apps are having a completely separate conversation about where you are — through timezone data, activity timestamps, and presence signals. This guide explains exactly what they're sending, where it goes, and what you can actually change.
The most important thing to understand first

Display Timezone vs. Metadata Timezone — These Are Two Different Things

Before we get into individual apps, you need to know something that almost nobody talks about. In every work app, "timezone" means two completely different things at the same time.

🎭
Think of it like this
A clock on the wall vs. a postmark on a letter
You can change what a clock on the wall says — that's display timezone. But the postmark on a letter is stamped by the post office, not by you. It records when and where the letter actually entered the mail system. App settings change the clock on the wall. The postmark is controlled by the server — and the server knows your IP address.
The two kinds of timezone data
✓ Display Timezone
What timestamps look like on your screen. When you change your timezone in Slack settings, this is what changes. It affects how times render for you — and sometimes how your status shows to others. You control this.
✗ Metadata Timezone
What gets written into server logs, audit trails, and compliance records. This is determined by the server receiving your request — using your IP address to infer your location. You do not control this from within the app. You control it at the network layer.

This distinction matters because most guides to "hiding your timezone in Slack" are only talking about display timezone. They're changing the clock on the wall. The postmark — the metadata — still says wherever your IP puts you. The only way to change the postmark is to change your IP. Which we cover in Part 2.

Where the data comes from

The Four Places Apps Get Your Timezone

Every app that shows a timezone is pulling that data from one or more of four sources. Understanding which source each app uses tells you how much control you actually have.

Source 1

Your Operating System Timezone

This is the first place every app looks. When Slack, Teams, or Zoom installs on your computer, it reads your OS timezone and uses it as the default. On a Mac this is System Settings → General → Date & Time. On Windows it's Settings → Time & Language → Date & Time.

Most computers are set to automatically update the timezone based on your location. That means the moment you land in Bangkok, your laptop quietly changes to Bangkok Standard Time — and every app that reads the OS timezone now knows you're in Southeast Asia.

User control
High — you can lock this
💡
The fix: Disable automatic timezone on your OS before you travel and manually set it to your home timezone. On Mac: turn off "Set time zone automatically." On Windows: turn off "Set time zone automatically." Do this before your flight, not after.
Source 2

Browser Timezone (for Web Apps)

When you use Slack, Notion, or any work app in a browser tab instead of the desktop app, something slightly different happens. The browser exposes your timezone through a built-in JavaScript feature. Every website can ask your browser "what timezone is this person in?" and the browser answers automatically.

🌐
Simple version
Your browser is always answering a question you didn't know was being asked
Every time a web app loads, it quietly asks your browser for your timezone. The browser answers with whatever your OS is set to. There's no warning, no permission prompt — it just happens. And the answer goes directly to the app's servers.

The good news: browser timezone almost always matches your OS timezone. So if you lock your OS timezone to home, the browser timezone follows automatically. You don't need to do anything extra — just fix the OS setting.

User control
High — flows from OS setting
Source 3

App-Level Profile Settings

Most apps let you manually set a timezone in your account profile or preferences. This is what most "how to hide your timezone" guides talk about. It's real, it's useful, and it affects what other people see — like your active hours in Slack or your calendar availability in Teams.

But remember the clock vs. postmark distinction. This only affects the display layer. The server has already logged your actual timezone from your IP before your profile setting is ever consulted.

User control
High — but display only
Source 4

Network-Inferred Timezone (The One You Can't App-Fix)

This is the invisible one. When your request hits Slack's servers, Microsoft's servers, or Google's servers, the server records your IP address. IP geolocation databases don't just give a city — they give a timezone. So even if your OS says EST and your Slack profile says EST, if your IP is resolving to Bangkok, the server has already inferred Bangkok Standard Time and written it into the activity log.

This metadata exists independently of everything in your settings. It's not visible to you anywhere in the app. But it's there, and it's what feeds into the compliance and security systems we covered in the corporate tracking guide.

User control
Low — requires network-layer fix
⚠️
This is why app settings alone aren't enough. You can set every timezone field in every app to EST. The server still knows your IP is in Thailand. The metadata still says Bangkok. App settings fix the display — only changing your IP at the network layer fixes the metadata.
Per-app breakdown

What Each App Exposes and How to Configure It

Here's exactly where to find the timezone settings in each major work app, what they control, and what they don't.

App Where to set timezone What it controls Hides from IT?
Slack Profile → Edit Profile → scroll to Time Zone Profile → Edit Profile → Time Zone Your active hours display, Do Not Disturb hours, how your status shows to others Display only
Microsoft Teams Settings → General → Language and region Settings → General → Language and region Calendar display, meeting times shown to you. Admin can still see your actual location via Azure AD logs. No — Azure AD logs separately
Zoom Profile → Edit → Time Zone dropdown zoom.us → Profile → Edit → Time Zone Meeting invitation timestamps, your calendar display Display only
Google Workspace Google Calendar → Settings → Time Zone calendar.google.com → Settings → Time Zone All Google products — Calendar, Gmail timestamps, Meet, Drive activity. This is the most important one to change. Display only
Outlook / Microsoft 365 Calendar → File → Options → Calendar → Time Zones File → Options → Calendar → Time Zones Calendar display, meeting invites. Does not affect Exchange server logs. No — Exchange logs separately
Notion / Linear / Jira Settings → Account → Language & Region (varies) Varies by app — look in Account Settings Activity timestamps shown in-app. These tools rarely feed into corporate SIEM systems directly. Lower risk
⚠️
Microsoft is the most important to understand. Teams, Outlook, and Azure Active Directory are all part of the same Microsoft 365 ecosystem. Your login location is recorded in Azure AD independently of any setting you change in Teams or Outlook. If your company uses Microsoft 365 — and most do — your login location is being logged at the identity layer regardless of your profile settings.

The Google Workspace special case

Google Calendar's timezone setting is the single most impactful app-level change you can make — because it propagates everywhere. Your Google Calendar timezone affects: meeting invite timestamps, Gmail "sent at" times, Google Drive activity logs, and Google Meet session records. It's one setting that touches everything.

Set it in Google Calendar → Settings (gear icon) → Time Zone → Primary time zone. Set it to your home timezone and leave it there regardless of where you travel.

Do Not Disturb hours are a location signal too

This one catches people off guard. In Slack, your Do Not Disturb schedule shows other people when you're unavailable. If you set DND from 10 PM to 8 AM — but your colleagues see you online and active at 3 AM their time — that inconsistency is a human flag even if the automated systems don't catch it. Make sure your DND hours are set to home timezone active hours, so your availability looks normal to anyone glancing at your profile.

The honest summary

What App Settings Actually Fix — and What They Don't

Here's the clean version of what changes when you update your app timezone settings:

What changesWhat stays the same
Timestamps displayed on your screen Server-side activity logs with your real IP timezone
Your active hours shown to colleagues Azure AD / Google identity login location records
Meeting times in calendar invites SIEM correlation data
Do Not Disturb schedule display Network-inferred timezone from your IP address
Human-visible location signals Automated system flags and audit trails

App settings matter — but they fix the human-facing signals, not the machine-facing ones. For the automated detection systems to see home timezone, your IP needs to be home. That's a network-layer problem, not an app-layer problem.