Who I Am
The website address is: https://tomstypewriter.com.
What personal data is collected and why it gets collected
When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection.
At this time comments are not allowed on this site. Who knows – that might change in the future, so we’re leaving this paragraph in just in case.
If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.
Contact forms do not stash any data on this site – other than perhaps in the webserver logs [over which I have no control]. Basically the form hands your message over to a mailserver, which then relays the message to my inbox – nothing special is stashed anywhere.
If you leave a comment on our site you may opt-in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year.
If you have an account and you log in to this site, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.
When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select “Remember Me”, your login will persist for two weeks. If you log out of your account, the login cookies will be removed.
If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day.
Embedded content from other websites
Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.
Who we share your data with
No one. Well, if someone forced me to with a court order, I’d have to comply. I’ve got better odds of winning the lottery without playing.
How long we retain your data
If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognize and approve any follow-up comments automatically instead of holding them in a moderation queue.
For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.
As above, the site allows neither of those at the moment. In the future, who knows? I certainly don’t.
What rights you have over your data
If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.
Where we send your data
Visitor comments may be checked through an automated spam detection service.
Use the contact info on the site – or do a web search for Tom Rule in Macon, Georgia. You’ll find me.
How we protect your data
None of the data collected is stashed on this server, since comments are not allowed. Email addresses that you provide to be notified when a new bit o’ wisdom or pondering is posted is stashed on a third party service that I have no control over.
What data breach procedures we have in place
If we’re breached, we’ll probably just wipe the site and start over. Since no private data is stored on this server – other than standard info that browsers and web servers exchange, that shouldn’t be an issue.
What automated decision making and/or profiling we do with user data
We don’t do this. We don’t use this.