Account and profile data
We process account details, role, profile information, provider categories, service areas, languages, subscription status, and moderation status to run the marketplace.
Legal placeholder
Privacy Notice
This draft notice explains the main data categories needed to operate a local-services marketplace, provider verification, matching, messaging, and support.
Draft updated May 31, 2026. Requires local legal review for every active launch country before production launch.Verification data
Provider KYC may include legal name, date of birth, nationality, identity document information, uploaded files, selfie, address, tax residency, consent records, review notes, and verification status. Access to this data should be limited to verification, trust and safety, legal, and support workflows.
Location and task data
We process task addresses, city, arrival pins, destination pins where relevant, category, budget, messages, events, provider availability, and live task location where needed for matching, tracking, support, and safety. Live location should be used only for relevant active tasks and should not be presented as permanent monitoring.
Device and language data
The app may use browser or device language preferences to select an interface or speech-recognition language. The app may also process device, browser, push-notification, and install-state information to provide security, app functionality, and provider alerts.
Payments and subscription data
Provider subscription billing is handled through Stripe. Remdo stores subscription status, Stripe customer identifiers, subscription identifiers, price identifiers, and billing event status needed to operate marketplace access. Remdo does not store customer task payment funds in the MVP model.
International transfers and processors
Remdo may use infrastructure, payment, email, push, analytics, storage, support, and verification providers that process data across borders. The final production policy must identify processors, transfer mechanisms, retention periods, and country-specific privacy rights before launch.
Retention and requests
Users can export account data and submit export or deletion requests from the account privacy page. A production privacy policy must still define retention periods, legal bases, processors, and cross-border transfer details before public launch.
Draft status
This notice is a product and engineering draft. It must be reviewed for every active launch country, including data protection, consumer, electronic communications, identity verification, and location-data requirements.