Dear WPBay Review Team,

Please review Ordrivo RideFlow – Taxi Booking 7.2.58.

Safety alerts now store an explicit participant_source (customer, driver, or
dispatch) on both the alert and its permanent event, alongside the alert ID,
timestamp and coordinates. Personal-data export includes only panic events
whose recorded source is customer; the actor/login field is no longer used as a
proxy for the participant. Driver and dispatch safety details remain excluded
from the booking customer's export.

For pre-7.2.58 history, the exporter classifies the participant from the role
recorded in the immutable alert message. It does not rewrite or delete historical
events. Customer alerts remain exportable after acknowledgement and booking
archival because the panic event stays in the ride history.

The complete package includes version 7.2.58, updated changelog, regression
fixture, and staging checklist. The new WordPress export workflows were not run
in this packaging environment; the checklist records the requested guest,
signed-in subscriber, acknowledgement and archive acceptance scenarios.

Thank you for reviewing the corrected package.

Best regards,
Baris Beydogan
