Skip to main content

Data Usage and Retention

Version: v1.0
Last Updated: June 6, 2026

This page describes, at a high public-policy level, how BookMaMe uses and retains operational data across the platform.

It complements the Privacy Policy by focusing more directly on the operational life of platform data.

Transaction and payment metadata​

BookMaMe may retain data related to:

  • orders
  • bookings
  • parcel delivery requests
  • payments and payment references
  • refunds
  • credits and vouchers
  • settlement and reconciliation records
  • invoice and offline-payment verification records where relevant

This data may be used for:

  • customer and partner support
  • accounting and finance operations
  • refund investigation
  • fraud prevention
  • reconciliation and audit
  • dispute resolution

Some of this information may need to be retained longer than visible customer-facing history because of finance, fraud, legal, tax, or audit requirements.

Location and fulfilment data​

BookMaMe may retain location and fulfilment-related data such as:

  • saved addresses
  • map-selected points
  • pickup and drop-off coordinates
  • delivery and routing context
  • delivery-task states
  • pickup, depot, retry, return, and handoff history

This data may be used for:

  • fulfilment and logistics operations
  • delivery-company selection and availability checks
  • delivery support and failed-delivery investigation
  • parcel sender and recipient flows
  • fraud or dispute investigation
  • service improvement and operational troubleshooting

We may keep some location and fulfilment records after a task is complete where those records are needed for support, finance, audit, compliance, or dispute purposes.

Support and dispute records​

BookMaMe may retain support and case-related records such as:

  • support case submissions
  • complaint details
  • uploaded screenshots or evidence
  • notes created by support, finance, or operations teams
  • dispute outcomes
  • escalation history

These records may be needed to:

  • resolve ongoing issues
  • investigate repeated patterns
  • support goodwill, refund, or policy decisions
  • maintain an audit trail of operational actions

Notification history​

BookMaMe may retain records of notifications and contact-channel usage, including:

  • in-app notification history
  • email-related operational records
  • SMS or other supported message-channel records where applicable
  • notification preference records

This may be used for:

  • customer and partner support
  • verification of whether a message or alert was triggered
  • operational audit
  • service troubleshooting
  • fraud, risk, and dispute investigations

Where the platform logs message attempts or provider responses, those logs may remain available for administrative review even after the customer-facing workflow is complete.

Delivery-task, logistics, and audit data​

BookMaMe may retain operational records for:

  • assignment and dispatch
  • confirmation PIN or handoff states
  • rider and delivery-company actions
  • depot and failed-delivery decisions
  • return and retry operations
  • administrative overrides or interventions

This information supports:

  • fulfilment integrity
  • complaint investigation
  • logistics auditing
  • finance and settlement linkage
  • policy enforcement

Onboarding, verification, and compliance records​

BookMaMe may retain records relating to:

  • partner onboarding
  • seller or participant verification
  • submitted documents
  • moderation and compliance decisions
  • suspension, restriction, or enforcement history

Retention of this information may continue where reasonably necessary for:

  • fraud prevention
  • auditability
  • re-review of suspicious patterns
  • legal, tax, customs, or compliance obligations

Deletion and retention limits​

BookMaMe does not necessarily delete every record immediately when:

  • an order is completed
  • a parcel is delivered
  • a support case is closed
  • an account is deactivated
  • a user requests deletion

Some records may need to be retained for:

  • accounting and reconciliation
  • tax and financial reporting
  • support and dispute history
  • fraud prevention and platform security
  • legal, regulatory, or compliance requirements
  • operational audit and investigation

Where deletion or minimization is possible, BookMaMe may reduce or remove data in line with platform policy, legal obligations, and operational needs.

Public-facing summary of retention logic​

At a high level:

  • customer-visible history and internal operational records are not always identical
  • some data may remain in internal systems longer than it remains visible in the app
  • records tied to money movement, logistics, disputes, moderation, or compliance may require longer retention than ordinary browsing activity

Review note​

This page is a public policy draft and should be reviewed by qualified counsel before broad production rollout.