Privacy
Privacy policy
What I collect, why, and how I keep it safe. In short: as little as possible, only to help you, and always encrypted.
Last updated 1 October 2026.
This policy covers this website, email with me, and documents you send me. I am Richard Verver, a canon lawyer based in Toronto, Ontario, and I am responsible for the personal information described here. I handle it in keeping with Canada’s Personal Information Protection and Electronic Documents Act (PIPEDA).
This website
The site sets no cookies and uses no analytics, advertising or tracking tools, and it loads nothing from outside services. It is hosted by GitHub, which keeps the standard server logs every web host keeps for security; I don’t receive or use them.
If you use the contact form, what you write (your name, email address, message and, if you choose, how you found me) is passed to my inbox by FormSubmit, a form-to-email service. I use it only to reply to you. Please don’t send confidential details through the form until I’ve confirmed I can speak with you about your matter.
My email is hosted by Proton Mail in Switzerland, where messages are stored encrypted. If you write from a Proton account too, our correspondence is end-to-end encrypted, so only you and I can read it.
Documents you send me
Clients may send me documents by email or upload them to a private, end-to-end encrypted Proton Drive folder that is shared with them alone. No other client can see it.
- I keep your documents only in encrypted form: in my Proton accounts and on encrypted devices that I control.
- Backups are encrypted on my own equipment before they leave it, so the storage provider holding them (Google Drive) cannot read them.
- I use your information only to advise and represent you in your matter. I share it only as your matter requires, for example in a submission to a tribunal or Church authority on your behalf, or with your consent, or where the law requires it.
- I keep files for as long as your matter and my professional obligations require, and then delete them securely.
Google user data
I use a private backup tool, connected only to my own Google account, to store the encrypted backups described above in my own Google Drive. It can access only the files it created itself. It does not access, collect or store any other person’s Google data, and nothing it handles is sold, shared or used for advertising. Use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Your choices and rights
You may ask to see the personal information I hold about you, ask me to correct it, or withdraw your consent to my using it, subject to any legal or professional reason I must keep it. Write to me at email and I will reply within 30 days.
If I change this policy, I will update the date at the top of this page.