Send the address and delete it after you've verified that the recipient is in your simplex contacts. You can verify via security code. You'll know when they use the link. Delete the address afterwards.
SimpleX Chat
Community of SimpleX Chat users – managed by the team.
SimpleX Chat is the first chat platform that is 100% private by design – it has no user identifiers of any kind and no access to your connections graph – it's a more private design than any alternative we know of.
Please ask any questions and make feature suggestions. Your ideas and criticism are very welcome!
https://github.com/simplex-chat/simplex-chat
Maybe ask them to establish private (end to end encrypted - E2EE) communication channel by using PGP or ask them to use the service like proton.me which has E2EE mail. If they know some answer to your question, you can send them link to an password protected paste at https://bin.disroot.org
Without face-to-face communication, you cannot guarantee you haven't been man in the middle MITM.
One of the benefits of public key cryptography, is everybody can publish their public key, and then you can have a reasonable assurance that you're talking to the appropriate person, cuz you can see the key, they can see the key, so in theory you have verified the key.
With simple x, if one of you publishes a known non-incognito, static receive address. IE on your public website, or in your letterhead, or something, then the other side knows they're talking directly to you. You don't know you're talking directly to them. Or at least to the published address
If you want to talk to somebody, in a deniable way, then you probably should not be sending them direct mail. Meet them in person, exchange addresses that way, use briar, something.
Well, there's not much they can do with the QR code. You can deactivate it as soon as you've made contact and established proof of identity with the recipient.
But, if it was really important, there are cryptographic key-exchange protocols you can do even over an insecure connection. The Diffie-Hellman key exchange is one of them. Using something like that, you can derive a shared secret key even if someone's listening.
But personally, I would just break it into two parts, and send one by email and one with pastebin's "burn-after-read" option.