Legal

Third-party processors

Match My GC uses specialized service providers to deliver core platform functionality. This page summarizes each provider's role.

Last updated: June 20, 2026

Clerk

Authentication, user account lifecycle, and session management.

Data categories: Account identifiers, authentication events, and account state metadata.

Required: Yes

Supabase

Primary database and private document storage.

Data categories: Profile records, onboarding fields, verification records, and stored documents.

Required: Yes

Didit

Identity and business verification workflows.

Data categories: Verification session identifiers, submitted verification fields, and outcomes.

Required: Yes

Stripe

Payment processing for optional paid feature flows.

Data categories: Checkout/payment identifiers, transaction metadata, and payment status.

Required: No (feature-dependent)

CloakBrowser

Browser automation runtime for anti-bot-protected verification checks.

Data categories: Verification run metadata and data entered/read during verification flows.

Required: No (feature-dependent)

Mapbox / Google Maps

Optional geocoding for location normalization.

Data categories: Address/location inputs and geocoding response metadata.

Required: No (feature-dependent)

Related policy pages