Modelcore Service Providers
Last updated: August 2, 2026
This list identifies material providers that may process customer or visitor information for Modelcore. A provider only receives the information needed for the relevant function.
| Provider | Function | Typical information |
|---|---|---|
| WorkOS / AuthKit | Authentication and identity | Email, name, profile, provider identifiers, session and security data |
| Vercel | Public site and web-app delivery; optional analytics and performance | Requests, IP and device data; optional usage and performance data |
| Railway | API, realtime service, and managed infrastructure | Account, project, request, log, and operational data |
| Cloudflare R2 | Object storage | Project snapshots, thumbnails, imports, and stored files |
| PostHog | Optional product analytics | Pseudonymous identifiers and allowed interaction events |
| Sentry | Error and performance monitoring | Error, stack, release, route, device, and limited application context |
| Resend | Transactional and waitlist email | Email, delivery status, source, and message metadata |
| Google Ads | Optional conversion measurement | Cookie/device, campaign, and conversion event data |
| OpenAI | User-invoked AI assistance | Prompt, selected project context, and generated response |
| Mapbox | Map tiles, search, and geospatial services | Requested location, map bounds, IP, and device/request data |
| OpenStreetMap / Overpass / Overture Maps sources | User-invoked site context | Coordinates, bounds, query, and returned public geographic data |
Provider roles, products, or hosting locations can change. Material changes are reflected here and in the Privacy Policy. Contact support@modelcore.app for questions.