Licence agreement

The grant

Subject to your licence being current, we grant you a worldwide, non-exclusive, non-transferable right to install, run and modify Attestra on the number of WordPress sites your plan covers, for your own purposes or those of your clients.

There's no cap on how many credentials you issue, how many people verify them, or how long you keep running a version you already have.

GPL and what it means here

Attestra's PHP code is licensed under the GNU General Public License v2 or later, in line with WordPress itself. That gives you the freedoms the GPL grants, including the right to modify the code and to redistribute it under the same licence.

Some parts of the package are not GPL and are licensed to you only for use with a valid key:

• Bundled images, fonts, certificate templates and other non-code assets.
• The licence activation and update system.
• Access to updates, and to support.

In practice: the GPL protects your freedom to use and change the software. What you're paying for is a supported, updated, ready-to-run distribution of it — and that's the part we ask you not to hand out.

Site count and activation

Each activation ties a key to a domain. Your plan sets how many can be active at once:

Staging, development and local environments matching common patterns (staging., dev., test., .local, localhost) don't consume a slot. Deactivating a site frees its slot immediately, with no cooling-off period.

Client work and whitelabel

Building sites for clients is an expected use, not a grey area. You may:

• Install Attestra on a client's site under your own licence.
• Use whitelabel mode so the plugin appears as part of your build.
• Charge your client for the work you did around it.

You may not present Attestra as a product you wrote and sell it as such. On the Agency plan, handover licences let a client take over their own key so they keep getting updates after you've moved on — that's the clean way to leave a project.

Restrictions

You may not:

• Remove, disable or circumvent the licence activation system, or distribute a build with it stripped out.
• Share a key beyond the site count you paid for.
• Sell, sublicense or bundle the plugin as a standalone product or as part of a theme or plugin package you sell.
• Redistribute the bundled non-code assets separately from the plugin.

Updates and support

An active licence includes every update we ship for a year — features, improvements and security fixes — plus support at the level your plan carries.

Security fixes go out to everyone on a supported version as soon as they're ready, whether or not a renewal is due imminently. We're not going to hold a security patch hostage to a renewal.

When a licence lapses

This is the part people most want clarity on, so plainly:

• The plugin keeps working. It isn't disabled and doesn't nag you into uselessness.
• Every credential you've published stays verifiable. Nothing you issued stops resolving.
• Your data is untouched. Records, categories and templates stay in your database.
• Updates and support stop. That's the only thing you lose.

Renew whenever you like and you're straight back onto the latest version.

Ownership

We keep ownership of Attestra, its name, its branding and everything in it, except for rights the GPL grants you over the code. Your licence is permission to use the software — it isn't a transfer of ownership.

Anything you create with it — your credentials, templates, field definitions and records — is entirely yours. We claim nothing over it.

Warranty and liability

Attestra is provided without warranty of any kind, express or implied, including merchantability and fitness for a particular purpose. You are responsible for testing it against your own requirements — which is exactly why the free trial exists.

Our liability is limited as set out in the terms of use.

Ending the licence

This licence lasts until it's ended. It ends automatically if you breach a material term — typically by redistributing the plugin or defeating its licensing. On termination you must deactivate the key and remove the plugin from your sites.

The GPL rights over the code you already hold survive termination. What ends is your right to updates, support and the non-GPL parts of the package.