Denton BBQ LLC · Proposed agreement template
Managed Backup & Recovery SLA Addendum
Optional paid recovery services — proposed project-specific schedule.
1. Client and project identifiers
Client legal name: [Client entity]. Project name and domain(s): [Project]. Primary and alternate incident contacts: [Name, email, telephone]. Master Service Agreement / SOW reference: [Reference].
Addendum start date: [Date]. Term, renewal and cancellation notice: [Agreed terms]. Monthly or other recovery service fee: [Quoted amount]. This draft does not set a price or constitute billing authorization.
2. Complimentary copy versus contracted managed recovery
Clients may receive internal backup copies of supported sources without a separate fee. Opting out of a paid managed recovery SLA does not instruct Denton BBQ to stop those operational copies. The distinction is between a best-effort internal safeguard and additional documented contractual services.
| Service feature | Complimentary protection | Paid managed recovery — proposed |
|---|---|---|
| Independent encrypted backup copies | For supported sources where configured | For sources specifically listed in the agreement |
| Backup job alerts | Internal monitoring and troubleshooting | Defined notification and escalation contacts, if agreed |
| Restoration assistance after an incident | Best-effort, quoted separately where required | Scoped restoration assistance under an executed service schedule |
| Recovery request priority | No dedicated recovery-priority commitment | Documented severity and response targets, when negotiated |
| Restore-test frequency and evidence | Internal tests at Denton BBQ's discretion | Customer-specific test schedule and evidence when contracted |
| Recovery point and recovery time objectives | No contractual RPO or RTO | Explicitly agreed objectives only; never assumed |
| Retention beyond standard configuration | No separately guaranteed extension | Optional, quoted extended retention if technically supported |
| Project recovery runbook and reporting | Not a dedicated client deliverable | Included only to the extent detailed in the signed addendum |
For example, a project may continue receiving baseline copies while its optional, separately billable managed recovery service remains unselected. This addendum becomes applicable only after the relevant client signs an agreed project-specific version.
3. Covered assets and dependencies
Source repositories: [Exact owner/repository names, branches and scope]. Databases: [Exact Neon project, database and production branch names]. Uploaded files or object stores: [Locations if contracted]. Other systems: [Kintone apps, QuickBooks, Clerk, Stripe, domain/DNS, email, etc. only if separately inventoried and explicitly covered].
A GitHub repository and PostgreSQL dump do not, by themselves, reproduce all third-party data, secret configuration, identity-provider state, stored files or running infrastructure. Each included source must be documented in an approved inventory.
4. Backup operation and retention schedule
Contracted backup frequency: [Schedule and timezone]. Backup destination(s): [Agreed storage/service and region]. Encryption and key custody: [Approved model and key-access contacts]. Versioning and object-lock configuration: [Scope, length and limitations].
Additional retention beyond the current operational configuration: [Exact terms, or Not included]. Data deletion, offboarding, geographic requirements and any legal hold: [Project-specific terms]. Nothing in this draft promises that backups can be retained indefinitely or recovered after agreed retention expires.
5. Recovery Point Objective (RPO) and Recovery Time Objective (RTO)
Proposed maximum RPO: [Number and unit, if feasible and agreed]. RPO describes the target age of recoverable data, not a guarantee of zero data loss. Daily backups alone should not be described as continuous protection.
Proposed target RTO: [Number and unit, if feasible and agreed]. RTO is the target time to restore a defined service under agreed prerequisites; it is separate from initial response time and can be affected by provider availability, damaged systems, third-party access and validation requirements.
No RPO/RTO commitment applies until completed values, start/stop measurement rules, scope and exclusions are approved in a signed addendum.
6. Recovery request, escalation and assistance
Authorized request methods: [Portal, verified email or phone]. Severity classification and support window: [Agreed details]. Target first human response for recovery requests: [Agreed interval]. Update cadence: [Agreed interval]. Restoration priority relative to other incidents: [Defined priority].
Client approves destructive restores or replacement of current production data through an authenticated authorization process. Restore actions should first target an isolated environment where practical. Client acceptance testing and production cutover responsibility: [Agreed owners].
7. Verification, reporting and exercises
Routine backup success reporting: [Frequency and delivery method]. Periodic isolated restore-test frequency: [Quarterly, semiannual, annual, or as negotiated]. Sample workload and acceptance criteria: [Scope]. Evidence retained: [Logs, test result and signoff].
Failed-run alert handling, coverage for a scheduled run that never starts, and escalation contacts: [Agreed details]. Monitoring automation alone does not mean a staffed overnight response team is retained.
8. Exclusions, charges and responsibility
Restoration outside the defined scope, custom rebuilds, customer-created data errors, compromised third-party accounts, recovery of unbacked external SaaS content and after-hours hands-on work may require separate written authorization and fees.
Extra charges, restoration exercises, retention upgrades, third-party storage/service fees and any service credit/remedy are determined by the signed SOW/MSA and this completed addendum. An unchecked billing checkbox does not remove the customer's ownership of its data or eliminate baseline safeguards where already configured.
9. Acceptance record
Client authorized signatory: [Name/title] ______________________ Date: __________
Denton BBQ LLC authorized signatory: [Name/title] ______________________ Date: __________
Included rate schedule / invoice reference: [Document ID]. Scope revision / attachment list: [Document ID].
Signature lines are provided as a template only; no electronic signature or consent is recorded by this page.
Execution and incorporation
This document becomes operative only if attached to or expressly incorporated into a signed client agreement that identifies the relevant project, scope, fees, effective date, service objectives, and authorized representatives. Until then, existing executed agreements control.
Document status: proposed template · Draft prepared October 26, 2026 · Not a representation of any client's current entitlement.
For a signed client-specific copy, contact jeff@dentonbbq.com. This page may be printed using your browser's Print command; printing it does not constitute acceptance.