Sub-processors
Updated 26 May 2026
The federation runs on a small set of trusted partners. Each processes personal data on our behalf, under a Data Processing Agreement and, for transfers outside the EEA, Standard Contractual Clauses.
This page lists every sub-processor that touches user data across syntrociety.org, syfers.eu, people.syntrociety.org, lens.syfers.eu, compass.syfers.eu and chart.syfers.eu. We update it before any material change.
If you want to object to a new sub-processor we add, write to privacy@syntrociety.org within 30 days of the change.
Hosting and infrastructure
| Processor | Role | Location | Data | Used by |
|---|---|---|---|---|
| Vercel Inc. | Application hosting + edge runtime | US (global edge network) | All HTTP traffic, server logs | All federation surfaces |
| Supabase Inc. | Managed Postgres + Auth + Storage | EU (Frankfurt) | Account identity, application data | people, lens, compass, chart |
| Upstash Inc. | Rate-limit Redis | EU (Frankfurt) | Rate-limit keys (hashed) | people, lens, compass |
| Fly.io Inc. | Pandoc microservice host | EU | Document content in transit (no retention) | lens |
Communication
| Processor | Role | Location | Data | Used by |
|---|---|---|---|---|
| Plus.io Inc. (Resend) | Transactional + newsletter email | US + EU sending | Email address, message content, delivery events | syntrociety, people, lens, compass, chart |
Analytics
| Processor | Role | Location | Data | Used by |
|---|---|---|---|---|
| Plausible Insights OÜ | Cookieless analytics | EU (Germany) | Aggregated page-views, no persistent identifier | syfers.eu, syntrociety.org |
AI processing (lens only)
These processors only apply to lens.syfers.eu and only for documents the user's organisation has uploaded.
| Processor | Role | Location | Data | Used by |
|---|---|---|---|---|
| Anthropic PBC | LLM (document classification, translation, chat) | US | Document content, prompts, responses | lens |
| Voyage AI Inc. | Embeddings for search and retrieval | US | Document chunks | lens |
Payments
| Processor | Role | Location | Data | Used by |
|---|---|---|---|---|
| Stripe Payments Europe Ltd. | Card processing for Friends subscriptions and Lab billing | IE + US (fraud prevention) | Card data (PCI scope at Stripe), customer email, amount | syntrociety, compass |
Source control and deployment
| Processor | Role | Location | Data | Used by |
|---|---|---|---|---|
| GitHub Inc. | Source hosting; document commit target for lens and chart | US | Application code; for lens: document content + frontmatter; for chart: generated Markdown | All federation surfaces |
Transfers outside the EEA
Where data leaves the EEA, we use Standard Contractual Clauses included in each processor's Data Processing Agreement. We do not rely on consent for routine transfers.
Sub-sub-processors
Each processor above maintains its own list of sub-sub-processors (AWS for Supabase, Google Cloud for Plausible, etc.). We track those internally and notify of material changes that affect data residency.