Hosting, domains & transitions

BlueDotHost is the hosting manager. DealDot’s design, development and web-presence responsibilities should be distinguished from BlueDotHost’s agreed hosting administration and the infrastructure provider’s operations. The engagement records the exact arrangement.

That must be confirmed in your engagement. The site does not establish a universal billing or direct-contract arrangement. Identify the contracting party, payment responsibility, authorized contacts and relevant hosting terms before launch.

No. Hosting serves the website; a domain identifies it; DNS connects the name to services; email may have another provider and configuration. The responsibility record should identify ownership, administration, renewals and changes for each.

No universal uptime, support-response or recovery commitment has been established. Any such promise must be issued and accepted by the party responsible for it. A third-party provider’s SLA is not automatically a DealDot guarantee.

The accepted hosting scope must define what is backed up, by whom, how often, for how long and how a restore works. Do not assume all content, records or integrations are covered. A backup arrangement is not a guarantee of zero data loss.

The engagement must identify the account owner, renewal payer, date, authorization and notices. Domain, hosting and software renewals can have different terms. Keep account contacts current and confirm the arrangement before an expiry or provider change.

Discuss exports, licenses, account access and platform restrictions before committing to a platform. Migration scope, format, timing and charges must be agreed with the responsible parties. A fully editable export or seamless free transfer is not promised by default.

It depends on the accepted arrangement. Ending DealDot work does not automatically end a separate BlueDotHost or infrastructure service. Confirm what continues, what stops, billing, access, backups and transition before the effective end date.