pluggable
Contact

Where to write

Sorted by what you need, because the fastest route is rarely the general address.

Something is wrong with a plugin

Use the Report a problem form on the plugin’s own page. It reaches the review queue directly, and a well-founded report suspends the listing while we look. Faster than email, and it carries the plugin and version with it.

A security issue in the platform itself

Write to [SECURITY EMAIL] before telling anyone else, and give us a reasonable window to fix it. We will not pursue anyone who reports in good faith and stays within the scope of their own account.

Billing, refunds, a licence that will not activate

[SUPPORT EMAIL], from the address on your account. Include the plugin name and roughly when you bought it — with those two things we can usually answer in one reply instead of three.

Publishing: a rejected version, a payout, your rate

[PUBLISHER EMAIL]. For a rejected version, send the version page link: the findings and rule ids are already there, and we can look at the same thing you are.

Legal, press, anything else

[GENERAL EMAIL]

Before you write about a plugin

Its page already shows the review record: which stages ran, what they found, the risk score and the digest of the exact archive you have. Quoting the version and the rule id from there turns a long exchange into a short one.

Open the catalogue

[LEGAL ENTITY NAME] · [REGISTERED ADDRESS] · VAT [VAT NUMBER]

We answer within [RESPONSE TIME] working days. There is no phone line: we would rather give you a written answer we can be held to.