1. Who this policy covers
Arriva Corporation operates Prism and PrismOne. This policy applies to the Prism Discord bot and the PrismOne web dashboard (together, “Prism”). The server operator that installs Prism chooses its configuration and is responsible for telling its community how moderation and logging are used.
2. Data we process
Depending on enabled features, Prism may process:
- Discord user, server, channel, role, and message identifiers.
- Usernames, display names, avatars, roles, and join information.
- Moderation records such as warnings, strikes, reasons, durations, moderators, reports, and case history.
- Server audit events, including deleted message content and message content before and after edits when available to the bot.
- Command usage, dashboard actions, and operational error logs.
- Text messages and images you choose to send through PrismOne support, their timestamps, and the Discord IDs, usernames, and avatar identifiers of participants.
- If a server enables Discord AutoMod through PrismOne, Discord evaluates spam or excessive mentions and blocks matching messages. Prism stores the rule settings and results in Discord, not message bodies from this feature in Firebase.
- Discord OAuth profile and server-list data needed to authenticate and authorize dashboard access.
3. Why we process it
Data is used only to operate requested bot features, enforce access permissions, apply and review moderation, maintain security, diagnose faults, and show authorized staff an audit history. Prism does not sell personal data or use it for targeted advertising.
4. Storage and service providers
Prism uses Discord to provide bot and identity services, Firebase Realtime Database to store configuration and operational records, Wispbyte to run the bot API, and Cloudflare Workers to run PrismOne. These providers may process technical data under their own terms and privacy policies. Dashboard traffic is encrypted in transit.
Support conversation text and hosted-image links are stored in Firebase. Images are uploaded to ImgBB and are therefore also processed and hosted by ImgBB under its own terms and privacy practices. Only the signed-in user and whitelisted Arriva Corporation support staff can access a conversation through PrismOne. Discord avatar images are loaded from Discord’s CDN when displayed; Support records may include avatar identifiers or avatar links used to display participants. Staff usually respond within 24 hours, but this is not guaranteed.
6. Retention and deletion
Configuration, cases, and audit records are retained while needed to operate the server’s configured features and maintain moderation history. Authorized staff can edit or delete supported case records. Server operators and affected users may request correction or deletion from Arriva Corporation through PrismOne support. Support chats retain at most the latest 100 messages per conversation. Older messages are removed as new ones arrive. Deleting a PrismOne conversation removes its text and image links from Firebase but may not immediately remove copies retained by ImgBB. A signed-in user can permanently delete their own support conversation, and authorized support staff can also delete it. Some information may be retained where required for security, legal compliance, or resolving abuse.
7. Security and access
Dashboard access is checked against configured Discord roles and permissions. Authentication cookies are encrypted and marked Secure, HTTP-only, and SameSite=Lax. No online system is risk-free, but access is limited to what is needed to operate Prism.
8. Your choices and rights
You may sign out to remove the active session cookie. Depending on where you live, you may have rights to access, correct, object to, or delete personal data. Contact the Prism operator through the officialsupport page and include the relevant Discord user and server IDs so the request can be verified.
9. Children
Prism is intended only for people permitted to use Discord under Discord’s terms and the minimum age rules that apply in their region.
10. Changes
This policy may change when Prism’s features or legal obligations change. The updated date above will be revised when material changes are published.
11. Data sources and ticket records
We receive information from Discord authorisation, events in connected servers, server staff, dashboard actions and content you submit. A person may appear in moderation or ticket records without signing in to PrismOne, for example when a moderator opens a ticket on their behalf.
Ticket records may include the opener, participants, panel and ticket type, form answers, claimant, channel ID, status and timestamps. Transcripts can include available message text, authors, attachments and conversation context. They are sent to the server’s selected Discord log channel. Closing a ticket does not necessarily delete its transcript or downloaded copies.
Reminders and temporary punishments store information needed to complete scheduled actions. Prism-wide access restrictions may include a user ID, reason, operator and timestamps. Technical providers may process network addresses, browser information, request timing and security logs.
12. Purposes and lawful bases
Where UK GDPR or EU GDPR applies, the lawful basis depends on the activity and our role. Providing an account or requested service may rely on performance of a contract. Security, preventing abuse, maintaining reliability and handling support may rely on legitimate interests, subject to the interests and rights of affected people. Legal obligations may require specific processing. Optional activities that require consent should rely on that consent, which can be withdrawn where applicable.
Server operators make their own decisions about community moderation, ticket forms and logging. They are responsible for identifying a lawful basis and giving their members appropriate notices. Installing Prism does not make every form of collection necessary or lawful.
13. Recipients and access
Discord provides identity, messages and bot services. Firebase stores configuration and operational records. Wispbyte hosts the bot and API. Cloudflare hosts PrismOne and provides network protection. ImgBB hosts support images. Resend may deliver email notifications for the separate Arriva Corporation status service.
Server staff see information allowed by server configuration and Discord permissions. Authorised Arriva Corporation staff may access records needed to operate the service, provide support, investigate faults or enforce restrictions. Hosting and database administration can provide operational access beyond the customer-facing interface.
We may disclose relevant information where legally required or necessary to address abuse or protect users. A transcript posted in Discord is visible according to that channel’s permissions. Providers process information under their own terms and privacy policies.
14. Images and sensitive information
Support images are uploaded to ImgBB, and their returned links are stored with the conversation. Hosted links are not a guarantee of private image storage. Anyone who obtains a link may be able to view the image. Deleting a conversation removes Prism’s stored text and links, but does not guarantee deletion from ImgBB, provider backups or another person’s device.
Redact screenshots before uploading them. Do not submit passwords, API keys, bot tokens, medical records or unnecessary identity documents. Server owners are responsible for the necessity, legality and safeguards of any sensitive ticket questions. Contact support for help with an image-deletion request.
15. Retention by record type
- Session cookies expire according to their configured lifetime. Signing out does not erase server records.
- Configuration, cases, ticket metadata and scheduled tasks remain while needed for the feature and its history. There is no universal automatic deletion period across these records.
- The current support process trims conversations to the latest 100 messages as new messages arrive. Conversation metadata and image links remain until deletion or an applicable retention decision.
- Discord logs, exported transcripts and downloaded attachments follow the server’s and provider’s arrangements.
- Security, abuse and dispute records may be retained where needed for their purpose or legal obligations. Providers have separate log and backup retention arrangements.
Removing the bot does not currently guarantee deletion of every stored record. Request a review through support. Retention decisions consider purpose, relevance, age, legal requirements and the rights of affected people.
16. Requests, rights and complaints
Depending on applicable law, you may request access, correction, erasure, restriction or a portable copy of eligible information, or object to certain processing. Consent can be withdrawn where it is the basis used. Rights have conditions and exceptions, and may not require deletion of another person’s records or lawfully retained evidence.
Submit a privacy request through PrismOne support with your Discord user ID, relevant server ID and the type of information concerned. We may need proportionate verification before sharing or changing records. Do not send credentials or identity documents unless a suitable verification process has been agreed. We aim to respond within the period required by applicable law.
Contact server administrators about their moderation decisions or exported transcripts. Where UK law applies, you may complain to the Information Commissioner’s Office. In other regions, contact the relevant data protection authority.
17. International processing
Providers may process information outside your country. Location depends on their infrastructure, account configuration and support arrangements. This policy does not promise that all records remain in the UK or EU.
Where an international transfer requires safeguards, applicable requirements must be addressed through the relevant provider arrangements. This notice does not claim a particular mechanism applies to every provider. Contact support for information relevant to your request.
18. Automation and service monitoring
Permission checks, cooldowns, scheduled actions and enabled moderation rules can operate automatically. Discord AutoMod evaluates messages within Discord. Server staff are responsible for reviewing their rules and decisions. Appeals should go to the server’s staff, or Arriva Corporation for a Prism-wide restriction.
Readiness monitoring uses limited read-only checks where possible. Public responses contain safe status information rather than personal records, credentials or internal addresses. Configuration checks do not prove a real upload, message, email or completed sign-in succeeded.
Access controls, encrypted dashboard transport and session protections reduce risk, but no system guarantees perfect security. Report suspected exposure privately through support.
19. Related services and notifications
The separate status page can collect an email address for notifications and may process delivery records and unsubscribe tokens. Use the unsubscribe link to stop notifications. Other Arriva Corporation products have their own notices.
External status links are informational. A Roblox listing does not itself send Prism support conversations or moderation records to Roblox. Visiting a provider’s website is subject to its own privacy practices.
20. Account authorisation and access decisions
Discord sign-in provides the profile and server-list information required to identify your account and determine available servers. An encrypted session can contain your Discord access token, profile and expiry information. The session is sent in a protected cookie rather than exposed as a public API key. Prism does not ask for your Discord password.
Access checks may use your Discord ID, server membership, roles, native Discord permissions, configured dashboard capabilities and Prism-wide restrictions. Changing roles or leaving a server can change access. These checks are separate from consent to optional processing.
Essential OAuth state and return-path cookies help prevent login tampering and return you to the requested area. Clearing browser storage can remove local preferences and sessions, but does not delete moderation records, tickets or support data stored elsewhere.
21. Server logging and record accuracy
When a server enables logging, Prism may process member changes, roles, channels, invites, moderation actions and available message content. The information displayed depends on the events and permissions supplied by Discord. Deleted-message content may be unavailable when the bot did not receive or retain it.
Some information is used temporarily for event comparison, including role snapshots used to distinguish real changes from first-time member loading. Logs can contain errors or gaps. Request correction where a record is inaccurate, and contact the server’s staff when they control the log message or moderation decision.
Public confirmation messages and configured log channels can disclose a user’s identity, action and reason to channel viewers. Administrators should avoid unnecessary personal details in reasons and restrict destinations appropriately.
22. Support conversation lifecycle
When you send support content, Prism associates it with your signed-in Discord account. Records may include your ID, display information, message text, image link, author role, timestamps, open or closed status, message count and unread indicators. Authorised staff can reply, change the status and delete the conversation through the supported interface.
Closing a conversation is a workflow change and does not itself delete its contents. Deleting it removes the active conversation and message records through Prism’s deletion operation. Copies previously downloaded, attached to a report, retained by an external host or included in infrastructure backups may require separate handling.
The 100-message limit is a technical trimming rule, not a fixed time-based retention promise. A conversation receiving no new messages may remain until deletion or review. Include a clear deletion request if you want support records reviewed rather than simply closing the conversation.
23. Forms, transcripts and onward sharing
Server owners decide which ticket questions to ask and who may access the resulting channel. Forms can collect information beyond ordinary Discord profile data, so answer only what is appropriate for the request. A ticket opened on someone’s behalf can associate them with a request they did not submit directly.
Transcript exports can preserve a conversation after the original channel is deleted. Copies delivered to a log channel or saved by staff may be controlled by the server operator or recipient. Prism support can help identify the relevant record, but may not control every onward copy.
Server owners should tell members what forms and logs collect, who sees them, how long they retain exports and how to make a request. Access restrictions within PrismOne do not remove access granted independently by Discord channel permissions.
24. Request verification and third-party information
To locate records, we may ask for relevant Discord IDs, timestamps, ticket references or a description of the issue. Verification should be proportionate to the sensitivity of the request. We may redact other people’s information or withhold protected security details when responding, subject to applicable law.
A request to delete your information may also affect a shared conversation or moderation record. We consider the rights of other participants, lawful retention requirements and the purpose of the record. We may explain why a record can be corrected, restricted or partially removed instead of erased completely.
You do not need to provide passwords, bot tokens or API keys to make a privacy request. If you cannot sign in, use the contact details in Arriva Corporation’s main legal documents and identify the product as Prism.
25. Scope, updates and main legal documents
This product notice supplements Arriva Corporation’s main privacy and legal documents. It describes Prism’s current features and does not promise that every provider offers identical retention, security or storage locations.
We update this notice when relevant features, data flows or practices change. The publication date identifies the current revision. A new notice does not make historical copies disappear or remove rights that apply under law. Ask support if you need clarification about a specific record, provider or version.
26. Optional AI support
Prism and PrismOne are owned and operated by Arriva Corporation. If you choose “Agree and start AI help”, conversation text sent after that choice, together with a limited recent AI conversation history and Prism support documentation, is sent to Google’s Gemini API to generate guidance. AI replies are labelled separately from human staff replies. You can use human support without opting into AI and switch to a person at any time. Staff replies stop AI handling of that conversation.
We do not deliberately send your profile name, avatar, Discord account ID or image attachments as model input. We apply best-effort redaction to common credentials, email addresses and Discord IDs in text, but cannot guarantee removal of every sensitive item. Do not submit secrets, identity documents or sensitive personal information. Text from before the most recent AI opt-in, including earlier human support replies, is excluded from model context. Switching to human support stops subsequent AI requests but cannot recall content already sent to the provider.
Google processes submitted content according to the applicable Gemini API terms, account tier and privacy arrangements. Provider retention and use of content can differ between paid and unpaid services, so we do not promise that all provider copies are immediately deleted or that every tier excludes product-improvement use. AI responses and processing-choice metadata are stored alongside your support conversation, subject to its existing retention and deletion rules. Authorised support staff can review the conversation when assisting you.
AI has no access to your live server or ability to carry out moderation, account changes or legal/privacy decisions. Its replies can be inaccurate. Ask human support to review uncertain guidance, sensitive requests or unresolved problems. Privacy rights and provider-processing questions can be raised through human support and Arriva Corporation’s legal contacts.