Document T · Notes for IT departments Riga Computing Company

DOC. T · REV. 1

Notes for IT departments.

An employee asked to run a small companion app on a work computer, and now you are reading this. Fair. Here is the complete picture: what runs, what leaves the machine, and what never does. It is a short read because there is genuinely little to disclose.

T·1Footprint

What runs.

A per-user status reporter. No services, no drivers, no admin rights, no integration with your tenant.

1.1 · MACOS

A sandboxed menu bar app

Distributed via TestFlight / the App Store, so it is sandboxed and notarized by construction. Entitlements: App Sandbox plus outgoing network. It never appears in the Dock.
1.2 · WINDOWS

A per-user tray app

Runs entirely in the user's session; installs to the user profile. No admin rights at any point, nothing machine-wide, no scheduled tasks.
1.3 · AUTOSTART

Ordinary, inspectable

macOS uses a login item. Windows uses the per-user HKCU Run key. Both are visible in the standard system UI and trivially removable.
T·2Detection

How detection works.

The companion answers one question: is any process currently capturing from the microphone? It reads the same indicators the operating system already shows the user.

2.1 · MACOS

CoreAudio, read-only

It reads the system-wide "is any process capturing input" flag. This requires no microphone entitlement and triggers no permission prompt, because the app never accesses audio. It cannot hear anything; it can only see that the light is on.
2.2 · WINDOWS

Registry, read-only

It reads the ConsentStore registry keys, the same data behind the microphone indicator in the system tray. No hooks, no audio APIs, no process inspection beyond that.
2.3 · SCOPE

Nothing app-specific

There is no Teams, Zoom, or Slack integration and no tenant involvement. The signal is app-agnostic by design, which is also why no employer approval or configuration is needed.
T·3Network

What leaves the machine.

Outgoing HTTPS to our API, authenticated with a per-device token. The entire payload, forever:

POST /v2/status
{ "status": "call" }  or  { "status": "free" }
plus a server-side timestamp. No app names, no meeting titles,
no participants, no audio, no calendar, no address book.
3.1 · INBOUND

None

The companion opens no listening ports and accepts no inbound connections. It polls; nothing calls it.
3.2 · REVOCATION

Per-device kill switch

Each device holds its own revocable token. When the user revokes a device from their phone, the reporter sees the rejected token and permanently stops itself.
3.3 · DATA PROTECTION

Minimal by construction

One boolean and a timestamp is the whole dataset, which keeps the GDPR story short. The service is operated from the EU (Latvia and Germany).
3.4 · UNINSTALL

Clean exit

macOS: quit and delete the app. Windows: the provided uninstaller removes the app, its config, and the Run key. No residue that requires admin rights to clean.

Questions, or a security review you would like us to walk through: hello@computing.lv