Who we are
Our website address is: http://otterdance.club.
Primary contact is Tom Geller (aka “Jack Newhorse”), JackNewhorse on Telegram.
What personal data we collect and why we collect it
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.
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.
Any information you send via a contact form on this site will be sent to the site’s administrator. That’s, uh, kind of the point.
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 visit our login page, 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
If you visit the site without signing into it, we will not intentionally share any data. But regardless of whether you sign in, WordPress and its supporting pieces (such as plugins) might send information to third-party providers, notably to Google (for our use of Google Maps). To the best of our knowledge, nobody can personally identify you via these data without taking extreme measures.
If you create an account, we may share your information within the organisation, but will not share it with any outside organisations.
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.
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.
How we protect your data
This site is hosted on third-party servers, using a shared hosting space. It’d be pretty easy for a high-level system administrator at our host to poke around the database, so any assurances we could offer regarding your privacy are pretty moot. Having said that: Our own backups are stored on a hard drive in a locked apartment.
What data breach procedures we have in place
None beyond complaining a lot.
What third parties we receive data from
Google, e.g. for Google Maps. Possibly other web services.
What automated decision making and/or profiling we do with user data
Industry regulatory disclosure requirements