Hello,
luiiuuuiiiii perhaps the workaround must be to somehow skip/change the bounce url.
Skipping it isn't an option as it's a core privacy functionality of CryptPad. However, we though about changing the URL on our flagship instance.
The only issue we see with this is that it will likely end up being flagged as phishing as well by Google. Also, with the submitted reports for false-positive, they wouldn't be able to replicate the issue anymore. Ideally we would like the issue to be fixed on Google's end for good.
As mentioned in an earlier post, Google Safe Browsing services can easily be disabled client-side, directly from your web browser. If you care about your privacy, it's likely something you'd want to do anyway. Otherwise all your browsing history is automatically sent to Google on real-time, leaking quite a lot of information about yourself and/or your activities.
