Who we share with.

A small, deliberate list. Each entry names what they do, what they get, and where they sit.

Subprocessors are the third-party vendors we use to deliver Felarity. We keep this list short on purpose. Every name below earns its place because we cannot reasonably replicate the function in-house, and because the alternative would compromise either reliability or cost in a way that would not serve you. When we add a new subprocessor, we notify customers thirty days in advance so you have time to object or migrate. To receive those notices, email subprocessors@felarity.com with the subject "subscribe", or write to hello@felarity.com and ask to be added to the subprocessor list.

Current subprocessors

The table below reflects every external service that may process customer data in the course of normal operation. If a vendor is not on this list, your data is not flowing through it.

Internal infrastructure

Almost everything that matters about Felarity runs on infrastructure we operate directly. The 30-specialist council, the 11-stage post-session pipeline, the 8-node SHA-256 Merkle attestation chain, Whisper large-v3 transcription, pyannote speaker diarization, contradiction detection, NLI re-scoring, and credibility-arc analysis all execute on our own hardware. We do not route your meeting content to a third-party LLM unless your workspace explicitly enables a BYOK integration listed in the table above.

That choice has a cost: we carry the operational weight of running our own GPU fleet, our own model weights, our own attestation chain. We carry it because it is the only way to honestly say what we say in the tagline. Private content stays on Felarity-operated infrastructure. Forensic outputs are signed by keys we control. The verification endpoint that confirms a report's integrity answers from our own servers, not a vendor's.

Sub-subprocessors

Several of the vendors above use their own infrastructure providers (for example, hyperscaler regions for compute and storage). Those relationships are governed by each vendor's own subprocessor disclosures, which we review before onboarding and re-review annually. We do not separately list sub-subprocessors here because doing so would imply control we do not have; the vendor's own list is the authoritative source.

Notification and objection

When we plan to add a new subprocessor, we send a notice to subscribed customers at least thirty days before that subprocessor begins processing customer data. The notice names the vendor, the purpose, the data category, and the location. Enterprise customers may object in writing during that window; if we cannot reasonably accommodate the objection, the customer may terminate the affected service with pro-rated refund of any prepaid fees.

Removals

When a subprocessor is removed from this list, we update the table and note the change in our trust changelog. Removal means the vendor no longer receives customer data; it does not retroactively delete data the vendor processed under their own retention terms, which is governed by the vendor's contract and any applicable DPA addenda.

Change subscription

To subscribe to subprocessor notifications, email subprocessors@felarity.com with the subject "subscribe". To unsubscribe, reply to any notification with "unsubscribe", or write to the same address. For all other trust and compliance questions, hello@felarity.com is the right address.

Last updated: June 7, 2026.