Who we are
This page is to help you understand the data we collect and hold on you. We receive and retain this via the day-to-day operation of this website.
What personal data we collect and why we collect it
By default, 1310nm.net does not collect any personal data about unregistered visitors. We only collect the data shown on the User Profile screen from registered users. You just have personal data on this blog if you are a registered user.
We use your IP address, username, and email address during registration (and at subsequent random times) to validate that you are not a comment spammer.
When registered 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.
Please bear in mind that comments are public. All users of this blog may read them, and the search engines that scan this site will index them.
If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the site can download and extract any location data from pictures on the website.
We place a cookie to denote if you have accepted the cookie notice displayed the first “time” (i.e., the acceptance cookie is not present) you access this blog. This cookie will expire within one month.
If you leave a comment on our site, you may opt-in to save 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. Closing your browser will discard this cookie.
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 continue for a year. If you select “Remember Me”, your login will persist for two weeks. Logging out of your account removes the login cookies.
If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and indicates the post ID of the item you just edited. It expires after one 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 same way as if the visitor has visited the other website directly.
All searches performed using the internal site search are logged, including the following information: the search query, the number of hits found, user ID (for users who are logged in), date and time and the IP address. The IP address is stored for security and auditing purposes for 60 days before they are automatically removed.
We use different analytics services to support our understanding of your use of this blog, so we can tailor content to reflect both what we wish to provide and what you do read.
Google Analytics and Automattic WordPress JetPack provide our analytics services. These take the URL visited, the IP address that visited the site, and the referring page from which you arrived. The WordPress JetPack statistics additionally takes browser language and country code settings. These are used to provide the following activity tracking: Post and page views, outbound link clicks, referring URLs and search engine terms, and country.
Please visit the Google Analytics Opt-Out Page to learn about opting out of the Google Analytics tracking and installing the appropriate browser add-on.
This feature is only accessible to users logged in to WordPress.com.
In order to process a post like action, the following information is used: IP address, WordPress.com user ID, WordPress.com username, WordPress.com-connected site ID (on which the post was liked), post ID (of the post that was liked), user agent, timestamp of event, browser language, country code.
When sharing content via email (this option is only available if Akismet is active on the site), the following information is used: sharing party’s name and email address (if the user is logged in, this information will be pulled directly from their account), IP address (for spam checking), user agent (for spam checking), and email body/content. This content will be sent to Akismet (also owned by Automattic) so that a spam check can be performed.
WordPress.com Secure Sign On
This feature is only accessible to registered users of the site with WordPress.com accounts.
To allow you to use a WordPress.com account to log in on this blog, we need to send your WordPress.com userID to them. This needs to map to User ID (local site and WordPress.com), role (e.g. administrator), email address, username and display name. Additionally, for activity tracking (see below): IP address, WordPress.com user ID, WordPress.com username, WordPress.com-connected site ID and URL, Jetpack version, user agent, visiting URL, referring URL, the timestamp of the event, browser language, country code.
The following usage events are recorded: starting the login process, completing the login process, failing the login process, successfully being redirected after login, and failing to be redirected after login. Several functionality cookies are also set, and these are detailed explicitly Automattic’s Cookie documentation.
WordPress will sync the user ID and role of any user who successfully signed in via this feature with the local username and email address used to login.
Who we share your data with
We share your IP address, email address and username with the following sites to prevent comment spam:
Akismet: IP Address, Username, Email Address, User Agent, Referrer, and Comment Text
Google Analytics: IP Address, URL, Referrer
Gravatar: hash of email address (if logged in to the site or WordPress.com — or if they submitted a comment on the site using their email address that is attached to an active Gravatar profile
JetPack Site Stats: IP Address, URL, Referrer
Stop Forum Spam: IP Address, Username, Email address
WordPress.com: User ID (local site and WordPress.com), role (e.g. administrator), email address, username and display name, IP address, WordPress.com user ID, WordPress.com username, WordPress.com-connected site ID and URL, Jetpack version, user agent, visiting URL, referring URL, timestamp of event, browser language, country code
How long we retain your data
If you leave a comment, we retain the comment and its metadata indefinitely. This retention is so we can recognise and approve any follow-up comments automatically instead of holding them in a moderation queue.
For users that register on our website, 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
We check user registrations via an automated comment spam user verification service. If rejected by the system, you have the option of requesting a human to review your request,
Visitor comments are checked through an automated spam detection service.
These services are hosted outside of the EU. If you are an EU citizen and prefer your personal information (your name as entered on the registration page) not be sent outside of the EU, you have a choice of:
- Not registering on this blog
- Using an alternate username (provided this is not for the purposes of impersonation, defamation or fraud)
- Continuing to register with your personal information, aware that it is held on servers outside of the EU and not subject to the EU-US Privacy shield protections.