Privacy Policy
How AgentAds collects, uses, shares, and protects information for developers, advertisers, and site visitors.
Last updated 2026-06-18
AgentAds is built for developer-native sponsorship without code or prompt surveillance. This policy explains the information we collect, why we collect it, and how to contact us about privacy requests.
This beta policy is written for the public websites, the AgentAds daemon, the advertiser portal, and related support workflows.
Information we collect
We collect the minimum information needed to operate accounts, serve sponsored statusline ads, measure billable events, prevent abuse, and support billing or payouts.
- Marketing leads: name, email, company, role, budget range, agent/platform interest, and submitted notes.
- Account identity: Google OAuth email, name where provided, organization membership, and session records.
- Advertiser data: organization profile, campaign settings, creative text, destination URLs, wallet funding, billing artifacts, moderation status, and reporting data.
- Developer device data: local device identifier, daemon version, OS, CPU architecture, locale, editor or agent metadata when available, adapter status, update state, and diagnostic telemetry.
- Ad activity: fill, serve, impression, click, payout, and ledger identifiers with timestamps and related state.
- Security and fraud signals: IP address, coarse network classification, event integrity checks, rate-limit signals, and invalid-traffic review results.
- Payment and payout metadata: Stripe payment, refund, dispute, Connect onboarding, transfer, and settlement identifiers and statuses.
- Support communications: messages, screenshots, logs, and troubleshooting details that you choose to send us.
What we do not collect
The daemon does not need private development content to measure a sponsored wait-state line.
- We do not collect source code, repositories, file contents, prompts, completions, AI conversations, terminal contents, secrets, tokens, or clipboard contents.
- We do not use code, prompts, files, or AI conversations for targeting because we do not collect them.
- We do not sell code, prompts, completions, files, or AI conversations because we do not collect them.
How we use information
- Authenticate users and protect accounts.
- Install, update, diagnose, and support the daemon.
- Select, rotate, render, measure, and bill sponsored statusline ads.
- Credit developer earnings and support payout workflows.
- Process advertiser wallet funding, refunds, disputes, receipts, and reporting.
- Review creatives, enforce policies, detect invalid traffic, and prevent abuse.
- Operate backups, logs, security monitoring, reconciliation, and incident response.
- Improve aggregate product reliability and support quality.
Sharing and service providers
We share information with service providers only as needed to operate AgentAds, comply with law, or protect the service.
- Stripe processes wallet funding, payment methods, refunds, disputes, Connect onboarding, transfers, and payout-related metadata.
- Google provides OAuth sign-in and may provide identity fields authorized during sign-in.
- AWS, Vercel, and related infrastructure providers host the API, sites, logs, storage, backups, and release artifacts.
- Email providers send receipts, moderation notices, payout notices, support messages, and operational alerts.
- We may disclose information if required by law, to prevent fraud or abuse, or to protect AgentAds, users, advertisers, developers, and the public.
Retention
- Ledger, payment, payout, tax, fraud, and dispute records are retained as long as needed for accounting, compliance, reconciliation, and support.
- Event and network data may be retained for fraud review, reporting, and billing integrity. IP data is designed to be minimized or truncated after scoring where implemented.
- Marketing lead and support records are retained while they remain useful for follow-up, support, audit, or legal purposes.
- Deletion requests may be limited where records are needed for security, accounting, tax, dispute, fraud, legal, or platform integrity reasons.
Your choices and requests
- You can uninstall the daemon with the AgentAds CLI and stop future device telemetry from that machine.
- You can contact us to request access, correction, deletion, export, or account closure, subject to legal and operational limits.
- California residents may have rights to know, delete, correct, opt out of certain sharing, limit sensitive-information use, and be free from discrimination for exercising privacy rights where applicable.
- If we later use cookies, analytics, or advertising technologies that require additional choices, we will update this policy and the product surfaces.
Security, children, and international use
- We use technical and organizational safeguards such as signed releases, token handling, production configuration guards, access controls, logging, backups, and reconciliation.
- AgentAds is not intended for children or for users under 18.
- AgentAds is operated from the United States. If you use it from another country, information may be processed in the United States and other countries where our providers operate.
Contact
For privacy requests, contact privacy@agentads.dev. For general support, contact support@agentads.dev.