Sub-processors and Service Providers
Providers receive personal information only when the relevant service or feature is used. The provider inventory below is being reviewed for the iOS release; service configuration, data flows, processing locations, and contractual terms must be confirmed before this notice is published. A listing does not by itself establish that a data-processing agreement has been signed or that a particular region is configured. See the Data Processing Addendum for the applicable agreement terms.
Previously disclosed web-service providers, verify before publication
| Sub-processor | Purpose | Data processed | Processing region |
|---|---|---|---|
| Replit, Inc. | Application hosting and managed Postgres database | All operator and customer data stored by Roooster | Confirm from production configuration |
| Stripe, Inc. | Payments, Connect onboarding, and payouts | Operator + customer identity, payment method, charge metadata | Confirm from production configuration |
| Anthropic PBC | AI photo-to-quote vision pipeline | Photos and property descriptions submitted by operators or customers | Confirm from production configuration |
| Mapbox, Inc. | Geocoding and satellite tiles for dispatch + property lookup | Service addresses and approximate coordinates | Confirm from production configuration |
| Inngest, Inc. | Background job execution (reminders, AI agents, async work) | Job payloads referencing operator + customer identifiers | Confirm from production configuration |
| Resend | Transactional and marketing email delivery | Recipient email address, message content, delivery metadata | Confirm from production configuration |
| Twilio, Inc. | SMS delivery and inbound message webhooks (A2P-10DLC) | Phone numbers, message content, delivery metadata | Confirm from production configuration |
| Functional Software, Inc. (Sentry) | Server error tracking and diagnostics | Stack traces, redacted request metadata | Confirm from production configuration |
| PostHog, Inc. | Product analytics (opt-out available) | Page views, anonymized event metadata | Confirm from production configuration |
iOS launch provider checklist
These are expected mobile-service integrations, not a confirmation of deployed use or a completed vendor review. Confirm each integration, data flow, provider role, applicable agreement, and processing location against the released app configuration before this page is published as a current vendor register. Apple and Google may process information under their own service terms and may not act as Roooster sub-processors for every purpose.
| Provider | Expected role, if enabled | Potential data, verify against configuration | Region and role |
|---|---|---|---|
| Clerk | Authentication, if enabled in the released app | Account identifiers, sign-in and session data, and profile fields enabled by the configured sign-in methods | Confirm from production configuration |
| RevenueCat | Subscription status and entitlement infrastructure, if enabled | App user identifiers and subscription or entitlement status; exact receipt and transaction data flow requires confirmation | Confirm from production configuration |
| Expo / EAS | Mobile build and update infrastructure, if enabled | Build, diagnostic, and update-delivery metadata as configured; confirm whether any app or user data is processed | Confirm from production configuration |
| Apple App Store | iOS in-app purchases and, if enabled, Sign in with Apple | Apple manages App Store purchase processing; Roooster may receive subscription status or sign-in profile information as configured | Apple determines its service locations and role; verify applicable terms and disclosures |
| Google Sign-In | Account authentication, if enabled in the released app | Account identifier and profile fields authorized by the user and requested by the app | Confirm provider role and processing locations |
Change notifications
We use commercially reasonable efforts to update this page at least 30 days before adding a new sub-processor that processes personal data. To be notified when this page changes, email contact@roooster.ai with the subject "Subscribe: sub-processor updates".
Contact
Questions about a sub-processor or to object to a proposed addition: contact@roooster.ai.