Marketplace Pilot

Vendor readiness register · September 2, 2026

Subprocessors

ProviderPurposeStatus
NetlifyHosting, server functions, database and media storage, deployment, logs, and delivery.Current
Auth0 by OktaUser authentication and session management.Current when sign-in is configured
OpenAIRequested AI-assisted listing and message generation.Optional; only when configured
Meta PlatformsSeller-authorized Facebook Page connection and Page Messenger events.Optional; approval and setup required
StripeSubscriptions and payments.Planned; not enabled
Sentry (Functional Software, Inc.)Error monitoring for app and server failures. Buyer names, messages, floors, emails and request bodies are removed before an error report leaves the app.Planned; active when configured
ResendTransactional account email, such as trial-ending and payment notices.Planned; active when configured
UptimeRobotUptime monitoring of the public health check. It receives no customer data.Planned; active when configured
Google or MicrosoftSeller-authorized calendar integration.Planned; not enabled
Comparable-data providerIdentification, comparable listings, and pricing research.Planned; not selected
Notification providerEmail, SMS, push, or webhook alerts.Planned; not selected

Launch requirements

Before production processing, Marketplace Pilot must document each vendor’s legal entity, location, data categories, retention, security, breach process, deletion support, data-processing agreement, and transfer mechanism. The final register should link provider privacy documentation and give required notice of material additions.

Seller-directed third parties

A seller-connected marketplace, calendar, or other service also processes information under its own terms and privacy policy. This register does not replace those independent notices.