This worldwide summary is designed to keep Baroow's App Store privacy details, Google Play Data Safety declarations, and Privacy Policy aligned. It lists possible data categories across active and future feature-gated capabilities. Baroow must disclose only what the released app and enabled third parties actually collect, but must never omit a category that is collected in production.
Last updated: July 29, 2026 · Version: 2026-07-29-global-1 · Worldwide baseline · Barbados home jurisdiction
Baroow must not submit Apple App Store or Google Play privacy answers that understate the data categories, purposes, sharing, tracking, or security practices described in this page and the Privacy Policy.
| Category | Examples | Apple label mapping | Google label mapping | Linked | Shared | Purposes |
|---|---|---|---|---|---|---|
| Contact information | Name, email address, phone number, delivery or service address, support contact details. | Contact Info | Personal info | Yes | Yes, where needed for account operation, transactions, delivery, support, insurance, safety, or legal compliance. | App functionality, account management, developer communications, safety, fraud prevention, compliance, marketing with consent. |
| Identifiers | Account ID, user ID, device or browser identifiers, push notification tokens, referral or campaign identifiers. | Identifiers | Device or other IDs | Yes | Yes, with service providers for authentication, analytics, security, notifications, and fraud prevention. | App functionality, analytics, fraud prevention, security, compliance, account management. |
| Location | Precise location when permitted, approximate location, saved addresses, pickup/dropoff/service locations. | Precise Location, Coarse Location | Location | Yes | Yes, with maps, delivery, booking, service, safety, and fulfilment providers where required. | App functionality, delivery, booking, meetup coordination, safety, fraud prevention, personalisation. |
| User content | Listings, photos, videos, reviews, ratings, bios, support messages, dispute evidence, uploaded documents. | User Content | Photos and videos, Files and docs, Other user-generated content | Yes | Yes, with counterparties, vendors, service providers, moderators, regulators, or law enforcement where required. | App functionality, marketplace publishing, moderation, dispute handling, support, fraud prevention, compliance. |
| Messages | In-app chat, offer negotiation, booking coordination, report text, moderation records. | Emails or Text Messages / Other User Content | Messages | Yes | Yes, with message infrastructure, moderation, support, safety, and legal processors where required. | App functionality, transaction coordination, safety moderation, fraud prevention, legal compliance. |
| Purchases and transactions | Only where a transaction feature is active: orders, bookings, tickets, refunds, chargebacks, holds, wallet activity, or payout status. | Purchases, Financial Info | Financial info, Purchase history | Yes | Only for an active feature, with the disclosed payment or payout provider, vendor, insurer, regulator, tax authority, or support provider where required. | Enabled transactions, refunds, permitted holds, payouts, tax reporting, fraud prevention, compliance, and support. |
| Financial and payout information | Only where enabled: vendor payout details, bank or settlement records, premium or payment status, and limited processor events. | Financial Info | Financial info | Yes | Yes, with payment, banking, insurance, tax, compliance, and audit partners where required. | Enabled payouts, settlement, authorised insurance facilitation, accounting, tax, AML, fraud prevention, and compliance. |
| Identity, verification, and compliance data | Government ID, selfie, proof of address, business registration, licences, insurance certificates, handoff ID scans. | Sensitive Info, User Content, Other Data | Personal info, Files and docs, Other info | Yes | Yes, with identity verification, insurance, safety, compliance, regulator, and law enforcement parties where required. | Verification required by an active feature, trust and safety, authorised insurance eligibility, regulatory compliance, fraud prevention, and disputes. |
| Health-sensitive and regulated content | OTC pharmacy orders, health-related search terms, product safety complaints, allergen or dietary notes submitted by users. | Health, Sensitive Info, Search History, User Content | Health and fitness, App activity, Other user-generated content | Yes, when submitted or tied to an account transaction. | Yes, with pharmacies, restaurants, support, regulators, health authorities, or emergency services where required. | Order fulfilment, safety review, product support, legal compliance, user-requested service delivery. |
| Search, app activity, and preferences | Search terms, viewed listings, taps, favourites, saved preferences, referrals, feature usage, session activity. | Search History, Usage Data | App activity | Yes | Yes, with analytics, fraud prevention, personalisation, and service-quality providers. | Analytics, app functionality, personalisation, search quality, fraud prevention, marketing attribution with consent. |
| Diagnostics and performance | Crash data, performance events, device type, operating system, browser type, technical logs. | Diagnostics, Identifiers | App info and performance, Device or other IDs | Sometimes, where needed to troubleshoot account-specific issues. | Yes, with hosting, reliability, analytics, security, and support providers. | App functionality, diagnostics, security, fraud prevention, service improvement. |
| Audio and voice input | Voice-search input or transcript where voice search is used. | Audio Data, Search History | Audio files, App activity | Yes, if submitted while signed in or tied to a transaction. | Yes, with contracted service providers where needed to process the requested feature. | App functionality, search assistance, safety filtering, service improvement. |
Deletion: Users may request access, correction, deletion, restriction, portability, or objection through the Privacy Policy contact routes. Records are retained only where an actual feature, transaction, dispute, safety need, fraud review, tax rule, AML rule, insurance obligation, or other legal requirement justifies retention.
Security: Baroow uses contractual, technical, and operational controls intended to protect personal data against unauthorised access, disclosure, alteration, or misuse.
Children: Baroow is restricted to users aged 18 or older. We do not knowingly allow registration by minors.