BearCat Websites Managed Website Service Agreement
This agreement describes the standard commercial relationship between BearCat Websites (“BearCat”) and the business purchasing the managed website service (“Customer”). The order, onboarding packet, approved scope, and any written addendum become part of this agreement when accepted.
1. Standard service
BearCat will design, build, host, and manage a professional small-business website within the agreed standard scope. The standard service uses the BearCat Standard Site OS baseline, including a responsive website, hosting, SSL, routine technical maintenance, lead/contact and private-feedback paths, owner controls and documentation, Digital Receptionist capability, analytics and source tracking, referral/QR utilities, review/service-recovery workflow, offers and announcements, a dedicated blog page with a managed weekly business-specific article, natural-voice audio playback for blog articles with Listen/Pause/Resume/Restart/Stop controls, brand-clean customer-facing deployment without site-builder badges or platform-branded public links, authenticated owner operations, backup/restore practices, accessibility and technical search foundations, site-quality monitoring, and optional owner-authorized Google connection for unread-Gmail summaries and Google Calendar booking delivery. Automated blog content is subject to factual and safety guardrails and is not a guarantee of search ranking, traffic, leads, or sales. Voice playback depends on browser/device speech support and always retains the written article as the primary accessible fallback. Features that depend on client-supplied facts, customer consent, third-party accounts, verified review profiles, sending domains, or an industry-specific workflow activate only when the required information or authorization is available. Features shown in demonstrations do not become contractual features beyond this standard baseline unless included in the approved client scope.
2. Introductory pricing and ongoing service
The current introductory offer is $50 per month for the first 12 successful monthly payments, with $0 upfront development fee, unless the Customer’s written order states otherwise. After the twelfth successful payment, ownership of the Customer-specific website transfers as described below. If the Customer chooses to continue BearCat-managed hosting, maintenance, support, and platform services after that transfer, the ongoing managed service is $99 per month unless BearCat and the Customer agree to another price in writing.
3. Billing and failed payments
Service is billed monthly. The Customer authorizes the agreed payment method for recurring charges until cancellation. BearCat may retry failed charges, request an updated payment method, suspend nonessential service after notice, or pause new work while an account is materially overdue. Fees already earned for a current service period are not automatically refundable because the Customer cancels during that period.
4. Cancellation
The standard service is month-to-month and may be cancelled by either party. Cancellation stops future managed-service billing after the applicable paid service period. If cancellation occurs before 12 successful monthly payments, the Customer may either leave the Customer-specific website with BearCat or pay the remaining ownership balance equal to the unpaid introductory monthly payments needed to reach payment 12, after which the transferable Customer-specific website may be delivered. The Customer’s domain, branding, Customer data, and Customer-supplied assets remain the Customer’s property regardless of cancellation.
5. Ownership and license
The Customer owns its domain, trademarks, logos, original photographs, business records, customer information, and other materials it supplies or already owns. After 12 successful monthly payments, BearCat transfers ownership of the Customer-specific website implementation created for that Customer, subject to payment of all amounts due. BearCat retains ownership of reusable templates, shared libraries, platform services, generic automations, internal tools, know-how, design systems, and components used across multiple customers. BearCat grants the Customer the rights necessary to operate the transferred Customer-specific site without implying transfer of those shared systems.
6. Customer responsibilities and factual approval
The Customer must provide accurate business information and promptly report important changes. The Customer is responsible for the legality and accuracy of pricing, promotions, credentials, licenses, financing claims, warranties, guarantees, testimonials, professional claims, emergency-service statements, and other business-specific representations. BearCat will not intentionally treat unverified demo language as a verified Customer claim. Before launch, the Customer must approve the public-facing business facts and materials.
7. Content and usage rights
The Customer represents that it owns or has permission to use all content supplied for publication, including photos, music, video, customer images, testimonials, logos, trademarks, and third-party materials. BearCat may decline to publish material when usage rights are unclear or when publication would create a material legal, security, or platform-policy concern.
8. Routine updates and out-of-scope work
Routine updates may include reasonable changes to hours, contact information, staff details, service descriptions, ordinary copy, photographs, prices, social links, and current offers. Major redesigns, substantial new page architecture, custom applications, complex databases, full ecommerce operations, large migrations, extensive copy production, paid advertising management, or advanced third-party integrations are outside the standard service unless separately agreed.
9. Support
BearCat targets a response to ordinary support and content requests within 48 business hours. This is a response target, not a guaranteed completion time. Urgent outages or material security incidents may be prioritized. Work requiring Customer clarification, third-party action, or out-of-scope development may take longer.
10. Security, forms, and access
BearCat uses reasonable safeguards such as HTTPS, authenticated administrative/client areas where supported, server-side authorization for privileged functions, validation, honeypots, and rate limiting on key public forms. No internet service is immune from interruption, misuse, software defects, third-party failures, or security incidents. Customers must protect login credentials and promptly report suspected unauthorized access.
11. Backup and recovery
BearCat follows the published Backup & Recovery Policy. In general, BearCat records a recoverable code/configuration restore point before client launch and before material managed changes when the platform supports restore points, tracks backup and site-health status in its operations system, and uses the most recent appropriate recoverable state when restoration is necessary. Database, email, analytics, uploaded-file, and third-party recovery capabilities may differ from code/configuration recovery.
12. Customer data and privacy
Information submitted through Customer forms may be made available to the Customer so it can respond to leads, service requests, feedback, and other customer interactions. The Customer is responsible for its own lawful handling of that information. BearCat’s Privacy Policy describes BearCat’s own data practices.
13. Third-party services
Domains, Google services, booking systems, payment processors, maps, analytics services, review platforms, social networks, hosting infrastructure, AI services, email systems, and other third-party services remain subject to their own availability, pricing, policies, permissions, and terms. Google-connected features require the Customer to authorize the relevant Google account and may stop working if authorization is revoked, expires, or Google changes access. BearCat is not responsible for a third party changing, restricting, or discontinuing its service.
14. AI, voice, analytics, and automated features
Website Assistant, Digital Receptionist, voice, analytics, summaries, recommendations, and other automated functions are convenience tools. They can make mistakes and do not replace professional judgment. BearCat does not guarantee that automated responses are complete, error-free, or appropriate for legal, medical, financial, safety-critical, or emergency decisions.
15. No guaranteed business results
BearCat does not guarantee search-engine ranking, traffic, leads, sales, revenue, reviews, accessibility outcomes, conversion rates, or other business results. Analytics and estimated-value metrics are informational and are not promises of revenue.
16. Transition after service ends
When a Customer owns the Customer-specific site and ends BearCat hosting, BearCat will provide a reasonable transition opportunity for available transferable Customer-specific materials. Unless otherwise agreed, the transition window is 30 days after the paid service period ends. Third-party accounts and the Customer-owned domain should remain under Customer control. Additional migration or redevelopment work may be quoted separately.
17. Suspension and acceptable use
BearCat may refuse, remove, or suspend content or functionality that is unlawful, fraudulent, malicious, infringing, materially deceptive, abusive to infrastructure, or prohibited by a platform provider. BearCat may also suspend service for material nonpayment after reasonable notice where practicable.
18. Electronic acceptance and entire agreement
The Customer may accept this agreement electronically, by signed document, approved checkout/ordering flow, or another written acceptance method BearCat provides. The accepted order details, this agreement, approved scope, and written addenda form the agreement between the parties and replace inconsistent informal discussions about the same service.
19. Questions and notices
Commercial questions, cancellation notices, and support requests may be sent to ContactBearCats@gmail.com or through another BearCat support channel designated to the Customer. BearCat may send operational notices to the Customer email address on file.
20. Practical launch requirement
BearCat may delay launch until critical readiness items pass, including correct contact details, functional forms, mobile layout, working links, social destinations, HTTPS, owner access, analytics where included, backup status, legal pages, and Customer approval.
Commercial version: September 29, 2026. Businesses with unusual regulatory, licensing, or contractual requirements may require an addendum.