Subprocessors

Roomiva · Version 2026-10-25.1 · Effective 25 October 2026

The companies that process personal data on our behalf to run Roomiva, what each one receives, and why. This list is compiled from the software's dependencies and configuration; a company that does not appear in the code is not on it. The operator ("we") is identified in the Operator details at the end of this document.

SubprocessorServiceWhat it processesLocation and transfer mechanism
Supabase, Inc.Authentication, database (PostgreSQL), private file storage; delivery of the sign-in link email through the mailer configured in our Supabase projectAccount identifiers, email address, sign-in links (transiently), session tokens, all database records listed in the Privacy Policy, uploaded photos and generated designsThe project region and the mailer are stated in the Operator details
Resend, Inc.Delivery of the sign-in link email, as the custom SMTP provider configured in our Supabase projectYour email address and the sign-in email (which contains the one-time link), transiently, for delivery and delivery logsSending region Tokyo (ap-northeast-1), from the verified sending domain send.roomivaapp.com; Resend's data-processing terms
Google LLC (Gemini API)Artificial-intelligence analysis of the photo, planning of each design, and the structural review of each generated design. On the free plan, Google's Gemini image model may also draw the design.The re-encoded photo, the design choices and the optional request text, and the generated designs for the structural review; when it draws a free-plan design, also the render instruction text. No account identifier, email or device identifier.Google's API processing locations; the service tier and its data-use terms are stated in the Operator details
OpenAI (Images API)Artificial-intelligence image generation of the design renders: the one call that draws each design on paid and trial plans (and on the free plan, unless Google's Gemini image model draws it)The re-encoded photo (and, for a refinement, the previously generated design together with the photo) and the render instruction text, which contains the design choices and the optional request text. No account identifier, email or device identifier.United States by default (OpenAI's regional processing is not configured for our account). Processed under OpenAI's API data-usage terms: content sent to the API is not used to train or improve OpenAI's models unless the customer opts in, and we have not; logs kept for abuse monitoring, which may contain the photo and the instruction text, are retained for up to 30 days unless a longer period is required by law; an image OpenAI's classifier flags as child sexual abuse material is retained for manual review. OpenAI offers zero data retention only on prior approval, which we have not applied for. The contracting entity and the agreement status are stated in the Operator details
RevenueCat, Inc.Subscription management: receiving purchase events from the stores and reporting entitlement statusYour app user identifier (the same random identifier as your account), purchase and subscription events from the storeRevenueCat's regions; see RevenueCat's privacy documentation
Apple Inc. (App Store)Distribution, payment and subscription billing on iOSYour Apple account and payment details, under Apple's terms — none of which reach usApple's regions
Google LLC (Google Play)Distribution, payment and subscription billing on AndroidYour Google account and payment details, under Google's terms — none of which reach usGoogle's regions
Render Services, Inc.Runs the API server, the background worker and the daily retention job (render.yaml: three services in the Frankfurt region); holds the server request logsRequest logs (request id, route, status, timing, network address, credentials redacted); data in transitFrankfurt, Germany (EU). Log retention is stated in the Operator details
Expo (650 Industries, Inc.) (Expo Application Services)Build tooling for the app binaries (EAS Build), and the Expo push service, which issues the push token for an installation of the app and passes each notification on to the platform's delivery serviceThe Expo push token for the installation, the platform, and — for each notification — its title, text and the in-app link it opens. No photo, design, email or account identifier. The build service compiles the app; no over-the-air update service is installed.United States; Expo's privacy policy and terms of service
Google LLC (Firebase Cloud Messaging)Delivery of push notifications to Android devices, from Expo's push service to the phoneThe push registration token for the installation and the notification's title, text and in-app link, transiently, for delivery. No photo, design, email or account identifier.Google's regions, under Google's Firebase data-processing terms

Notifications on Apple devices would be delivered by Apple Push Notification service; there is no iOS app today, and this list will be updated before one is released.

Not used: no content-delivery network, no analytics provider, no crash-reporting provider, no advertising network, no customer-messaging or marketing-email provider, no data broker. Offers and tips are sent only through the push service above, and only to people who turned that switch on.

Changes

When we add or replace a subprocessor we update this document, bump the version at the top, and show the new version in the app. Where the law where you live requires us to give you a chance to object to a new subprocessor, we will do so by the notice methods described in the Privacy Policy.

Operator details

The Supabase project region, the server log retention period, the AI providers' terms and data use (the Gemini API service tier and its data-use terms; the OpenAI API terms and contracting entity that apply to our account), and the status of our data-processing agreements are published below.