A financial marketing site is a regulated document that happens to be published on the web. What matters is not only that it is fast, but that you can prove what it said on a given day.
The traffic is ordinary. The obligations attached to what the pages say are not.
If a regulator asks what your rates page said last March, the answer has to be better than a backup somebody hopes still exists.
Published rates change on a schedule and must be correct the moment they do. Clearing the whole cache to update one table throws away everything else at the same time.
An application enquiry carries financial and identity information. It bypasses caching, is encrypted at rest, and never appears in a request log.
Products that cannot be marketed in a jurisdiction should not be served there. Blocking at the edge is enforcement; a disclaimer in the footer is not.
Availability commitments in a vendor questionnaire need numbers behind them. Independent monitoring produces a record you can hand over.
Most of the work here is not preventing incidents, it is being able to reconstruct exactly what happened months later without a fire drill.
One table has to be correct immediately across every page that embeds it, while the rest of the site keeps serving from cache.
These differ from a standard WordPress site on the same plan, and each follows from the page being a regulated statement rather than only a page.
| Setting | What we do | Why |
|---|---|---|
| Revision retention | Unlimited revisions on disclosure and rate content, retained to your policy | WordPress prunes revisions by default, which removes the only record of what a regulated page said on a date somebody may later ask about. |
| Cache invalidation | Scoped to the pages embedding a changed rate table | Published rates must be correct the instant they change, and a full purge to achieve that discards the cache protecting every unrelated page. |
| Application and lead forms | Cache-exempt, encrypted at rest, excluded from request logs | Financial enquiries carry identity and income data, and default request logging captures query strings that were never meant to persist. |
| Jurisdictional access | Enforced at the edge rather than declared in page copy | Marketing a product where it is not authorised is a supervisory issue, and a footer disclaimer does not stop the page being served. |
| Access log retention | Immutable and held for the full audit window | Vendor due-diligence and incident reconstruction both need logs older than a standard rolling window keeps. |
Every plan includes free migration, daily backups, SSL and 24/7 support.
Free migration, versioned disclosures, and rate changes live in seconds.