Legal
Sub-processors
Last updated: November 7, 2026 · AgentKeeper by RAD Security, Inc.
To provide the hosted AgentKeeper service, RAD Security, Inc. engages the third-party sub-processors below. Each processes personal data only to deliver its function and under contractual data-protection obligations. This list supplements our Privacy Policy.
| Sub-processor | Purpose | Data processed | Location |
|---|---|---|---|
| Amazon Web Services | Hosting, database, storage and backups; AI analysis through Amazon Bedrock | All service data — accounts, organizations, hosts, events, sessions, policies | United States (US region); Germany, Frankfurt (EU region) |
| Anthropic | AI-assisted detector drafting and exception triage, when you have not supplied your own Anthropic key | Event and policy details needed for the requested analysis, limited by your organization's AI privacy settings; not used for model training | United States |
| Cloudflare | Edge network and DDoS protection | Network traffic in transit, including IP addresses | Global edge network |
| Groundcover | Application logs and metrics (US region only) | Operational logs and metrics, which may include user and organization identifiers | United States |
| PostHog | Product analytics and session recordings (US region only; load only with consent) | Pseudonymized usage events, hashed email, organization id hash, plan. Recordings of a sample of sessions, with all text and inputs hidden | United States |
| Sentry | Application error reports (US region only) | Error details and limited request context, with personal data scrubbed | United States |
| Stripe | Billing and subscriptions for paid plans | Billing contact name, email, address and tax ID, organization and user identifiers, plan and payment metadata (card data is handled by Stripe directly) | United States |
| Resend | Transactional email (welcome, invitations, alerts, reports) | Recipient email address and message content | United States |
| Linear | Support and feedback requests | Request content and the requester's name and email | United States |
| HubSpot | Marketing CRM and marketing-site analytics (marketing pages only; loads only with consent) | Name, email and company from requests you send us (such as a demo request); pages visited on the marketing site | United States |
| Slack | Internal operational notifications | Signup and usage notifications (organization name, plan) | United States |
Services you connect to AgentKeeper, such as your identity provider, EDR, AI providers' compliance APIs, ticketing, SIEM or GitHub, exchange data with AgentKeeper at your direction and under your own agreements with them; they are not our sub-processors.
Geolocation
Country-level geolocation uses an embedded MaxMind GeoLite2 database. The lookup runs on our own servers and the raw IP address is never sent to MaxMind or any third party, nor is it stored — only the resulting two-letter country code is retained. MaxMind is therefore not a sub-processor.
This product includes GeoLite2 data created by MaxMind, available from https://www.maxmind.com.
Self-hosted & on-premises deployments
When AgentKeeper runs in a customer's own environment (on-premises / BYOC), none of the external sub-processors above are used by default — billing, source integration, and AI analysis are off unless explicitly enabled, and all data stays inside the customer's infrastructure.
Changes & objections
We will update this page before engaging a new sub-processor that processes customer personal data. To request advance notice of changes or to raise an objection, contact [email protected].