Indexing is an asynchronous process so while the data won't be deleted as soon as the deletion API call returns, the data will be deleted shortly after. Usually

Indexing is an asynchronous process so while the data won't be deleted as soon as the deletion API call returns, the data will be deleted shortly after. Usually we're talking about hundreds of milliseconds or a few seconds. This is pretty much the same for all search-engines. Algolia also exposes a "task" API endpoint to check the state of an indexing operation and to be able to "wait" until the operation has actually been processed. This is for instance what is used in unit tests where we need to wait until the indexing operation has been processed to continue testing. Then for GDPR; if one of Algolia's customers receives a "personal data deletion" request on their side, it's of course their responsibility to forward it to Algolia using the deletion API (and a few seconds later it will be removed from all indices).