Mero Rides Legal

Mero Rides QA Privacy & Permissions Checklist

This checklist is primarily for internal QA and release review, and complements the public-facing privacy documentation.

Overview

Please read this policy carefully. It explains how the Mero Rides rider and driver apps work with your data and safety.

This Quality Assurance (QA) checklist is intended for engineers, designers, and testers working on the Mero Rides rider and driver apps. It helps ensure that runtime permissions, privacy dialogs, and data usage explanations match what is documented in our legal policies and in store disclosures.

1. Location Permissions

  • Verify that the apps request precise and/or approximate location only when needed, with clear in-app rationale screens (for example, onboarding slides and inline tooltips).
  • Confirm that background location is requested only in flows that truly require it (active trips, drivers online) and that we explain why background access is needed.
  • Ensure that disabling location in system settings results in graceful degradation and that users are guided back to settings if full functionality is required.

2. Permissions For Notifications & Contacts

  • Check that push notifications are requested with a clear explanation of what we send (trip updates, safety alerts, account messages) and not for unrelated marketing without consent.
  • If emergency contacts or contact book access is ever introduced, verify that:
    • The user sees a clear explanation before the OS prompt.
    • Only the necessary data is accessed and stored.
    • Users can view and update or remove emergency contacts later.

3. Privacy Policy & In-App Links

  • Confirm that the Mero Rides Privacy Policy and Terms of Service are linked from app onboarding, settings, and any relevant permission dialog flows.
  • Ensure that links to this web-based legal center (/mero-rides/legal) are correct and that policies render consistently on mobile browsers.

4. Account Deletion & Data Requests

  • Test in-app "Delete account" flows (where implemented) for both rider and driver apps.
  • Verify that the web request form at /mero-rides/legal#request-form is accessible and works on mobile, with appropriate validation and confirmation text.
  • Check that help text matches the Data Deletion & Account Closure Policy.

5. Store Metadata Consistency

  • Before each release, compare the behaviour of the apps against the App Store and Google Play privacy questionnaires to ensure answers remain accurate.
  • If new data types are collected (for example, new analytics events, new sensors), update the data inventory and re-run this checklist.

6. Logging & Debug Builds

  • Confirm that debug-only logging of sensitive information (tokens, personal identifiers) is stripped or disabled in production builds.
  • Verify that any feature flags or staging endpoints are not accidentally shipped to the production app store builds.

This checklist is a living document. As the apps evolve, update these items so that QA and reviewers always have a single source of truth for privacy and permissions behaviour.