Ophraxx
Disclaimer: This website is currently in beta testing. Some features may not be complete, and content may be out of date.

Service Terms

Back to Other Policies

Last updated: March 2026

1. Overview and Relationship to Terms of Use

These Service Terms apply to specific features, access channels, and plans and supplement our Terms of Use. Our platform—including the conversational bot and the website and web applications—is built and operated by us. All models in our platform run on the Ophraxx Web Core, our proprietary infrastructure. Feature availability, limits, and behavior are defined and enforced in-house. By using the Service, you agree to these Service Terms in addition to the Terms of Use. In the event of a conflict, the Terms of Use govern unless these Service Terms expressly state otherwise for a specific feature.

2. Bot and Conversational Service

When you use our conversational AI (e.g. in a server or connected space where the bot is installed):

  • Availability: The bot responds in real time subject to our rate limits and quotas (e.g. 25 messages per user per day, 3,000 per server per month, 1 request per 2 seconds per user). We do not guarantee uninterrupted availability; we may perform maintenance or deploy updates that briefly affect availability.
  • Session and context: Conversation context is held in memory for a limited session (e.g. 15 minutes of inactivity) and is not persisted to a long-term database. Restarts or session expiry clear in-memory context.
  • Safety and moderation: All inputs and outputs pass through our in-house safety pipeline (validation, safeguard models, output checks, PII redaction). Violations may result in blocked messages, soft-blocks, or escalation as described in our Trust & Transparency and Security & Privacy pages.
  • Configuration: Server or space administrators may configure channels, invoke behavior, and toggles; such configuration is stored by us to apply consistently. You must use the bot in compliance with our Usage Policies and the rules of the space.

3. Website and Web Applications

When you use our website and web applications:

  • Account and profile: You may register an account and set a profile (username, display name, bio, preferences, etc.). You are responsible for the accuracy of your data and for keeping your credentials secure. We may offer two-factor authentication (2FA); use of 2FA is subject to our authentication and security practices described in our Security page.
  • Settings and preferences: Settings (e.g. notifications, language, accent color, custom instructions) are stored and applied by our systems. Changes may take effect immediately or on next use depending on the feature.
  • Sessions and activity: We may show you active sessions and login activity for account security. This data is used only by us and is not shared for advertising.
  • Availability: We do not guarantee uninterrupted availability of the website or web app. We may perform maintenance or updates that temporarily affect access.

4. Beta and Experimental Features

We may offer beta or experimental features (on the bot, web, or both). Such features may be provided without warranties and may change or be removed at any time. We may collect feedback or usage data for these features to improve the product; that use is subject to our Privacy Policy and Your Data and Model Performance. Participation in beta features is at your own risk. We will use reasonable efforts to communicate material changes or deprecations.

5. Usage Limits and Fair Use

We enforce rate limits, usage quotas, and tier-based restrictions to protect service reliability and ensure fair access. Limits vary by subscription tier across the Ophraxx Web Core model network: the Free tier (OW-F1) includes approximately 500 messages per month; the Basic tier (OW-B12) includes approximately 1,000 messages per month; the Ultra tier (OW-U45) includes 10,000+ messages per month with priority processing; and the Pro tier (OW-P88) includes 50,000+ messages per month with the highest priority processing and API access. Additional limits (e.g. file upload sizes, request rates, feature access) correspond to each tier. Exceeding or circumventing these limits may result in throttling, temporary restrictions, or suspension. We apply limits consistently; our enforcement logic is built and operated by us.

6. Integrations and Access Channels

Ophraxx may be used through various access channels or integrations we provide (e.g. our bot in connected servers, our website, or future APIs or clients). Your use of the Service remains subject to these Service Terms and our Terms of Use regardless of the channel. Where you access Ophraxx in an environment that has its own terms or rules (e.g. a server or community), you must comply with those rules in addition to ours. We are not responsible for the policies or conduct of those environments.

7. No SLA or Uptime Guarantee

Unless we have agreed in writing to a separate service level agreement (SLA), we do not guarantee any particular uptime or availability. We strive for reliability and will use reasonable efforts to restore service after incidents, but we are not liable for downtime or degradation.

8. Changes

We may update these Service Terms as features and access channels evolve. Material changes will be posted with an updated "Last updated" date and, where appropriate, communicated via the Service or policy index. Continued use after changes constitutes acceptance of the updated Service Terms.