Privacy Policy

Who we are

My website address is: https://twykr.com.

What personal data we collect and why we collect it

Comments

When visitors leave comments on the site we collect the data submitted via any of the forms on the website, and also the visitor’s IP address and browser user agent string to help spam detection.

Contact forms

Cookies

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 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.

Analytics

I use Google Analytics to track usage of my site and it’s contents.  If you do not approve of this, you may simply block Google Analytics from loading in your browser via whatever means you choose 🙂

Who we share your data with

If you’re viewing this page, then it’s probably because you’re using one of my WordPress plugins, or a VUI skill / action on an Amazon Echo or Google Home device.  In that case, note that your usage data for that skill or action is obviously tracked by Amazon and/or Google, respectively.

However, no information collected on this website is shared with anyone else, other than for basic purposes of teaching friends (or gloating to them), or as required by law for some reason (I can’t even imagine why that would happen – but who can say in this litigious world).

How long we retain your data

If you leave a comment or fill out a form on this site, then the information and related 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.

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 will be moderated, and may also be checked through an automated spam detection service.

Your contact information

If you need to contact me, please use this form.

Additional information

How we protect your data

Any data that I collect – other than via my contact form – is stored on 3rd party PCI-compliant systems, such as Google’s Analytics services, or WPMU’s servers.  So it’s as safe as I can make it at this point.

I maintain SSL security on this site, and do everything I can to maintain the highest level of security on my site, and with my code – as security is very important to me. That said, no one is perfect – so, beyond that, you’re on your own, if you choose to use anything I produce 🙂

Industry regulatory disclosure requirements

Plugin: Defender Pro

Third parties

This site may be using WPMU DEV third-party cloud storage to store backups of its audit logs where personal information is collected.

Additional data

This site creates and stores an activity log that capture the IP address, username, email address and tracks user activity (like when a user makes a comment). Information will be stored locally for 30 days and remotely for 1 year. Information on remote logs cannot be cleared for security purposes.