Current Providers
| Provider | Purpose | Data involved |
|---|---|---|
| Stripe | Payment checkout, payment confirmation, tax calculation, billing records, and payment disputes. | Checkout session metadata, account or billing identifiers, transaction records, tax information, and payment-provider records. |
| Resend | Email delivery for account, form, access, and operational messages. | Email address, message metadata, delivery events, and message content needed to deliver the requested communication. |
| Production infrastructure providers | Hosting, storage, network delivery, logging, backups, abuse prevention, and security operations for genxis.com and gavel.genxis.com. | Submitted artifacts, receipts, account metadata, operational logs, IP addresses, user agents, request metadata, and service configuration. |
Foundation-model training
Submitted source or artifacts are not used to train foundation models unless a separate written agreement says otherwise. If a customer engagement requires a model provider or other specialized processor, that processor should be documented in the applicable order, DPA, or managed-onboarding terms before use.
Changes
We may update this page as providers change. Material service engagements can require additional provider disclosures in a written agreement.