Who we are

Our website addresses include everything related to *, *, and (so far) other domains that begin with SLTy such as SLTyCommunity.

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, be careful when 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.


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, the site sets 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, the site sets 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.

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, if you are able to interact with the content (eg click to see something happen.)

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


Please refer to the appropriate Google Analytics documentation for the specific type of data it collects.  ICTA has enabled Google IP anonymization, which zeros the last “octet” of your IP (e.g. This site sends all page view events to Google Analytics for consumption.

Who we share your data with

If you subscribe to email updates, we share that information with MailChimp according to their policies, so they can send you email on our behalf. Other than that, we don’t share your data with anyone.

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.

Our contact information

Please use the contact links on this site for any questions or concerns.

Additional information

How we protect your data

ICTA regularly updates its understanding of the state of data protection issues and policies. We recently changed hosting providers to improve our ability to protect information.

Our best understanding is that unknown parties are capable of breaking in to any online system without detection.

What data breach procedures we have in place

We use a variety of host-provided tools for breach detection and amelioration. We will perform custom processes if a breach is ever detected.

What third parties we receive data from


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