Security
What could go wrong here, who could cause it, and what stops them?
A template's security is whatever its last update left behind. We treat every build as something someone will try to break, and we write down what we checked.
The usual template studio
- Whatever access rules the theme or plugin shipped withOne wrong setting and every client sees every record.
- Every form field stored, keys pasted into settings pagesA breach exposes years of data you never needed.
- No limits until the spam or the outage arrivesThe inbox fills with junk, and the real inquiry is lost in it.
- Dozens of plugins nobody has read, updated when they breakEach update is a coin toss between a fix and a new hole.
- A green badge from a scanner, no record of what was checkedWhen something goes wrong, nobody can say what was tested.
What it costs you: the first sign of trouble is a customer telling you.
EWC
- Access checks where they matter mostEvery route decides on the server who may read or change what, before any data moves. Not a setting in a plugin that the next update resets.
- As few secrets and personal details stored as possibleWe keep only what the work needs and give it an expiry. Less stored means less to leak and less to explain.
- Limits on requests, senders, and form input where neededForms, logins and public endpoints have rate limits and input rules from day one, so abuse is boring instead of expensive.
- Reviews of third-party code and releasesEvery dependency is chosen, read and pinned. Releases go out on a checklist, not a hunch.
- Security checks you can retraceEach check leaves a record of what was tested, when and by whom. You can show it to an auditor or a client.

