Dear WPBay Team,

Ordrivo RideFlow 7.2.52 addresses both review items.

1. Dispatch ETA replacements and customer responses now share a per-ride database lock. Each estimate has a unique revision marker, and the tracking page submits the revision shown to the customer. A stale response receives HTTP 409 after a replacement. ETA metadata writes are verified, cancellation status is checked before success is returned, and cancelled rides show no pending response controls.

2. RideFlow settings now include a capability- and nonce-protected “Remove saved key and disable Google route estimates” checkbox. Saving it removes the stored key. The existing blank-means-keep behavior remains; without a key, public route estimation exits before making a Google request and ride bookings remain available with the fare confirmed by dispatch. The README and settings description document this control.

The package includes the updated 7.2.52 changelog and a manual verification checklist for the race and key-removal scenarios.

Best regards,
Baris Beydogan
