Account and profile data
We process account details, role, profile information, provider service descriptions, AI matching signals, service areas, languages, subscription status, and moderation status to run the marketplace.
Legal
Privacy Notice
This notice explains the main data categories needed to operate a local-services marketplace, provider verification, matching, messaging, and support.
Updated June 5, 2026.Verification data
Provider identity checks are external-first. Remdo should not store identity document files or selfies in the main application; the verification provider keeps those records where required. Remdo stores only the provider name or account reference where needed, external session or check identifiers, verification status, timestamps, review notes, and consent records for marketplace trust and safety.
United States verification boundary
For United States operations, Stripe Identity may be used as the external verification provider. Remdo stores verification session identifiers, status, timestamps, and review metadata only, not local identity document files or selfies.
Montenegro verification boundary
For Montenegro operations, Stripe Identity remains the external verification model unless a country approval record requires another provider. Remdo should store only external session or check identifiers, verification status, timestamps, and review metadata, not local identity document files or selfies. Montenegro privacy, transfer, consent, and retention requirements are recorded in the approved launch package.
Location and task data
We process task addresses, city, arrival pins, destination pins where relevant, AI matching signals, 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.
United States location notice
For United States operations, precise location and live tracking are limited to task matching, arrival-point accuracy, provider availability, active task coordination, safety, and support. The product keeps controls for sharing precise location and does not present live location as permanent monitoring.
Montenegro location notice
For Montenegro operations, precise location and live task tracking are limited to marketplace matching, arrival-point accuracy, provider availability, active task coordination, safety, and support. Remdo should not use live location as permanent monitoring, and Montenegro retention periods and user-rights text are maintained in the approved privacy launch record.
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
Web provider subscription billing is handled through Stripe. Native iOS and Android provider subscriptions use App Store or Google Play billing when native store products and verification are connected. Remdo stores subscription status, web Stripe customer identifiers, store transaction or subscription identifiers, price or product identifiers, and billing event status needed to operate marketplace access. Remdo does not store customer task payment funds in the current direct-payment 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 from the account privacy page and submit account deletion requests from the dedicated account deletion page. Remdo defines retention periods, processors, transfer details, and country-specific privacy rights in its operational privacy program.
United States state privacy trigger
For United States operations, Remdo monitors state privacy-law thresholds, including California privacy requirements, before scaling. The public notice is updated if thresholds are met or if an operating state requires additional rights, notices, processor terms, or data-retention disclosures.
Montenegro privacy authority
Montenegro privacy preparation uses the Agency for Personal Data Protection and Free Access to Information as the regulator source target. The approved Montenegro Privacy Notice covers controller/processor roles, cross-border processors, data-subject requests, precise location, Stripe Billing, Stripe Identity metadata, and retention-period controls.
Country review and approval
Country-specific privacy records are maintained in the Remdo admin launch board. The United States privacy notice includes data-minimization, precise-location, Stripe Billing, Stripe Identity metadata, state privacy threshold, processor, retention, and user request boundaries based on official FTC and California Privacy Protection Agency source checks. Montenegro privacy wording is approved from official AZLP and Montenegro government source checks with operator-confirmed counsel approval recorded on June 3, 2026.