Is there a more straightforward way to delete a nested path using cloud-functions?

I have the following code that proves to be really stable in deleting nested data from Firestore. However, I have a concern since it is using the Firebase token. I mean, is there a more straightforward way to eradicate nested collections using a cloud function ? or would you consider this to be a good solution. I am using this code when I user is deleting his account and due to some GPDR regulations, I need to make sure that no data are left and I don't want to use any extinctions.

<!-- begin snippet: js hide: false console: true babel: false -->

<!-- language: lang-js -->

// recursive delete function..

export const recursiveDeleteClients = functions
.runWith({
timeoutSeconds: 300,
memory: '512MB',
})
.https.onCall(async (data, context) => {
await firebase_tools.firestore.delete('data-personal-data/${context.auth?.uid}/nested-data/', {
project: process.env.GCLOUD_PROJECT,
recursive: true,
yes: true,
token: functions.config().fb.token, // firebase tools generated token
force: true,
});
return null;
});
<!-- end snippet -->

If you're worried about who can call this Cloud Function to delete data, consider implementing the security measure that is present in the code sample in the documentation on deleting collections on which the code you use is based:

exports.recursiveDelete = functions
  .runWith({
    timeoutSeconds: 540,
    memory: '2GB'
  })
  .https.onCall(async (data, context) => {
    // 👇 This part is missing in your code
    // Only allow admin users to execute this function.
    if (!(context.auth && context.auth.token && context.auth.token.admin)) {
      throw new functions.https.HttpsError(
        'permission-denied',
        'Must be an administrative user to initiate delete.'
      );
    }
    // 👆

    const path = data.path;
    console.log(
      `User ${context.auth.uid} has requested to delete path ${path}`
    );

    // Run a recursive delete on the given document or collection path.
    // The 'token' must be set in the functions config, and can be generated
    // at the command line by running 'firebase login:ci'.
    await firebase_tools.firestore
      ...