Here's a list of subprocessors handling user data for ISMS Copilot:

AWS (Amazon Web Services):

• Role: Hosting provider for EU users.
• Location: Amsterdam, Netherlands.
• Data Handled: Conversation data for ISMS Copilot Chatbots (EU option).

Mistral:

• Role: AI processing provider for EU users.
• Location: Sweden.
• Data Handled: Conversation data for ISMS Copilot Chatbots (EU option).

Chatbase:

• Role: Chatbot platform provider for US users.
• Location: United States.
• Data Handled: Conversation data for ISMS Copilot Chatbots (US default option).

OpenAI:

• Role: AI processing provider.
• Location: United States.
• Data Handled: Conversation data for ISMS Copilot Chatbots (US default option) and policy text generation for ISMS Policy Generator.

Anthropic:

• Role: AI processing provider.
• Location: United States.
• Data Handled: Conversation data for ISMS Copilot Chatbots (US option).

Our chatbots can alternatively rely on OpenAI or Anthropic models (or Mistral, for the EU version).

Bubble.io:

• Role: Application development platform.
• Location: United States.
• Data Handled: User inputs for ISMS Policy Generator.

Zapier:

• Role: Automation tool for policy generation and email delivery.
• Location: United States.
• Data Handled: User inputs and generated policy data for ISMS Policy Generator.

Google Docs:

• Role: Document conversion and storage.
• Location: United States.
• Data Handled: Policy text for ISMS Policy Generator.

Stripe:

• Role: Payment processing.
• Location: United States.
• Data Handled: Payment information for subscription upgrades.

PostHog:

• Role: Analytics provider.
• Location: United States.
• Data Handled: Anonymized usage data across the platform.

This list includes all known subprocessors involved in handling user data for ISMS Copilot.