Terms & Conditions

Agreeing to this

Buying, downloading or using a jkdevstudio product means these terms apply to you. They sit alongside our Privacy Policy, our Support Policy and our Refund Policy, and where any of those says something more specific about its own subject, the specific one wins.

If you bought on a marketplace, that marketplace’s terms also apply and take precedence over ours wherever the two differ. See the Envato section.

Words we use

• We, us, the studio: jkdevstudio, Ivano-Frankivsk, Ukraine.
• Product: a theme, a plugin or an add-on we publish, together with its documentation and demo content.
• Hub: our customer portal at hub.jkdevstudio.com, where licenses, downloads, documentation and support live.
• Activation: one license key registered against one site, which is how a license counts the sites it covers.
• End product: the website you build with one of our products.

What your license lets you do

A license is a right to use the product. It does not transfer ownership of it, and the number of sites it covers is stated where you bought it.

Bought directly from us

A direct license is perpetual. That word is worth unpacking, because “lifetime” is a term other people use loosely:

• The product keeps working on the sites it is activated on, permanently. Nothing expires, nothing phones home and shuts off, and there is no renewal that has to be paid to keep a site running.
• Every version released while your license is in good standing is yours to use, permanently, including after the support period ends.
• Support has its own duration, described in our Support Policy. When it ends you lose access to the queue and nothing else.

The tiers are Premium, which covers one activation, and Agency, which covers unlimited activations for sites you own or build for clients. What each one includes is set out on the product’s pricing page and that page is the authority on it.

Bought on Envato

Products bought on ThemeForest carry Envato’s Regular or Extended License. Those terms decide what you may do with the product, and they are Envato’s to write: see the Envato license terms and the Envato Terms of Use. Nothing here narrows what Envato grants you.

Free products on WordPress.org

Products we publish in the WordPress.org directory are licensed under the GPL, version 2 or later, in their entirety. That is the directory’s requirement and we are glad to meet it. You may use them on any number of sites, modify them, and redistribute them under the same license. No key, no activation, no account.

The restrictions further down this page are about our commercial products. They do not apply to a GPL release, and we will not pretend otherwise.

What you may do

• Install and run the product on the sites your license covers.
• Modify it for those sites, including through a child theme, the hooks and filters we provide, or the code itself.
• Build sites for clients with it, within the activation count your license allows, and hand the finished site over.
• Keep using every version you received, forever.

What you may not do

• Redistribute, resell, sublicense or publish the product files, original or modified, outside what your license allows.
• Put it on more sites than your license covers without buying the difference.
• Share your license key, or use one that was not issued to you.
• Remove or alter copyright notices, license headers or authorship attribution in the code.
• Interfere with license verification or updates, or distribute anything that does.
• Repackage the product, or a recognisable part of it, as your own product, template, starter kit or theme.

Who owns what

The products, the branding, the documentation and Hub itself belong to jkdevstudio.

Our commercial WordPress products carry the split license the platform’s GPL heritage requires. PHP code is licensed under the GNU General Public License version 2 or later. The other half of the product, meaning the JavaScript, CSS, images, fonts, demo content and other creative assets, is licensed under our own terms, or Envato’s for an Envato purchase, and is not GPL. Those assets may be used in the end products your license covers and may not be redistributed on their own.

Third-party libraries shipped inside a product keep their own licenses, which are named in the source or in the documentation.

Piracy, nulled copies and copied code

This is the one section where we are not relaxed, so here it is plainly.

Nulled and pirated distributions. Where our commercial products are published without a license, on a nulled site, in a bundle, in a marketplace listing or anywhere else, we file DMCA takedowns. Every time, against every host, mirror and search result we can identify, and we do not negotiate about it. Where a jurisdiction offers more than a takedown, we use that too.

If you are considering running a nulled copy, the practical warning matters more than the legal one: nulled WordPress themes are one of the most reliable ways to get a site backdoored, because whoever stripped the license check had access to every file and no reason to be kind. We cannot help you clean that up, and our Support Policy says so.

Copied code. Lifting our source into a product of your own is a copyright infringement and we treat it as one. Where we find our code, our markup structures or our assets in somebody else’s commercial product, we pursue it: with the marketplace hosting it, with the host serving it, and where it is worth doing, further than that. Being a developer is not a defense, and neither is a rename.

Breaking the activation. Anything whose purpose is to get past the license check is a breach of these terms, whether or not it works. A key generator. A patched or repackaged build with the check taken out. A loader that fakes a successful activation. A key that was never issued to you, or one that came bundled with something you bought from somebody who was not us. Probing our activation endpoint for a weakness counts as well. If you are a security researcher and you have found one, write to hello@jkdevstudio.com instead. We have never been sorry to hear from one.

Two things follow. We deactivate the license and every activation on it, close the Hub account behind it, and decline a refund under our Refund Policy. And in most countries getting past a technical protection measure is an offence in its own right, separate from the copyright infringement underneath it.

What we do when our software turns up on a site that has not paid for it. We look for this, and we work through the whole list rather than picking one item off it:

• The host and the CDN: a DMCA notice to whoever is serving the files and to whoever is caching them.
• The registrar: an abuse report against the domain, with the notice attached.
• The money: the marketplace, the ad network or the payment processor, wherever the site earns from it. That relationship is usually easier to end than the site is.
• Search: removal requests for every result that points at it.
• The authorities: where the scale or the money involved warrants it, a report to the police or the copyright body in the country the operator sits in, and in ours.

We do not negotiate about any of it and we do not stop after the first notice. A site that puts the files back gets the list again, and somebody who has done it repeatedly gets all of it at once rather than in order. We do not tolerate piracy of our work in any form, and there is no version of this where waiting us out is the cheaper option.

Every alternative costs less than that. Buy the license, here or on ThemeForest. Use our free products from the WordPress.org directory, which are GPL and carry no key and no activation at all. Open the live demo of the thing you are considering and click around it before you spend anything. Where we offer a trial, it is on the product’s own page. And if the price is what is stopping a project rather than the product, write to hello@jkdevstudio.com and say so. That conversation goes better than most people expect.

None of this is aimed at people learning from our code. Read it, take an idea from it, work out how something is done. That is what reading code is for. The line is publishing our work as yours.

If you break the terms

Depending on what happened, we may deactivate the license and its activations, close the Hub account, refuse a refund under our Refund Policy, and pursue the matter legally. A deactivated license means updates and support stop; sites already built keep running, because we do not put a kill switch in anybody’s website.

We would rather write to you first, and usually do. Most breaches turn out to be somebody who put a one-site license on three sites and did not think about it, and that is a conversation and an upgrade rather than a dispute.

Who we sell to, and who we do not

We are a Ukrainian studio based in Ivano-Frankivsk. Russia is waging a war of terror against our country, and Belarus is actively facilitating it. We do not sell to either country, support either government, or make our software available there. This position is non-negotiable. The rest of this section explains how it works in practice rather than arguing for it.

The first reason is the law, and it is not ours to waive. We are a company registered in Ukraine and bound by Ukrainian law, including the sanctions currently in force against the Russian Federation and the Republic of Belarus, and by the sanctions regimes our payment and distribution partners work under. Those rules govern what can be sold, to whom, through which banks, and into which territories. We do not look for loopholes.

The second is that we could not deliver even if we wanted to. Payments from those countries are not accepted by our merchant of record. Our license and update infrastructure does not respond to requests from there. Support is a working relationship with a studio that is being shelled by one of those countries. Nobody there ends up with a product that works and a service behind it.

What is blocked. A site hosted on infrastructure in Russia or Belarus. A domain registered in either country. A company, an invoice, a card or any other payment instrument registered in either country. Occupied Ukrainian territory falls under the same rule, because the servers there answer to the same authorities.

What that means in practice. The block sits in our infrastructure, not in a policy someone has to remember to apply:

• Activation: a license key will not activate from there. No warning and no grace period. The request simply fails.
• Updates: an installed copy stops receiving them. Nothing is switched off on a site that is already running, because we do not put a kill switch in anybody’s website, but the version on it is the last one it will get.
• Support: tickets go unanswered and bug reports are not reviewed. Our Support Policy says the same thing.
• Buying: checkout is refused. If a payment gets through anyway, we cancel the license and refund the money. We have no interest in keeping it.
• Appeals: there is no address to write to about this one, and a message about it will not get a reply. Everything else on this page has a human behind it. This does not.

Supporting the invasion ends the relationship, wherever you are and whatever passport you hold. A Z or a V. The ribbon. A profile celebrating a strike on a Ukrainian city, or a public endorsement of one. A company that kept trading there after February 2022 and says so openly. This is about what a person does, not where they were born, and it is the one thing on this page we act on immediately: the license and all its activations are deactivated the same day, the Hub account is closed, and the money goes back. We are not keeping it, and there is nothing to appeal.

And we are not obliged to sell to anyone. We may decline an order, cancel one after the fact, or close an account at our own discretion and without giving a reason. That is an ordinary commercial right, and we intend to use it. Whenever we do, the money is refunded in full; nobody is left out of pocket by a decision of ours.

Working around any of this is a breach of these terms. A VPN or a proxy. A front-end host in one country while the site is actually served from another. A reseller, an agency buying on behalf of a client there, or a license bought by someone else and handed over. Each of those ends the same way: the license and all its activations are deactivated, the Hub account is closed, and we keep a record so the same buyer cannot come back through a second address.

Getting the product and keeping it

Direct purchases are delivered through Hub, normally within a few minutes of payment. You need a valid email address to receive access, and a hosting environment that meets the product’s stated requirements: a supported WordPress version, a supported PHP version, and the server extensions the product names.

Envato purchases are delivered by Envato, and you can connect that purchase to a Hub account to get updates and documentation in one place.

If access has not arrived shortly after a payment, write to hello@jkdevstudio.com and we will sort it out.

Updates, support and how long a product lives

Updates arrive through Hub for as long as we publish them. Support is a separate thing with its own duration and its own rules, all of which are in our Support Policy.

We can retire a product, and here is what that means

We may stop selling a product, withdraw it from ThemeForest, or stop publishing updates for it. Studios do this: a product stops earning what it costs to maintain, or the platform underneath it changes, or it is replaced by something better.

What that does not do is take anything away from you:

• Your license stays valid on the terms you bought it under.
• The sites it is on keep working.
• Every version you already have remains yours, and stays downloadable from Hub.
• Support runs out its remaining period rather than being cut short.

Where a product is retired we say so on its page and to the people who own it, rather than letting it go quiet.

A marketplace can also make its own decisions about listings, which is one of the reasons the direct store exists: what we sell there, we control.

Paying

Direct purchases are sold by Creem as merchant of record. Legally Creem is the seller: it takes the payment, calculates and remits any tax due, and its terms govern the transaction itself. Prices are shown before tax and the total including tax is shown before you pay.

Marketplace purchases are sold by Envato under Envato’s terms.

Prices change from time to time. A change never reaches back to a purchase already made, and the price you were shown at the moment you pressed the button is the price you are charged. If those two ever disagree the checkout refuses rather than proceeding.

Subscriptions

Where a product or plan is sold on a recurring basis, these terms apply to it.

• It renews until you stop it. The billing period and the amount are stated at checkout, and Creem charges the same payment method each period until the subscription is canceled.
• You cancel it yourself, from your account, at any time, without asking us and without giving a reason.
• Canceling stops the next charge, not the current period. You keep everything you are paying for until the period you have already paid for runs out.
• When it ends, the subscription’s benefits end: updates, support and anything else the plan included. Any perpetual license you hold separately is untouched, and a site running a version you already had keeps running it.
• A price change is announced before it takes effect, in time for you to cancel first. It never applies to a period already paid.
• A failed payment is retried, and we tell you rather than closing the account quietly. Continued failure suspends the subscription’s benefits.
• Refunds on a recurring charge follow our Refund Policy, counted from the charge rather than from the original signup.

Refunds and cancellations

The full terms are in our Refund Policy and that page is the authority. In short: buy directly and you have 14 days, no questions asked, with a further window up to 30 days considered case by case. Buy on a marketplace and the request goes to that marketplace under its rules, reviewed on whether something is actually wrong with the product.

A refunded purchase revokes the license it paid for. You must remove the product from every site it is installed on and delete your copies of its files, and updates and support for it end.

Free products cost nothing and so there is nothing to refund.

Your account

You are responsible for what happens under your Hub account, so keep the password to yourself and tell us if you think somebody else has it. Give us an email address that works, because it is how a license, a receipt and a security notice reach you.

One account per person or per business. Accounts created to work around license limits, or to abuse trials, offers or refunds, get closed.

You can ask us to close your account whenever you like. What we do with the data at that point is in our Privacy Policy.

How we talk to each other

Our Support Policy sets out how support works and what it covers, and it asks for ordinary courtesy in return. Breaking it can end access to support, and to a refund. That is rare, and it is never our answer to somebody being frustrated with a broken site.

If you start a checkout, enter an email address and then leave without paying, Creem may send one reminder to that address. It is not part of the mailing list, it carries an unsubscribe link, and what happens to the address is set out in our Privacy Policy.

What we do not promise

Products are provided as they are. We test them properly and we fix what turns out to be broken, and we cannot promise that any piece of software is free of defects, or that it will run on every combination of host, WordPress version, PHP version, plugin and theme that exists.

Take a backup before installing or updating anything. That is not a disclaimer, it is the advice we would give a friend.

To the fullest extent the law allows, we are not liable for indirect or consequential loss, lost profit, lost data or business interruption arising from the use of a product, and our total liability for any claim is limited to what you paid us for the product it concerns. Nothing here excludes liability that cannot lawfully be excluded, including for death, personal injury or fraud, and nothing here affects the statutory rights of a consumer.

Ending it

You can stop using a product at any time. We can end a license where these terms are broken, as described above. The sections on ownership, liability and governing law survive whichever way it ends.

Which law applies

These terms are governed by the law of Ukraine, where the studio is established, and the courts there have jurisdiction. If you are a consumer in the European Union or the United Kingdom, this does not deprive you of the protection of the mandatory rules of your own country, or of your right to bring a claim there.

Where a marketplace sold you the product, that marketplace’s own governing law applies to the sale.

Changes to these terms

We update this page as the products and the way we sell them change, and the date at the top moves with it. A change never applies retroactively to a purchase already made: the terms you bought under are the terms you keep.