Sub-processors
Effective date: October 8, 2026
Our current sub-processors
Antigency uses the sub-processors below to operate the service. They are grouped by category, with the purpose of the processing and the location where data is primarily processed. We keep this list current and update it before a new sub-processor processes Customer Personal Data.
Infrastructure and hosting
- Vercel — hosting and serverless compute — United States
- Supabase — database, authentication, and file storage — United States
- Fly.io — hosting for the per-merchant agent containers — United States
- Upstash — rate limiting and caching — United States
- Sentry — error monitoring and session replay for the dashboard — United States
Payments and commerce
- Stripe — payment processing and subscription billing — United States and other countries
- Shopify — commerce platform integration and merchant billing — United States and other countries
Messaging and background jobs
- Resend — transactional email delivery — United States
- Inngest — background job orchestration — United States
AI model providers
Third-party AI model providers — large language model inference used to analyse the data you connect and to draft content. We select these providers and may change them as the service evolves. Data we send them may be processed in the United States and other countries where they operate.
Recipients (not sub-processors)
Antigency also shares data with the following recipient that is not a sub-processor:
- Slack — Slack Connect messaging: delivering briefs, findings, decision summaries, approval prompts, and chart images to private channels in Antigency’s Slack workspace, and receiving your team’s messages and approval actions there — United States and other countries where Slack operates
Slack is a recipient of this messaging, not a sub-processor, and is not engaged under a processor agreement.
Questions
If you have a question about a sub-processor, or want to object on reasonable grounds to a new one, contact us at support@antigency.ai. The Privacy Policy at /legal/privacy and the Data Processing Agreement at /legal/dpa describe how this list fits into our wider data practices.