Overview
Rolebotz, Inc. uses the following sub-processors to deliver the Rolebot service. Each sub-processor is bound by contractual obligations to protect your data in accordance with our Privacy Policy and applicable data protection laws.
We will update this page when we add or remove sub-processors. If you would like to be notified of changes, contact privacy@rolebotz.ai.
Infrastructure & Hosting
| Sub-Processor | Purpose | Location |
|---|
| Amazon Web Services (AWS) | Cloud infrastructure, compute, storage, database hosting, AI model hosting (Amazon Bedrock), encryption (KMS) | United States |
AI & Machine Learning
| Sub-Processor | Purpose | Location |
|---|
| Anthropic | Large language model inference (Claude) for agent responses, analysis, and content generation | United States |
Communication Platforms
| Sub-Processor | Purpose | Location |
|---|
| Slack (Salesforce) | Messaging platform integration — Rolebot receives and responds to messages in customer Slack workspaces | United States |
| Microsoft (Teams, Outlook, Copilot) | Messaging platform integration, email and calendar access via Microsoft Graph API with user-delegated OAuth | United States |
| Google (Gmail, Calendar) | Email and calendar access via Google Workspace APIs with user-delegated OAuth | United States |
Third-Party Integrations
| Sub-Processor | Purpose | Location |
|---|
| Merge.dev | Unified accounting API — connects Rolebot to customer ERP/accounting systems (QuickBooks, Xero, NetSuite, Sage, etc.) | United States |
| Plaid | Bank account connectivity — enables Rolebot to retrieve bank transactions and balances for reconciliation | United States |
Payments
| Sub-Processor | Purpose | Location |
|---|
| Stripe | Payment processing for subscription billing. Rolebotz does not store credit card numbers — all payment data is handled by Stripe. | United States |
Data Handling Principles
- All sub-processors are contractually required to protect data confidentiality and security.
- Customer data is encrypted in transit (TLS 1.2+) and at rest (AES-256 via AWS KMS).
- OAuth tokens for third-party integrations are encrypted with AWS KMS before storage.
- Rolebot does not permanently store email content, calendar events, or financial records — data is queried on-demand and returned to the user.
- Sub-processors only receive the minimum data necessary to perform their function.
Questions
For questions about our sub-processors or data processing practices, contact us at privacy@rolebotz.ai.