hey @callstack1 this is possible. You want to override the all the passwordless recipe functions on the backend (not APIs) to hash the input email before using the original implementation.
That being said, this may cause issues for resending the magic link. But if you don't hash the email in createCode, then this should be fine (essentially, you only want to has the email in consumeCode and getUserByEmail functions)