Sub-processors

Register scope and verification status

This is the current source-based provider inventory, not proof that all supplier contracts, locations or transfers have been verified. Names below are service names; exact contracting entities and role allocation need contract review. See /privacy for Remi's controller/processor distinction and /dpa for authorisation and objections.

For every entry below: processing region, onward subprocessors, retention and applicable UK transfer safeguards are UNVERIFIED unless separately supported by reviewed customer due-diligence evidence. No UK-only, adequacy, IDTA, UK Addendum, training prohibition or zero-retention assertion is made.

Replit hosting and managed PostgreSQL

Purpose: application compute and database. Data: accounts, agency/property/contact data, maintenance and tenancy history, migration source metadata/rows/provenance, communications, billing references and audit/delivery records. Role: processor/subprocessor for Customer-controlled data; separate controller-service activities require review. Exact contracting entity, regions, retention and transfer route: UNVERIFIED.

Replit App Storage / Google Cloud-backed storage

Purpose: private files and photographs, migration originals and supporting documents/media where supported. Data: file bytes and metadata, which may contain multiple persons' information. Exact supplier chain, storage region, access/backup lifecycle and transfer safeguards: UNVERIFIED.

Replit AI Integrations and Anthropic

Purpose: text triage using Claude Haiku 4.5. Data: maintenance title/description and text-only triage context. Photographs are not currently submitted for AI assessment. Exact entities, processing locations, retention, training terms and transfer safeguards: UNVERIFIED. Previous 'primarily United States' wording is not retained as verified location evidence.

Clerk

Purpose: authentication, credentials, sessions and identity-provider integration as configured. Data: account identity/contact information, authentication identifiers, credential/session and security/device information handled by the enabled methods. Remi stores application identity references rather than local account passwords. Exact entities, processing roles, storage lifetimes, regions and transfer safeguards: UNVERIFIED.

Resend

Purpose: transactional and enquiry email delivery, provider delivery events and associated service logs. Data: recipient addresses/names, message content and delivery/account/API metadata. Processing roles, contracting entity, delivery and log locations, retention and transfer safeguards: UNVERIFIED.

Stripe

Purpose: subscriptions, checkout, billing portal and payment administration where approved and enabled. Data: agency/customer and billing references, subscription/invoice and payment information. Remi does not store card details. Stripe may have independent-controller activities for payment/regulatory purposes; not every Stripe activity is covered as Remi subprocessing. Exact entity, role allocation, region and safeguards: UNVERIFIED. This register does not activate billing.

Expo and downstream device push delivery

Purpose: contractor mobile push notifications. Data sent by implemented code: device push token, job title, property address, job identifier and deep link. Downstream Apple/Google push delivery, exact entities, roles, locations, retention and transfer safeguards require verification. Avoid sensitive details visible on a device lock screen.

Google Fonts

Purpose: remote typography resources on the public site and web app. The browser makes requests disclosing ordinary network metadata such as IP address. No optional tracking consent is inferred from loading a font. Exact provider controller role, resource/storage behaviour and transfer implications: UNVERIFIED. This is a recipient inventory entry, not an assertion that Google is a contracted Remi subprocessor for fonts.

Changes and objections

For relevant subprocessors, Remi gives at least 30 days' email notice before an intended addition or replacement. Customers may object on reasonable data-protection grounds within that period using hello@remi.properties; see /dpa for discussion, alternatives and unresolved objections. Verify contracts and transfer safeguards before approving affected processing.