LoyalBase
Legal

Service Level Agreement

LoyalBase Platform — SLA

Effective Date: April 12, 2026

Introduction

This Service Level Agreement ("SLA") describes the service availability commitments, support response times, and credit policy provided by LoyalBase LLC ("LoyalBase," "we," "us") to customers ("Customer") of the LoyalBase platform.

This SLA forms part of the Terms of Service between LoyalBase and Customer. In the event of a conflict between this SLA and the Terms of Service, this SLA prevails with respect to service availability matters.

Effective Date: April 12, 2026.

1. Definitions

  • "Monthly Uptime Percentage" means the total minutes in a calendar month minus the total Downtime minutes in that month, divided by the total minutes in the month, expressed as a percentage.
  • "Downtime" means the total accumulated minutes per calendar month during which the LoyalBase platform is unavailable and not responding to authenticated API requests, excluding Scheduled Maintenance and Excluded Events.
  • "Scheduled Maintenance" means maintenance periods announced by LoyalBase at least 48 hours in advance via the status page or email notification.
  • "Excluded Events" means events as described in Section 7 of this SLA.
  • "Service Credits" means the percentage of the applicable monthly subscription fee credited to Customer's account as the sole remedy for failure to meet the uptime commitment.
  • "Billing Cycle" means the monthly period for which Customer is billed for the Services.

2. Service Availability Commitment

2.1 Uptime Target

LoyalBase targets a Monthly Uptime Percentage of 99.9% for all paid subscription plans. This target applies to the core platform services: the Member App, the Tenant Dashboard, and the LoyalBase API.

2.2 Service Credit Schedule

If LoyalBase fails to meet the uptime target in any calendar month, Customer is eligible for Service Credits according to the following schedule:

  • Monthly Uptime < 99.9% and ≥ 99.0%: 10% Service Credit
  • Monthly Uptime < 99.0% and ≥ 95.0%: 25% Service Credit
  • Monthly Uptime < 95.0%: 50% Service Credit

2.3 Plan-Based Applicability

Service Credits apply as follows by subscription plan:

  • Starter Plan: Service Credits are not available. LoyalBase commits to a best-effort 99.9% uptime target, but no credits are issued.
  • Pro Plan: Service Credits apply per the schedule in Section 2.2.
  • Scale Plan: Service Credits apply per the schedule in Section 2.2. Scale customers also receive priority incident response as described in Section 5.
  • Enterprise Plan: Custom uptime commitments and credit schedules are defined in the applicable Order Form.

3. Service Credit Conditions and Limitations

Service Credits are Customer's sole and exclusive remedy for any failure by LoyalBase to meet the Monthly Uptime Percentage commitment. Service Credits are not refundable as cash and may only be applied toward future subscription fees.

The maximum total Service Credits issued to Customer in any single calendar month shall not exceed fifty percent (50%) of the subscription fee paid by Customer for that month.

Service Credits do not apply if Customer's account is past due or suspended at the time of the incident.

4. Scheduled Maintenance

LoyalBase performs scheduled maintenance to ensure the reliability, security, and performance of the platform. Scheduled maintenance is excluded from Downtime calculations.

LoyalBase will provide at least 48 hours' advance notice for scheduled maintenance expected to impact service availability. Notices will be published on the LoyalBase status page and sent by email to the primary account contact.

LoyalBase targets a scheduled maintenance window of Sunday 02:00–06:00 UTC. LoyalBase endeavors to complete all maintenance within the announced window and to minimize actual impact on service availability.

Emergency maintenance required to address critical security vulnerabilities or active incidents may be performed with shorter notice. LoyalBase will provide as much advance notice as circumstances permit.

5. Support Tiers

5.1 Support Channels

Support is available through the following channels based on subscription plan:

  • Starter: Email support via support@loyalbase.dev. Response target: 2 business days.
  • Pro: Email support + live chat (Crisp widget in dashboard). Response target: 1 business day for email; same-day for chat during business hours.
  • Scale: Email support + live chat + dedicated Account Manager contact. Response target: 4 business hours for email; real-time for chat.
  • Enterprise: Dedicated support channel. Response times defined in the applicable Order Form.

5.2 Severity Levels

LoyalBase categorizes support requests by the following severity levels and targets:

  • Critical (P1) — Platform completely unavailable or data loss in progress. Target first response: 1 hour (Pro/Scale/Enterprise). Starter: 4 hours.
  • High (P2) — Major feature unavailable, significant business impact. Target first response: 4 hours (Pro/Scale/Enterprise). Starter: 1 business day.
  • Medium (P3) — Feature degraded, workaround available. Target first response: 1 business day (all plans).
  • Low (P4) — General questions, feature requests, minor issues. Target first response: 2 business days (all plans).

5.3 Business Hours

Business hours for support purposes are Monday through Friday, 09:00–18:00 Eastern Time (ET), excluding U.S. federal holidays. Critical (P1) issues are handled on a best-effort basis outside business hours for Pro and Scale plans.

6. Status Page and Incident Communication

LoyalBase maintains a public status page where current platform status, active incidents, and historical uptime data are published.

Upon identifying an incident affecting service availability, LoyalBase will post an initial incident report within 30 minutes of detection, followed by regular updates until the incident is resolved.

A post-incident report will be published within 5 business days for P1 incidents, summarizing the root cause, timeline, and corrective actions taken.

7. Exclusions

The following events are excluded from Downtime calculations and do not entitle Customer to Service Credits:

  • Scheduled Maintenance as defined in Section 4
  • Events caused by factors outside LoyalBase's reasonable control, including Internet outages, force majeure events, and acts of government or regulatory bodies
  • Actions or omissions by Customer or Customer's users, including unauthorized access to Customer's account, misconfiguration by Customer, or use of the Services in violation of the Terms of Service
  • Failures of third-party services or infrastructure not within LoyalBase's direct control, including Supabase, Vercel, or other sub-processors, except where such failures result from LoyalBase's failure to implement reasonable failover or redundancy measures
  • Denial-of-service (DoS) or distributed denial-of-service (DDoS) attacks targeting Customer's account or the platform generally
  • Customer's failure to maintain current browser or operating system software compatible with the platform
  • Beta features or services explicitly designated as experimental or preview

8. Measurement and Monitoring

LoyalBase measures Monthly Uptime Percentage using internal monitoring systems that perform authenticated health checks against the LoyalBase platform endpoints at regular intervals. Monitoring is performed from multiple geographic regions.

A service is considered "unavailable" when three or more consecutive health checks from at least two independent monitoring locations fail to receive a successful response within a 30-second timeout.

Uptime records are retained for a minimum of 12 months and are available to customers upon written request.

9. Claims Procedure

9.1 Submitting a Claim

To receive a Service Credit, Customer must submit a claim within 30 days of the end of the affected calendar month. Claims must be submitted by email to legal@loyalbase.dev with the subject line "SLA Credit Request — [Month/Year]" and must include: the Customer's account name, the dates and times of the claimed Downtime, and a description of how Customer was affected.

9.2 Credit Determination

LoyalBase will evaluate the claim using its monitoring data within 15 business days of receipt. If the claim is validated, LoyalBase will apply the applicable Service Credit to Customer's next invoice. LoyalBase's determination is final, subject to Customer's right to dispute via the process in the Terms of Service.

10. Limitation of Liability

Service Credits are the sole and exclusive remedy available to Customer for any failure by LoyalBase to meet the service availability commitments set forth in this SLA. The maximum aggregate liability of LoyalBase under this SLA in any calendar month shall not exceed the Service Credit caps described in Section 3.

Nothing in this SLA limits either party's liability for fraud, death or personal injury caused by negligence, or any liability that cannot be excluded by applicable law.

11. Updates to This SLA

LoyalBase may update this SLA from time to time. Material changes will be communicated to Customer by email at least 30 days before taking effect. Customer's continued use of the Services after the effective date of any update constitutes acceptance of the updated SLA.

If LoyalBase reduces the uptime commitment or service credit levels applicable to Customer's current plan, Customer may terminate its subscription for cause with a pro-rated refund of prepaid fees by providing written notice within 30 days of the effective date of such change.

12. Governing Law

This SLA is governed by the laws of the State of Florida, United States, without regard to conflict of laws principles. Any disputes arising under this SLA shall be subject to the exclusive jurisdiction and venue set forth in the Terms of Service.

SLA and Support Contact

For SLA claims, uptime inquiries, or support escalations, contact us at legal@loyalbase.dev or support@loyalbase.dev

LoyalBase LLC

7901 4th St N, Ste 300

St. Petersburg, FL 33702, USA

+1 (561) 408-5283

Service Level Agreement — LoyalBase