January 19, 2024

Privacy Policy

Who we is

Our website address is: http://tinymoo.tech.  Anything more than that is hearsay.  Or heresy.  Maybe both.

Enhanced Boilerplate Follows

Snide commentary is italicized

What personal data we collect and why we collect it

We might use web access logs to figure out how well the website is working (or not), but nothing non-technical.  We aren’t in the business of making money, especially not from something as ephemeral and difficult to monetize as personal information.


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.

An anonymized string created from your email address (also called a hash) may be provided to the Gravatar service to see if you are using it. The Gravatar service privacy policy is available here: https://automattic.com/privacy/. After approval of your comment, your profile picture is visible to the public in the context of your comment.

Nobody on our end is going to collate and/or market that data.  For one, we don’t want to go to that much trouble.  For two, we couldn’t get very much for it.


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.

We aren’t going to steal your stuff or the rights to it.  Unlike most of the civilized world, we know that reverse image lookup and archive.org still exist.  Maybe we’ll look at your GPS info and make fun of your house or something.  I can’t rule that out.

Contact forms

There may be contact forms.  If you don’t want us to use the information on contact forms, maybe…don’t fill them out?  Just a suggestion.


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.

We aren’t tracking you to sell rights for ads.  We don’t have ads.  We don’t deal with advertisers.  They are, by and large, impossibly insufferable.

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.

We aren’t going to use cookies to track you for anything nefarious or even especially entertaining.  It’s not that we’re especially moral.  There’s just no benefit.  There’s no resultant amount of money or entertainment that would make the hassle of implementation worthwhile.

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.

These websites may collect data about you, use cookies, embed additional third-party tracking, and monitor your interaction with that embedded content, including tracing your interaction with the embedded content if you have an account and are logged in to that website.

Yes, embedded Facebook posts might bring with it Facebook evils.  Keep that in mind when you note exactly how much Facebook-based content you see here.


…Yes, we have analytics.  We might…look at them.  …I don’t know, what am I supposed to say here? 

Who we share your data with

Uh, nobody, really.  The hosting company will have that data.  The US government will probably grab it if it really wants it.  The Russians will probably hack it from the Americans if they really want it.  If it gets subpoenaed, we’ll probably give it up because American lawyers are expensive and difficult to be around.  But we don’t sell it or share it of our own accord.

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.

We reserve the right to flush the whole damn site whenever we feel like it.  If this is an issue, maybe back up your stuff.

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.

(Note that the boilerplate says you can request all of this.  It doesn’t necessarily say we’ll acknowledge your request.  …No, seriously, we’ll listen.)

Where we send your data

Visitor comments may be checked through an automated spam detection service.

This being a WordPress blog, God only knows how well that will work.

Your contact information

Try sigma7@tinymoo.tech.  Anything else would be telling.

Additional information

Elton John helped Eminem kick his drug habit.

How we protect your data

Uh, we don’t.  Our hosting service, SSDPage, has some impressive security features, though.  Ask them.

What data breach procedures we have in place

Again, don’t ask us, ask them.  We will probably just curse a lot.

What third parties we receive data from

None we can think of.  Why?  Do you know any?

What automated decision making and/or profiling we do with user data

Pffft, we don’t make automated decisions, especially not with user data.  And we don’t profile.  Maybe we should.  But it seems like a lot of work.  That’s not why we’re in this.

Industry regulatory disclosure requirements

Your guess is as good as mine, really.