If you'd like any photos removed from my website or the internet in general, please contact me.
This page details two privacy policies. The first relates to photography and image security, and the second relates to this website.
In addition to personal photography or art, I do photojournalism, for my blog or for The Linfield Review. The newspaper prints photos and publishes them online. I would only remove an image if there were a compelling reason to do so.
The most secure way of doing photography is on film, as there's no digital component required. The entire cycle, from exposure to final print, can be achieved without a computer. For now, I only develop black and white film, so for the time being, it's the most secure option. My color reversal film (E-6) is processed by Blue Moon, and my color negative film (C-41) is handled by PhotoVision. After the negatives are developed, it's common to scan them, which I could do, but I usually pay the labs. PhotoVision uses Box for filesharing. Color development is something I'll consider down the road, but I'm not interested at the moment.
Once I have the digital photos, they can be delivered online or preferrably through phyiscal storage (USB, DVD, etc). I can encrypt your files, too.
My site doesn't collect information about its visitors. I don't know who reads my stuff, and I don't make any effort to identify people. Online surveillance is easy, and it's standard for many sites, but it serves no purpose for me, and it isn't necessary for most businesses, either. In fact, surveillance and tracking practices, commonly misrepresented as "advertising," contribute to poor web design, malware distribution, and click-bait journalism. Analytics and user-tracking create more distractions than value, so I deliberately avoid those things. These include web-fonts, social media widgets, and other 3rd party resources. My pages are designed to be as small as possible, so they load quickly and save data.
You can inspect the page content in your browser, or you can view the source code on Github.
These files are served from Netlify, and my contact form is processed by their computers. It tries to detect spam, so they do have access to the form message. If you want to communicate privately, without your message being read by other people or computers, you can text/call me with Signal, at the phone number on my contact page. Signal is an app that encrypts your messages, preventing other people from listening. Please be aware that my number is provided by Google Voice, so traditional telephone communication will be intercepted and analyzed by Google, along with your cellphone provider. This isn’t unique to Google. All carriers perform aggressive surveillance and cooperate with illegal spying programs. The only private way is through Signal.
Netlify pays for Amazon's content delivery service, Cloudfront, to store copies of my website across the world. This enables the page to download faster, because there's a greater chance they have a copy near your city. But to be completely realistic, most people interested in my website are going to be near me, right here in Oregon. So I could just serve the website myself, and I would like to eventually. In either case, sending a file requires knowing the destination, so Netlify and Cloudfront know when you visit my website. This is perfectly normal and how the internet is designed to function.
However, you can use anonymization networks, such as Tor, to disguise your identity from your internet service provider, Netlify, and Cloudfront.
I hope that clears up everything. Contact me with any questions.