Privacy Policy

Who we are

Our website address is: https://convexum.net.

What personal data we collect and why we collect it

Comments

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.

An anonymised string created from your email address (also called a hash) may be provided to the Gravatar service to see if you are using it. The Gravatar service Privacy Policy is available here: https://automattic.com/privacy/. After approval of your comment, your profile picture is visible to the public in the context of your comment.

Media

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.

Contact forms

If you contact me via any contact form that will generate an email to my own email account. Fields you fill in the form will be logged in the site’s database. The site also logs the IP address you were using when you submitted the form, this is used exclusively to prevent abuse of the system. Anything entered in the form will be used exclusively for the purposes of replying to your contact unless you have explicitly ticked an option to subscribe to a newsletter at when submitting the form, in which case your email address would be included in the relevant email subscription software (see MailPoet below).

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

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.

Analytics

Who we share your data with

Your data is only shared for the explicit purpose of the site functionality: anonymised tracking data is gathered by Google Analytics.

How long we retain your data

If you leave a comment, the comment and its metadata are retained indefinitely. This 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 (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. Note that website administrators cannot access your password.

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. Emails are sent by MailPoet’s mail sending service (see MailPoet section below).

Your contact information

For any queries, please contact me either by the Contact form or by a social media channel.

Additional information

MailPoet newsletter & emails

If you have subscribed to a newsletter or if you are a member of our website (you can log in) or if you have purchased on the website, there is a good chance you will receive emails from us.

We will only send you emails which you have signed up to receive, or which pertain to the services we provided to you.

To send you emails, we use the name and email address you provide us. Our site also logs the IP address you used when you signed up for the service to prevent abuse of the system.

This website can send emails through the MailPoet sending service. This service allows us to track opens and clicks on our emails. We use this information to improve the content of our newsletters.

No identifiable information is otherwise tracked outside this website except for the email address.

How we protect your data

All traffic to the site is encrypted with SSL security. MySQL, PHP and Apache are maintained and updated to minimise and patch security flaws. The MySQL database is accessible only from the site itself. Access to all functions on the web host is protected with two-factor authentication. WordPress admin logins are protected with two-factor authentication. Brute force attacks are blocked. Security plugins are enabled and active within the WordPress installation. WordPress software and all installed plugins have latest updates applied frequently.

What data breach procedures we have in place

In case of any data breach you will be informed as soon as it is discovered. Appropriate mitigation steps will be taken, including immediately taking the site offline until the breach is secured.