in which mr. john makes explains his stand on your privacy
I really don't collect much info about you. Just enough to power the basics of the site and some tools to see if folks are using the site. Here is a policy I nicked from another site and changed to meet my needs. Enjoy.
Who I AM
For any privacy-related questions, you can reach me at firstname.lastname@example.org.
Sharing Your Data
I use third-party services (data processors) across our sites. The extent to which your data is shared with these providers depends on your use of our services, and we list the specific third-parties in use (with links to their privacy policies) in the sections below.
Each third-party provider has been vetted to ensure that privacy policies and practices meet or exceed the same levels of compliance and standards that I follow. Where appropriate and available, I hold additional signed Data Privacy Agreements with these companies as an additional layer of accountability to help ensure your data is safe and secure.
Personal Data We Collect
- Users that email me, or use any of the contact forms on our websites, will have their email address, IP address, and any data provided in the contact form or body of the email stored in G Suite archives.
- I keep all email and chat communication indefinitely to help provide support and improve services. Individuals can request copies of any previous correspondence with me at any time.
Embedded Content From Other Websites
- Scribd (US)
- SlideShare (LinkedIn)
- Speaker Deck
- Spotify (US)
- WordPress Plugin Directory
- YouTube (Google)
Hosting and API Services
- All web servers and hosting are managed by the WordPress.Com platform located in different regions around the world. This includes website hosting, backups, web database, file storage, APIs, and log files.
- In order to check login activity and potentially block fraudulent attempts, the following information is used: attempting user’s IP address, attempting user’s email address/username (i.e. according to the value they were attempting to use during the login process), and all IP-related HTTP headers attached to the attempting user.
- To initiate and process subscriptions, the following information is used: subscriber’s email address and the ID of the post or comment (depending on the specific subscription being processed). In the event of a new subscription being initiated, we also collect some basic server data, including all of the subscribing user’s HTTP request headers, the IP address from which the subscribing user is viewing the page, and the URI which was given to access the page (REQUEST_URI and DOCUMENT_URI). This server data used for the exclusive purpose of monitoring and preventing abuse and spam.
- For video play tracking via WordPress.com Stats, the following information is used: viewer’s IP address, WordPress.com user ID (if logged in), WordPress.com username (if logged in), user agent, visiting URL, referring URL, timestamp of event, browser language, country code. Google Analytics is enabled, and video play events will be sent there, as well.
If you are a registered user or have left comments on our site, you can request to see or download the data we have about you.
Typically for visitors that have left comments, the data will be their email address, any IP addresses assigned to them at the time of leaving the comments, and the user agent strings of the browsers they used. The rest of the data is public, as published by the visitors.
For registered users or paying customers, this will also include profile information and download, payment, and support ticket histories.
You can also request “to be forgotten,” and we will erase any personally identifiable data we have about you. Of course, this excludes information we need for administrative or security purposes or if we are required by law to retain some of the data.
An individual who seeks access, or who seeks to correct, amend, or delete inaccurate data, should direct his/her query to email@example.com. We will respond within a reasonable timeframe, not to exceed one week.
Protecting Your Data
The security and reliability of our service is our number one priority. We invest heavily in the training of our staff and our infrastructure to ensure that best practices are followed in everything that we do.
See wordpress.org/about/security for details on the security of the WordPress core itself.
- Prevention is best when it comes to security, and as a first step, we follow all WordPress Code Standards in the plugins that we build and use.
- In addition, we have an extensive internal review and Quality Assurance process in place specifically to prevent potential security vulnerabilities in our plugins and services.
- Every Incsub employee and contractor goes through background checks and an onboarding process that includes a trial period where access to customer data is provided only when working directly under the supervision of another staff member.
- All staff only have access to systems that are directly required to complete the functions of their job. We use dual factor authentication for all critical systems and communications services, and automatically log all staff activity using an internal logging tool, Google ‘G’ Suite features, and Amazon Cloud Trail.
- All staff (including any contractors) undergo initial training to ensure proper understanding of all security-related processes. Staff regularly attend industry conferences and otherwise stay informed of best practices and relevant trends. Staff review and agree, in writing, to all policies and procedures annually.
- We only use third-party services, such as Amazon Web Services, that are fully vetted and adhere to the highest levels of privacy and security practices.
Data Breach Procedures
Should any event occur where customer data has been lost, stolen, or potentially compromised, our policy is to alert our customers via email no later than 48 hours of our team becoming aware of the event. We will also report such incidents to any required data protection authority. We will work closely with any customers affected to determine the next steps, such as any end-user notifications, needed patches, and how to avoid any similar event in the future.
- October 28, 2019 – Created.