Sub-Processors

Current list of sub-processors Finsi engages to deliver the platform. Categorized by function, with the data each one may access and the location of processing.

Sub-Processors

Last Updated: May 15, 2026 Company: Finsi (finsi.ai)


Overview

Finsi engages a small number of third-party services to operate the platform. This page lists every sub-processor that may access customer data on our behalf, categorized by function. We update this list whenever a sub-processor is added or removed.

Customers can subscribe to change notifications by emailing privacy@finsi.ai. We notify subscribers at least 14 days before adding a new sub-processor that will process customer data.

This list does not include third-party platforms that customers connect to Finsi (Shopify, Klaviyo, Meta Ads, Google Ads, Recharge, etc.). Those are customer-controlled integrations where the customer owns the relationship with the third party. Finsi accesses those platforms only via OAuth credentials the customer grants, with the scopes the customer authorizes.


1. Cloud Infrastructure

Sub-processorPurposeData accessedLocation
Amazon Web Services (AWS)Application hosting, compute, storage (RDS, S3), KMS, networkingAll customer data at rest and in transitUnited States (us-east-1)
AWS RedshiftAnalytics warehouse for aggregated customer dataAggregated customer data for analysis and reportingUnited States (us-east-1)

AWS holds SOC 2 Type II, ISO 27001, PCI DSS, and other independent attestations.


2. Artificial Intelligence and Language Models

When Finsi generates recommendations, weekly memos, email copy, or other AI-driven outputs, customer data may be processed by the providers below. We use providers with enterprise privacy commitments that do not train on customer prompts or outputs.

Sub-processorPurposeData accessedLocation
Anthropic (via AWS Bedrock)Primary LLM for analysis, recommendations, copy generationCustomer business data, promptsUnited States (us-east-1)
OpenAIFallback LLM and embeddingsCustomer business data, promptsUnited States
Google (Gemini paid API)Specialized analysis for image and multimodal use casesCustomer business data, promptsUnited States
Nano BananaAd creative image generationCustomer prompts, brand assetsUnited States

All LLM providers above are accessed under paid/enterprise terms and are contractually bound to not train on customer data when accessed via Finsi.


3. Data Integration and Sync

Sub-processorPurposeData accessedLocation
NangoOAuth broker for 50+ third-party platform integrationsOAuth refresh tokens (encrypted), connection metadataUnited States / Europe
AirbyteData sync between connected platforms and Finsi's warehouseCustomer business data flowing into the warehouseUnited States

4. Application Services

Sub-processorPurposeData accessedLocation
ResendTransactional email (account notifications, audit reports, weekly memos)Email addresses, content of notificationsUnited States
StripePayment processingBilling data, payment method (card data stored only by Stripe, never by Finsi)United States
PostHogProduct analytics and feature usage telemetryAccount email, in-app event data; no customer business dataUnited States
AttioCustomer relationship management; customer business data syncs from Finsi for sales and account managementAccount contacts, company data, communication history, synced business metricsUnited States

5. Categories Not Listed

Customer-controlled integrations. Shopify, Klaviyo, ActiveCampaign, Postscript, Attentive, Meta Ads, Google Ads, TikTok Ads, Recharge, Appstle, Stay AI, Gorgias, Zendesk, Google Analytics, Shopify Search Console, and similar platforms are not Finsi sub-processors. Customers own the contractual relationship with these platforms. Finsi accesses them via OAuth or API keys the customer provides, with the scopes the customer authorizes.

Open-source dependencies. Software libraries (Next.js, React, PostgreSQL, etc.) used to build the platform are not sub-processors. They do not receive customer data.


6. Subscribing to Change Notifications

To receive notification when this list changes, email privacy@finsi.ai with the subject "Sub-processor notifications" and the email addresses to notify.

We commit to notifying subscribers at least 14 days before adding a new sub-processor that will process customer data, and immediately when removing one.

Customers may object to a new sub-processor by emailing privacy@finsi.ai within the notification window. If we cannot accommodate the objection through alternate technical or commercial arrangements, the customer may terminate the affected service without penalty.


7. Audit and Documentation Requests

Customers under NDA may request:

  • Copies of relevant SOC 2 reports for sub-processors that maintain them (AWS, Neon, Stripe, others)
  • Data Processing Agreements (DPAs) we have in place with each sub-processor
  • Our internal vendor security review documentation

Send requests to security@finsi.ai.


Contact

Do more with the team you have.

Finsi gives the reconciling, reporting and first drafts to AI agents that work from verified numbers, ask before they act, and leave a record. Your team makes the calls.