Privacy Policy
Full session files stay on your Mac.
Agent Callout is a product of White Tiger Streetwear LLC, a Texas limited liability company. This policy explains what the Agent Callout website and macOS app collect, why we use it, and the choices you have.
Who this policy covers
Agent Callout is offered only to people who are at least 18 years old. Accounts and the free trial are available generally, while paid plans are currently sold only when the billing address, and an individual's ordinary residence or an organization's principal place of business, are in the 50 United States, the District of Columbia, or Argentina. This policy applies to information collected through the website and the app wherever you use them.
If paid plans are not available in your country yet, you can leave your email on the pricing page to receive one notification when they are. We store that email with your coarse request country only for that single message, and we delete the entry after the notification is sent or on request to support@agentcallout.com.
Local sessions and callout content
- The app reads coding-agent session records already stored on your Mac. Current sources include Claude Code, Codex CLI, Cursor IDE and CLI, Pi, Gemini CLI, and Antigravity CLI. We do not upload or store your full transcript files on our servers.
- A response leaves your Mac when you start a callout or when auto-play starts one. Auto-play is on by default and can be turned off in Settings. Only the response selected for that callout is sent, not the full session file.
- For Bro code, Casual, and Professional styles, the selected response is sent through our authenticated backend to the Google Gemini API for summarization. If Gemini does not return an English summary and Groq is configured as a fallback, the selected response can instead be sent to Groq for summarization. Spanish summaries use Gemini only. The resulting summary is sent to Inworld to generate voice audio.
- For Complete style, the selected response is cleaned for speech and sent through our authenticated backend directly to Inworld. It is not sent to Gemini or Groq for summarization.
- We do not intentionally write selected response text, generated summaries, or generated audio to our application database. Gemini, Groq when configured as an English fallback, and Inworld process the material under their own terms and retention practices. We do not promise that these providers offer zero data retention for this processing.
- The Mac app keeps app-owned local state under
~/.cache/agent-callout. This can include summary and audio replay caches, session identifiers and transcript paths, recent agent status events, project or working-directory labels, terminal routing identifiers, queued reply text, pending approval request data, decision outcomes, usage snapshots, and diagnostic logs. These files support replay, the session board, replies, approvals, focus, and troubleshooting. They remain on that Mac until cleared, consumed, or removed when Agent Callout is uninstalled.
Do not route secrets, regulated data, or other highly sensitive content through a callout unless you are authorized to send it to these providers. The coding-agent services whose sessions you use have their own privacy terms.
Account, device, usage, and billing data
- Account data can include your email address and, if you use Google sign-in, the name and profile image Google makes available to the sign-in flow. Supabase provides authentication and stores account records.
- The app sends a one-way hash derived from a Mac hardware identifier for trial eligibility, device binding, and the four-Mac device limit. The raw hardware identifier does not leave your Mac.
- The app stores its sign-in token in the macOS Keychain and mirrors it to an app-owned local file for the background engine. Signing out requests server revocation and removes both local copies. The documented uninstall also removes the Agent Callout Keychain item and local file.
- Usage records contain metadata, not session content. This can include the agent, style, language, character count, audio minutes, provider, model, token counts, cost estimates, timestamps, and entitlement status used to meter and protect the service.
- We retain the version and time of legal acceptances and the eligibility statements made with them so we can operate the account and document the agreement.
- Stripe processes payment details and billing addresses. We do not receive or store your full card number. We store subscription, entitlement, invoice, refund, dispute, tax, and referral records that are needed to provide and account for the service.
- If you contact support, we receive your contact details, message, and any diagnostics you choose to attach. Diagnostics are not intended to contain transcripts.
Website analytics, cookies, and location
Vercel hosts the website and provides aggregate web analytics such as page views, referrers, approved campaign labels, device type, and country. Vercel also receives request information needed to deliver and secure the site. Server logs can contain pseudonymous account and billing references such as Stripe object IDs and notice keys when they are needed to diagnose an operation. They do not contain full card numbers or session content by design.
Optional PostHog analytics starts only after you allow it. We record a limited list of product actions, such as using the hero sound, requesting a download, selecting pricing, and beginning checkout. We disable autocapture, session replay, heatmaps, surveys, dead-click capture, exception capture, and performance capture. Allowed events can still include standard browser, device, page, campaign, network, and coarse-location metadata that PostHog attaches or derives during event delivery. We use this to understand product use, locales, and language needs. If you sign in after allowing analytics, those events can be linked to your internal account identifier.
- Strictly necessary Supabase cookies keep a signed-in web session. A path-restricted, HttpOnly
ac_app_handoffcookie can carry a newly issued app token for up to two minutes while the browser hands sign-in back to the Mac app. - A first-party theme cookie keeps the website experience stable for one year. Your analytics choice is stored in your browser.
- If you allow optional analytics, a random first-party browser ID is stored for one year. It can be associated with your internal account identifier after sign-in.
- A referral cookie stores a referral code for 30 days so a later account creation can be attributed to the person who referred you. A second referral marker can remember during the same 30-day period that the referred visitor requested a download.
- Allowlisted campaign labels, such as source, campaign, and demo name, can be kept in browser session storage for the current tab session. The tab also keeps short-lived markers that prevent duplicate campaign analytics events.
- Our operational activity ledger can store coarse city and country text derived from Vercel request headers for about 30 days. We use it to understand downloads, checkout activity, locales, languages, and service health. We do not send location data in owner alerts.
Analytics does not receive transcripts, selected response text, summaries, audio, card details, raw Stripe payloads, or free-text cancellation comments. Agent Callout honors Global Privacy Control and browser Do Not Track as an opt-out from optional analytics.
Your analytics choice
You can change optional analytics at any time. Turning it off removes the random analytics ID from this browser and stops new PostHog events. Aggregate Vercel traffic measurement remains active.
Service providers and disclosures
Our current service providers are listed on the Subprocessors page. They include Vercel, Supabase, Stripe, Google Gemini, Groq as a conditional English summarization fallback, Inworld, Resend, optional PostHog analytics, and Telegram for limited operational alerts. Telegram alerts are limited to operational counts, plan or SKU, amount and currency, environment, and status. They exclude email, account identifiers, location, session content, summaries, commands, and raw provider payloads.
We can also disclose information when required by law, to protect users or the service, or as part of a merger, financing, acquisition, or sale of assets, subject to appropriate confidentiality and notice where required. We do not sell or rent personal information, and we do not use it for cross-context behavioral advertising.
Email and provider updates
Resend delivers support, account, legal, and optional update messages. These service messages are separate from marketing. You can ask to join a monthly product and privacy update. Each edition includes links to the current provider list, including Gemini, Groq, and Inworld, and an unsubscribe link. You can sign up by email. You can unsubscribe from optional messages at any time. We may still send service messages needed for your account.
We update the Subprocessors page when our provider list changes. The monthly update does not replace direct notice when a change materially affects how we handle your information. You can also email us at any time for the current list.
Retention and deletion
We keep account and usage data while your account is active and as reasonably needed to provide the service. We keep coarse operational location records for about 30 days. Billing, tax, referral, fraud, legal-acceptance, and dispute records can be kept longer when reasonably needed for accounting, security, contract enforcement, or legal obligations. Service providers keep information under their own policies.
To request access, correction, or deletion, email support@agentcallout.com. We may need to verify the request. Deletion can end your account and does not require us to delete records that we must or may lawfully keep. Applicable state law may give you additional rights. We will not discriminate against you for exercising a privacy right.
Security and changes
We use administrative, technical, and organizational safeguards designed for the information we handle. No transmission or storage system is completely secure.
When this policy changes, we will post the revised version with a new date. For a material change, we will provide additional notice and seek fresh acceptance when required before the new terms apply.
Contact
Questions and privacy requests: support@agentcallout.com.
Effective July 22, 2026.