Hi @guillex,
This issue looks like it may be related to the sameSite changes that Chrome has recently enacted.
Please review this doc and make sure you conform to the changes:
Thanks, Dan