# AgentAlerts Privacy Policy

Information Agent Alerts collects, how it is used, and your privacy choices.

## Privacy Policy

ReportKit ("AgentAlerts," "we," "us," or "our") provides an iPhone app, widget extension, command-line tool, and related hosted services that let you send operational updates, agent progress, alarms, and other report events to an iPhone Live Activity surface.

This Privacy Policy explains what information AgentAlerts collects, how we use it, and the choices you have. If you do not agree with this Privacy Policy, do not use ReportKit.

## Information We Collect

### Account information

When you create or sign in to a AgentAlerts account, we collect information needed to authenticate you, such as your email address and authentication identifiers managed through Supabase Auth. We use this information to create your account, keep you signed in, and associate your iPhone app, CLI, widgets, agent tokens, Live Activity sends, and alarms with the correct user.

### Device and notification information

When you use the iPhone app, AgentAlerts may collect device-specific identifiers needed to deliver Live Activities and notifications, including:

- ActivityKit push-to-start tokens
- APNs device tokens
- a AgentAlerts-generated device installation identifier
- APNs environment information, such as sandbox or production
- token sync timestamps and token upload status
- notification, Live Activity, and alarm permission/status information shown in the app

We use this information to register your device, start or update Live Activities, send alarm notifications when requested, retry token uploads, and show token-sync status in the app.

### Report, Live Activity, alarm, and widget content

AgentAlerts processes the report content you or your workflows send through the CLI, hosted agents, or app, including fields such as titles, summaries, statuses, metrics, source names, icons, actions, deep links, builder specs, and other payload data you choose to provide.

AgentAlerts does not decide what external business, analytics, infrastructure, or agent data you put into report payloads. You are responsible for avoiding sensitive personal information, secrets, credentials, private customer data, or regulated data in the payloads you send to AgentAlerts.

### Agent token information

If you create AgentAlerts agent tokens for hosted agents or automation workflows, ReportKit stores the token name, token prefix, token hash, scopes, status, creation time, last-used time, and related metadata. Plaintext agent tokens are shown once when created and are not stored by AgentAlerts after creation.

### Usage and delivery metadata

AgentAlerts stores operational metadata needed to provide and debug the service, including Live Activity event records, idempotency keys, payload hashes, target counts, delivery counts, APNs response metadata, delivery status, daily Live Activity usage counts, entitlement/quota information, and timestamps.

### Local CLI information

The AgentAlerts Swift CLI authenticates with a scoped Agent Alerts token supplied through an environment variable or a private local token file. Running `agentalerts setup` saves the approved pairing token to `~/.config/agent-alerts/token.env`, or the equivalent location under `XDG_CONFIG_HOME`. The file is owned by the current user and uses mode `0600` permissions so only that user can read or write it. The CLI parses the file as data, not as a shell script, and sends the token to AgentAlerts to authorize requests. It does not store a Supabase account session or back up credentials to macOS Keychain.

## How We Use Information

We use the information we collect to:

- authenticate users and keep sessions active
- connect the CLI, iPhone app, widget extension, and hosted edge functions to the same account
- register iPhone Live Activity and APNs tokens
- send, update, or end Live Activities that you request
- send alarm notifications that you request
- manage agent tokens and authorize hosted automation sends
- store and render widget configurations and builder templates
- enforce plan limits, quotas, and abuse-prevention controls
- record delivery outcomes and troubleshoot failed sends
- maintain security, prevent unauthorized access, and protect the service
- respond to support requests and improve product reliability

## What We Do Not Do

AgentAlerts is designed as a narrow operational delivery surface. We do not:

- sell your personal information
- use your report payloads for third-party advertising
- require access to your Slack, email, analytics, App Store Connect, infrastructure, or other source systems
- run a scheduler inside the CLI
- store plaintext AgentAlerts agent tokens after creation
- ask hosted agents to use your Supabase password or Supabase account session credentials

AgentAlerts only receives the payloads and credentials you explicitly configure or send through the app, CLI, hosted edge functions, or your own automation.

## How We Share Information

We share information only as needed to provide AgentAlerts, comply with law, protect rights and safety, or operate the service.

AgentAlerts currently relies on service providers for functions such as authentication, database storage, edge functions, and push delivery. For example, Supabase is used for authentication, database records, and edge functions, and Apple services are used for APNs, notifications, Live Activities, and app platform functionality.

We may disclose information if required by law, legal process, or enforceable governmental request, or if we believe disclosure is necessary to protect the rights, property, or safety of AgentAlerts, our users, or others.

## Data Storage and Security

We use technical and organizational safeguards intended to protect ReportKit data, including account-scoped authorization, row-level access controls where applicable, private local CLI token-file permissions, hashed agent-token storage, and avoiding privileged secrets in the public source repository.

No method of transmission or storage is completely secure. You should protect your account credentials, local CLI token files and token environment variables, cloud-agent secrets, and generated ReportKit agent tokens. Revoke any agent token that may have appeared in logs, prompts, commits, screenshots, or untrusted transcripts.

## Data Retention

We retain account, token, widget, event, delivery, usage, and entitlement records for as long as needed to provide ReportKit, support operational debugging, comply with legal obligations, resolve disputes, and enforce agreements.

Some records are deleted automatically when the related account is deleted because they are associated with the account user identifier. Other operational records may be retained as needed for security, auditability, reliability, or legal compliance.

## Your Choices

Depending on your account status and applicable law, you may have choices or rights to:

- access, correct, or delete certain account information
- sign out of the iPhone app
- revoke ReportKit agent tokens
- remove ReportKit from hosted agent environments
- disable notifications or Live Activities through iOS settings
- remove the local CLI token file and unset CLI token environment variables; revoke the token to disable any remaining copies
- request account deletion or other privacy assistance by contacting us

To make a privacy request, use the contact details below.

## Children

ReportKit is not intended for children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided personal information to ReportKit, contact us so we can take appropriate action.

## International Users

ReportKit may process information in the United States or other countries where we or our service providers operate. These locations may have privacy laws different from those in your jurisdiction.

## Changes to This Policy

We may update this Privacy Policy from time to time. If we make material changes, we will update the effective date and provide notice as required by law. Your continued use of ReportKit after an updated policy becomes effective means you accept the updated policy.

## Contact

For privacy questions or requests, contact:

Andreas Ink

me@andreas.ink


Source: https://www.andreas.ink/agent-alerts/privacy
