Security
How we keep your website safe
A Send to Site website has no WordPress admin, no login page, no add-ons (plugins) and no database behind its pages, so the usual ways into a hacked website are not there. Only the email addresses you give us can ask for a change. Each change is made on a copy, checked twice, and goes live only when you tap Publish.
Last updated
What a hacker finds on a Send to Site website
- No WordPress admin area
- No login page
- No plugins or themes to break into
- No database behind the pages
What is there instead
- Plain, finished pages, served securely on Cloudflare
- Changes only from email addresses you have named
- A record of every change
Why sites get hacked
Why WordPress sites get hacked, and what a rebuilt site removes
The weak point of most WordPress sites is their add-ons (plugins). In 2025, 91% of new WordPress security flaws were found in plugins. A rebuilt site has no plugins, no login page and no database, so those ways in are gone.
Patchstack, a WordPress security company, counted 11 334 new security flaws around WordPress in 2025, 42% more than the year before. Themes had 9% of them. WordPress itself had just six, all of them low priority. The figures are in its State of WordPress Security in 2026 report.
Speed is the hard part. Patchstack found that 46% of those flaws had no fix when they were made public, and that the most targeted ones were typically attacked within hours, not days. A WordPress site is only as safe as its most neglected plugin.
Being hacked costs more than a clean-up. Google can show "This site may be hacked" under your name in search, and browsers can show a warning before your site even opens. To clear it you must clean the site and ask Google to look again, as its help page on sites labelled as dangerous explains.
No website is untouchable. With the usual ways in gone, two questions are left: who can change your site, and what can a change do? The rest of this page answers both.
| The usual way in | On a typical WordPress site | On a Send to Site website |
|---|---|---|
| Plugins and themes | Code from many different makers, each needing its own security updates | None. Your pages are finished files. |
| The login page | A public login page that password-guessing bots try day and night | No login page. Changes come by email from senders we have checked. |
| The database | Each page is put together from a database when someone visits | No database behind the pages |
| Updates | A steady stream of updates, any of which can break a page | Nothing of that kind to update |
Sender checks
Who can change your site
Only the email addresses you give us can ask for a change. And each email must prove it really came from that address.
Named addresses only
You tell us which email addresses may send changes: yours, and anyone on your team you choose. Mail from anyone else is never acted on.
We check the email is real
Email has its own tests for telling a real message from a fake. (The trade calls them DKIM, DMARC and SPF.) Every request must pass. A fake is refused.
Strangers get silence
An email from an address we do not know gets no reply. A person here is alerted.
Only your new words count
Text quoted from earlier emails is cut before your reply is read. An old instruction further down the email is never acted on.
Every change, every time
How every change is checked before it goes live
Every change is made on a copy of your site and must pass three checks before it can go live. Then it waits for you.
- 1
A separate copy
The change is made on a copy. Your live site is not touched while we work.
- 2
Automatic tests
The copy is built and tested, the same way every time.
- 3
A second pair of eyes
A separate reviewer reads the change and confirms it does only what you asked. It can read but not write, so it cannot change anything itself.
- 4
A block on outside code and deletions
Added tracking code, or a window onto another website, is blocked. So is any page that has been deleted or emptied.
- 5
You tap Publish
You get a preview with Publish and Cancel buttons. Reply to ask for something different. Nothing goes live until you tap Publish.
Every job also has a time limit, so a stuck job stops. See the whole change process, step by step
Publish buttons
Links that cannot be reused
Each Publish and Cancel button in our emails works for one change, once, for a limited time.
- Signed. Each link carries a seal we check, so a made-up or altered link does not work.
- Named. A button can only publish or cancel the change it was sent for.
- Single-use. Once tapped, it stops working.
- Expiring. It stops working after a set time, even if nobody taps it.
So an old email, or one forwarded to someone else, cannot publish something else.
Send to Site to you
Your preview is ready
Have a look, then publish it or tell us what to change.
Each button is tied to this one change, works once and expires.
Your data and POPIA
Your data, your visitors' data and POPIA
There is no database behind your pages and no login to steal. A change that would publish sensitive numbers or add tracking is stopped.
No ID, card or bank numbers on a page
South African ID numbers, card numbers and bank account numbers are never put on a page. A request that would publish one is stopped.
No new tracking
Tracking code and other outside code are blocked. A change cannot quietly add something that collects details about your visitors.
Nothing outside your website
Your domain, email, hosting accounts, social media accounts, payments and bookings are never touched. They stay under your control.
The Protection of Personal Information Act (POPIA) sets the rules for how South African organisations handle personal information. How Send to Site collects, uses and protects yours is set out in our privacy policy.
Version history
Version history and undo
Every change is kept on record: what went live on your site, and when.
A record of every change
Nothing reaches your site without leaving an entry. The record is kept in git, the tool software teams use to track every edit.
An undo is one reply
Reply to the email about a change and ask for it to be undone. The undo puts the page back exactly as it was, not roughly.
Archived, never deleted
Articles you say no to are filed, not thrown away, so the record of what was offered stays.
Limits, stated plainly
What we refuse, by design
Some requests get a no every time, because each would put your site, your visitors or your accounts at risk. If yours is one of them, a person explains why.
- Add tracking code or other outside code. It slows the site and can leak your visitors' details.
- Delete or empty a whole page. Too easy to do by mistake from a short email.
- Put an ID, card or bank account number on a page. The request is stopped.
- Touch anything outside the website. Your domain, email, hosting, social media, payments and bookings stay with you.
- Redesign the whole site from one email. That is a design project, not a change.
- Guess. When the system cannot handle a request, a person responds within one business day.
We tested this on purpose before launch. We sent the system 20 odd requests, among them defamatory text, a request to copy a competitor's design, a password reset and a South African ID number. Every one was handled correctly: refused, passed to a person, or stopped.
FAQ
Questions about website security
Can a static website be hacked?
It can be attacked, but there is far less to attack. There is no login page to guess, no plugin to break and no database to get into: only finished pages, served securely. What is left to protect is who can change the site. That is why every change must come from an address you have named, pass the checks and get your yes.
What stops someone pretending to be me?
Two checks. The email must come from an address you have named for your site. It must also pass the tests that email itself uses to tell a real message from a fake (DKIM, DMARC or SPF). A fake is refused. An unknown sender gets no reply, and a person here is alerted.
Do I still need security updates or a security plugin?
No. The site has no WordPress, theme or plugins, so there is nothing of that kind to update and nowhere to install a security plugin. The pages are plain files, served securely (over HTTPS) from Cloudflare.
Could an old or forwarded email publish something?
Not something else. Each Publish and Cancel button names one exact change, works once and then expires. An old email cannot publish a newer change, and a used button does nothing. Replies are safe too: text quoted from earlier emails is cut before your reply is read.
What if a published change turns out to be wrong?
Reply to the email about that change and ask for it to be undone. Every change is kept on record, and the undo puts the page back exactly as it was. The undo arrives as a preview, like any other change.
Does ChatGPT know your business?
Almost three in four of the Johannesburg businesses we tested were never named by an AI assistant. We check yours, free: how fast your site is, where you show on Google and whether AI mentions you. Then we talk you through it in plain words. Nothing to sign.
R1 500 a month for the first 6 months, then R750 a month. No setup fee.