Getting helpWhat to include in a support request
The fastest requests are the ones we can reproduce without a back-and-forth. Give us your name or business name, the website address, what you expected versus what happened, the page or feature involved, and roughly when it started. A screenshot helps for anything visual.
Getting helpHow updates and turnaround work
Content updates are handled in the order received. Simple text and image changes are usually quick; new pages, new functionality and design changes are scoped first so you know what is involved before work starts. What is included depends on your Managed Website plan.
Your websiteBackups and restores, explained
A backup is a point-in-time copy of your site files and database. Restoring rolls the site back to that point — which also removes anything added since. That is why we confirm the target backup with you first, rather than restoring the newest one by default.
Your websiteKeeping your website secure
Most small-business sites are compromised through out-of-date software or a reused password, not a targeted attack. Keeping platform and plugin updates current, using unique passwords with two-factor authentication, and limiting admin accounts to people who need them removes most of the risk.
Security & complianceWhat PCI compliance means for your website
PCI DSS governs how card data is handled. Most small-business sites never touch it: payments run through a hosted processor such as Stripe or PayPal, so card details go straight to them and your site only sees the result. That keeps you in the simplest self-assessment category. It changes if you capture card numbers on your own pages — which we would advise against.
Security & complianceHIPAA and websites: what actually applies
HIPAA covers protected health information. An informational site for a practice — services, staff, hours, directions — generally does not hold PHI and is not the part of your operation HIPAA is concerned with. It becomes relevant when a site collects patient details through forms or portals, in which case the handling, storage and any vendor agreements need to be planned deliberately rather than assumed.
Security & complianceAccessibility: ADA and WCAG basics
WCAG 2.1 Level AA is the standard most ADA-related expectations point at. No plugin or overlay makes a site conformant, whatever it claims — real accessibility comes from structure, colour contrast, keyboard operation and text alternatives. We build to sensible accessible defaults; a formal conformance claim needs a dedicated audit.
Branded emailSetting up email on a new device
Add the account as IMAP rather than POP so it stays in sync, use your full email address as the username, and make sure the outgoing server has authentication switched on. The exact servers and ports are in the table below. If mail arrives but will not send, the outgoing settings are where to look first.
Branded email settings
Use these when adding your email to a phone, tablet or desktop mail app. Every connection uses SSL — if an app offers an unencrypted option, do not use it.
| Connection | Server | Port | Security |
|---|
| Incoming — IMAP recommended | secure.emailsrvr.com | 993 | SSL |
|---|
| Incoming — POP3 | secure.emailsrvr.com | 995 | SSL |
|---|
| Outgoing — SMTP | secure.emailsrvr.com | 465 | SSL |
|---|
- Your username is your full email address, including the domain.
- The outgoing server requires authentication — the same username and password as incoming.
- Choose IMAP unless you have a specific reason to use POP.
These guides are general information, not a compliance assessment or legal advice. If your business has a specific regulatory obligation, talk to us about it directly and we will tell you plainly what we can and cannot take on.