Quaggaby Q Sales

Subprocessors

The companies Matthew Maus uses to run Quagga, what each one does, and what data reaches it.

VendorPurposeData it receivesLocation
RailwayApplication hosting: API and databaseAccount data, workspace settings, pipeline notes, unlock and billing recordsUnited States
VercelWeb application hosting and deliveryPages you request, IP address, session cookieUnited States, global edge
Cloudflare R2File storageCourt filings bought from PACER, profile pictures, sample dockets you uploadUnited States
StripePayments and subscriptionsBilling contact, payment method (held by Stripe; card numbers never reach us), invoicesUnited States
ResendTransactional emailName, email address, the content of invitations, alerts and receiptsUnited States
SentryError monitoringError reports, which can include user ID, URL and browser detailsUnited States
AnthropicLanguage model that drafts briefsPublic docket text and public court filings. No customer account data is sentUnited States
Free Law Project (CourtListener)Source of public docket dataThe docket queries we make. No customer dataUnited States
PACER (Administrative Office of the U.S. Courts)Source of public dockets and filingsThe docket and document requests we make under our own PACER account. No customer dataUnited States