Last updated: 27 September 2026
Automation Watchdog ("the app") is operated by Samet Ateşen (Atesen Software) ("we"). This policy explains what the app reads from a monday.com account that installs it, what it keeps, and what it sends.
It watches the rhythm of automations on your boards — how often each one normally acts — and emails the person who installed it when an automation that used to act regularly goes quiet, and again when it starts working. It never changes anything in your account. Every permission it asks for is read-only.
| Permission | Used for |
|---|---|
boards:read | Reading board names and each board's activity log |
users:read | Telling actions taken by people apart from actions taken by automations |
me:read | Finding out who installed the app, so alerts go to them |
account:read | Finding out which account the app was installed into |
It does not read item names, column values, updates, files or documents: the activity log is requested without the field that would carry them.
The board view reads the same activity in your browser, directly from monday.com, to show you the results. That reading does not pass through our server.
When you ask monday's AI assistant, sidekick, which automations have stopped, the app reads the same activity at that moment with a token monday issues for that one request (valid for five minutes), answers with the names of stopped automations and their boards, and keeps nothing: the answer goes back to sidekick and is not stored by the app.
Everything is stored on monday.com's own infrastructure (monday code), not on servers we run.
| What | Where | Kept until |
|---|---|---|
| The account's access token, the installer's email address, the install time | monday code secure storage | Deleted when the app is uninstalled |
| Alert state: a key per watched automation made of the board id, performer id and event type, with timestamps of when it went quiet and when we last told you | monday storage, separated per account | See below |
| A log of recent checks: when each ran, how many automations were watched, how many had stopped, whether an email was sent, and a short error summary if the check failed | monday storage, separated per account | See below |
Alert state and the check log contain ids and timestamps, not names, addresses or tokens. They cannot be deleted by us after an uninstall, because deleting them requires the account's access token and monday revokes that token at uninstall. Whether monday removes them on uninstall is not something we have been able to confirm.
Mutes you set in the board view, and whether you have seen its welcome page, are stored in your browser only.
The app's server writes short operational log lines to monday code's logging: installs and uninstalls with the account id, whether the email provider answered at startup, and check failures with their error text, scrubbed of access tokens and secrets. That error text comes from monday.com or the email provider; a delivery error can include the address it could not deliver to. How long monday code keeps logs is set by monday.com.
Alert emails go to the address of the user who installed the app. They name the board and describe the automation that stopped — for example, "An automation moves an item between groups on Client Projects".
| Who | Why |
|---|---|
| monday.com | The app runs on monday code, monday.com's hosting, and stores everything listed above there |
| Google (Gmail) | Delivers alert emails over SMTP; it processes each email only to deliver it |
Nothing else leaves monday.com. There is no analytics, no tracking cookies, no advertising, and no data is sold or shared. The only cookie the app sets is a short-lived, HttpOnly security cookie used during installation.
Uninstalling the app stops all checks and deletes the stored token and email address. For any question, or to ask what is held about your account, write to support@atesensoftware.com.