Privacy policy
Last updated: 28 October 2026 (draft)
1. Who we are
SeatGuard ("SeatGuard", "the app") is an app for monday.com published by Gautam Krishnan, trading as DashApps ("we", "us"). Contact: support@dashapps.net.
This policy covers the SeatGuard app inside monday.com and this website (seatguard.dashapps.net).
2. In short
- SeatGuard runs only on monday code, monday.com's own app hosting. It has no other backend, database or third-party service.
- It reads your monday account's users, boards, teams and workspaces to build its reports. It stores identifiers, counts and board titles, not people's names or email addresses, with one exception: the audit trail (section 4).
- Names and emails that are stored are kept in monday code secure storage, which monday encrypts at rest.
- When SeatGuard is uninstalled, all of the account's data is deleted automatically. This happens as soon as monday tells us about the uninstall, and in any case within 10 days.
- SeatGuard sets no cookies and uses no tracking or analytics.
3. What SeatGuard reads from monday
When an admin connects SeatGuard, monday asks them to approve the permissions ("scopes") below. SeatGuard asks for nothing else.
| Permission | What SeatGuard uses it for |
|---|---|
Read your profile (me:read) | Show who is signed in; check that the person who connected SeatGuard is an admin of the same account, and stop scheduled work if they stop being an admin. |
Read the account (account:read) | Seat counts and the account's plan, for the seat headroom figures and the free-plan limit. |
Read users (users:read) | Guests, members and viewers with their type, status, last activity and how they were invited; who is on each board under review; names and emails at the moment a decision is recorded (section 4). |
Read boards (boards:read) | Shareable boards and docs, their owners and subscribers, whether they are open to everyone at the account, who owns a board right now, and when a board last had activity. |
Read teams (teams:read) | Expand team-based access and team owners. |
Read workspaces (workspaces:read) | Workspace names in tables and in the "selected workspaces" option of a review campaign. |
Change boards (boards:write) | Remove a person's access to a board after an admin confirms or a board owner submits a review (and undo it); add the "Access review" tab to boards in a campaign; archive stale boards after confirmation. |
Change users (users:write) | Deactivate removed guests, and apply seat-recovery suggestions (change a member to a viewer, or deactivate), always after an admin confirms the named people, with undo. |
Send notifications (notifications:write) | Tell board owners in monday that a review is waiting, send reminders, escalate overdue boards to the admin, and give archive notices. The text names boards and campaigns, never the people being reviewed. |
The SeatGuard screens inside monday also ask monday for people's names and email addresses (for example to show a guest's name in a table). This happens in your browser, only for display. It is not sent to our backend and not stored.
4. What SeatGuard stores, and where
Everything is stored on monday code, in the app's database ("Document DB") or in its encrypted secure storage. Each record belongs to one monday account and is only ever read for that account.
| Data | Where |
|---|---|
| Account snapshot from the latest scan. User ids, types, status, last activity and invitation method; team ids, names and member ids; board ids, titles, kinds, workspace ids and names, last-updated times, owner and subscriber ids; seat counts and plan; for stale-board checks, a board's item count and the time of its newest activity entry (not its content). Each scan replaces the previous one. No names or emails of people. | Document DB |
| Settings. Thresholds, schedule, notification preferences and the renewal date an admin enters. | Document DB |
| Actions and reviews. Bulk actions (user and board ids and the outcome of each step, kept so they can be undone), review campaigns and each board's review (ids, board and campaign titles, owners' keep/revoke decisions by user id, outcomes), and stale-board archive requests (board ids and titles, owner ids). | Document DB |
| Audit trail. One entry per action SeatGuard takes and per decision an owner makes: time, who (user id and role), what, which board or person (ids), before and after, outcome. Entries are linked with a hash chain so edits or deletions can be detected. No names or emails in this record. | Document DB (head of the chain also in secure storage) |
| Names and emails at the time of a decision. When an audit entry involves people, SeatGuard saves their name and email as they were at that moment, so the evidence stays readable if the person is later deleted from monday. They appear in the audit screen and in CSV and PDF exports. | Secure storage only |
| Who installed and connected SeatGuard. The installer's user id and name, and the OAuth connection: access token, refresh token (where monday issues one), granted scopes and the authorizing admin's id and name. The installer's email address arrives from monday and is discarded. | Secure storage (the connection's status and a short-lived sign-in check value are in Document DB, with no token) |
| Subscription details. Account id, plan tier, number of seats and subscription terms, as sent by monday. | Document DB |
SeatGuard does not store your boards' or docs' content, items, updates or files.
5. Where data is processed, and who else is involved
All SeatGuard processing takes place on monday code, hosted by monday.com. monday.com is the only sub-processor involved in the app: it provides the hosting, database, secure storage, logging, the scheduler that runs an hourly job, sign-in (OAuth), the API we read from, and the app lifecycle notices (install, uninstall, subscription). SeatGuard makes no calls to any other domain, and its screens load no third-party scripts, fonts or analytics.
The website at seatguard.dashapps.net is hosted on Cloudflare Pages. It processes ordinary web-server data (such as visitors' IP addresses) to deliver pages. We do not use cookies, analytics or any third-party script on the website. Mail sent to support@dashapps.net is handled by DashApps' email provider.
6. How long we keep data
| Data | Kept |
|---|---|
| Account snapshot, settings, bulk actions, campaigns and reviews, archive requests, subscription details, installer and OAuth connection | Until the app is uninstalled (each scan replaces the previous snapshot, so no history builds up). The connection is replaced when another admin reconnects. |
| Audit trail and the names and emails saved with it | 12 months. An hourly job deletes older entries and any saved names no remaining entry uses. Everything is deleted on uninstall. |
| Application logs | Held by monday code. monday does not publish how long it retains these logs. We keep no copy. |
What is logged
The app's logs record event names with ids and counts, for example "scan completed" with a count of users and boards, or an error id. They never contain names, email addresses, session tokens, OAuth tokens or codes, webhook contents, request bodies or secrets.
7. Deletion when you uninstall
When SeatGuard is uninstalled, monday sends the app an "uninstall" notice. The app then permanently deletes everything it holds for that account, in the same request: every record in the database, the OAuth connection, the installer details, the audit chain anchor and every saved name and email. This normally takes seconds, and in any case is done within 10 days of the uninstall. We do not keep data longer unless you give us your express written consent.
Data already written by SeatGuard to your monday account (for example a board owner's removal from a board, or a notification) is part of your monday account and is not touched by the uninstall.
8. Security
- All traffic uses HTTPS.
- Every request from the app's screens to our backend carries a session token issued by monday and verified on the server. The account is taken only from that verified token (or a signed monday notice), never from anything the browser sends.
- Admin-only functions refuse non-admins, and board owners can only act on boards they currently own, which is checked live.
- OAuth tokens and saved names and emails are kept in monday code secure storage, encrypted at rest by monday, and are never logged or sent to the browser.
- The app's screens can be embedded only by monday.
9. Cookies, tracking and email
SeatGuard sets no cookies. This website sets no cookies and has no analytics, advertising or tracking. If you email support@dashapps.net we use your message and email address only to reply and to look after your request.
10. Your rights
You may ask us to tell you what personal data SeatGuard holds about you, to correct it, or to delete it, and you may object to our use of it, subject to applicable law. Write to support@dashapps.net. We will answer within a reasonable time.
SeatGuard works on behalf of your organisation's monday account. If you are a guest, owner or member whose data appears in SeatGuard, your organisation's account admin decides how the app is used, so you may also need to contact them.
11. Changes
If we change this policy we will update the date above and describe material changes at the top of this page before they take effect.
12. Contact
Gautam Krishnan, trading as DashApps
support@dashapps.net