1. How to read this list
17 processors are engaged for the purposes in the Privacy Policy. A processor is used when the feature that calls it is switched on and you use that feature. Higgsfield video and FLUX images on fal are lanes that stay off until they are switched on. The others are part of hosting, billing, email, monitoring, or the model and research paths the product can run.
Transfers outside the EEA follow GDPR Articles 44 to 46. “Data Privacy Framework” means the provider is certified under the EU-US Data Privacy Framework (an Article 45 adequacy decision for that certified transfer). “Standard Contractual Clauses” means the clauses in Commission Implementing Decision (EU) 2021/914. Where a row does not name the Framework, this page does not claim that certification.
2. Processors
| Processor | Role | Data | Location | Transfer tool |
|---|---|---|---|---|
| Vercel, Inc. | Hosting, Web Analytics, Speed Insights, and the AI Gateway that routes model requests. Routing can include a short task description sent to the Gateway evaluation model (Jev). | Account traffic, pages, and the model request the Gateway forwards. Analytics and Speed Insights only after consent. | United States company. Application functions run in Frankfurt (fra1). Model requests go through the Vercel AI Gateway. | EU-US Data Privacy Framework (Article 45) and Standard Contractual Clauses (Article 46). |
| Supabase, Inc. | Database, authentication and file storage. | Account, workspace, brand and project content, and the cost and security records described above. | United States company. The production database is in AWS eu-central-1 (Frankfurt). | Storage stays in the EEA. Access from the United States uses Standard Contractual Clauses (Article 46). This page does not claim a Data Privacy Framework certification for Supabase. |
| Stripe, Inc. and Stripe Payments Europe, Ltd. | Payments, invoices and Stripe Customer records for plans and credits. | Billing details entered on Stripe Checkout, plan and payment status. Not the card number, and not the CV text. | Ireland and the United States. | EU-US Data Privacy Framework (Article 45) and Standard Contractual Clauses (Article 46). |
| Resend | Transactional email about the account, an invitation or billing. | Recipient address and the message. | United States. | EU-US Data Privacy Framework (Article 45) and Standard Contractual Clauses (Article 46). |
| Cloudflare, Inc. | Turnstile bot check on the email and password sign-up form, only when both Turnstile keys are configured. The check is off otherwise. Google and GitHub sign-in do not use it. | Browser signals Cloudflare uses to issue a one-time token, that token, and the IP address sent with the check. Not the name, email or password. The token is not stored. | United States company. The widget is loaded from challenges.cloudflare.com. | EU-US Data Privacy Framework (Article 45) and Standard Contractual Clauses (Article 46). |
| Functional Software, Inc. (Sentry) | Error reports and a sample of performance traces. Session replay, when it is switched on, is sent only after analytics consent. | Technical error context, with secrets, cookies and email addresses scrubbed first. | United States. | Standard Contractual Clauses (Article 46). This page does not claim a Data Privacy Framework certification for Sentry. |
| PostHog, Inc. | Product analytics, only after you accept analytics. | Usage events from the signed-in product. | United States company. The browser is pointed at the EU host eu.i.posthog.com. | The events are sent to the EU host. Access from the United States uses Standard Contractual Clauses (Article 46). |
| Anthropic, PBC | Language models, through the AI Gateway and, if the Gateway leg fails, Anthropic’s own API. | The prompt and the context the task needs. | United States. Direct calls use Anthropic’s own API. | Standard Contractual Clauses (Article 46). This page does not claim a Data Privacy Framework certification for Anthropic. |
| OpenAI Ireland Ltd. and OpenAI, L.L.C. | Language models, image generation, text embeddings and safety moderation, through the AI Gateway or OpenAI’s own API. | The prompt, images you ask us to make or edit, and text sent for an embedding or a safety check. | Ireland and the United States. Direct calls use OpenAI’s own API. | Standard Contractual Clauses (Article 46). This page does not claim a Data Privacy Framework certification for OpenAI. |
| Google LLC and Google Ireland Limited | Gemini image, Veo video, and YouTube search used for trend research. | The image or video prompt and frames the task needs, or the search keywords for a trend check. | Ireland and the United States. | EU-US Data Privacy Framework (Article 45) and Standard Contractual Clauses (Article 46). |
| ElevenLabs (Eleven Labs Inc.) | Speech, dialogue, music, sound effects, alignment and dubbing, called on ElevenLabs’ own API. | The text or audio you ask us to turn into sound. | United States. Calls use ElevenLabs’ own API. | EU-US Data Privacy Framework (Article 45) and Standard Contractual Clauses (Article 46). |
| fal (Features & Labels Inc.) | Kling video on fal, and FLUX images when that evaluation lane is switched on. | The video or image prompt and reference frames for that lane. | United States. Calls use fal’s queue API. | Standard Contractual Clauses (Article 46), as fal describes contractual clauses for restricted transfers. This page does not claim a Data Privacy Framework certification for fal. |
| Higgsfield | Video generation when the Higgsfield lane is switched on, including a MiniMax model requested from Higgsfield rather than from a MiniMax endpoint. | The video prompt and reference frames for that lane. | Requests are sent to Higgsfield. This codebase does not record the country where inference runs. | No adequacy decision is claimed. The transfer uses Standard Contractual Clauses where Higgsfield’s data processing terms include them. |
| Tavily (AlphaAI Technologies Inc.) | Web search used to find sources for research. | Search queries built from the brand and research context. Not the whole workspace. | United States. Calls use Tavily’s search API. | No adequacy decision. The transfer uses Standard Contractual Clauses where Tavily’s data processing terms include them. |
| Reddit, Inc. | Trend search of public Reddit posts when the Reddit adapter is configured. | Search queries built from industry, goal and brief text. Not account passwords. | United States. Calls use Reddit’s API. | No adequacy decision is claimed on this page. The transfer uses Standard Contractual Clauses where Reddit’s terms include them. |
| DataForSEO | Google Trends figures for keyword checks. The official Google Trends adapter in this codebase returns no data. | The keywords being checked, and a region. | Lithuania, inside the EEA. DataForSEO queries Google for the trend figures. | No Chapter V transfer to DataForSEO. Google’s processing of the keyword check is covered by the Google row. |
| Voyage AI | Multimodal embeddings used to compare frames during media quality checks. | Text and images from the asset being checked. | United States. Calls use Voyage’s embeddings API. | No adequacy decision is claimed. The transfer uses Standard Contractual Clauses where Voyage’s terms include them. |
3. Platforms you connect
These are not processors we use for every customer. They receive data when you connect the account and ask Marshi to publish or sync. They then act as separate controllers of the published content.
| Platform | When data is sent | Transfer |
|---|---|---|
| Meta (Facebook and Instagram) | When you connect a Page or a professional Instagram account and ask Marshi to publish or read publishing status. Calls go to graph.facebook.com and graph.instagram.com. | Meta is a separate controller of what is published on its service. Meta Platforms, Inc. is certified under the EU-US Data Privacy Framework. Standard Contractual Clauses also apply under Meta’s terms. |
| When you connect LinkedIn and ask Marshi to publish or read the connected profile. Calls go to api.linkedin.com. | LinkedIn is a separate controller of what is published there. LinkedIn’s terms cover the transfer, including Standard Contractual Clauses and the EU-US Data Privacy Framework where LinkedIn’s certification applies. | |
| X | When you connect X and ask Marshi to publish. Calls go to api.x.com. | X is a separate controller of what is published there. No adequacy decision is claimed on this page. The transfer uses Standard Contractual Clauses where X’s terms include them. |
4. What this list leaves out, on purpose
Pusher is not a Marshi processor. The content-security policy allows the browser to reach pusher.com because Vercel Live, on preview deployments, uses it for comments. Production workspace content is not sent to Pusher by our application code.
Public RSS feeds and ordinary web pages are read when research needs them. Reading a published page is not a processor relationship. YouTube search is the Google row. Reddit search and DataForSEO are their own rows.
The marketing site names further model families that the AI Gateway catalogue can carry, including DeepSeek, Moonshot (Kimi), Alibaba (Qwen), Ideogram and Runway. The models this repository pins for production tasks are Anthropic, OpenAI, Google, fal, ElevenLabs and the Gateway evaluation model. MiniMax video, when the Higgsfield lane is on, is requested from Higgsfield, not from a MiniMax host in this codebase. An operator setting, such as an optional video quality-check model, can select another Gateway catalogue model. The Commission’s adequacy list has no decision for China. This page does not claim a Chapter V tool for a transfer to China. A model is not used for production traffic merely because the marketing page names it.
Provider terms differ on how long a prompt is kept. This list does not state a training rule for any provider.
5. Changes
We update this page when the set of processors changes, and we change the date at the top. Questions go to support@marshi.ai. Business customers can also ask for the signed Article 28 terms from the Data Processing page.
