this is a good question

You can have a cronjob somewhere which checks for these users and then calls the delete API in supertokens

Alternatively, you can insert the user in your db on login / sign up, but in the session, you can save a flag indicating if they have provided the required fields or not. If they haven't you don't give them access to your backend routes (except for the one in which they can submit the fields), and on the frontend, you always redirect them to the page asking them for the fields. Once they have successfully given the fields, you can modify the session payload accordingly and then they will have access to the app.

Thanks for thinking with me! 👍

js
              createNewSession: async function (input) {
                const userInfo = await ThirdPartyEmailPassword.getUserById(input.userId)

                const user = await sdk.getUserByEmail({ email: userInfo.email })

this is our logic don't see any reason to store supertokens user-id in our own db right?

hey, quick question... any way to refresh session on the frontend?

so, fixed all steps... problem is when user register in database

i need to refresh the session with new payload