Eklo Subprocessors (0.9 private beta)

Last updated

Eklo uses nine subprocessors during the 0.9 beta, including Stripe for billing and sales tax, and Google and Apple as independent providers for optional sign-in. All are checked against the code and Eklo's own accounts. Effective date: November 3, 2026.

ProviderPurposeData involvedLocationPrivacy and DPAIn the beta
Amazon Web ServicesHosting: servers, database, queues, self-hosted realtime updates, file storage (S3) with short-lived signed links for files and thumbnails, malware scanning of uploaded files (GuardDuty), database backups (S3), content delivery (CloudFront) and firewall (WAF), logs (CloudWatch), secrets (Secrets Manager), alarm emails to Eklo staff (SNS), and this websiteAll account and church data; database backups; application logs, scrubbed of emails, tokens and IP addresses; firewall logs with the IP addresses of blocked or flagged requestsUS East, us-east-1 (Northern Virginia); CloudFront also serves the app and this website from edge locations worldwide.Privacy Notice · GDPR Center and DPAActive
Resend (Plus Five Five, Inc.)Sends sign-in codes and links, workspace invitations, beta-approval emails, direct-message and away notifications, notification digests, questions to form submitters, submission decisions, workflow emails, Ask Eklo reminders, export-ready notices, account-deletion codes and service notices to workspace ownersRecipient email addresses and email contentUnited StatesPrivacy Policy · DPAActive
OpenAIAI provider for Ask Eklo, the AI assistant, including the images it makes, and Library image tagging (see below)Prompts, workspace content Ask Eklo retrieves, attached files, remembered notes, image descriptions, images, AI outputUnited StatesDPA · Enterprise privacyActive
AnthropicAI provider for Ask Eklo, the AI assistant, including the web searches it runs, and Library image tagging (see below)Prompts, workspace content Ask Eklo retrieves, attached files, remembered notes, web search words and addresses, images, AI outputUnited StatesPrivacy Policy · DPAActive
Braintrust (Braintrust Data, Inc.)Traces a sample of Ask Eklo requests to monitor how AI features performAI model, tool names, content kinds and sizes, token counts and timing. No prompts, workspace content, AI output or user or workspace identifiersUnited StatesPrivacy Notice · DPAActive; about 5% of Ask Eklo requests are traced
Sentry (Functional Software, Inc.)Error reporting for the web app, API and workers; no performance tracingError messages, stack traces, request route, browser and device data; may include identifiers that appear in errorsUnited States and other countries where Sentry's subprocessors operatePrivacy Policy · DPAActive
Cloudflare (Turnstile)Bot checks on public forms and the request-access formVisitor IP address, TLS fingerprint, browser user agent, site key and page originCloudflare's global networkTurnstile Privacy Addendum · DPAActive; required in production
Google Workspace (Google LLC)Email for Eklo's own addresses, such as hello@eklo.io and privacy@eklo.io: support, privacy and security requestsSenders' names and email addresses, and what they write to usUnited States and other countries where Google operatesPrivacy Policy · Cloud Data Processing AddendumActive
StripeSubscription billing, payments and the billing portal; sales tax calculation (Stripe Tax)The church's legal name, billing address and owner's email, whether the church is tax-exempt, plan and subscription, and payment details entered with StripeUnited States and other countriesPrivacy Policy · DPAActive
GoogleOptional "Continue with Google" sign-inName, email, profile image, Google account ID and the sign-in tokens Google returnsGoogle's infrastructure; Google acts as an independent sign-in providerPrivacy PolicyOptional
Apple"Sign in with Apple"Name, email or relay address, Apple ID tokenApple's infrastructure; independent sign-in providerPrivacy PolicyNot active: the code supports it, but deployed config doesn't set it up

Ask Eklo, and Library image tagging once the Library is available, use OpenAI and Anthropic. We choose which one answers Ask Eklo, may switch from one to the other at any time, and may use each for a different feature; both are listed here so a switch doesn't change who can receive this data. As Eklo is set up, Anthropic answers Ask Eklo and OpenAI makes its images, so both receive Ask Eklo data at the same time: OpenAI gets the description of each image someone confirms, which can include workspace content. Ask Eklo searches the web only while Anthropic answers it, and Anthropic, not Eklo, runs those searches and opens those pages.

Realtime updates (chat messages, notifications and live updates) run on our own servers at Amazon Web Services, not a third-party service. We will give at least 15 days' notice before adding or replacing a subprocessor, by email to each workspace owner and an update to this page. Anyone else who wants to hear about changes can email hello@eklo.io.

How Eklo protects church data, in plain words, is on the Security page.