Built For — website and Play Console content

Prepared October 5, 2026. 

Privacy policy — website draft

Built For Privacy Policy

Effective date: Oct 5, 2026
Operator: Built For (delivery)

Contact: stlnutritiondoc@gmail.com

Built For connects customers, merchants, and drivers for local orders and deliveries. This policy explains how we handle information when you use Built For.

Information we collect

We collect account and contact information, such as names, email addresses, phone numbers, account identifiers, and delivery or business addresses. We collect order details, purchase history, delivery instructions, favorites, order status, and transaction records.

We collect in-app messages, support requests, incident reports, and photos submitted for pickup or delivery verification. Photos can contain personal information or location details visible in the image. Please avoid including unrelated people or sensitive information in photos or messages.

Driver applications collect legal name, contact information, date of birth, home address, driver-license details, vehicle and registration information, insurance details, and eligibility attestations. Merchant applications collect business and representative information and may include the last four digits of a tax identifier. Verification services may process additional information when you separately provide it through their services.

We process driver earnings, payout status, payment and connected-account identifiers, and transaction information. Stripe processes checkout and payout-account setup. Built For does not store full payment-card numbers or full bank-account numbers entered into Stripe-hosted forms. Stripe handles that information under its own terms and privacy policy.

Our app and service providers may process technical information needed to operate the service, including network information, device or notification identifiers, and service logs.

Location and background tracking

With your permission, Built For uses location to display maps, identify nearby service areas and delivery opportunities, and verify pickup and drop-off locations.

For drivers who enable online delivery tracking, Built For collects location in the background, including when the app is closed or not in use, to support live delivery tracking, arrival detection, and nearby delivery offers. During an assigned delivery, location is made available to the assigned customer. Customers may see the driver's progress while the driver completes earlier stops in a bundled delivery. This does not require disclosing another customer's name or exact delivery address.

You can manage location permissions in Android settings. Drivers can go offline to stop background delivery tracking. Disabling location can limit delivery features.

How we use information

We use information to create and manage accounts, review driver and merchant applications, process orders and payments, dispatch and complete deliveries, provide tracking and notifications, verify pickup and delivery, calculate earnings and payouts, provide support, investigate incidents and disputes, prevent fraud, and meet legal obligations.

Who receives information

Customers, assigned drivers, and merchants receive information needed to fulfill their orders, communicate about delivery, and resolve order problems. Assigned customers receive delivery-tracking information. Support personnel may access relevant records to assist users and investigate reports.

We use service providers, including Supabase for backend services, Stripe for payment processing and payouts, Google Maps for maps and navigation, and notification and app infrastructure providers. Driver verification providers receive information when verification is enabled and requested. These providers process information under applicable agreements and their own policies where relevant.

We may disclose information when required by law, to address fraud or safety issues, or to protect legal rights.

Retention and deletion

We retain information for as long as needed to operate accounts and fulfill orders, and as necessary for payment reconciliation, tax and accounting obligations, safety investigations, disputes, fraud prevention, and legal requirements. We delete or de-identify information when it is no longer needed. To request deletion of your Built For account and associated information, email stlnutritiondoc@gmail.com with the subject “Built For account deletion” using your account's email address. We may verify your identity before processing the request. Do not send passwords, full payment-card numbers, or bank-account numbers. Some records may be retained for the purposes described above; we will explain applicable exceptions when responding. Uninstalling the app does not delete your account.

Your choices and security

You can update available account details, manage Android permissions, and contact us about access, correction, or deletion. We use access controls and secure connections to protect information. No service can guarantee absolute security.

Age and changes

Built For is intended for adults aged 18 and over. Age-restricted products, if offered, require additional eligibility checks and the applicable legal minimum age. We may update this policy and will publish the revised effective date. For privacy questions, contact stlnutritiondoc@gmail.com.

Separate public account-deletion page

Delete your Built For account

To request deletion of your Built For account and associated data, email stlnutritiondoc@gmail.com from your registered email address. Use the subject “Built For account deletion.” Identify whether your account is a customer, driver, or merchant account. Do not include your password or financial account numbers.

We may verify account ownership. We will delete or de-identify associated information that is no longer needed. We may retain records required for taxes, accounting, payment reconciliation, disputes, fraud prevention, safety investigations, or legal obligations. We will explain any applicable retention exceptions in our response.

Implementation requirement: add an in-app route for requesting deletion as well as this public page. Email instructions on a website alone do not satisfy both routes. Put the final public URL in Play Console; link the privacy policy within the app too.

App access / sign-in details

Select “All or some functionality in my app is restricted.” Supply separate entries for each role with actual working credentials.

Instructions draft — adapt to the actual review environment:
“Built For has customer, merchant, and approved-driver roles. Use the supplied accounts to access each role. The merchant and driver accounts are already approved. Customer: open Orders and select the seeded review order to inspect order details, tracking, and messaging. Merchant: open Orders to inspect the matching order, and open Locations to review address and phone editing. Driver: open Home to review the assigned delivery and Earnings to view bank and payout features. Enable location only when testing location-dependent features. Review does not require using a personal bank account or making a real payment.”

Do not provide admin credentials. Keep reviewer accounts working, reusable, and free of OTP or approval barriers. Seeded examples must not be represented as real live deliveries. Do not promise a review mode that does not exist.

Content rating questionnaire

Use the shopping/delivery category closest to the offered choices. Describe app-provided content separately from unrestricted user messages.

• User interaction / exchange of user-generated content: Yes — customers and drivers can exchange delivery-related messages; support and incident reporting also accept user submissions.

• Sharing user location with other users: Yes — assigned customers receive driver tracking.

• Purchases of physical goods/services: Yes, if asked.

• Alcohol: answer Yes to the relevant alcohol sale/reference question if alcohol listings or purchases are actually accessible in the submitted service. If no alcohol products or references are accessible, answer accordingly; planned capability alone is not an active catalog.

• Violence, sexual content, gambling, drugs, profanity, etc.: answer according to content actually supplied or accessible and the precise wording of each question. Do not automatically answer all No just because this is a delivery app.

• Reporting/blocking/moderation: only claim mechanisms actually implemented and usable.
  Google assigns the rating from the questionnaire; selecting an adult target audience does not dictate that rating.

Target audience

Select “18 and over” if Built For is intended only for adults. Website wording: “Built For is intended for customers, merchants, and drivers aged 18 and over. Age-restricted products require the applicable legal minimum age and verification.” Do not select child age groups or claim the app is designed for children.

Data safety — source-grounded starting point

Answer Yes to collection of user data. Declare all applicable roles and SDKs, not only the customer screen. The categories below are candidates supported by the available source and features; final required/optional and sharing answers require a complete integration audit.

Play categoryData in Built ForTypical purpose

Location: precise locationDriver tracking, arrival verification; customer/device location when transmittedApp functionality; fraud prevention/security for verification

Location: approximate locationCity/area location if separately transmitted or used by SDKsApp functionality

Personal info: name, email address, user IDs, address, phone numberAccounts, orders, role applicationsAccount management; app functionality

Personal info: Other infoBirth date, license/vehicle/insurance and verification application detailsAccount management; fraud prevention/security

Financial info: Purchase historyItems ordered and order/payment recordsApp functionality

Financial info: Other financial infoDriver earnings, balances, payout and settlement recordsApp functionality; fraud prevention/security where actually used

Messages: Other in-app messagesCustomer-driver/support messagesApp functionality

Photos and videos: PhotosPickup/drop-off photos and any uploaded evidenceApp functionality; fraud prevention/security

App activity: Other user-generated contentIncident reports, delivery instructions, submitted application content as applicableApp functionality; fraud prevention/security

App activity: App interactions / Other actionsFavorites and recorded delivery actions, if covered by these categoriesApp functionality

Device or other IDsPush notification tokens and identifiers processed by SDKsApp functionality

App info and performance: Diagnostics / Crash logsSelect only where transmitted by the actual app/SDK configurationDiagnose and operate the app, if applicable

Payment-card and bank-account numbers: do not automatically declare them as collected by Built For simply because Stripe collects them. Inspect whether Built For ever accesses them or whether Stripe collects them directly under its own terms. Purchase history and earnings remain separately declarable.

Collected vs shared: the privacy policy must describe real disclosures. Play's narrower “shared” field has exceptions for service providers and reasonably expected user-initiated transfers or qualifying consent. Evaluate each recipient and data type before choosing Yes/No; do not assume either “nothing is shared” or “every transfer is shared.”

Required vs optional: determine whether all users can decline that collection while using the app. Data required only for a particular role needs careful treatment in the global form. Do not mark every data type optional merely because users choose to register or order.

Ephemeral processing: stored orders, messages, delivery evidence, and retained location records are not ephemeral. Only choose ephemeral for flows proven to be memory-only and retained solely for the immediate request.

Encryption in transit: choose Yes only after verifying every app and SDK data flow uses secure transport. Supabase/Stripe HTTPS alone does not establish this for the entire app.

Deletion: describe the actual request process and exceptions. Do not claim completed automatic deletion or an in-app button before implementing and verifying it. Independent security review: do not claim one unless completed and eligible.