Security & Privacy

Built to watch your network,
not to take it.

WatchMyTech runs on your own machine and never sees the contents of your network traffic, and it requires two-factor authentication for every sensitive action. Here's exactly what leaves your machine and what doesn't — no vague reassurances.

Data handling

What leaves your network — and what doesn't

WatchMyTech is local-first: the app runs entirely on the Windows PC you install it on. To make alerting and the remote portal work, it sends a defined set of data — device status, latency, Active Directory account-change events, and temperature sensor readings — but never the contents of your network traffic, your IP addresses, or any credentials.

Leaves your machine

  • Up/down status for each monitored device
  • Latency (round-trip time) figures
  • A heartbeat confirming the app itself is running
  • The name or label you give each monitored device
  • Active Directory account-change events — a user created or deactivated, with their name and a timestamp
  • Temperature sensor readings, and the sensor labels (from the SensorPush API)

Never leaves your machine

  • The contents of your network traffic or packet data
  • IP addresses
  • Passwords or credentials
How it's protected

Three principles

🔑

Two-factor everywhere

TOTP two-factor authentication is enforced at every layer — local app access, system login, and the external portal each require a code. Configuration can only be changed at the PC hosting WatchMyTech.

➡️

Outbound-only by design

Communication is passive and one-way. WatchMyTech opens no inbound listener and accepts no remote commands, so it can't be used as a route into your network.

💻

Local-first

Monitoring happens on your own machine. If the connection to our servers drops, local monitoring keeps running — you don't lose visibility of your own network.

Telemetry, in detail

The specifics

For anyone assessing WatchMyTech for a client or an internal approval, here's the precise behaviour.

Telemetry interval
Status is reported to WatchMyTech's servers every 30 seconds.
Heartbeat
A 10-second heartbeat confirms the app is alive and reporting.
Payload
Per monitored device: an up/down flag, a latency value, and the device label. Active Directory account-change events and temperature sensor readings are also sent. No network traffic, packet contents, IP addresses, or credentials are included.
Direction
Outbound only. No inbound connections are accepted.
Encryption in transit
All telemetry is transmitted over HTTPS (TLS).
Authentication
TOTP two-factor required for app access, system login, and the external portal.
Devices per instance
Up to 30. Run a separate instance per client for independent, isolated monitoring.
Storage & operator

Where your data lives

The data held off your machine — device status and latency, Active Directory account-change events, and sensor readings — is stored by the company behind WatchMyTech.

Operated by
RECCEIT LTD, a company registered in England & Wales (No. 13400175).
Hosting location
United Kingdom. WatchMyTech's servers are hosted in a UK data centre.
Retention
Status and latency telemetry is kept for one week, then deleted.
Everything held off-site is limited to what is listed above: device status and latency, the labels you give your devices, Active Directory account-change events and sensor readings. Your network traffic, IP addresses and credentials are never collected or stored.
Questions about data handling for a compliance or procurement review? Email hello@watchmytech.com and we'll answer directly.
Responsible disclosure

Found a security issue?

If you believe you've found a vulnerability in WatchMyTech, please report it privately so we can fix it before it's made public. Email hello@watchmytech.com with the details and steps to reproduce. We'll acknowledge your report and keep you updated on the fix.

Start your free trial

Last updated: November 2026