Teambridg's Transparency Pledge: What We Track, What We Don't, and Why

Why We're Publishing This

In an industry where most vendors bury data collection practices in 40-page privacy policies, we're doing something different. This is a complete, plain-language disclosure of everything Teambridg monitors.

We're publishing this because the monitoring industry's trust problem starts with opacity. As Marcus wrote in his 2022 privacy outlook, 56% of monitored employees experience surveillance anxiety. We can't fix that industry-wide, but we can be unambiguous about our own practices.

What Teambridg Monitors

The exhaustive list:

• Active application categories — We detect which category is in the foreground ("Communication," "Development," "Browser - Work"). We categorize, not log. No window titles, URLs, or content.
• Focus time blocks — Periods of sustained work in a single category without switching. Duration and category only.
• Work session boundaries — Start, end, and break periods. This supports data minimization by only processing data during active hours.
• Meeting time — Duration of calls via calendar integration and app category. No meeting content, attendees, or recordings.
• Project time allocation — Via project management integrations (Jira, Asana). Opt-in, metadata-based.

Five categories of data, all focused on work patterns rather than content.

What Teambridg Will Never Monitor

These aren't just things we don't currently do — they're architecturally excluded:

• Screenshots or screen recordings — No screen capture capability exists in our codebase.
• Keystrokes or typing patterns — Zero keystroke data captured.
• Webcam or microphone — Our agent doesn't request these permissions.
• Email, chat, or message content — Never read, scanned, or analyzed.
• Specific URLs — We know you're using a browser. We don't know which sites.
• Personal device activity — Only operates on managed devices with explicit installation.
• Location or GPS — Never tracked.
• Off-hours activity — Our agent respects configured work hours.

Who Sees the Data

Access follows strict least-privilege:

Individual employees see their own work patterns — everything their manager sees about them.

Direct managers see aggregated team patterns and individual data for direct reports only.

Department heads see department aggregations. Individual data only for direct reports.

Organization admins see org-wide trends. Individual access requires documented justification, logged and auditable.

No one at Teambridg has standing access to customer employee data. Support access requires customer authorization, is time-limited, and is fully auditable.

How This Pledge Evolves

A static pledge doesn't build lasting trust. Here's how we stay accountable:

• Quarterly transparency reports starting Q2 2022, detailing any changes to data practices.
• Customer advisory board focused on privacy, with advance notice of proposed changes.
• Independent audits — pursuing SOC 2 Type II certification.
• Open architecture documentation — our agent's capability boundaries are public.

Trust isn't a feature you ship once. It's a practice you maintain every day.