← Security

Subprocessor List

Draft — pending legal review, particularly the change-notification commitment below.

A subprocessor is any third party that processes customer data on ExposureIQ's behalf. This list reflects what's actually integrated in the codebase, not a generic template.

SubprocessorPurposeData involvedLocation
SupabaseDatabase (Postgres), authentication, hosting for all application dataAll customer/account/organization/asset/finding dataap-south-1 (Mumbai, India)
VercelApplication hosting, serverless function execution, edge networkNothing persisted independently — serves the app and executes Server Actions, which then talk to Supabase; function logs may transiently include request metadatabom1 (Mumbai, India) for application functions; Vercel's own edge network and logging follow Vercel's terms
ResendTransactional email delivery (alert notifications, sign-up confirmation)Recipient email addresses and alert content (finding titles/summaries — no raw scan data)Per Resend's own infrastructure
ScreenshotOneOptional asset screenshot capture (only when a user requests a screenshot of a discovered asset)The public URL of the asset being captured; the screenshot image is returned to ExposureIQ and stored in SupabasePer ScreenshotOne's own infrastructure

Public data sources queried

Not subprocessors in the traditional sense — no customer data is sent to them.

SourcePurposeWhat's sent
CISA (KEV feed)Vulnerability intelligenceNothing — a public feed is fetched, nothing about your organization is sent
NVDCVE enrichment (CVSS, descriptions, affected versions)CVE identifiers only
FIRST / EPSSExploit-probability scoringCVE identifiers only
crt.shSubdomain discovery for authorized domainsThe domain name being assessed (already public via certificate transparency)
Cert Spotter (SSLMate)Second certificate-transparency source for subdomain discovery of authorized domainsThe domain name being assessed (already public via certificate transparency)
Cisco security advisories (CSAF)Vendor advisories for Cisco products, including affected releases and any exploitation Cisco statesNothing — a public feed is fetched, nothing about your organization is sent
GitHub Advisory Database (malware advisories)Packages reported as malicious, matched against dependencies you declareNothing about your organization: the newest public advisories are fetched; your declared dependencies are never sent
Public Telegram channels (web preview)Early-warning leads reviewed by the operator only; never shown to customers as posts and never treated as evidenceNothing about your organization - one fetch per channel per day
CISA advisories feedThreat intelligence: government security advisoriesNothing — a public feed is fetched, nothing about your organization is sent
UK NCSC feedThreat intelligence: government publicationsNothing — a public feed is fetched, nothing about your organization is sent
Microsoft Security Blog feedThreat intelligence: vendor threat researchNothing — a public feed is fetched, nothing about your organization is sent
The Hacker News feedThreat intelligence: security news reportingNothing — a public feed is fetched, nothing about your organization is sent

These are called directly by our server-side code with only public, non-identifying query parameters — no organization name, no customer identity, no account information is ever transmitted to them.

Notification of changes

We intend to notify customers before adding a new subprocessor, with an opportunity to object. The specific notice period and process hasn't been finalized yet — see the Data Processing Agreement, currently in legal review.