Last Updated on June 10, 2025
34.1 No Guaranteed Uptime
Chariot does not guarantee uninterrupted availability. Maintenance, updates, or infrastructure issues may cause periodic service disruptions.
34.2 Scheduled Maintenance
We may schedule planned maintenance windows with or without notice. During such periods, parts or all of the app may be inaccessible.
34.3 Performance Variability
Performance may vary by user location, device, OS, or third-party vendor (e.g., OpenAI, Supabase). Chariot does not ensure uniform performance across all devices or regions.
34.4 System Load Impact
High demand may result in temporary slowdowns, rate-limiting, or access gating to preserve core functionality for other users.
34.5 Infrastructure Scaling
While Chariot uses elastic infrastructure (e.g., Supabase, Railway), rapid user growth may temporarily exceed capacity before autoscaling is complete.
34.6 No Bug-Free Warranty
We do not warrant that Chariot will be error-free. Minor bugs, visual glitches, or intermittent issues are expected in active development phases.
34.7 User-Reported Bugs
You may report bugs through official channels. Chariot will assess severity and prioritize accordingly but is not bound by response timelines.
34.8 Feature Beta Warnings
Some features may be marked as “beta” or “experimental.” Their functionality is not final and may break, degrade, or be removed without notice.
34.9 Refunds for Bugs Not Guaranteed
Unless a bug materially prevents access to a paid core feature for an extended period, no automatic refund or credit is offered.
34.10 Dependency Failures
Failures in external services (e.g., OpenAI outage, Apple In-App Purchase delay) are not considered “bugs” attributable to Chariot.
34.11 No Control Over External Events
Chariot is not liable for delays, interruptions, or failures caused by events beyond our reasonable control, including but not limited to:
Power outages
Internet disruptions
Cloud provider outages
Cyberattacks
Fires, floods, or natural disasters
War, riots, or terrorism
Governmental restrictions
AI provider outages (e.g., OpenAI)
34.12 No SLA Compensation for Force Majeure
We are not obligated to compensate users for downtime caused by force majeure unless otherwise stipulated in a written SLA.
34.13 Act of God Provisions
Chariot shall be excused from performance under this agreement if a qualifying force majeure event prevents continued operation.
34.14 Data Loss From Catastrophic Failure
In case of unrecoverable data loss due to force majeure, users are encouraged to maintain backups of critical reports or exports.
34.15 Priority of Restoration
In such events, restoration priority will be given to critical systems such as user login, report access, and AI response functionality.
34.16 Use At Your Own Risk
By using Chariot, you accept the possibility of temporary outages, partial failures, or unintended behavior due to bugs or outages.
34.17 No Guarantee of Result Delivery
We do not guarantee that every prompt, upload, or report will succeed. Retries may be necessary.
34.18 Retrying Is User Responsibility
If a prompt or upload fails, users are expected to retry when service is restored. We may issue credits but not refunds in these scenarios.
34.19 Third-Party Bug Dependencies
SDKs and APIs used in Chariot (e.g., RevenueCat, Supabase, OpenAI) may introduce bugs. These are tracked, but outside our codebase and control.
34.20 Unsupported Device Risks
Devices or OS versions not explicitly supported may experience degraded performance. Chariot assumes no liability for issues on outdated systems.
34.21 Total Downtime Threshold
Only if system-wide, premium-tier outages exceed 72 cumulative hours in a 30-day period will refund eligibility be considered.
34.22 Bug Fix ETA Not Guaranteed
We do not commit to fixing any bug within a specific timeframe. Priority is based on severity, reproducibility, and impact.
34.23 Subservice Dependency Mapping
Bug root causes may originate from multiple layers (e.g., frontend, backend, AI model, API latency). Users acknowledge complexity of diagnosis.
34.24 Waiver of Indirect Damages
You agree that Chariot is not liable for lost profits, productivity, or business opportunity due to bugs, outages, or degraded service.
34.25 Cloud Provider SLA Subordination
Our infrastructure runs on providers like Railway, Supabase, and AWS. Chariot’s availability is subject to their uptime commitments.
34.26 Status Page and Incident Log
We may offer a public-facing status page or changelog to track bugs, downtimes, and fixes. This is provided for transparency, not warranty.
34.27 No Punitive Damage Eligibility
Bugs, downtime, or interruptions shall not entitle any user to punitive, incidental, or consequential damages.
34.28 Notification of Extended Downtime
We will make commercially reasonable efforts to notify users of prolonged outages via in-app banner, email, or landing page alerts.
34.29 Service Restoration Rights
We reserve the right to prioritize restoration of paying users before free-tier users during major outages.
34.30 Survival of Clause
These terms survive termination of account and remain enforceable post-outage for any residual disputes.
Contact Us
If you have any questions or concerns about our Terms of Service or the handling of your personal information, please contact us at support@chariotreport.com