Web Hosting in Richmond, VA

Writing down what the site actually does

The fix is dull and it is mostly an inventory. Before anybody writes a word of policy, somebody lists what the site collects, where each piece goes, and how long it stays. Across the offices here that list runs long in different ways: an intake form in one, a document upload and a scheduling tool in another, a driver application in a third. It takes about an hour and hardly anyone has made one.

Four questions worth answering before anything is written

• What arrives. Every form field, every file upload, every login. A free text message box that people paste account numbers and case details into collects account numbers and case details, whatever the label above it says.
• Where it lands. An inbox, a spreadsheet, a database on the hosting account, an outside tool, or several of those at once. One enquiry form commonly delivers the same message to three places while the policy mentions one.
• Who else gets a copy. Analytics, a chat widget, a map, a font service, an embedded scheduler. Each one is a separate company receiving something about your visitors, and each one belongs in the sentence.
• How long it stays. Not the number printed in the template. The number you will actually keep to, which for a firm holding client files usually means saying plainly that enquiries are kept as business records rather than deleted on a timetable nobody operates.

Once that list exists the policy more or less writes itself, and it will be shorter than the one you copied. Short and true beats long and borrowed. The same holds for a terms page, an engagement or fee schedule, and a cookie notice. Each is a claim about behaviour, and where the words are the service, a claim you cannot demonstrate is worse than making none.

There is a hosting consequence, which is why this sits on a hosting page rather than a legal one. The inventory is only stable if you can see what your own pages load. A site built inside a tool that injects scripts you did not choose can acquire a new recipient of visitor data on a Tuesday when you did nothing, and the policy becomes untrue without anybody editing it.

None of it needs a lawyer for most firms, which is a strange thing to write for a city with this many of them, though a regulated practice should have somebody qualified read the result. What it needs is a person looking after the site who can say exactly what it loads, and text you can correct the same afternoon a tool comes off. Stale here means inaccurate rather than merely old.

Moving a site without losing anything

Most enquiries here are about leaving something rather than launching something, and the order of work is the whole job. Copy the site where it can be tested, check it on a temporary address, and repoint the domain last. There is then never a moment when your published address leads nowhere. Website migration sets out that sequence.

The failure is nearly always mail. Somebody rebuilds the domain settings for the website and does not carry the mail entries across, and the firm goes off the air in the way that actually costs money, because in law, finance and freight the inbox is where the work lives. Email migration covers keeping mail alive through the change.

Two things get overlooked. Documents other people have linked to, a rate sheet or a set of terms, keep their old addresses inside emails you will never see again, so those either stay put or get redirected deliberately. And legal pages should move with dated copies attached, because what your policy said in a particular month is occasionally the whole question.

A move is judged on whether anything quietly stopped working, never on whether the home page looks the same. Enquiry forms are the usual casualty and they fail silently: the page still says thank you, the message goes nowhere. Send a real test through every form the day after the switch.