1. Application and parties
Use this addendum with a Website/Web Presence Engagement when hosting administration, ongoing support or transition needs clearer allocation. BlueDotHost is the Hosting Manager for DealDot Website/Web Presence services. This draft does not establish BlueDotHost’s legal entity, ownership relationship with DealDot, direct Client contract or infrastructure ownership.
Record $HOSTING_CONTRACTING_PARTY, $BLUEDOTHOST_LEGAL_ENTITY, authorized contacts, billing party and the accepted hosting document. Bindings and promises must be accepted by the party responsible for them; naming an entity does not make it a signatory.
2. Responsibility record
For each function, identify who performs it, who owns the account, who authorizes changes and who receives notices. Cover hosting account administration, deployment, content updates, domain registration, DNS, email DNS records, certificates, platform updates, user access, monitoring and incident communication.
DealDot performs the design/development/web-presence tasks it accepts. BlueDotHost administers the hosting tasks established for it. Infrastructure providers operate their own systems under their terms. Client controls business information and authorized users, and any accounts assigned to it. Resolve gaps and overlaps before launch rather than assuming one party handles everything.
3. Service levels and support
Complete $HOSTING_SCOPE and $SUPPORT_BOUNDARIES, including which issues go to DealDot, BlueDotHost or another provider and how requests are escalated. Define availability of channels, support hours or response commitments only if the responsible party accepts them.
There is no invented uptime percentage, service credit, recovery objective or response deadline. A provider SLA, if any, must be identified and reviewed; it is not automatically a DealDot guarantee. Scheduled maintenance and provider incidents follow the accepted arrangement and mandatory duties.
4. Domains, DNS and renewals
Record domain registrant, registrar, renewal payer, renewal date, account recovery contact and permitted DNS changes. Distinguish hosting renewal, domain renewal, email services, certificates and software licenses. Client should receive appropriate notice of actions requiring its approval or payment.
Set $RENEWAL_RULES and $PRICE where applicable. No automatic renewal, domain transfer, registration ownership or payment-on-behalf authority is inferred. Before a DNS migration, identify affected email, verification and external service records and an agreed change plan.
5. Backups and restoration
Complete $BACKUP_SCOPE with data covered, frequency, retention, location, responsible party, restoration procedure, test responsibility and exclusions. Specify any Client export or independent backup requirement and whether the platform supports it.
Backups may be incomplete, corrupted or unavailable; no recovery or zero-loss guarantee arises from this draft. Recovery objectives and paid restoration work require express terms. A configuration change or content deletion may affect available restore points and should be assessed before destructive action.
6. Security and incidents
Assign authentication, privilege management, patching, monitoring and incident contacts. Use proportionate safeguards and secure access exchange. Client must keep authorized users current; providers and DealDot must perform the specific controls they accept.
A relevant incident should be reported through the agreed contact without undue delay as required by applicable law and the accepted terms. Determine affected information, mitigation and communication responsibilities. Do not promise a security certification or a fixed breach-notification period without a verified accepted basis.
7. Restrictions, fees and suspension
Identify platform limits, acceptable-use rules, approved software, resource allowances and billing authorization. Provider restrictions can limit plugins, backups, storage, export or migration. Changes outside allowed use may require corrective action or revised scope.
Suspension should follow the responsible party’s accepted terms and lawful security requirements, with notice and a cure process where appropriate. Do not treat cancellation of a DealDot design service as authority to suspend a separately maintained hosting account. Any refund or credit policy must be stated in the relevant accepted document.
8. Transition and end of DealDot work
When DealDot services end, record whether BlueDotHost hosting continues, who remains authorized to manage it and how billing and support are handled. If hosting also ends, coordinate account access, exports, domains, DNS, third-party subscriptions and retention instructions before the effective end date.
Specify $TRANSITION_SCOPE, formats, feasible dates, fees and $DATA_DISPOSITION. No seamless migration, free transfer, indefinitely retained backup or automatic deletion promise is invented. Record platform and license limits, and preserve accepted documents even if the public directory moves.