Questions worth answering before you apply.
If a question you have isn’t here, write a short e-mail. The answer is faster than you’d expect, and the same person answers every time.
§ A. The programme
Is this really free, or free with conditions?
It is free for legally registered nonprofits. There is no fee, no upsell to a paid tier, and no requirement to publish a logo, tweet, or write a testimonial. The cost we ask is the time of submitting a short application.
Why does the licence last for the entity’s lifetime?
Because nonprofit teams change, and an annually renewed licence creates a hidden cost: the cost of remembering. Tying the licence to the organisation rather than to a person or a year removes that cost.
How many plugins can my organisation request?
All of the plugins listed on the catalogue page. There is no separate quota for “free” vs “paid” plugins inside the programme; if it is on the catalogue, you can ask for it.
§ B. Eligibility
My organisation is registered abroad. Does that matter?
Not as long as it is registered as a non-profit under its country’s law. The form lists a few common forms; if yours isn’t there, choose “other” and explain in the notes.
We’re a small project, not yet incorporated. Can we apply?
Not yet. The programme requires a current registration document. When you incorporate, write again.
We’re a religious congregation. Are we eligible?
Yes, if you’re registered with the relevant civic registry. Doctrine plays no part in the decision.
§ C. Licence & support
What does “lifetime support” cover?
Configuration help, troubleshooting, and the human attention of the author. It does not include theme work, custom development, or third-party plugin support, but the line tends to be drawn generously.
What is the response time?
Within five working days, usually faster. There is no service-level agreement; there is the author, in writing.
Can I transfer the licence if our developer changes?
The licence is tied to the organisation, not the person. Pass the key on. If you lose it, write to the author and we’ll re-issue.
§ D. Privacy
What happens to the registration document I upload?
It is stored encrypted, used only to verify eligibility, and deleted after twelve months — or earlier if you request it. It is never shared with third parties.
Will my organisation’s logo be used to promote the programme?
Only with explicit permission, and never as a condition of being in the programme. The default is silence.
§ E. After approval
Who installs the plugin?
Your team or your developer. The author can answer questions during the install but does not request hosting credentials.
When more plugins join the programme, do I get them automatically?
You’re notified. Adding a plugin to your licence takes a single short reply — no new application.