Who runs this site
purplish.io is run by me, Shameem Reza. I build and maintain the Purplish plugin and run this site myself. Under privacy laws like the GDPR and the UK GDPR, that makes me the controller: the person who decides what happens to the little data this site handles.
- Who. Shameem Reza, maker of Purplish.
- Where I'm based. Bangladesh.
- Privacy contact. hello@purplish.io
The Purplish plugin
Purplish runs on your own WordPress site. Its readme on WordPress.org says:
"Purplish doesn't collect, store or send personal data. It sets no cookies and makes no outside requests."
Its settings are saved in your own WordPress database, like any other block or WooCommerce setting. Nothing is sent to purplish.io or to me. The readme puts it this way too: "no outside requests, no tracking and no account to sign up for." Since the plugin collects nothing, it adds nothing to your own store's privacy policy.
What this website collects
purplish.io is a WordPress site with the Purple theme, WooCommerce and Purplish. These are the only places it handles data about visitors.
- Server logs. Like most web servers, the ones this site runs on keep logs of the requests they get, which can include your IP address, your browser and the page you opened.
- Cart cookies. If you add a demo product to the cart, WooCommerce sets three cookies.
woocommerce_items_in_cartandwoocommerce_cart_hashtell the page your cart has something in it.wp_woocommerce_session_followed by a random string links your browser to the cart, which WooCommerce keeps in the site's database. The cart holds the demo products you picked, nothing about who you are. - Security cookies. Cloudflare and the hosting network sometimes show a short "checking your browser" page to stop bots, and may set a cookie such as
__cf_bmorcf_clearanceto remember that your browser passed. - Comments. If you comment on a blog post, the site stores your comment, your name, your email address, your IP address and your browser's user agent. Your name and comment show with the post. Your email address and IP address are never shown. Your first comment waits for me to approve it. To turn away fake and throwaway addresses, the site checks that your email's domain can receive mail, by looking up the domain name only. It never sends anything to your address. Comments are checked for spam on the site's own server, using the comment, your IP address and your user agent. Nothing is sent to an outside spam service.
- Comment cookies. Under the comment form there's a box to save your name and email for next time. If you tick it, the site sets two cookies,
comment_author_andcomment_author_email_, each followed by a random string. If you don't tick it, no comment cookie is set. - Profile pictures. Next to each comment, the site shows a picture from Gravatar. To find it, a scrambled form of the commenter's email address (a hash) goes to Gravatar, and your browser loads the picture from Gravatar's servers, which see your IP address.
- Newsletter. If you sign up, I keep your email address to send you each new guide the day it's out, and nothing in between. Kit (kit.com) stores it and sends the emails for me. Open and click tracking is turned off, so Kit doesn't record whether you open an email or which links you click. Every email has an unsubscribe link.
- Analytics. If you accept analytics in the cookie banner, the site loads Google Analytics to count visits and see which pages people read. It sets two cookies,
_gaand_ga_followed by an ID, and sends Google your browser details, the pages you open, roughly where you are, and actions like scrolling, clicking a link to another site, downloading a file or using a form. Google sees your IP address when the script loads, and says Google Analytics doesn't store it. If you decline, or don't answer, Google Analytics never loads. - Cookie choice. The banner remembers your answer in a cookie,
purplish_consent, for 6 months, so it doesn't ask again on every page. - Videos. Some pages have a video. Nothing loads from YouTube until you press play, and the preview picture is served from this site. When you press play, the video loads from youtube-nocookie.com, and Google receives your IP address and browser details and may store data in your browser, under the Google privacy policy. If you don't press play, nothing is sent.
The site doesn't do any of this:
- No outside fonts. The fonts are served from this site, so your browser doesn't contact Google Fonts or any other font service.
- No orders. Checkout is turned off on the demo store. The site takes no orders and no payments, and never asks for an address or a card.
- No accounts. There are no visitor accounts and no contact form.
- No ads. No advertising, no ad profiles, and no automated decisions about you. Google Analytics is set up with Google's advertising features turned off.
Why, and on what basis
Privacy laws ask for a reason, called a legal basis, for each kind of data. Here's the basis for each.
- Server logs: legitimate interest. A website can't run safely without them. Logs help keep the site up, spot attacks and fix errors, and they hold no more than each request already sends. This is the legitimate interests basis in Article 6(1)(f) of the GDPR and the UK GDPR. You can object to it, see Your rights.
- Cart cookies: strictly necessary. They're only set when you add a product, and only to remember the cart you asked for. Under the EU and UK cookie rules, cookies that are strictly necessary for something you asked for don't need consent. So the cookie banner doesn't ask about them.
- Comments: your consent. You choose to post a comment and what goes in it, and the comment cookies are only set if you tick the box. You can ask me to edit or delete your comment any time. The IP address and user agent kept with a comment are there to fight spam, which is a legitimate interest.
- Newsletter: your consent. You sign up yourself, and you can take that back any time with the unsubscribe link in every email.
- Analytics: your consent. Google Analytics only loads after you accept it in the cookie banner. You can change your mind any time from Cookie settings at the bottom of every page, and the site removes its analytics cookies when you do. If your browser sends a Global Privacy Control signal, the site takes it as a no.
The security cookies from Cloudflare and the hosting network are there to keep the site up and safe, which counts as strictly necessary too. So does the cookie that remembers your answer in the banner.
How long it's kept
- Server logs. Kept only as long as the hosting provider needs them to run and protect the servers, then deleted.
- Cart cookies. The two cart cookies end when you close your browser. The session cookie and the saved cart end about 2 days after your last visit, and WooCommerce clears out ended carts twice a day.
- Comments. Kept with the post for as long as the post is up, unless you ask me to remove yours. Comments I don't approve are deleted, and comments marked as spam are deleted after 30 days.
- Comment cookies. End after one year.
- Newsletter. Kept until you unsubscribe. After that, Kit keeps your address only marked as unsubscribed, so you're never emailed again, and I delete it completely if you ask.
- Analytics. The cookies last up to 2 years. Google keeps the detailed visit data for 2 months, and after that only totals remain.
Who else sees it
The logs, carts and comments sit on my hosting provider's servers. It handles them for me, as what the GDPR calls a processor, under a data processing agreement.
Cloudflare sits in front of the site to keep it fast and safe, so every request passes through its network first, including your IP address. It handles that for me as a processor, under its data processing addendum and its privacy policy.
Kit stores the newsletter list and sends the emails for me, as a processor, under its privacy policy.
Google runs Google Analytics for me, as a processor, under its data processing terms. Google explains how it uses data from sites that use its services.
YouTube, which Google runs, plays the videos. It only gets your data when you press play, and it uses that data under the Google privacy policy.
Gravatar runs on its own servers and follows its own privacy rules. It only gets a hash of a commenter's email address and, when a page with comments loads, the visitor's IP address.
I don't sell your data, share it for advertising or give it to anyone else, unless the law requires it, like a valid court order. For US state privacy laws like California's, that means there's no sale or sharing to opt out of, and no sensitive data is collected. Analytics only runs if you say yes, and a Global Privacy Control signal counts as a no.
Where the data is
The site's servers are in a data center in Phoenix, Arizona, in the United States. Cloudflare and the hosting network pass each request through a point near you on the way. If you visit from another country, your request travels to the United States, as with any website. Kit and Google also keep their data in the United States.
If the data moves out of the EU or the UK to a country without an adequacy decision, each provider's data processing terms cover it with the EU's standard contractual clauses and the UK's addendum to them. Google and Cloudflare are also certified under the EU-US Data Privacy Framework. Ask me if you'd like a copy of the clauses.
Your rights
Wherever you live, you can ask me to:
- tell you what data about you the site holds, and give you a copy;
- correct it, or delete it;
- limit how it's used, or stop keeping it, including objecting to the server logs;
- send it to you in a common file format.
In the EU and the UK, the GDPR and the UK GDPR give you these rights by law, and some US states give similar ones. Asking is free, and I answer within one month. Using your rights never changes how the site works for you.
For comments and the newsletter, your email address is enough for me to find your data. For server logs, I'll need details like your IP address and the date and time you visited. Analytics data isn't tied to your name or email, so I can't look it up by them. I'll only use what you send me to answer you.
Send requests to hello@purplish.io.
If you're not happy with my answer, you can complain to a data protection authority. In the UK that's the Information Commissioner's Office. In the EU, find yours on the European Data Protection Board's list of members.
Children
This site is for people who run WooCommerce stores. It isn't aimed at children and doesn't knowingly collect their data.
Sites you leave for
The plugin page and the support forum are on WordPress.org. The code, bug reports and security reports are on GitHub. Once you're there, their own privacy policies apply: the WordPress.org privacy policy and the GitHub General Privacy Statement.
The share and follow links on blog posts are plain links. Nothing loads from X, LinkedIn, Facebook, Bluesky or YouTube until you click one.
Posts in the support forum and GitHub issues are public, so leave out anything private, like passwords or order details.
Questions
For a privacy request, email hello@purplish.io. For questions about the plugin, ask in the Purplish support forum on WordPress.org.
For a security issue, use the private report form in the security policy on GitHub, never the forum.
Changes to this page
When this page changes, the date at the top changes with it. If the site starts collecting anything new, this page will say so before it starts.
This page covers purplish.io and the Purplish plugin. It isn't legal advice for your own store.