Sub-processors
Last updated: October 22, 2026
These are the services Herman Foundry Oy uses to run FeedSquad in production that receive personal data. Each one processes the data under its data processing terms with us, unless the table says otherwise, and may use it only to provide its service. The list covers only what runs today: a new provider is added here, with notice, before the feature that uses it launches.
Our main database, file storage and server functions are in the EU (Ireland and Frankfurt). Some providers are in the United States; the table says which, and names the safeguard for each. For US providers certified under the EU–US Data Privacy Framework we rely on it, together with the EU Standard Contractual Clauses in their data processing terms; Supabase, OpenAI and Anthropic are not certified, so for them we rely on the Standard Contractual Clauses alone. Our only AI providers are OpenAI and Anthropic. We checked each provider against the official Data Privacy Framework list on October 21, 2026.
How FeedSquad uses your data is described in the privacy policy. If you are a customer, the Data Processing Agreement covers the personal data we process on your behalf, and this list is its Annex 3.
Infrastructure
| Service | What it does for us | Data it receives | Location | Transfer safeguard |
|---|---|---|---|---|
| Supabase | Database, sign-in and file storage for the whole Service. | Everything stored in your account: profile, content, connections, uploaded images and recordings, and your password as a hash if you set one. | Stored in the EU (Ireland). See Supabase’s data processing terms for the contracting entity. | Data is stored in the EU. Access from outside the EU is covered by the EU Standard Contractual Clauses (Modules 2 and 3) in its data processing terms |
| Vercel | Hosting, server functions, background jobs, page analytics and the bot check at sign-up. | Every request to the Service (IP address, browser details, the data you send and receive), the inputs and outputs of background jobs, and short-lived request logs. | EU (Frankfurt, Germany) for server functions | EU–US Data Privacy Framework (the provider is certified under it), and the EU Standard Contractual Clauses in the provider's data processing terms |
| Vercel Sandbox | Isolated computers for Pixel’s media work: capturing web pages you approve, and rendering moving visuals. | The web pages you approve for capture, and the images and text that go into a moving visual. | United States | EU–US Data Privacy Framework (the provider is certified under it), and the EU Standard Contractual Clauses in the provider's data processing terms |
Payments
| Service | What it does for us | Data it receives | Location | Transfer safeguard |
|---|---|---|---|---|
| Stripe | Subscriptions, payments, invoices and refunds. | Name, email address, your FeedSquad account ID, billing address and payment details. You enter card details on Stripe’s own checkout page; FeedSquad never sees your card number. | Ireland (contracting entity); Stripe processes globally, including the United States | EU–US Data Privacy Framework (the provider is certified under it), and the EU Standard Contractual Clauses in the provider's data processing terms |
| Service | What it does for us | Data it receives | Location | Transfer safeguard |
|---|---|---|---|---|
| Resend | Account and notification email, and the newsletters Herald sends to your subscribers (with delivery, bounce, open and click events). | Recipient email address and name, the email content, and delivery events. | United States; newsletter sending domains are set up in the EU (Ireland) | EU–US Data Privacy Framework (the provider is certified under it), and the EU Standard Contractual Clauses in the provider's data processing terms |
Monitoring and analytics
| Service | What it does for us | Data it receives | Location | Transfer safeguard |
|---|---|---|---|---|
| Sentry | Error monitoring. Session replay is switched off. | Error details, the page or request that failed, your FeedSquad account ID, and browser details including IP address for errors in the browser. | EU (Frankfurt, Germany); its terms allow processing in the United States | Stored in the EU. Access or processing from the United States is covered by the EU–US Data Privacy Framework (the provider is certified under it) and the EU Standard Contractual Clauses in its data processing terms |
| PostHog | Product analytics: which features are used and where people get stuck. Session recording is switched off. | In the browser, only after you accept analytics cookies: page views and clicks (which can include the label of what you clicked), your FeedSquad account ID when you are signed in, browser and device details, and IP address. From our servers: product events, unless you switched product analytics off in Settings. Server events never contain post text, prompts, messages, email addresses or access tokens. | EU (Frankfurt, Germany); the contracting entity is PostHog, Inc. (United States) | Stored in the EU. Access or processing from the United States is covered by the EU–US Data Privacy Framework (the provider is certified under it) and the EU Standard Contractual Clauses in its data processing terms |
| Google Analytics | Website analytics, in Google’s basic consent mode: the tag loads only after you accept analytics cookies. | Only after you accept: pages visited, referrer, browser and device details and IP address, with analytics cookies. Before you accept, or after you decline, Google receives nothing from us. | Ireland (contracting entity); Google processes globally, including the United States | EU–US Data Privacy Framework (the provider is certified under it), and the EU Standard Contractual Clauses in the provider's data processing terms |
AI providers
FeedSquad uses these providers through their business APIs. Under their API terms they may not use the data to train their models. They may keep it for a limited time to detect abuse.
| Service | What it does for us | Data it receives | Location | Transfer safeguard |
|---|---|---|---|---|
| Anthropic | Much of the writing and planning (including Ghost, Pulse, Stitch, Chief and Cite), web research while drafting and planning, sorting and extracting what you tell Stash, qualifying Scout leads, describing shelf images, inspecting Pixel visuals, and Cite’s checks of whether Claude’s answers cite your site. Also the automatic fallback when OpenAI is unavailable. | The text of the request: your drafts and posts, your brand context from Stash, notes and transcripts, comments you reply to (with the commenter’s name and headline), public posts Scout found, images being described or inspected, and web-search queries built from your topic, industry or audience (with email addresses and phone numbers taken out). | United States | EU Standard Contractual Clauses (Modules 2 and 3) in Anthropic’s data processing terms |
| OpenAI | Writing for other tasks (for example general post drafts, campaign strategy and Momentum plans, and translation), and the automatic fallback when Anthropic is unavailable, including for web research. Also image generation, search over your Stash and Chief’s memory (embeddings), transcription of recordings and voice notes, the live voice interviewer in Parley, and Cite’s checks of whether ChatGPT’s answers cite your site. | The text of the request (as for Anthropic), images to edit, audio to transcribe, and, during a live Parley interview, your microphone audio and IP address: your browser connects to OpenAI directly for that. | United States; for EU customers the contracting entity is OpenAI Ireland Ltd | EU Standard Contractual Clauses in the provider's data processing terms |
Channels you choose
These are not our sub-processors. If you connect Chief to one of them, you use it with your own account under its own terms, and it receives what Chief sends you there and what you reply.
- Telegram: Chief on Telegram, and sending images to Pixel’s shelf. Telegram receives your Telegram user ID and username, the messages and approval cards Chief sends you, your replies and the images you send, under Telegram’s own terms and privacy policy.
Independent recipients
These services are not our processors. Our servers send them no personal data; what they receive from your browser they handle under their own terms.
- Pexels: Stock photo search for visuals. From our servers Pexels receives only search words: a short phrase describing a scene, picked from your post by our AI provider and checked so that it holds no names, handles, email addresses or phone numbers; or your own stock keywords; or the words you type into the search yourself. Never your post text, and no account details. When you look at the results, your browser loads the photos from Pexels, which then sees your IP address and browser details, as with any image on the web.
Connected platforms
These services are not our sub-processors. You connect them with your own account, and FeedSquad sends or reads data only on your instruction: to publish what you approved, to read what you asked us to read, or to answer your AI assistant. What they do with that data is governed by your own agreement with them.
- LinkedIn: Publishing to your profile and the Company Pages you manage, and post and page analytics.
- X: Publishing, your posts and their metrics, replies and mentions, likes, reposts and bookmarks you make through FeedSquad, and public search.
- Threads: Publishing, post insights, and replies to your posts.
- Google and GitHub sign-in: Signing in to FeedSquad.
- Google Calendar: Read-only access to your calendar for Chief’s planning.
- WordPress: Publishing Cite articles to your site.
- Google Search Console and Bing Webmaster Tools: Read-only search data for your site, for Cite.
- AI assistants you connect (MCP): ChatGPT, Claude or another assistant you authorise receives your FeedSquad data in its answers to requests it makes for you (privacy policy section 6).
Changes to this list
Last changed: October 22, 2026.
Before we add a new sub-processor, we tell account owners by email or by a notice in the app at least 14 days in advance, and update this page. Under the Data Processing Agreement you can object to a new sub-processor on reasonable data-protection grounds during that period (DPA section 8).