Dear WPBay Team,

Ordrivo RideFlow 7.2.53 addresses the privacy-erasure batching finding.

The eraser now deletes at most 100 matching rides per callback and returns done=false while more eligible records remain. It continues querying from the first page, avoiding offset skips after deletions. A failed ride is tagged with the current erasure run token so later callbacks can move past it without repeatedly retrying it or maintaining an unbounded exclusion list. The failure count is reported; a fixed 1,000-ID fallback is used only if a failure marker cannot be saved. A new erasure run uses a new token, so a previously retained ride can be retried.

The package includes an updated changelog, version metadata, a source regression check, and a staging checklist for multi-batch deletion and failed-record handling. Live WordPress erasure workflows are documented for staging and are not claimed as completed here.

Best regards,
Baris Beydogan
