Catch up on everything announced at Firebase Summit, and learn how Firebase can help you accelerate app development and run your app with confidence. Learn More

Using the Delete User Data extension

Stay organized with collections Save and categorize content based on your preferences.

The Delete User Data extension (delete-user-data) lets you delete a user's data when the user is deleted from your Firebase project. You can configure this extension to delete user data from any or all of the following: Cloud Firestore, Realtime Database, or Cloud Storage. Each trigger of the extension to delete data is keyed to the user's UserId.

This extension is useful for respecting user privacy and fulfilling compliance requirements. However, using this extension does not guarantee compliance with government and industry regulations.


Install the extension

To install the extension, follow the steps on the Install Firebase Extension page. In summary, do one of the following:

  • Firebase console: Click the following button:

    Install the Delete User Data extension

  • CLI: Run the following command:

    firebase ext:install firebase/storage-resize-images --project=projectId-or-alias

During the installation of the extension, you will be prompted to specify a number of configuration parameters:

  • Cloud Functions location:

    Select the location of where you want to deploy the functions created for this extension. You usually want a location close to your database. For help selecting a location, refer to the location selection guide.

  • Cloud Firestore paths:

    Which paths in your Cloud Firestore instance contain user data? Leave empty if you don't use Cloud Firestore. Enter the full paths, separated by commas. You can represent the User ID of the deleted user with {UID}. For example, if you have the collections users and admins, and each collection has documents with the User ID as document IDs, then you can enter users/{UID},admins/{UID}.

  • Cloud Firestore delete mode:

    (Only applicable if you use the Cloud Firestore paths parameter.) How do you want to delete Cloud Firestore documents? To also delete documents in subcollections, set this parameter to recursive.

  • Realtime Database instance:

    From which Realtime Database instance do you want to delete user data?

  • Realtime Database location:

    (Only applicable if you provided the Realtime Database instance parameter.) From which Realtime Database location do you want to delete user data?

  • Realtime Database paths:

    Which paths in your Realtime Database instance contain user data? Leave empty if you don't use Realtime Database. Enter the full paths, separated by commas. You can represent the User ID of the deleted user with {UID}. For example: users/{UID},admins/{UID}.

  • Cloud Storage paths:

    Where in Google Cloud Storage do you store user data? Leave empty if you don't use Cloud Storage. Enter the full paths to files or directories in your Storage buckets, separated by commas. Use {UID} to represent the User ID of the deleted user, and use {DEFAULT} to represent your default Storage bucket.

    Here's a series of examples:

    • To delete all the files in your default bucket with the file naming scheme {UID}-pic.png, enter {DEFAULT}/{UID}-pic.png.
    • To also delete all the files in another bucket called my-app-logs with the file naming scheme {UID}-logs.txt, enter {DEFAULT}/{UID}-pic.png,my-app-logs/{UID}-logs.txt.
    • To also delete a User ID-labeled directory and all its files (like media/{UID}), enter {DEFAULT}/{UID}-pic.png,my-app-logs/{UID}-logs.txt,{DEFAULT}/media/{UID}.

Discovering data for deletion

There are a few mechanisms that this extension uses to discover data for deletion. These mechanisms have to be explicitly configured for the extension to delete data. The extension will only delete data that is explicitly configured to delete based on the mechanisms provided.

Be aware of the following behavioral differences between each service:

  • Cloud Firestore: the default behavior is to shallow delete a document (sub-collections will not be deleted). To recursively delete all sub-collections of a document, set the "Cloud Firestore delete mode" option to "Recursive".
  • Realtime Database: all data at the specified node will be deleted.
  • Storage: if a directory path is specified, all files and sub-directories will be deleted.

By path

When configuring the Cloud Firestore, Realtime Database & Cloud Storage paths, it’s possible to define a UID variable in the paths which will be replaced with the authenticated user’s UID. When a user is deleted, the extension will delete all data keyed on that UID at the given paths, for example:

  • Cloud Firestore path(s): users/{UID},admins/{UID}
  • Realtime Database path(s): likes/{UID}
  • Cloud Storage path(s): {DEFAULT}/uploads/{UID},{DEFAULT}/avatars/{UID}.jpeg

Auto Discovery (Cloud Firestore)

To enable the extension to automatically discover Firestore documents to delete, set the "Enable auto discovery" configuration parameter to "Yes".

Auto-discovery works by automatically traversing the database to find collections and documents which should be deleted according to your configuration. The extension identifies those collections and documents with the following methodology:

  1. First, the extension finds all root collections in the database. If a collection’s ID matches that of the user’s UID, the entire collection is deleted (deletion is either recursive or shallow, depending on the extensions’s configuration for "Cloud Firestore delete mode").
  2. Secondly, if the collection ID does not match, the extension will attempt to identify and delete a document if its the document ID matches that of the user’s UID.
  3. Finally, for each document: a. If the current search depth (see below) is less than or equal to the configured search depth, the process will be repeated for all of the current document’s sub-collections. b. If search fields have been configured, the extension will check if the provided fields match the user's UID. If a match is found, the document will be deleted.

Search Depth

The extension offers a configurable search depth value (defaulting to 3). Traversal will only be executed if the current search depth is less than or equal to the configured search depth. The current search depth is based on the depth of the current collection or documents parent collection, for example

/users = 1
/users/<document-id> = 1
/users/<document-id>/comments = 2
/users/<document-id>/comments/<document-id> = 2

This extension will NOT automatically delete UIDs stored in arrays or maps, and it will not search for data keyed by user ID stored in deeply nested subcollections past the depth specified above.