The short list of who touches data.
Barkrow runs on a deliberately small set of subprocessors.
Each provider is bound by appropriate data-protection terms. Model providers receive document text after privacy checks. Automated detection has limits, and some identifying information may remain. Other providers receive only the data listed below for their service purpose. See the PII boundary and Data Processing Addendum.
The table below is what processes data today. Changes we have decided but not yet made are listed separately, under Planned changes, and no provider appears in the current table until it actually processes data.
Your application data, extracted text, citations, and embeddings are stored in the United States, in the us-west-2 (Oregon) region. Uploaded documents are stored with a western North America location preference, and compute runs in western North America. Two exceptions are disclosed rather than buried: text embeddings are computed on our edge provider’s network, which is not pinned to a region, and workflow job state, including the short excerpts a result cites, is cached on our global edge network so a run survives a reload.
Current subprocessors
Subprocessor Purpose What it processes Location Cloudflare Hosting of this site and the application, application compute and background workflows, document storage, text embeddings, product email delivery, edge delivery, DNS, and web application firewall Customer documents and derived text, tenant-isolated; email recipients and message content; network traffic, request metadata, and cached workflow job state including cited document excerpts Compute and document storage in western North America · embeddings and edge on Cloudflare’s global network Supabase Managed Postgres database, the system of record Account data, application data, document metadata, extracted text, citations, and embeddings, tenant-isolated with row-level security United States · us-west-2 (Oregon) WorkOS Identity provider behind Barkrow-rendered sign-in: credential verification, multi-factor, social sign-in, organizations, roles, SSO, and directory sync; authentication email Account identifiers, memberships, and authentication data. Passwords and factor codes are passed to WorkOS for verification and are never stored, logged, or hashed by Barkrow United States Stripe Checkout, subscriptions, invoices, tax, and Customer Portal Billing identity, subscription data, and payment data entered directly into Stripe United States Anthropic Language-model inference for workflows, chat, and the support agent, called directly through Anthropic’s API in a workspace configured for zero data retention Document text processed through privacy checks and context needed for the requested task; some identifying information may remain United States processing preference Google (Maps Platform) Map rendering, address autocomplete, and geocoding for address entry Map coordinates, entered address text, and browser and network request metadata. Google never receives document text, prompts, citations, tenant identifiers, or model data Provider-operated regions Microsoft (Microsoft 365) Company email, intake of website forms and in-product support requests into Microsoft Teams, and meeting booking Name, work email, company, and message content you send us. Never customer documents Provider-operated regions HubSpot Customer relationship management for sales conversations and newsletter subscriptions Business contact details and communication preferences. Never customer documents Provider-operated regions Recent changes
On 29 September 2026, Amazon Web Services stopped being a Barkrow subprocessor. Hosting, compute, and document storage moved to Cloudflare, the database moved to Supabase in the same Oregon region, text embeddings moved to Cloudflare, product email moved from Resend to Cloudflare, and model inference moved to Anthropic directly.
Planned changes
These moves are decided and are not yet in effect. We give advance notice before any of them takes effect, and this page is updated when one does.
Change What it would move Status Website and newsletter sign-ups are recorded in HubSpot automatically Name, work email, company, and newsletter consent from site forms Built, not switched on Read-only document connectors for Google Drive, Microsoft OneDrive and SharePoint, and HubSpot, through WorkOS Files and records you choose to connect, on Pro and Enterprise plans Not available; nothing is connected today How we manage this list
Vetting. Before we engage a subprocessor, we review its security posture, data-handling practices, and certifications, and we put a data-processing agreement in place.
Notice and objection. We give advance notice before adding or replacing a subprocessor. Customers may subscribe to change notifications and, as described in the DPA, object on reasonable data-protection grounds.
Responsibility. We remain responsible to you for any subprocessor’s performance of these obligations.
Stay notified
To receive notice of changes to this list, write to legal@barkrowsystems.com and ask to be added to subprocessor change notifications.
Questions? Write to legal@barkrowsystems.com.