Terms of Service

These Terms of Service ("Terms") govern access to and participation in Srev's Crew (.SREC.), including the website, .SREC. ID accounts, official community systems, the .SREC. Community Hub, tickets, applications, events, contests, public votes, staff tools, custom battle moderation controls, and other official Srev's Crew services.

By accessing, creating an account, submitting content, joining official spaces, or using Srev's Crew systems, users agree to follow these Terms, the Privacy Policy, applicable platform rules, staff instructions, and applicable law.

These Terms are written for community clarity and operational safety. They do not replace mandatory consumer, privacy, platform, or legal rights that cannot be waived under applicable law.

(1) "Srev's Crew", ".SREC.", "we", "us", and "our" refer to Srev's Crew and its official web, Discord, moderation, event, and custom battle systems. ".SREC." is used as the short name for Srev's Crew and selected branded systems. The canonical public name is "Srev's Crew (.SREC.)"; the short name is ".SREC." with a leading and trailing dot.

(1a) Srev's Crew (.SREC.) was founded by Srevuplo on 01 September 2025. Srevuplo is the founder, sole owner, rights holder, and Chief Executive of Srev's Crew (.SREC.).

(2) "User", "member", "you", and "your" refer to any person who accesses or uses Srev's Crew services, including guests, registered .SREC. ID users, Discord members, applicants, contestants, and staff.

(3) ".SREC. ID" means the local website account identity used for .SREC. web access, profile features, account linking, tickets, votes, applications, and staff permissions.

(4) "Content" means anything a user submits, uploads, writes, sends, links, displays, votes on, or otherwise makes available through Srev's Crew, including text, images, GIFs, video, profile data, tickets, evidence, contest entries, feedback submissions, and chat messages.

(5) Additional rules, Staff Regulations, event rules, ticket instructions, software notices, or platform rules may apply to specific systems. Where rules overlap, the more specific rule applies unless it conflicts with mandatory law or an explicit CE directive.

(6) Public staff structure is organized by role tier, department, elected department-head service, and administration authority. Role tiers may include Trainee Staff, Junior Staff, Experienced Staff, Senior Staff, Supervision, Administration, temporary Acting Chief Executive continuity during a documented CE absence, Chief Intelligence, and Chief Executive. Department areas may include Support, People & Integrity, Integrity Review, Community Operations, Technology & Systems, Security & Intelligence, Community & Communications, Financial, Legal, and community-facing operations.

(7) People & Integrity handles staff applications, onboarding, training, transfers, lifecycle requests, absence/resignation administration, and personnel administration. Integrity Review handles restricted staff misconduct complaints and staff-integrity concerns. This public structure summary does not disclose internal permissions, private workflows, security controls, investigation methods, tool implementation, bot behaviour, or bypass information.

(1) Users must meet all minimum age requirements imposed by applicable laws and by the external platforms they use, including Discord, Roblox, Steam, War Thunder, Bungie services, console networks, or other linked services.

(2) The standard minimum age for normal Srev's Crew participation and .SREC. ID account creation is fourteen (14) years old.

(3) The previous pre-minimum-age buffer is not active. .SREC. ID accounts below fourteen (14) are not eligible and may be blocked, restricted, or held until the user becomes eligible. Any future buffer policy must be expressly enabled and published before it applies.

(4) Private member-to-member .SREC. Community Hub direct messages require the user to be at least sixteen (16) years old. Staff applications, staff access, staff tools, and Discord staff-role synchronization require the user to be at least eighteen (18) years old.

(5) Users under eighteen (18) may create or continue using a .SREC. ID only if their parent or legal guardian has agreed to the .SREC. ID registration and the current Terms of Service and Privacy Policy. Where the website asks for this confirmation, the user must confirm that this parent or legal guardian agreement exists before the account or updated documents may be accepted.

(6) Features, events, applications, or access areas with their own published eligibility rules may require additional age, verification, security, or review checks before access is granted.

(7) Users must provide an accurate birthday when required. False age information, account sharing to bypass age-gating, or evading age restrictions may lead to account restriction, application rejection, sanctions, or permanent exclusion.

(8) A user who entered an incorrect birthday may request a correction through the official support flow. A user may also voluntarily request age verification where a verified age status is useful for future eligibility or trust-sensitive features. The request must include the evidence requested in that flow. If legal identification is used, the user must cover all information except the birthday and the document photo before uploading it. Srev's Crew may refuse repeated, incomplete, suspicious, or unnecessary correction or verification requests.

(9) If authorized staff have a reasonable, documented concern that a user's birthday or age information is inaccurate, Srev's Crew may require the user to complete the official age-verification or birthday-correction flow before protected account features continue. Users must not submit unnecessary personal data and must follow the redaction instructions exactly.

(10) Age verification and birthday-correction evidence is reviewed by authorized human staff only. Srev's Crew does not use a machine-only process to verify legal identification images, decide age verification, or inspect unrelated document details.

(1) Users must provide accurate account information and keep their .SREC. ID, email inbox, password, authenticator app, linked accounts, reset links, and active sessions secure.

(2) Each person may use only one .SREC. ID unless Srev's Crew expressly approves an exception. Alternate accounts, duplicate accounts, shared accounts, or accounts used to bypass moderation, age checks, vote limits, applications, bans, cooldowns, evidence requirements, or other safeguards are prohibited.

(3) Srev's Crew usernames may be restricted to basic Latin characters, spaces, and limited separators. Usernames may be normalized for duplicate checks, impersonation prevention, readability, and security.

(4) Users may not create accounts, usernames, linked identities, profile content, or display names intended to impersonate another person, staff member, public figure, platform account, or official Srev's Crew system.

(5) Users must not share passwords, one-time codes, authenticator secrets, reset links, session cookies, API keys, or other credentials. Staff will not ask for passwords or 2FA codes.

(6) A .SREC. ID can be created and used without Discord. Discord and other external providers may be used as optional login or linking methods where enabled, but Discord login or linking is not required to activate, keep, or use a normal .SREC. ID. Members who actively use Srev's Crew on external platforms should link the relevant platform accounts where available so identity, optional sync, notifications, feature eligibility, and moderation context can work correctly. External-provider login alone does not grant staff access.

(7) If a user enables a trusted device for 2FA, the user must immediately report the device to Support if it is lost, stolen, shared, compromised, or no longer fully under their control.

(8) External-provider login or linking may create or attach a random .SREC. ID, but users may still need to complete email verification, birthday completion, Terms acknowledgement, Privacy Policy acknowledgement, or security checks before using protected features.

(9) Users are responsible for promptly reporting suspected account compromise, unauthorized access, suspicious login activity, or security issues affecting their .SREC. ID or linked accounts.

(10) Deleting, disabling, or restricting a .SREC. ID does not automatically remove moderation records, audit logs, ticket records, security records, legal acknowledgement records, or other records that must be retained for safety, accountability, legal compliance, abuse prevention, or dispute handling. The Privacy Policy explains deletion and retention in more detail.

(11) User-requested .SREC. ID deletion is handled through an Intelligence & Security or authorized privacy review ticket. If the request is accepted, the .SREC. ID login account may be scheduled for deletion after a thirty (30) day waiting period. Logging in during that waiting period reactivates the .SREC. ID login account and cancels the scheduled deletion; the user must submit a new request if they still want deletion.

(12) The scheduled deletion of a .SREC. ID login account does not by itself guarantee erasure of every connected record. Eligible public profile data, linked-platform references, friend links, public .SREC. Community Hub data, or other associated records may require separate Data Erasure review and may be removed, anonymized, restricted, or retained according to the Privacy Policy and the recorded review outcome. The stable .SREC. ID reference may be retained where needed to prevent broken records or preserve moderation, safety, legal, or audit context.

(1) Users must treat others respectfully and act in good faith.

(2) Harassment, threats, intimidation, discrimination, hate speech, targeted abuse, bullying, encouragement of self-harm, encouragement of violence, and illegal activity are prohibited.

(3) Discrimination based on ethnicity, nationality, sex, gender, sexual orientation, disability, religion, or comparable personal characteristics is prohibited.

(4) Trolling, baiting, disruption, deception, repeated provocation, spam, flooding, mass mentions, command abuse, false reports, and ticket abuse are prohibited.

(5) NSFW, gore, extremist, shock, phishing, scam, malware, credential theft, unsafe links, doxxing, private personal data, or content that violates platform rules or law is prohibited.

(5a) Sexual exploitation, grooming, sexualized content involving minors, or attempts to share, request, preserve, trade, or normalize suspected child-abuse material are prohibited. Users must not repost or download suspected illegal material; they should use the provided report flow once and allow authorized IAS staff to handle preservation, restriction, and escalation.

(6) Content that would violate these Terms remains prohibited when censored, partially covered, edited, misspelled, abbreviated, implied, replaced with overlay text, hidden behind symbols, emojis, sound-alikes, or other workarounds, or used as part of a meme, joke, profile, status, image, video, or template if the prohibited meaning, target, intent, or effect remains reasonably clear. This includes slurs, discriminatory terms, hate symbols, extremist slogans, NSFW or sexual phrasing, harassment, threats, and other rule-breaking content.

(7) Political, religious, or highly controversial topics may be restricted to designated spaces or stopped where they become disruptive, unsafe, targeted, or hostile.

(8) English is the primary Srev's Crew language. Staff may require English where moderation, evidence, safety, ticket handling, or operational clarity requires it.

(1) Users are responsible for their Content and must only submit Content they are allowed to submit.

(2) Public profile pictures, banners, statuses, bios, linked-account display text, .SREC. Community Hub messages, replies, feedback submissions, and public contest entries must comply with these Terms.

(3) Public .SREC. Community Hub channels and public profiles are not private support channels. Users must not post passwords, one-time codes, private evidence, staff-only material, sensitive case details, or private personal information there.

(4) Public .SREC. Community Hub media uploads are limited to supported image, GIF, and video formats. Users may not upload executable files, HTML, scripts, malware, disguised unsafe files, or files intended to exploit another user's device or browser.

(5) Staff may hide, restore, delete, restrict, flag, or review public profile and community chat content where needed to enforce rules, protect users, prevent abuse, preserve safety, or satisfy legal duties.

(5a) Public or community-facing content, including the .SREC. Community Hub, connected Discord messages, profiles, uploads, tickets, reports, appeals, and support contexts, may be processed by .SREC.-controlled safety and moderation-assistance systems to detect possible Terms violations, preserve context, route human review, or create review records. Such assistance does not by itself impose sanctions or replace authorized human review.

(5aa) Images or videos in standard, non-TE2EE .SREC. Community Hub messages may only be connected to a child-safety scanning provider if that provider is an official European Union or German public-authority backed system. Commercial or other third-party child-safety scanner providers are not authorized for this purpose. TE2EE-protected content remains inaccessible to .SREC. AI and staff moderation after it is sent.

(5ab) Standard, non-TE2EE .SREC. Community Hub messages, uploads, reports, account-linking signals, access attempts, website/API traffic metadata, and related security telemetry may be logged, scanned, restricted, or reviewed by .SREC.-controlled safety systems and authorized staff where needed for child-safety risks, abuse prevention, security, moderation, legal duties, or audit accountability. Internal operational details, review thresholds, and restricted security tools are confidential.

(6) Profile trust signals such as .SREC. ID, join date, staff badge, role badge, linked public profile reference, or verification state may be shown where needed for identity context, impersonation prevention, votes, tickets, contests, staff/member trust, or moderation integrity.

(7) Users may report public profile or .SREC. Community Hub content through the provided tools. Abuse of report tools may itself be sanctioned.

(8) Profile visibility settings control what ordinary members can see. Authorized staff may still access non-public profile details and moderation context where necessary for support, safety, moderation, abuse prevention, legal duties, or account-integrity review. Staff may not share or disclose private profile information outside authorized .SREC. workflows.

(1) Tickets, reports, appeals, complaints, applications, status reports, and support chats must be truthful, relevant, respectful, and submitted through the correct official flow.

(2) Evidence must be authentic, relevant, and limited to what is necessary for review. Forged, manipulated, misleading, malicious, or excessive evidence is prohibited.

(3) Evidence containing prohibited content may only be submitted through official report, appeal, complaint, or support channels where necessary for review. It must not be posted publicly.

(3a) Screenshots are accepted as primary evidence only for War Thunder chat reports where chat context is visible and relevant. For other report types, screenshots or still images alone are not sufficient evidence because they are too easy to alter or remove from context; staff may require video, logs, message links, system records, or other stronger context before acting.

(3b) Srev's Crew does not process ordinary third-party reports. The affected person or account holder must submit the official report, appeal, complaint, or legal/safety request themselves unless a documented safeguarding, legal, or platform-integrity exception requires otherwise.

(3c) Where an official Srev's Crew Roblox experience provides an in-game report flow, the report may include the reporter's and target's Roblox identifiers, the selected reason, and game-session context needed to let authorized staff review the correct incident. In-game reports are official reports and must not be abused, spammed, forged, or used to harass another player.

(3d) Where an official Srev's Crew Roblox appeal experience is provided, users may be asked to acknowledge that Roblox identifiers, ban references, appeal text, game/session context, and consent metadata are sent to Srev's Crew systems for review. The appeal experience may remove users who do not have an active Srev's Crew Roblox game ban, and a submitted in-game appeal is not a promise that the ban will be removed. Users may also be required to confirm an appeal statement that the appeal is honest, that future rule compliance is expected if the appeal is accepted, that acceptance remains at the discretion of authorized Srev's Crew staff, and that Roblox platform services are used to transmit the appeal.

(4) Ticket messages and attachments may be reviewed by authorized staff for the relevant department, authorized oversight, or legal/security review where necessary.

(5) Complaints involving staff conduct are restricted Integrity Review matters and must not be exposed publicly or shared with unauthorized users. People & Integrity handles staff applications, onboarding, lifecycle, training, transfers, and related personnel administration; Integrity Review is separate from ordinary lifecycle administration and is the restricted review route for staff misconduct.

(6) Applications and request forms must contain truthful, applicant-owned information and must follow the requirements shown in the relevant official flow. False, copied, misleading, or incomplete application information may lead to rejection, restriction, or later review.

(6a) Staff applications, promotion requests, and transfer requests may include quiz-based competence checks. A rounded quiz score of at least ninety (90) percent is required before People & Integrity may accept the relevant application or request. Applicants and requesters may see their final score, but answer keys and quiz solutions are not provided.

(7) Closed tickets are read-only unless reopened by authorized staff. Rejected or closed tickets are not automatically deleted and may be retained for audit, appeal review, abuse prevention, or Admin oversight.

(1) Official moderation, support, security, and admin actions may be carried out through verified Srev's Crew staff accounts, website tools, platform tools, classified safety controls, or other official systems.

(2) Staff-specific duties, permissions, internal hierarchy, lifecycle decisions, and staff conduct standards are governed by the Staff Regulations and internal authority rules, not by these member-facing Terms.

(3) Users must not impersonate staff, misuse staff-only names or systems, interfere with official moderation, pressure staff to act outside official processes, or attempt to access staff-only areas.

(4) Appeals, complaints, access questions, or concerns about official actions must be submitted through the appropriate support, report, appeal, or complaint flow rather than through public callouts or harassment.

(5) Staff and anyone receiving internal .SREC. information must not discuss staff-only, moderation, user-related, security, ticket, evidence, ban-reason, or operational information on Discord or any external communication platform that is not approved for that sensitivity level. Internal .SREC. matters must stay inside authorized .SREC. systems and protected communication channels.

(1) Srev's Crew may take moderation action to enforce these Terms, protect community safety, prevent abuse, preserve evidence, or satisfy legal or platform obligations.

(2) Possible actions include content removal, warnings, strikes, timeouts, chat bans, website restrictions, account restrictions, Custom Battle bans, Roblox game bans, Discord bans, linked-platform restrictions, appeal limits, application rejection, role removal, or permanent exclusion.

(2a) Custom battle moderation may use official website controls, verified-user actions, authorized review paths, and related audit records. These controls may require a verified .SREC. ID and may be cancelled, ignored, reviewed, delayed, or reversed where abuse, manipulation, staff protection, protected infrastructure, or technical inconsistency is detected.

(2b) Users must not abuse custom battle controls, report flows, tickets, appeals, status reports, contact forms, website actions, or API endpoints. This includes request spam, repeated unfounded submissions, scripted bulk submissions, coordinated manipulation, false target information, attempts to overload .SREC. systems, and attempts to force moderation action against protected staff, protected infrastructure, or unrelated users.

(2c) Custom Battle restrictions may be applied or reviewed based on existing moderation records, verified identity data, relevant case context, or authorized staff/admin action. Affected users may request review through the official appeal or support flow.

(2ca) Official Srev's Crew Roblox experiences may use Roblox game reports, website moderation tools, active game-ban records, and appeal outcomes to restrict access to those experiences. Roblox game bans may use a five-step strike ladder for repeated or serious violations, including exploiting, gameplay disruption, harassment, hate speech, slurs, NSFW conduct, ban evasion, security abuse, or comparable Terms violations. A fifth strike may result in a permanent game ban. Abuse of in-game report, ban, or appeal systems, including false submissions or attempts to use staff-only functions without authority, may itself lead to enforcement.

(2d) Appeals against sanctions, restrictions, moderation records, access decisions, or other official actions should include relevant evidence, context, or correction information from the appealing member showing why the action should be changed. Where a complaint alleges that an official action was improper and is submitted within three (3) days after the action was applied, Srev's Crew should be prepared to support the action with internal evidence or official records. After that period, the complaining member should provide relevant evidence, context, or correction information showing why the action should be reviewed, changed, or reopened.

(2e) SREC-wide restrictions are reserved for serious, repeated, permanent, custom-duration, or comparable high-impact cases. They may restrict .SREC. Community Hub access and selected linked platform identities connected to the target .SREC. ID, such as Discord, War Thunder, Roblox, or other supported platforms. Staff must select only the platform targets that are supported by identity evidence, proportionality, and operational availability.

(3) Discord conduct may be handled through the strike system. A first strike may be treated as a warning, repeated strikes may result in timeouts, and severe or repeated cases may result in bans.

(4) Severity, intent, context, prior record, age/safety factors, cooperation, evidence quality, and risk to the community may be considered.

(5) Attempts to bypass sanctions, evade bans, manipulate linked identities, abuse alternate accounts, or exploit loopholes are prohibited.

(6) Where account identifiers are insufficient to prevent evasion or security threats, proportionate IP-based website restrictions may be used. Raw IP addresses are handled under the Privacy Policy and should not be publicly exposed.

(7) Users may appeal eligible sanctions through official appeal channels. Appeals must be respectful, truthful, relevant, and may be denied where no new relevant information is provided.

(7a) Where Srev's Crew removes, hides, restricts, suspends, terminates, bans, or otherwise moderates user content, account access, or platform-linked participation because of illegal content, safety risk, or Terms incompatibility, the affected user should receive or be able to request a clear statement of the action, the main reason, the affected service or platform scope, the duration where applicable, and the available appeal or complaint route. Srev's Crew may withhold implementation details, private third-party data, confidential staff information, or security-sensitive information where disclosure would compromise safety, privacy, platform integrity, or an active review.

(8) Accepted appeals may result in corrected records, removed or reduced strikes, lifted timeouts, unbans, adjusted Custom Battle restrictions, or other proportionate follow-up actions where technically and operationally possible.

(9) Appeal decisions may be final, but Admins or authorized oversight may reopen or review closed cases where operationally justified.

(1) Srev's Crew may use or interact with third-party platforms such as Discord, War Thunder, Roblox, Steam, Bungie services, console networks, hosting providers, email providers, or other services.

(2) Users are responsible for complying with each external platform's own terms, community standards, age rules, account rules, anti-cheat rules, and content rules.

(3) Srev's Crew is not responsible for outages, platform moderation, account restrictions, data loss, service changes, or actions taken by third-party platforms.

(4) External login, account-linking, account-verification, profile-data, and social-link features may use supported third-party provider flows or APIs where enabled or configured. Those services are subject to the provider's own terms and privacy practices.

(5) Users may link external platform identities, such as game accounts, Discord identities, Roblox accounts, Steam accounts, War Thunder usernames, Bungie identities, or other supported services, to their .SREC. ID. Users must only link accounts they control or are authorized to use.

(6) Srev's Crew will not ask users to provide external platform passwords. Where an official or approved verification flow is available, Srev's Crew may require that flow before treating a linked platform account as verified. Verification may use provider login flows, provider APIs, public profile checks, staff review, or another approved method depending on the platform and available technical support.

(7) Verified external links may be removed, rechecked, downgraded to unverified, or rejected if ownership changes, provider data cannot be verified, verification fails, platform access changes, or abuse, impersonation, evasion, or security risk is suspected.

(8) Where a platform does not provide a reliable official verification method, Srev's Crew may treat the link as user-provided or staff-reviewed rather than fully provider-verified. Such links may be limited before they are used for permissions, feature eligibility, Custom Battle access, moderation context, or trust signals.

(9) Official Srev's Crew game experiences may exchange the minimum moderation data needed to submit reports, enforce active game bans, process unbans, check whether an appeal experience applies, and support appeals. Users must also follow the relevant game platform's own rules and enforcement systems. Because Roblox is a third-party platform, Srev's Crew cannot guarantee Roblox client availability, server-instance lifetime, API behaviour, transport reliability, account availability, platform-side moderation results, or Roblox-side data handling. Srev's Crew remains responsible for its own systems and review processes, but Roblox is responsible for Roblox's own platform services and independent processing.

(1) Srev's Crew may host optional events, contests, public votes, feedback flows, giveaways, reward-based activities, and Executive Council votes. Participation is voluntary and may require a verified .SREC. ID.

(2) Contest uploads and voting may require verified email, age eligibility, platform eligibility, rate limits, approval, and anti-abuse review.

(3) For photo, video, trailer, screenshot, and other media contests, users must confirm that they own the submitted media or have permission to submit it, and must grant Srev's Crew usage rights for contest operation, review, display, reposting, slide shows, social media, event material, promotional material, and other community media. Entries without this confirmation cannot be submitted.

(4) Users remain responsible for ensuring that submitted media, captions, descriptions, links, credits, and files comply with these Terms, platform rules, copyright, personality rights, privacy rights, and other third-party rights.

(5) Feedback, proposals, and feature ideas submitted through support tickets or currently enabled feedback flows may be reviewed, discussed, adapted, implemented, declined, archived, or published by Srev's Crew without creating an obligation to implement the idea, provide compensation, or keep the submission confidential. Users must not submit private, confidential, or third-party personal information through public feedback channels.

(6) Public votes are community feedback and integrity signals. They may be considered by staff but do not automatically determine winners, rewards, policy outcomes, or final decisions.

(7) Creating or using alternate accounts, coordinated fake votes, scripted vote manipulation, false identities, coercion, or other attempts to influence results unfairly is prohibited.

(8) Srev's Crew may review voting patterns, account links, login security signals, and related abuse indicators where necessary to protect event, contest, feedback, or vote integrity. Suspicious votes may be ignored, removed, or treated as grounds for disqualification or account restrictions.

(9) Executive Council votes require a verified .SREC. ID and may elect department heads and a Member Representative according to the Staff Regulations and the active EC vote system. Eligibility, voting rights, skipped empty categories, and role application follow the current Staff Regulations.

(10) Rewards may be substituted, withheld, delayed, reduced, or cancelled where required by availability, fraud prevention, platform rules, legal requirements, tax or payment issues, safety concerns, or failure to satisfy event requirements.

(11) .SREC. Coins are optional virtual community points for minigames and engagement features. They have no real-money value, are not e-money, cryptocurrency, real-money gambling credits, or a stored-value product, cannot be cashed out, sold, transferred for payment, or purchased for now, and may be adjusted, reset, withheld, revoked, or disabled to fix bugs, prevent abuse, or protect system integrity. Some minigames may use fixed virtual antes, pots, or score-based coin changes, but only with non-purchasable .SREC. Coins and never for real-money payout or real-money exchange.

(1) The Srev's Crew name, the .SREC. short name, logo, branding, designs, website materials, documents, systems, original text, graphics, and other original Srev's Crew materials are reserved.

(2) Users may not falsely present themselves as officially representing Srev's Crew or use Srev's Crew or .SREC. branding in a misleading, unauthorized, harmful, or commercial manner.

(3) Users retain ownership of their own Content where they have such rights. By submitting Content to Srev's Crew, users grant Srev's Crew the rights needed to host, store, display, transmit, moderate, review, secure, preserve, and operate that Content in connection with the relevant feature.

(4) Public Content, including profiles, public messages, public feedback submissions, public contest entries, and slide show submissions, may be displayed to other users or the public according to the feature's visibility settings and these Terms.

(5) Ticket evidence and support chat content are not public content. They may be processed internally for support, moderation, appeals, security, audit, legal, and accountability purposes.

(6) Contest entries, event banners, and media expressly submitted with a usage-rights confirmation may be reused by Srev's Crew for the community media purposes described in Section 10.

(7) Users must not submit Content that infringes copyright, trademarks, privacy rights, publicity rights, platform rules, or other rights of another person or organization.

(8) War Thunder mission files submitted to .SREC. Mission Hosting remain user-submitted Content. Administration approval means the mission was reviewed for the selected hosting/listing flow, Terms compliance, safety, and platform-rule consistency. It does not transfer ownership and does not give Srev's Crew blanket permission to use a private mission outside the owner's selected hosting settings or documented consent.

(9) Mission Hosting may process .blk mission files, mission names, descriptions, banners, version notes, visibility settings, owner/dev-team access, generated mission links, safety review metadata, approval decisions, rollback versions, and mission activity logs. Public missions may be listed for the community. Private missions are link-controlled. Private mission owners and listed devs may enable mission-use notifications and view relevant activity logs, but internal detection and safety methods remain confidential .SREC. security information.

(10) Public War Thunder custom battle statistics on the .SREC. website relate only to official .SREC.-moderated custom battle rooms. Mission Hosting does not publish player statistics, tournament statistics, ratings, or usage analytics for user-hosted missions or third-party custom battles.

(1) The Privacy Policy explains what data Srev's Crew processes, why it is processed, who may receive it, how long it may be retained, and what rights users may have.

(2) Srev's Crew currently uses technically necessary first-party session cookies for authentication, account security, staff access checks, and requested website features. Non-essential tracking, advertising, or third-party embed cookies require appropriate notice or consent handling before use.

(3) A user-enabled trusted-device 2FA cookie may be used for up to 30 days on the same browser as a necessary account-security feature. It does not authorize staff access by itself and may be revoked or ignored where security review requires a fresh 2FA challenge.

(4) Public .SREC. AI guidance, staff-only AI tools, Discord-facing .SREC. AI, and internal .SREC. Assistant draft suggestions are informational, support, drafting, routing, and review-assistance tools only. They do not issue sanctions, decide appeals, replace staff review, create binding decisions, change policies, change code, change account permissions, or automatically disclose data.

(5) AI-assisted systems may help prepare summaries, draft replies, support-navigation hints, translations, training notes, safety-review alerts, possible Terms-violation classifications, or moderation context. Final moderation, appeal, account, access, privacy, legal, and staff decisions remain subject to authorized human review and the official workflows that apply to that case.

(5a) AI-assisted review may flag possible prohibited content in Discord, the .SREC. Community Hub, public profile areas, tickets, support chats, reports, appeals, or other .SREC.-connected channels where the feature is enabled. Flags are review signals only; staff must verify context, identity, evidence, and proportionality before taking action.

(5aa) Child-safety reports in standard Community Hub messages may be routed to restricted IAS review with message, attachment, reporter, and audit metadata. Automated image or video matching must remain disabled unless the configured scanner is an official European Union or German authority-backed system.

(5ab) External or public .SREC. AI mode must not disclose internal .SREC. information, staff records, ticket evidence, member records, credentials, operational methods, or private account data. Internal staff AI mode may use authorized internal context only inside approved staff tools, ticket assistants, or Staff Central surfaces, and only where the signed-in .SREC. ID has the required backend permission. Internal access by staff AI does not create a right for external AI mode, public chat, Discord chat, or ordinary users to receive the same information.

(5b) Where public web lookup is offered for chat assistance, it may be used only to read public information for the user's requested answer. It must not be used to create accounts, submit forms, perform actions on external services, disclose confidential .SREC. information, or send private member, staff, ticket, evidence, security, or operational data to external websites.

(6) Public explanations may state that support or review workflows can use automation or AI assistance, but users must not request or demand disclosure of internal security design, operational thresholds, tool implementation, monitoring methods, bot behavior, or bypass information.

(7) Users must not attempt to bypass, overload, probe, scrape, exploit, reverse engineer, attack, or interfere with Srev's Crew systems, APIs, staff tools, rate limits, upload protections, authentication, authorization, internal services, or security controls.

(8) Security vulnerabilities must be reported responsibly through official contact or support channels and must not be exploited, publicly disclosed before review, or used to access data without permission.

(1) Srev's Crew services may change, be interrupted, be limited, be removed, be unavailable, or require maintenance. Srev's Crew does not guarantee uninterrupted access, permanent availability, or permanent preservation of every feature or user submission.

(2) Srev's Crew may add, remove, redesign, restrict, or discontinue features where needed for safety, security, legal compliance, platform changes, operational capacity, or community needs.

(3) Staff software, Staff Central moderation tools, classified safety systems, and related systems are provided only for authorized use. Users must not modify, redistribute, reverse engineer, abuse, or bypass access controls for Srev's Crew software unless explicitly authorized.

(4) Access to internal software or staff tools may be revoked at any time where permissions, security, linked identity, 2FA, staff status, platform eligibility, or operational trust no longer satisfies requirements.

(1) Advertising, promotion, recruitment, poaching, referral abuse, scams, or unsolicited commercial activity are only allowed where explicitly permitted by Srev's Crew rules or staff approval.

(2) Advertisements and public promotions must be suitable for the community, comply with these Terms, and comply with all relevant platform rules.

(3) Staff may not use staff authority, tickets, internal access, or privileged information for personal commercial gain, retaliation, favoritism, private disputes, or unauthorized promotion.

(4) Giveaways, donations, supporter tiers, rewards, sponsorships, paid events, or similar features may require separate terms, tax review, payment-provider compliance, and consumer information before use.

(1) Participation in Srev's Crew is voluntary and at the user's own risk, subject to mandatory rights that cannot be excluded under applicable law.

(2) Srev's Crew is not responsible for user-generated content, user behaviour, external links, third-party platforms, platform outages, user devices, internet connection issues, or losses caused by other users.

(2a) Where a user chooses to use a Roblox game, report, ban-check, or appeal experience, Roblox may process and transmit data through Roblox-controlled services. Srev's Crew does not assume responsibility for Roblox's independent platform failures, outages, API delivery issues, account restrictions, misuse, leaks, security incidents, or platform-side processing, except where mandatory applicable law does not allow such responsibility to be excluded.

(3) Srev's Crew does not guarantee that user-submitted information is accurate, complete, safe, lawful, or reliable.

(4) Users may be responsible for harm, claims, costs, or losses caused by their Content, misconduct, rights violations, illegal activity, abuse of systems, or breach of these Terms, to the extent permitted by applicable law.

(5) Nothing in these Terms limits liability where limitation is prohibited by applicable law, including liability for intent, gross negligence, injury to life, body, or health, or mandatory consumer rights.

(1) Srev's Crew may amend these Terms where systems, community needs, legal requirements, platform rules, security measures, or operational structures change.

(2) Major updates should be announced through official channels where practical. Updated Terms become effective upon publication unless stated otherwise.

(3) Where the website requires renewed acknowledgement of updated Terms, Privacy Policy, or Staff Regulations, the relevant document must be accessible before acknowledgement is submitted. Staff Regulations acknowledgements apply only to staff-enabled .SREC. IDs.

(3a) Material updates affecting account deletion, data retention, AI-assisted review, moderation complaint handling, staff-tool access, or privacy rights may require renewed acknowledgement before protected website or staff features continue.

(4) Account security, verification, password reset, legal acknowledgement, operational service, and staff-access notices may be sent even if a user is not subscribed to optional newsletters. Optional newsletters and event announcements may be unsubscribed from where the feature is available.

(5) Continued access or participation after updated Terms become effective may be treated as acceptance, except where law requires a different process.

(1) German law applies where legally relevant.

(2) Disputes shall be handled by the competent courts of the Federal Republic of Germany where applicable, unless mandatory law provides another venue or protection.

(3) If any provision of these Terms becomes invalid or unenforceable under applicable law, the remaining provisions remain unaffected.

(4) An invalid or unenforceable provision shall be replaced by a lawful provision that most closely reflects the original purpose where legally possible.

(1) Legal and privacy contact details are listed in the Impressum and Privacy Policy.

(2) Support, appeals, complaints, reports, account questions, data requests, and security concerns should be submitted through the official website flows where available.