Privacy and Google data use

Data collected

Your verified Google email and account identifier, encrypted OAuth tokens, granted scopes, project titles and optional Script IDs, function names, execution types, statuses, timestamps and duration. TriggerOps also stores your aliases, monitoring preferences, incident history, verified Telegram chat ID and SDK key hashes.

What Google permissions allow

Requested scopes are openid, email and https://www.googleapis.com/auth/script.processes. No Drive scope is requested. TriggerOps does not read Gmail messages, Sheet cells, Drive file contents, Calendar events or script source code. Google projects and triggers are not modified or deleted.

Use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. Google user data is not sold, used for advertising, or used to train general-purpose AI models.

Purpose and service providers

Data supports project discovery, monitoring, incident resolution and alerts. The application runs on Vercel and stores data in the configured Upstash Redis service. When you connect Telegram, incident summaries containing project and function names are sent to your verified private chat through Telegram. Provider locations and backup retention require operator confirmation before public launch.

Retention

The visible execution history is limited to 30 days and 5,000 records per workspace. Sync and scheduled maintenance prune stored execution history and resolved incidents older than 30 days. Scheduler outages delay physical pruning. Project and job summaries, monitoring preferences and active incidents remain while your account exists. Anonymous aggregate product counters contain no script or file contents.

Session records expire after 14 days. OAuth state expires after 10 minutes. A Telegram pairing link expires after 15 minutes. Short-lived request counters prevent abuse.

Account controls

Settings provides reconnect, Google disconnect, SDK key revocation and account deletion. Disconnect removes stored Google tokens and requests revocation. If Google revocation is unavailable, remove access through your Google Account permissions as well. Account deletion removes the active TriggerOps workspace, connection and sessions. Google Apps Script projects remain untouched. Provider backup deletion schedules are not yet represented as an instant deletion guarantee.

Product analytics

TriggerOps records aggregate sign-in intent and per-workspace setup milestones, sync completion, projects discovered, monitoring started, first alert connection, incident occurrence, seven-day return and plan interest. No session replay, advertising tracking, script source or Workspace file contents are collected.

Questions or deletion support

Use the self-service controls in Settings or the private-beta support page. Support contact details and provider retention confirmations must be finalized before a public commercial launch.