Updated: October 3, 2021
Who we are
Our website address: https://www.roughpixels.com
What personal data we collect and why we collect it
Registered User Accounts
If and when you create an account on our site, you will be creating a username along with adding your email address. When choosing a Username, we strongly recommend that you do not use your real name. IMPORTANT: Usernames cannot be changed.
When you create a Username and include an email address for your account, they are stored in the Rough Pixels database. Your email address is required so that we can send you a link to reset your password.
Although optional, you can also set up your account profile with additional information such as your first name, last name, website URL (if you have a website), and bio information. These additional details are also saved in the website’s database. You may modify these details any time that you want, which will then update the database on our website.
When you log into the Rough Pixels website, 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.
If you select “Remember Me”, your login will be saved for a period of time, but it will be removed once you log out.
Publishing Content (Comments, Pages, Posts, Forums)
Your Profile Picture (Gravatar), Display Name, Website (URL) (if any), and Biographical Info (if any) may be visible to visitors to the website (e.g. if you leave a comment, forum post, or contribute an article/post).
If you upload media (e.g. images) to the website (in forums, posts, or comments), visitors to the website can download or extract this information.
When visitors leave comments on one of our sites 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.
Comments may require manual approval by our website. If you leave a comment on a site you may opt-in to saving your name, email address, and website in cookies so we can recognize you as a commenter.
Published content and comments are stored indefinitely unless deletion/removal is requested by the original author.
All forum posts and replies are public. When you create a topic or a reply, we collect your logged-in account data and the IP address where the post came from. The IP address is only visible to our support staff. You can edit or delete your existing posts/topics at any time by logging in.
We’ve turned on the IP Anonymization feature in Google Analytics. You can learn more about this here: https://support.google.com/analytics/answer/2763052?hl=en
We use email marketing to communicate with customers and potential customers from time to time. All email lists and campaigns are “opt-in” meaning we will not send you these sorts of emails unless you indicated that you wish to receive them during signup or other interactions on our website.
All marketing emails sent by us will include an unsubscribe link in the footer of the email. Emails sent to you may also include standard tracking, including open and click activities.
If you purchase using PayPal, we ask for:
- Email Address: So we can deliver our products and contact you if needed.
- First Name: To personalize your account experience.
- Username: So you can log in to your account to ask questions or download our products.
- Billing Country: For tax purposes.
- Billing Province: If you live in Canada, which is where we are located, we need to know which province you live in for tax purposes.
If you purchase using your credit card, we ask for all of the above, and:
- Credit Card Information: So we can process your payment. This data is sent to Stripe, and is never stored on our server.
- Billing City and Zip/Posal Code: To verify your credit card purchase.
You’re also asked if you’d like to receive email updates and news. If you check this box, your information will be added to our MailChimp list.
License Keys and Automatic Updates
When you add your license key to your Dashboard to receive automatic updates, your website URL and computer IP address are logged in our license key system.
If you come to our site through a link provided by one of our affiliates, a cookie will be added to your browser in order to remember the affiliate. This cookie will remain in your browser for 60 days, or until you delete it.
Backup Saving & Management
What Rights You Have Over Your Data
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 histories.
You can also request “to be forgotten” and we will erase any personally identifiable data we have about you. Of course, this excludes data we need for administrative or security purposes or if we are required by law to retain some of the data.
You may edit or delete any post or topic you make in our support forums at any time.
An individual who seeks access, or who seeks to correct, amend, or delete inaccurate data, should contact Rough Pixels.
How We Protect Your Data
For WordPress, itself, see wordpress.org/about/security for details for its own security details.
To help with prevention and security, we follow WordPress Code Standards in the development of the Rough Pixels website, our themes, and plugins.
At this time, only one primary administrator has full access to the administrative back-end of Rough Pixels. No other person(s) have access.
Rough Pixels, also uses an extensive security-based system plugin to ensure compromising situations are set to pursue prevention.
What Data Breach Procedures We Have In Place
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.