Prooflytics
— Sub-processors

Who else touches your data.

Every third party we rely on to run Prooflytics, what each is used for, and what actually reaches it. If a service is not on this page, your data does not go there.

The list

Running the product

ServiceWhat it doesWhat reaches it
ClerkAuthentication, workspace and team managementName, email address, sign-in metadata
StripeSubscription billing and payment processingBilling contact, payment method (held by Stripe, never by us)
VercelApplication hosting and deliveryRequest metadata for every page and API call
InngestBackground job scheduling and executionJob payloads referencing workspace records
Cloudflare R2File storage for generated reportsReport documents produced for your workspace

Reading your data

ServiceWhat it doesWhat reaches it
NangoConnector infrastructure for the integration catalogueOAuth credentials and the records each connector syncs
AnthropicThe language model behind briefings, recommendations and the assistantPerformance metrics and account context sent with each request
ApifyCompetitor advertising researchCompetitor domains you ask us to track — no customer data

Operating and support

ServiceWhat it doesWhat reaches it
ResendTransactional email deliveryRecipient address and message contents
SentryError monitoringStack traces and request context on failures
PostHogProduct analytics and session contextIn-product events tied to a user identifier

How this list changes

Every service above is bound by a data processing agreement and may not use your data for anything beyond delivering its service to you.

We notify customers before adding a sub-processor that receives customer data. Subscribe to notices →

The processing terms behind this list — our Article 28 commitments, transfer safeguards and the sub-processor change procedure — are in the Data Processing Addendum. For a countersigned copy made out to your legal entity, email privacy@prooflytics.io.