Client-controlled registration
The client remains the registrant and billing owner of the domain whenever practical. HatterHosting receives only the access needed to complete the agreed work.
The contractor ownership pledge
These are HatterHosting's public operating standards. The signed proposal confirms the exact scope, payment status, licensed components, support allocation, cancellation notice, and handoff timing for a client project.
The client remains the registrant and billing owner of the domain whenever practical. HatterHosting receives only the access needed to complete the agreed work.
Local business profile, analytics, advertising, customer-management, calendar, payment, and other core business accounts remain client-owned. HatterHosting is added only in the supported role required for service.
After final payment, the client receives the administrative access, custom content, files, database export, media, and lead export listed in the agreement. Third-party themes, extensions, fonts, stock media, and software remain subject to their licenses.
Lead records collected for the client can be exported in a practical format when the service ends, subject to the client's retention instructions, privacy obligations, payment status, and platform limitations.
Recurring-care term and cancellation notice are confirmed before payment. Standard offboarding targets a documented handoff within five business days after identity, access, final balance, destination, and licensed-component questions are resolved.
The website is not intentionally made dependent on HatterHosting-only business accounts. A replacement provider may still need compatible hosting, active licenses, technical skill, and new service credentials.
Managed-service standards
Targets describe the managed service, not an unconditional warranty or a promise about third-party platforms.
Excludes planned maintenance, client-caused issues, upstream platform incidents, force majeure, and services outside the plan. A service-credit promise applies only if written into the agreement.
SSL, monitored hosting, software updates, backups, access controls, and other safeguards are configured according to plan. No internet service can promise absolute security.
We build and review semantic structure, keyboard paths, labels, contrast, responsive behavior, and alternative text within scope. This is not a blanket legal-compliance certification.
Critical availability or security reports receive priority review. Routine edits and improvements are scheduled within the support allocation of the plan.
Responsible automation
A feature appearing in a concept or sales page is not automatically live for every plan.
General contact permission does not activate marketing texts. SMS requires an approved disclosure, consent evidence, sender identification, opt-out handling, and a verified provider connection.
Call recording is not included by default. It stays off until the business has a jurisdiction-reviewed notice and consent workflow.
Review requests use the same documented completion milestone for every eligible customer—without incentives, requested ratings, selective routing, or suppression of negative feedback.
Fields, ownership, software fees, permissions, error handling, and the receiving inbox, calendar, CRM, or platform are verified before a connection is represented as active.
Calls to action and forms can come from the website. Response time, estimates, booked jobs, and revenue are reported only when reliable workflow or CRM data is available.
Agreed pages, mobile actions, forms, privacy language, search fundamentals, analytics events, account ownership, and connected handoffs are checked against the written scope.
Put the promise to work
We will inspect ownership risk alongside message clarity, mobile actions, trust, estimate friction, local foundations, and follow-up gaps.