diff --git a/src/fragments/lib/auth/js/delete_user.mdx b/src/fragments/lib/auth/js/delete_user.mdx index 87fc910478b..681a703aaba 100644 --- a/src/fragments/lib/auth/js/delete_user.mdx +++ b/src/fragments/lib/auth/js/delete_user.mdx @@ -14,7 +14,7 @@ If your application uses a Cognito User Pool, which is the default configuration - Before invoking the “delete user” API, you can first delete associated user data from the GraphQL API. For example, if you are using Amplify CLI's [GraphQL transformer](https://docs.amplify.aws/cli-legacy/graphql-transformer/overview/) to persist user data via [owner based access control](https://docs.amplify.aws/cli/graphql/authorization-rules/#per-user--owner-based-data-access), you could follow [these instructions](https://gist.github.com/aws-amplify-ops/27954c421bd72930874d48c15c284807) to delete associated user data. + Before invoking the “delete user” API, you can first delete associated user data from the GraphQL API. For example, if you are using Amplify CLI's [GraphQL transformer](https://docs.amplify.aws/cli/graphql/overview/) to persist user data via [owner based access control](https://docs.amplify.aws/cli/graphql/authorization-rules/#per-user--owner-based-data-access), you could follow [these instructions](https://gist.github.com/aws-amplify-ops/27954c421bd72930874d48c15c284807) to delete associated user data. This allows you to address any guidelines that require your app to delete data associated with a user who deletes their account. diff --git a/src/fragments/lib/auth/native_common/delete_user/common.mdx b/src/fragments/lib/auth/native_common/delete_user/common.mdx index c1c5bd9d597..d8e8bd8285e 100644 --- a/src/fragments/lib/auth/native_common/delete_user/common.mdx +++ b/src/fragments/lib/auth/native_common/delete_user/common.mdx @@ -15,7 +15,7 @@ If your application uses a Cognito User Pool, which is the default configuration - Before invoking the “delete user” API, you can first delete associated user data from the GraphQL API. For example, if you are using Amplify CLI's [GraphQL transformer](https://docs.amplify.aws/cli-legacy/graphql-transformer/overview/) to persist user data via [owner based access control](https://docs.amplify.aws/cli/graphql/authorization-rules/#per-user--owner-based-data-access), you could follow [these instructions](https://gist.github.com/aws-amplify-ops/27954c421bd72930874d48c15c284807) to delete associated user data. + Before invoking the “delete user” API, you can first delete associated user data from the GraphQL API. For example, if you are using Amplify CLI's [GraphQL transformer](https://docs.amplify.aws/cli/graphql/overview/) to persist user data via [owner based access control](https://docs.amplify.aws/cli/graphql/authorization-rules/#per-user--owner-based-data-access), you could follow [these instructions](https://gist.github.com/aws-amplify-ops/27954c421bd72930874d48c15c284807) to delete associated user data. This allows you to address any guidelines that require your app to delete data associated with a user who deletes their account.