App rejected - Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage

I want to clarify why both email and phone number are mandatory at registration, while still allowing users to log in with either method if one fails.

  1. Email Address (Collected at Registration)

Account Creation & Verification: We use email to establish a unique, verifiable account for each user. This prevents duplicate or fraudulent profiles.

Primary Communications: All booking confirmations, trip updates, support requests, and in-app chat messages between care seekers and carers are sent via email. This ensures users have a reliable record of every transaction and message.

  1. Phone Number (Collected at Registration)

OTP-Based Security: We send a one-time password (OTP) via SMS during registration and login. This SMS-OTP step is critical to confirm that the user owns the provided phone number and to safeguard against unauthorized account access.

Critical Trip Notifications: During a booked trip, carers and care seekers must receive time-sensitive alerts (e.g., gate changes, flight delays, check-in reminders) even if they’re not actively using the app. SMS ensures immediate delivery—even if a user’s internet connection is unavailable.

Support & Emergency Contact: If there’s an urgent issue mid-trip (e.g., a missed flight, sudden cancellation, or a medical concern), our support team can reach users directly via phone to resolve issues in real time.

  1. Flexible Login Options

Fallback Mechanism: If a user cannot access their email (e.g., server delay or no internet), they can request an OTP via SMS to log in. Conversely, if SMS delivery fails (e.g., network outage), they can choose to receive a OTP by email. This redundancy guarantees that users aren’t locked out due to a single point of failure.

We believe both email and phone number are directly tied to our app’s security model, communication requirements, and overall user experience. All collection and usage details are transparently disclosed in our Privacy Policy (https://b4t.com/legal/privacy-policy) and User Terms and Conditions (https://b4t.com/legal/user-terms-and-conditions).

The review team keeps rejecting the app, despite the fact that the login and registration workflows are identical to those in the previously approved build.

Thank you for your post. We believe we have resolved this issue. If you still need assistance, please contact us.

App rejected - Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage
 
 
Q