Legal
How AgentPays collects, uses, and protects your information.
AgentPays (“we”, “us”, “our”) provides infrastructure that lets you control how your AI agents spend money. This Privacy Policy explains what information we collect, how we use it, and the choices you have. By using AgentPays, you agree to the practices described below.
When you create an account, our authentication provider (Clerk) collects your email address, name, and Google profile information used during sign-in. We receive a user identifier from Clerk and the basic profile details associated with your account.
If you connect Privacy.com to issue virtual cards, we store your Privacy.com API key encrypted at rest in our database. The key is used to create single-use virtual cards on your behalf when your agents make approved purchases.
When you save a payment method, Stripe stores your card details and returns a token to us. We never store your full card number or CVC. Stripe is used to collect our transaction fee.
We store the agents you create, their spending rules, every purchase request your agents submit (including the merchant, amount, description, and justification), and the resulting transaction record.
We collect product analytics through PostHog (pageviews, feature usage, basic device and browser metadata, and session recordings of dashboard activity) and privacy-friendly aggregate traffic measurement through Vercel Analytics. PostHog analytics run only after you consent through the banner shown on your first visit. Vercel Analytics is cookieless and does not identify individual users. We use this to understand how the product is used and to improve it.
We do not sell your personal information, and we do not use your purchase data to build advertising profiles.
AgentPays relies on the following sub-processors to operate. Each one receives only the data necessary to perform its function.
Clerk
Purpose: Authentication and account management
Data received: Email, name, Google profile data, sign-in events
Supabase (PostgreSQL)
Purpose: Primary application database — hosts agents, purchase requests, transactions, and spend rules
Data received: All application data, including encrypted Privacy.com API keys
Privacy.com
Purpose: Virtual card issuance for approved purchases
Data received: API calls made on your behalf using your API key; purchase amount and merchant for each card issued
Stripe
Purpose: Payment method storage and AgentPays fee collection
Data received: Card token, billing details, amount of each fee charged
Resend
Purpose: Transactional email delivery (purchase approval notifications)
Data received: Email address, message content
PostHog
Purpose: Product analytics, session recordings, and error tracking (only after you consent)
Data received: Pageviews, feature usage, device/browser metadata, dashboard session recordings. We delete your PostHog data when you delete your account.
Vercel
Purpose: Application hosting, edge delivery, and privacy-friendly aggregate analytics
Data received: For hosting and edge delivery: server logs, IP addresses, and request metadata. For analytics: cookieless, anonymized page view data (timestamp, page URL, referrer, approximate location derived from IP but not stored, device and browser type), identified only by a daily-rotating hash that cannot track visitors across days or sites.
Each provider has its own privacy policy that governs how it handles the data it receives. You should review their policies if you have specific concerns.
We retain your account and application data for as long as your account is active. When you delete your account, we permanently remove your agents, spend rules, encrypted Privacy.com API key, stored payment methods, purchase requests, transaction records, and your analytics data held in PostHog. We also delete your customer record and saved payment methods from Stripe.
Records of fees we charged you (the AgentPays transaction fee) are retained by our payment processor, Stripe, as part of our own financial records. We keep these to meet accounting, tax, and regulatory obligations. These records reflect fees we collected and are separate from the purchase and account data we delete.
Backup snapshots may retain deleted data for up to thirty days before being expired.
You have the right to:
To exercise any of these rights, email kevin@agentpays.dev. We respond within a reasonable timeframe and consistent with applicable law.
We take reasonable measures to protect your information:
No security measure is perfect. We cannot guarantee absolute security, and you are responsible for keeping your AgentPays credentials and connected API keys secure.
You have the right to know what categories of personal information we collect, the purposes for which we use it, and the categories of third parties with whom we share it. You can request access, correction, or deletion of your personal information, and you have the right not to be discriminated against for exercising these rights. AgentPays does not sell personal information.
We process personal data on the following legal bases: (a) performing the contract we have with you, for the core functionality of operating your account and processing your agents' purchases, (b) your consent, for product analytics through PostHog, which you can give or withhold through our consent banner and withdraw at any time, (c) complying with our legal obligations, including retaining financial records of fees we charged, and (d) our legitimate interests in securing the service and preventing fraud and abuse. You have the right to access, rectify, erase, restrict, or port your data, to object to processing, and to withdraw consent for analytics at any time. You also have the right to lodge a complaint with your local data protection authority.
To exercise any of these rights, contact kevin@agentpays.dev.
AgentPays is not intended for use by children under 18. We do not knowingly collect personal information from children. If we learn that we have collected information from a child, we will delete it promptly.
We may update this Privacy Policy from time to time. When we make material changes, we will update the “last updated” date at the top of the page and, where appropriate, notify you by email or through the product. Continued use of AgentPays after a change indicates your acceptance of the updated policy.
If you have questions about this policy or how we handle your data, contact us at kevin@agentpays.dev.