Customer app privacy

Information we use

Account and contact information

We collect your name, email address, password, account identifier and the phone number you provide. Business accounts can include a business name and account type. We use this information to create and secure your account, show your requests and orders, update your profile, and contact you about service. Passwords are stored as one-way hashes. The app keeps a sign-in token in the device’s protected credential storage so you can remain signed in.

Delivery and quote information

We collect pickup, drop-off and intermediate-stop addresses; shipment descriptions and weight; service and scheduling choices; handling instructions; and contact information you include for a delivery. We keep quote references, order identifiers, prices, delivery status, dates and payment status. Dispatch uses these details to review requests, arrange deliveries and respond to questions. Please provide another person’s contact details only when you are authorized to arrange the delivery.

Location and maps

If you choose “Use current location” and allow access, the app reads your foreground location to help fill in a pickup address. Address lookup uses your device’s location/geocoding service. On Android, address lookup may also require foreground location permission. Pickup and delivery coordinates can be included in a quote or booking. The customer app does not request background location tracking.

Address-lookup and road-pricing services process addresses and coordinates needed for those features. Our server uses Google Routes to calculate driving routes. The current Android release does not display a native map. Availability of address lookup and automatic pricing depends on the device and service configuration.

Payments

Where in-app checkout is available, Stripe collects the payment and billing details required for the payment method you choose. Card details entered in Stripe’s payment screen are sent to Stripe; our delivery API does not receive or store your full card number or security code. We retain transaction amounts, payment references, payment status and refund information linked to the order.

Stripe’s payment components also collect device characteristics and interactions for payment functionality, analytics and fraud prevention. The Android payment component can send authentication error reports to Stripe containing exception details, stack traces, app information, and device and operating-system information. Card authentication may share device information with the card network and issuing bank. A quote request by itself does not charge you.

If a payment screen offers Link and you choose to use it, Link is a separate Stripe service governed by its own terms and privacy policy. Available payment methods and required billing fields depend on the payment screen and the method you select.

Support and technical information

We use information you send to support to investigate and answer your request. Our hosting and web services receive connection information such as IP addresses, request paths, times, response codes and device/browser information. These records help operate the service, diagnose faults and prevent abuse. Avoid sending passwords, full card details or unnecessary sensitive information in delivery instructions or support messages.

Who receives information

• NYC Rapid Courier dispatch and assigned couriers: delivery addresses, necessary contact details and instructions are used to arrange and complete your delivery.
• Amazon Web Services: hosts our delivery API, database and website in the United States.
• Mapping providers: your device’s mapping/geocoding provider and Google Maps, when enabled, process information needed for address lookup, maps and routes. Their services may also process technical usage data.
• Stripe and payment participants: process checkout, authentication, fraud checks, payments, refunds and disputes where checkout is available.
• Support providers: when you contact us by email or phone, the communication services involved process your message or call information.

The customer app does not display third-party advertisements or include an advertising analytics integration. We do not sell customer app information to advertisers. Service-provider data handling may be subject to the provider’s own privacy policy, including its retention requirements.

Your choices

You can review and change your contact information under Account → Edit Profile. You can decline or revoke location access in your device settings. Features that need location or Android address lookup may then be unavailable; you can still enter addresses in a custom quote request for dispatch review.

You can sign out to remove the app’s saved sign-in token. Uninstalling the app does not delete your account or the records held by our service. Contact us to request access to, correction of, or deletion of your information. We may need to verify account ownership before acting on a request.

The intended audience is teens age 13 and older and adults. The app is not intended for children under 13. If you believe a child under 13 has provided personal information, contact us so we can review it. Service and payment requirements still apply to a delivery request.

Deletion and retention

Request account deletion in Account → Delete Account, or use our website even if you no longer have the app.

Request account deletion

What completed deletion removes

From the active app database, we remove or anonymize your profile and sign-in credentials, linked contact and quote data, delivery addresses and location details, and delivery instructions. Account access is disabled. Limited order identifiers, transaction amounts, payment references and status records remain for accounting, refunds and disputes. A minimal record of the deletion request is retained to support confirmation and recovery checks.

When a request needs review

An unfinished delivery, unresolved payment, stored file or linked payment account can require review before deletion completes. The request is saved with a reference number, and new app bookings and quote requests are blocked while it is pending. The service checks pending requests hourly. Contact support with the reference number for the outstanding steps and expected timing. Account deletion does not itself cancel a delivery or refund a payment.

We keep an internal deletion follow-up record to check whether payment-related review remains. It records the deletion request reference, review status, counts of linked payment records, reconciliation flags and check times. It does not contain names or contact details, but its reference can be connected to the original deletion request. These checks do not themselves erase records held by a payment provider. The follow-up record and its review history currently have no automatic expiry; contact us for the status of your request.

We keep private records of our review of deletion requests. These records include the request reference, review dates, status and reason codes, and a supporting case reference when one is available. They help us track follow-up and corrections. Supporting documents are kept separately. Recording a review does not itself confirm that a payment provider has deleted information. These review records do not yet have an automatic expiry schedule.

Payment-provider follow-up is handled separately by the business owner. We review the payment references associated with a deletion request and use the provider’s supported deletion or redaction process for eligible information. An unresolved refund, dispute, fraud-prevention requirement or other legitimate retention requirement can delay that step. We keep the follow-up open until the provider outcome or retention reason is documented. Contact us with your request reference for an update; completion of local account deletion alone does not mean that every provider record has been erased.

Backups, logs and other retained records

Account and delivery records remain in the active service until removed through the deletion process or another applicable record review. Completed account deletion does not immediately erase every older recovery copy, service log, support message or record held by a payment provider.

We keep a separate, encrypted archive of minimal deletion receipts to support deletion checks during recovery. It contains receipt identifiers, status and reason codes, and timestamps, rather than names, contact details or payment details. The archive is updated hourly, so a recent receipt may not yet be included. Recovery tools use these receipts to reapply deletion restrictions to restored data; older recovery copies still require controlled review before use.

Our database change logs are configured to expire after 30 days. Web logs rotate daily with up to 14 rotated archives; this is an archive count, not a guaranteed 14-day deletion deadline. On October 11, 2026, we adopted a records policy with manual review thresholds: 30 days for ordinary technical recovery copies, 90 days after routine support issues close, and seven years after the later applicable filing or payment date for financial supporting records. These are review thresholds, not automatic deletion deadlines. Existing recovery copies receive a full 30-day grace from adoption. Recovery copies remain protected until a usable replacement and deletion checks are verified; open matters, required financial records and legal or insurance holds can require longer retention. Filed tax returns and records with longer requirements are not covered by the seven-year review baseline. Older manual backups and server snapshots currently have no automatic expiry schedule. Contact us for the retained categories, reason and expected timing relevant to your request.

Security

The app’s API and the account-deletion website use HTTPS. Sign-in is required to access account data. Access to retained records is limited to operating and supporting the service.

Changes to this notice

We will update this page when the service or its information handling changes. The date above identifies the latest published version.