Atripb

Privacy Policy

Effective date: October 31, 2026.

AtripB Inc. ("AtripB," "we," "us") operates Atripb, a service connecting people who need to send eligible personal documents with travelers. This policy explains how we handle information in the mobile app and associated account, delivery, payment, verification, and support services.

For privacy questions or requests, contact support@atripb.com. Please do not send passwords, full payment details, or identity-document images by email.

1. Information we handle

• Account and profile: your name, email, phone number, account identifier and role, profile photo if supplied, password hash, verification and sign-in records, preferences, and agreement acceptance. Traveler setup may also include date of birth and residence or payout country.
• Trips and document requests: flight numbers, airports, travel dates and itinerary, pickup and destination addresses, saved addresses, document descriptions, availability, matching preferences, and request or trip status.
• Communications and delivery evidence: in-app messages, moderation records, support inquiries, reviews, issue reports, photos you submit, handoff confirmations, and timestamps. Submit only the evidence requested; avoid unnecessary document contents or unrelated personal information.
• Payment and payout records: amounts, currency, transaction references, payment/refund/dispute status, earnings and transfer records, connected-account identifiers, payout eligibility, bank name and last four digits where supplied by Stripe. Full card numbers and full bank credentials are collected by Stripe rather than stored in AtripB's application database.
• Identity verification: verification session references, status, attempt/check timestamps, and a protected value used to compare your verified name with your AtripB account name. See section 3.
• Location: addresses and flight locations associated with your requests or trips, and precise device location when you enable supported delivery-location sharing. See section 4.
• Device and service information: push notification tokens, device/platform information used for notifications and app operation, network and request information, and security or error logs produced while operating the service.

2. How we use information

The app also uses Stripe and map-provider software that collects device identifiers, app interactions, diagnostics, and performance information, such as component load times, to operate, secure, analyze, and improve those services. Google Maps on Android may process this information for Google’s own service-improvement purposes. These provider practices are described in their privacy notices; they are separate from optional delivery-location sharing. Atripb does not use these integrations for advertising tracking.

Provider notices: Stripe Privacy Policy and Google Privacy Policy.

We use information to create and secure accounts; find compatible requests and travelers; check flight and identity information; coordinate pickup, delivery, and recovery; show delivery updates; process payments and payouts; send service notifications; respond to support requests; investigate fraud, abuse, disputes, and safety issues; moderate in-app communications; and meet applicable legal and accounting obligations.

Verification, flight checks, and payment eligibility can affect whether you can accept a request or receive a payout. If a check appears incorrect, contact support so we can investigate. Identity verification does not establish ticket ownership or guarantee a delivery.

3. Stripe Identity, payments, and payouts

Stripe processes payments, traveler payout onboarding, and identity verification. During identity verification, Stripe collects the identity document and selfie that you provide and may use biometric processing to compare them, subject to the notices and choices shown in Stripe's verification flow.

AtripB sends a user identifier to associate the verification session with the correct account. Our backend retrieves verification results, including the verified name for comparison, and stores verification status and a keyed name-match value. It does not persist the Stripe ID images, selfie images, biometric templates, or a separate copy of the verified name in its identity-verification records. Your account profile still contains the name you supplied.

Stripe also processes information for its own legal, security, and fraud-prevention purposes. See Stripe's Privacy Policy and Stripe's identity-information guidance for its practices and privacy choices. Contact AtripB for assistance with a verification or deletion request; Stripe's own retention requirements may also apply.

4. Optional location sharing and device permissions

Live delivery sharing is optional and requires your permission and an active, eligible delivery session. When you start sharing during supported ground-delivery stages, AtripB collects precise coordinates, accuracy, capture time, and related location measurements to show the assigned delivery participants where the traveler is. If you grant background permission, updates can continue while the app is in the background. Authorized administrators can access delivery tracking for support and safety.

You can stop sharing in the app or revoke location permission in device settings. Revoking permission may prevent further updates; an offline stop request is sent to the server when connectivity returns. Server sessions also expire. Tracking does not itself confirm physical handoff or trigger payment.

The app can temporarily hold up to 100 recent location samples in encrypted device storage while uploads are pending. The server retains the latest accepted position rather than a continuous precise-location history. On ending or expiring a session, the application clears its current position and route; maintenance removes ended session metadata after seven days. Logs and backups are subject to the separate handling described below.

Map and address features use Google Maps/Places or Apple Maps, depending on the platform and configuration. Address searches are sent to the address provider. Where route estimates are enabled, current coordinates and the destination are sent to the routing provider to calculate the route.

Camera or photo access supports profile pictures and delivery/booking evidence, and Stripe may request camera access for verification. Notification permission enables push alerts. Optional device biometric sign-in uses the operating system's authentication mechanism; AtripB does not receive your fingerprint or device Face ID template. Stripe's selfie verification is a separate process.

5. Who receives information

• Other AtripB users: we display relevant profile, trip, request, and review information for matching. Assigned participants can access information needed to coordinate their delivery, including messages, handoff information, and permitted delivery tracking. In-app information should be used only for the delivery.
• Service providers: Stripe for payments, payouts, and verification; AWS for application/database hosting, operational logs, and email; Expo and Apple/Google push services for notifications; map/address providers; and flight-data providers such as AirLabs or AeroDataBox according to configuration. We send the information needed for the relevant service, such as a notification token and message or flight number and date.
• Authorized personnel: support and administrators can access information needed to resolve delivery issues, moderate abuse, review evidence, manage financial operations, and process privacy requests.
• Legal and safety recipients: information may be disclosed where required by law or reasonably necessary to protect people, investigate fraud, resolve disputes, or protect the service.

The reviewed app does not include advertising placements or an advertising-data sale feature. This policy does not authorize using private chats, location, identity evidence, or document contents for advertising.

6. Retention and account deletion

We retain account and service records while needed to provide the service and address outstanding deliveries, payments, disputes, security issues, and legal obligations. Retention varies by record type; deleting the app alone does not delete your account.

• Live tracking: current location/route data is cleared when a session ends or expires; ended session metadata is scheduled for removal after seven days.
• Private flight-booking uploads: uploaded images are encrypted, expire seven days after upload, and are scheduled for removal from the active database by maintenance. Superseded pending images may be removed earlier. Review status and operational records can remain.
• Identity evidence: Stripe holds the original verification evidence. Account deletion includes requesting redaction of the associated Stripe verification sessions and waiting for that process to complete.
• Account content: after a deletion request is verified and outstanding obligations are resolved, the deletion process removes or de-identifies profile information, saved addresses, document details, associated chats and uploads, location sessions, notification tokens, and other personal content in the active application database.
• Operational copies: the production application's ECS log group is configured for 30-day retention and automated database backups for seven days. Manual database snapshots, other infrastructure logs, and provider/support records have separate lifecycles and are included in the operator's cleanup review. These settings do not mean every copy of your data disappears within seven or 30 days.
• Exceptions: necessary financial or legally required records may remain with restricted access. The operator records the retention reason and a review date. A minimal deletion audit record can remain. Provider records, support mail, infrastructure logs, and backups require separate retention and cleanup review; application deletion does not instantly erase every external or backup copy.

Request deletion in Account → Delete account, through our public account-deletion page, or by contacting support. We verify the request using your account email. Our processing target is 30 days; outstanding deliveries, payments, disputes, legal holds, or provider cleanup may require additional handling. We send status or completion information and explain any recorded retention exception. Administrator accounts require separate offboarding.

7. Your choices and requests

You can update supported profile fields, manage notification preferences, stop location sharing, change device permissions, and request account deletion. Depending on your location and applicable law, you may have additional rights to access, correct, obtain a copy of, restrict, or object to processing of your information. Send requests to support@atripb.com. We may verify your identity before acting, and some requests may be limited by ongoing delivery, financial, security, or legal obligations.

Only supply another person's details when necessary for a lawful delivery and when you are authorized to do so. Avoid placing unnecessary sensitive information in chat messages, document descriptions, or delivery photos.

8. Security and international processing

We use HTTPS, authentication and role-based access controls, password hashing, and protected storage for sensitive application credentials and private booking images. No system can guarantee absolute security. Keep your credentials private and contact support about suspected misuse.

AtripB's production application and database are hosted in the United States. Our providers may process information in other countries under their applicable terms and privacy practices. Privacy laws may differ from those where you live.

9. Children and changes to this policy

Atripb is intended for adults aged 18 and older. If you believe someone under 18 has supplied personal information improperly, contact us so we can investigate.

We may update this policy as the service or its practices change. The published policy will identify its effective date. Where required, we will provide additional notice or obtain consent for material changes.

Contact: AtripB Inc., Delaware, United States · support@atripb.com