1. Acceptance
By installing, configuring, accessing, or using Prism, you agree to these terms and the Privacy Policy. If you administer a Discord server, you confirm that you are authorized to enable Prism there.
2. The service
Prism provides moderation, utility, logging, staff-management, and server-configuration features. Some actions can warn, time out, kick, ban, change roles, or otherwise affect Discord members and servers. Server administrators control which authorized staff may use them.
3. Responsible use
You must not use Prism to:
- Break applicable law or Discord’s terms and policies.
- Harass, deceive, threaten, or unlawfully monitor another person.
- Access a server, account, dashboard, or record without permission.
- Disrupt, overload, bypass access controls, exploit vulnerabilities, or attempt to obtain another person’s credentials or records.
- Upload secrets, malware, or content that infringes others’ rights.
PrismOne support chat is for product help, not urgent safety response. Do not send bot tokens, passwords, API keys, or other secrets in chat. Supported image attachments are uploaded to a third-party image host. Only submit content you are entitled to share. The typical human response time is within 24 hours, but this is an estimate, not a guaranteed deadline or a 24/7 service. Sending a support message does not create an emergency-response obligation.
4. Server administrator responsibilities
Administrators are responsible for Prism’s role hierarchy, permissions, logging configuration, staff decisions, moderation reasons, and compliance with rules applicable to their community. Review permissions carefully before allowing dashboard or command access.
5. Accounts and security
PrismOne uses Discord OAuth. You are responsible for securing your Discord account and must report suspected unauthorized dashboard use. Do not share sessions, credentials, API keys, or bot tokens.
6. Availability and changes
Features may be changed, suspended, rate-limited, or discontinued to maintain security, reliability, or compliance. Prism is provided on an “as available” basis and uninterrupted operation is not guaranteed.
7. Enforcement
Access may be restricted or terminated where these terms are broken, where continued operation creates security or legal risk, or where Discord requires it. A server administrator may remove Prism at any time.
8. Liability
To the extent permitted by law, Prism’s operator is not liable for indirect or consequential loss, moderation decisions made by server staff, Discord outages, lost records, or unauthorized use caused by a server’s configuration. Nothing here excludes liability that cannot legally be excluded.
9. Privacy and third-party services
Use of Prism is also governed by the Privacy Policy. Discord, Firebase, Wispbyte, and Cloudflare provide separate services under their own terms.
10. Contact and updates
Prism is made and operated by Arriva Corporation. Questions, reports, or legal requests may be sent through PrismOne support. Material updates will be published here with a revised date.
11. Eligibility and account access
You must meet Discord’s minimum age requirements in your region and be permitted to use its services. If you need parental or guardian permission under applicable law, obtain it before using Prism. You may act for a server or organisation only with authority to do so. Signing in does not automatically give you management access to every server.
Access depends on server membership, configured roles, permission mode and operator restrictions. Losing a role, leaving a server or being suspended may remove access. Server owners must review access when staff responsibilities change.
12. Moderation and automation
Server staff remain responsible for moderation decisions, reasons, evidence and appeals. Prism performs actions requested by authorised users or enabled rules. Role hierarchy, missing Discord permissions, service outages and configuration errors can prevent an action from completing.
Review command toggles, automatic moderation, reminders and temporary punishments before enabling them. Do not assume that a dashboard confirmation replaces an independent review of a sensitive action. Appeals about a server’s rules should normally go to its administrators. Prism access restrictions can be raised with Arriva Corporation support.
13. Tickets, transcripts and attachments
Server administrators choose ticket panels, forms, staff access, categories and log destinations. Ticket messages and form answers may be visible to the opener, assigned staff, server administrators and other users added to the channel. Claiming a ticket does not make it private from other authorised staff.
Transcripts may be exported and posted to the configured Discord log channel. Closing or deleting a ticket channel does not necessarily delete its transcript, attachments, backups or copies saved by participants. Administrators must provide appropriate notices and restrict log-channel access.
Do not request passwords, tokens, unnecessary identity documents or sensitive personal information through Prism. If your community performs age verification or another sensitive process, you are responsible for its necessity, legality, security and deletion procedures. Prism’s ticket tools do not certify those procedures.
14. Support and uploaded content
You retain your rights in content you submit. You permit Arriva Corporation and the relevant service providers to process, store and display that content as needed to deliver the requested feature, provide support, investigate abuse and meet legal obligations. This permission is limited to those purposes.
Support is provided by authorised staff. The estimated response time is within 24 hours, but demand and availability may cause delays. Screenshots should be redacted before upload. Hosted image links may be accessible to anyone who obtains the link, even when the conversation itself requires sign-in.
Support images currently accept PNG, JPEG, WebP and GIF files up to 8 MB. Technical limits and supported formats may change. Report security issues privately through support and avoid publishing credentials or exploit details that could harm other users.
15. External providers and status reports
Prism relies on Discord, Cloudflare, Firebase, Wispbyte, ImgBB and other providers used by specific features. Status notifications may use Resend. These providers can impose limits, change interfaces or experience outages. Their terms and privacy policies apply to their own services.
The status page combines periodic checks, provider reports and staff notices. It is informational and may be delayed or incomplete. A successful check does not guarantee that every user, location or feature is working. Configuration checks do not prove that a full sign-in, message, upload or email has completed.
16. Removal, records and surviving obligations
You may stop using Prism, sign out or remove the bot from a server. Removal does not automatically erase moderation history, exported Discord transcripts, support conversations or provider-held copies. Use the Privacy Policy and support process to request deletion where applicable.
We may retain information where needed for security, abuse prevention, disputes or legal obligations. Provisions concerning submitted content, privacy, lawful retention and limitations of liability continue where relevant after access ends.
17. Legal rights and interpretation
These terms do not remove mandatory consumer rights or other rights that cannot lawfully be restricted. Any exclusion or limitation applies only to the extent permitted by applicable law. If a provision is unenforceable, the remaining provisions continue where they can reasonably operate.
Questions about these terms, disputes, accessibility or a restriction should be submitted through support with enough information to identify the relevant account or server. Do not include authentication secrets. Material revisions will carry an updated publication date.
18. Configuration, access and least privilege
Server owners choose whether dashboard permissions follow Discord permissions automatically or use custom role assignments. Owners are responsible for understanding that choice, reviewing each role’s capabilities and removing access when staff leave or change duties. A role name or dashboard label alone is not proof of authority.
Give Prism and staff only the Discord permissions required for enabled features. Discord administrators may have broad access to channels and records regardless of a ticket’s assigned support roles. Do not rely on a ticket claim, hidden dashboard control or renamed staff tier as a security boundary.
Saving settings and publishing a Discord panel are separate actions where the interface presents them separately. Review the saved configuration, channel destination, support roles and permission rules before publishing. Configuration mistakes may disclose records or allow unwanted actions, so test new setups in a suitable channel before broad use.
19. Action results, limits and recovery
A ban, role change, deletion or bulk action can affect people who have not interacted with PrismOne. Banning a user by ID can also affect someone who is not currently in the server. Verify identifiers, scope, reason and permissions before confirming an action. The operator’s cross-server tools may affect selected servers and should be reviewed with the same care.
Discord limits, rate limits, role hierarchy, missing channels, deleted messages, expired interactions and external outages can prevent completion. A request may time out after Discord has already processed it. Check the current state before repeating a destructive action, and do not assume that an error always means nothing happened.
Prism does not guarantee that deleted messages, channels, roles, conversations or records can be restored. Administrators should keep any independently required records and define their own recovery and appeal procedures. Automatic reminders or temporary-ban expiry can be delayed while the bot is offline.
20. Public messages, announcements and logs
Enabled modules may publish moderation confirmations, role changes, ticket updates and other notices to Discord. Server administrators select destinations and are responsible for their audience, mention settings and visibility. Review notification options before enabling them in a public channel.
Prism operators may send service announcements to configured log channels. Such announcements should be treated as service information and do not grant server privileges or request authentication secrets. Avoid trusting messages or links merely because they resemble Prism’s branding.
Event logs reflect information available to the bot and may be incomplete, delayed or affected by Discord cache and event delivery. A log entry alone should not be treated as conclusive evidence of who performed an action. Check Discord’s available audit information and other evidence when investigating a dispute.
21. Credential handling and incident reports
Keep Discord tokens, API keys, service-account files and active browser sessions confidential. Do not place them in ticket forms, support screenshots, public logs or shared archives. If a secret is exposed, revoke or rotate it through the relevant provider rather than relying solely on message deletion.
Report suspected Prism vulnerabilities through the support channel or the contact information in Arriva Corporation’s legal documents. Include a description, affected feature, approximate time and safe reproduction details. Do not access other users’ records, deliberately cause disruption or publish sensitive data while reporting an issue.
We may temporarily restrict affected features or access while investigating an incident. A support report does not guarantee immediate restoration, compensation or a particular investigation outcome. Mandatory legal rights remain unaffected.
22. Product scope and documentation
Available commands and modules depend on the deployed version, server configuration, Discord permissions and provider availability. Website descriptions, help output and previews may change as features are updated. A preview does not guarantee identical rendering in every Discord client.
Prism is not an emergency service, identity-verification provider, legal adviser or guaranteed archive. Moderation and support tools should not be used as a substitute for professional advice, mandatory reporting procedures or an independently secured records system.
These product terms supplement the main Arriva Corporation documents. Read both sets of documents for the applicable service and organisation details. This supplement does not remove statutory rights or imply that every server operator’s conduct is approved by Arriva Corporation.
23. Automated support guidance
Prism’s optional AI assistant provides automated guidance based on product documentation and limited conversation context. It is an Arriva Corporation support feature, not a human representative or an autonomous account-management service. AI messages are labelled. Choosing AI help authorises the described processing through Google’s Gemini API, as explained in the Privacy Policy. Human support remains available without AI.
AI may misunderstand a question, omit relevant facts or provide incorrect guidance. Check permissions, targets and the actual result before carrying out actions, particularly bans, deletions and configuration changes. AI cannot approve an appeal, grant access, verify current service health or make commitments on Arriva Corporation’s behalf. Privacy, security and legal requests should be reviewed by authorised human staff.
Do not use the assistant to obtain other users’ records, bypass controls, extract credentials or cause disruption. AI availability is subject to provider access, quotas and service limits. If generation fails, your saved message remains available and human support can take over. Neither AI nor human support guarantees an immediate response or a particular outcome, without limiting applicable statutory rights.