1. Introduction and acceptance
These Terms of Service govern access to and use of Grizzly Client Systems, referred to as GCS in this document. By submitting a setup review, creating an account, using a client workspace, or authorizing a subscription, the client agrees to these draft terms as the operating terms pending final lawyer-reviewed contracting.
2. Who may use GCS
GCS is intended for business use by local service businesses, their owners, authorized team members, and approved representatives. It is not intended for consumer household use, children, or anyone who lacks authority to bind the business or provide accurate setup, billing, and customer workflow information.
3. Account registration and workspace access
A client workspace may be provisioned after a setup review, verified payment, manual activation, or administrator approval. Client users must provide accurate names, emails, business details, and contact information. GCS may require email activation, passwords, two-factor authentication, and role-based workspace permissions before access is granted.
4. Client responsibilities
The client is responsible for business decisions made through the platform, customer relationship management, customer consent records, team access, password security, workspace accuracy, and the lawfulness of instructions given to GCS. Client staff must review prepared actions before relying on them or sending any customer-facing communication.
5. Platform role and limitations
GCS prepares, organizes, scores, recommends, and queues actions for owner review. It is an operations and revenue workflow tool, not a substitute for professional judgment, legal review, financial advice, advertising management, employment advice, or direct supervision of customer communications.
6. Approval-first workflow
The default GCS workflow is approval-first. Prepared messages, customer summaries, Close Assist materials, quote follow-up prompts, intake records, and revenue-at-risk queues remain internal until an authorized person reviews them and decides what to do. No external customer message is sent automatically unless provider settings, consent/compliance settings, and account rules are configured.
7. No guarantee of outcomes
GCS does not guarantee revenue, leads, bookings, jobs, advertising performance, legal compliance outcomes, customer responses, collection of unpaid invoices, online rankings, customer satisfaction, or specific business results. Any examples or scenario values are informational and depend on client conduct, market conditions, customer behavior, and third-party systems.
8. Revenue estimates and scoring
Revenue-at-risk estimates, lead scores, quote follow-up priorities, pipeline values, and suggested next actions are informational only. They may be based on client inputs, customer records, assumptions, or deterministic scoring rules. The client must verify values, timing, priority, and commercial judgment before taking action.
9. AI-assisted drafts and Close Assist
If AI-assisted or rule-based drafting is used, outputs may be incomplete, inaccurate, outdated, inappropriate for a specific customer, or unsuitable for regulated communications. Close Assist scripts are internal coaching material. They should be reviewed for tone, accuracy, consent, pricing, warranties, and business policy before use.
10. Customer communications
The client remains responsible for reviewing and approving business decisions and customer-facing communications. GCS may prepare email drafts, reminders, summaries, and owner-review tasks, but the client is responsible for confirming the customer relationship, consent status, message content, sender identity, unsubscribe requirements, and timing.
11. Email automation and approval rules
Email automation features, if enabled, must be configured with approved provider credentials, compliance settings, suppression rules, and account-level sending permissions. Unless those requirements are configured, GCS does not automatically send marketing campaigns or customer follow-ups. Transactional account messages may be handled separately from commercial customer outreach.
12. Inbound call and voice features
Inbound call, call transcript, voice assistant, voicemail, or phone-provider features may be introduced later. If enabled, they may require additional consent, recording notices, telecom-provider terms, data-retention settings, and jurisdiction-specific review. No client should assume voice features are active unless account settings explicitly show they are enabled.
13. Payment, subscriptions, taxes, and Stripe
Subscriptions and hosted checkout are handled through Stripe when configured. GCS may store Stripe customer, checkout, price, and subscription identifiers, but it does not store card numbers or card security codes. The client is responsible for applicable taxes, accurate billing details, and any signed order terms.
14. Cancellations, failed payments, and suspension
Failed payments, expired cards, chargebacks, misuse, security concerns, or unpaid balances may result in past-due status, feature limits, suspension, or manual review. Cancellation, refund, renewal, proration, and data-return terms should be finalized in a lawyer-reviewed subscription agreement or order form.
15. Client data and customer data
Client data includes business profile information, workspace configuration, users, setup records, billing metadata, internal notes, and support communications. Customer data includes inquiry records, request details, contact information, follow-up history, and related workflow information supplied by or on behalf of the client.
16. Acceptable use
The client must use GCS only for lawful business purposes and in a manner consistent with the Acceptable Use Policy. The client must not use GCS to send spam, impersonate others, deceive customers, ignore unsubscribe rules, collect data unlawfully, harass people, or bypass platform security.
17. Prohibited activities
Prohibited activities include unauthorized access, credential sharing outside approved users, reverse engineering, scraping, abusive load, malware, deceptive offers, unlawful regulated claims, harassment, discrimination, fraudulent billing, attempts to disable logging, or use of GCS to prepare messages the client has no lawful right to send.
18. Security responsibilities
GCS uses reasonable safeguards, but clients remain responsible for strong passwords, account access decisions, role assignments, device security, secure email accounts, careful review of activation links, and prompt reporting of suspected unauthorized access. No system, provider, or workflow can be guaranteed perfectly secure.
19. Third-party services
GCS may depend on third-party services, including Stripe, hosting providers, email providers, analytics or logging providers, security tools, and, if later enabled, voice or telephony providers. Third-party availability, pricing, terms, outages, and data handling may affect platform operation and remain partly outside GCS control.
20. Service changes and availability
GCS may update workflows, features, routes, templates, pricing pages, security requirements, and supported provider integrations over time. Availability may be affected by maintenance, security events, provider outages, infrastructure changes, or emergency fixes. No uninterrupted or error-free service is promised in this draft.
21. Beta and pilot features
Some features may be released as pilot, beta, preview, or manually operated features. These features may change, be removed, have limited support, or require additional review before production reliance. Pilot use does not create a guarantee that a future feature will be released.
22. Intellectual property
GCS, its platform structure, templates, software, workflows, visual design, internal tools, documentation, and operating methods remain owned by GCS or its licensors. The client receives only the limited right to access and use the subscribed service for its own business during the subscription term.
23. Client content license
The client grants GCS a limited license to host, process, display, analyze, format, and use client content and customer data as necessary to operate the platform, provide support, secure the service, prepare workflows, maintain records, and comply with legal or contractual obligations.
24. No client code or repository access
Client portal, workspace, setup review, and paid subscription access do not include access to source code, repositories, deployment credentials, internal admin tools, platform controls, infrastructure accounts, or proprietary automation logic. Any such access would require a separate written agreement.
25. Confidentiality
Each party may receive non-public business, pricing, customer, workflow, security, or operational information from the other. Confidential information should be used only for the service relationship and protected with reasonable care, subject to legal obligations, provider needs, and authorized support access.
26. Disclaimers
GCS is provided as an operations tool and draft workflow system. To the extent permitted by law and subject to final legal review, warranties not expressly stated in a signed agreement are disclaimed, including implied warranties of merchantability, fitness for a particular purpose, and non-infringement.
27. Limitation of liability
Liability limitations require lawyer review before full commercial reliance. This draft anticipates reasonable limits tied to fees paid, exclusion of indirect damages where permitted, and exceptions that may be required by law, fraud, intentional misconduct, confidentiality, data protection, or indemnity obligations.
28. Indemnity
The client should be prepared to defend or reimburse GCS for claims arising from unlawful client instructions, customer communications, consent failures, inaccurate client data, misuse, prohibited activities, or customer-facing claims approved by the client. Final indemnity language requires lawyer review.
29. Termination
GCS may terminate or suspend access for non-payment, security risk, unlawful use, material breach, or discontinuation of the service. The client may stop using the service and request cancellation according to the applicable subscription terms. Data export, deletion, and retention terms require final review.
30. Governing law placeholder
The anticipated governing law placeholder is Ontario and the laws of Canada applicable there, pending lawyer review. Venue, arbitration, class action waiver, consumer-law interaction, and cross-border enforceability should be reviewed before full commercial reliance.
31. Contact
Questions about these draft Terms may be sent to [email protected] or the configured GCS support email shown on this page. Legal notices, if any, should use a final lawyer-approved notice process once commercial documents are completed.
32. Lawyer-review notice
These Terms are serious draft legal documents for review, not final lawyer-approved documents. Draft for review. Not legal advice. Lawyer review required before full commercial reliance.
Support
For questions about these terms, your data, or your account, contact [email protected].