Sub-processors

Linkeddit uses the third-party services below to deliver the product. This page lists every one that may process customer data, what it does, and where processing takes place.

Last updated 12 September 2026.

Infrastructure and storage

Sub-processorPurposeProcessing location
SupabasePrimary application database (PostgreSQL).United States
Google Cloud PlatformBackend compute (Cloud Run), job queueing (Cloud Tasks), secret storage (Secret Manager) and hosted model access (Vertex AI).United States (us-central1)
VercelWeb application hosting and edge delivery.United States

Measurement providers

Sub-processorPurposeProcessing location
OpenAIAnswer engine measured on your behalf, and the model used for classification tasks.United States
AnthropicAnswer engine measured on your behalf.United States
GoogleAnswer engine measured on your behalf, accessed through Vertex AI.United States
Perplexity (via Oxylabs)Answer engine measured on your behalf. Queries reach Perplexity through our retrieval provider rather than a direct integration.United States

Data retrieval

Sub-processorPurposeProcessing location
OxylabsRetrieves publicly available web pages and search results that appear as evidence in your reports.United States and European Union
ScraperAPIFallback retrieval provider, used only when the primary is unavailable.United States

Business operations

Sub-processorPurposeProcessing location
StripeSubscription billing and payment processing. Card details are handled by Stripe and never reach our systems.United States
ResendTransactional and product email delivery.United States
MailgunSecondary email delivery provider.United States

Analytics

Sub-processorPurposeProcessing location
PlausiblePrivacy-focused website analytics. No cookies, no cross-site tracking.European Union
Google AnalyticsWebsite analytics for marketing pages.United States

The Presell measurement tag

If you place our measurement script on a page you own, you are the data controller for your visitors and Linkeddit is your processor. The script adds no sub-processor beyond the ones listed above: it is served by Vercel, the endpoint it reports to runs on Vercel, that endpoint forwards to our backend on Google Cloud Platform, and the records are stored in Supabase.

It sets no cookie, collects no personal information, never stores a visitor IP address in any form, and stops before recording anything when a visitor sends Do Not Track or Global Privacy Control. Raw records are kept for 90 days. The full detail your own compliance review will want is in our privacy policy.

Changes to this list

We update this page when a sub-processor is added or removed. If you have a written agreement with us that requires advance notice of changes, contact team@om.linkeddit.com and we will add you to the notification list.