Sub-Processors

List Version: 2026-04-25

This page lists every third party that processes Personal Data on FeedSense's behalf, plus every third-party service our customers authorize via OAuth. It is the live source of truth for the tables that appear in our Privacy Policy and DPA.

When we add or remove a sub-processor, we publish the change here and email all paying customers using our existing customer mailing list. Customers may object to a new sub-processor on reasonable grounds within 30 days; see Section 5 of the DPA for the full procedure.

Core Sub-Processors

Vendors we engage directly to operate FeedSense.

Sub-ProcessorPurposeData CategoriesRegionTransfer Mechanism
RailwayCloud infrastructure: hosts backend, AI service, PostgreSQL database, and Redis cache
  • All application data
  • Customer admin accounts
  • End-user feedback
  • AI-generated insights and embeddings
United StatesSCCs
VercelHosting for the public marketing site (feedsense.co)
  • Visitor IP addresses (server logs)
  • Page request metadata
United StatesSCCs
CloudflareDNS, network edge, DDoS protection
  • DNS query metadata
  • Network-level connection metadata
GlobalSCCs
PaddleMerchant of Record: handles billing, payments, sales tax, refunds, and chargebacks globally
  • Customer admin email and name
  • Billing details
  • Payment metadata
  • Webhook event payloads (incl. source IP)
European UnionEEA-resident
ResendTransactional email delivery (account verification, invitations, password resets, sub-processor change notifications)
  • Recipient email address
  • Recipient name
  • Email subject and body
European UnionEEA-resident
OpenRouterRoutes AI inference requests to underlying LLM providers for feedback analysis, daily insights, and AI chat. Routing varies by request. See OpenRouter's documentation for current model providers and their data-handling posture (which differs by provider).
  • Sample feedback text submitted for sentiment / theme / keyword analysis
  • AI chat user prompts and retrieved feedback context
  • Insight generation context bundles
United StatesSCCs
MixpanelProduct analytics for the dashboard and marketing site (consent-gated; EU data residency endpoint)
  • Hashed user identifier
  • Page and feature event metadata
European UnionEEA-resident
Grafana Cloud (Loki, Faro, Prometheus)Application logs, metrics, and frontend Real-User Monitoring (consent-gated for Faro)
  • Backend application logs (may contain user identifiers)
  • Browser performance metrics
  • Frontend errors and traces
United StatesSCCs
SentryError tracking across backend, frontend, and AI service
  • Stack traces
  • User identifiers (when authenticated)
  • Request breadcrumbs
United StatesSCCs
BetterStackUptime monitoring and public status page
  • Service health metadata
  • Outbound heartbeat pings
European UnionEEA-resident
Google Analytics 4 (GA4)Marketing site analytics (consent-gated)
  • Pseudonymous visitor identifiers
  • Page interaction events
United StatesSCCs

Authorized Integrations (Customer-Connected Services)

Third-party tools FeedSense can read or write to only after a customer authorizes them via OAuth. Strictly speaking these are not sub-processors under GDPR Article 28 (the customer retains the relationship with the third party), but we list them here so the data flow is fully visible.

Sub-ProcessorPurposeData CategoriesRegionTransfer Mechanism
IntercomCustomer-authorized: ingests Intercom conversations as feedback when the customer connects the integration
  • Conversation messages
  • Conversation participants (id, email, name)
  • Tags
United StatesCustomer-Authorized
ZendeskCustomer-authorized: ingests Zendesk tickets as feedback when the customer connects the integration
  • Ticket subjects, descriptions, and comments
  • Requester identity (id, email, name)
United StatesCustomer-Authorized
SlackCustomer-authorized: ingests messages from monitored Slack channels as feedback (source) and posts cluster summaries / alerts (destination) when the customer connects the integration
  • Channel message content
  • Sender id and team metadata
  • Outbound notification content
United StatesCustomer-Authorized
Jira / AtlassianCustomer-authorized: posts AI-generated cluster summaries as Jira issues when the customer enables auto-rules
  • Outbound issue summary, description, labels, priority
United StatesCustomer-Authorized

How We Evaluate New Sub-Processors

Before engaging a new sub-processor, FeedSense applies the following review:

  1. Necessity check: the vendor must address a real operational need that cannot be met by an existing sub-processor. We do not add vendors speculatively.
  2. Security posture: the vendor must publish a Data Processing Agreement (or equivalent), have a documented breach-notification SLA, and publish at least one of: SOC 2 Type II, ISO 27001, or comparable certification. For smaller vendors without certifications we require a written security questionnaire response.
  3. Legal posture: the vendor's DPA terms must be no less protective than our DPA with our customers. We use the EU SCCs Module 2 where the vendor is outside the EEA / UK and there is no adequacy decision.
  4. Region and transfer mechanism: we document the vendor's primary processing region and the cross-border transfer mechanism (SCCs / Adequacy / EEA-resident) on this page.
  5. Customer notification: we publish the change here, increment the List Version, append a changelog entry, and email all paying customers via our existing customer mailing list at least 30 days before the new sub-processor begins processing Personal Data, except where an emergency security or legal requirement prevents the notice period (in which case we notify as promptly as practicable).
  6. Customer right to object: customers may object on reasonable grounds within the 30-day notice window. If we cannot accommodate the objection, the customer may terminate the affected services with pro-rata refund of any prepaid fees for the unused term; see DPA Section 5 for the full procedure.

An automated subscribe form and daily diff cron are on our roadmap. Until those ship, the manual customer email blast is our notification mechanism.

Changelog

  • 2026-04-25

    Initial published list. Documents all production sub-processors and customer-authorized integrations active as of this date.

    Added: Railway, Vercel, Cloudflare, Paddle, Resend, OpenRouter, Mixpanel, Grafana Cloud (Loki, Faro, Prometheus), Sentry, BetterStack, Google Analytics 4 (GA4), Intercom, Zendesk, Slack, Jira / Atlassian

Questions

For sub-processor questions, contact us at [email protected].