Terms of Service

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

By accessing, creating an account, submitting content, joining official spaces, or using .SREC. 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 the .SREC. community and its official web, Discord, moderation, event, and custom battle systems.

(2) "User", "member", "you", and "your" refer to any person who accesses or uses .SREC. services, including guests, registered .SREC. ID users, Discord members, applicants, contestants, Peacekeepers, 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 .SREC., including text, images, GIFs, video, profile data, tickets, evidence, contest entries, suggestions, 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.

(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 participation in .SREC. services is sixteen (16) years old.

(3) .SREC. ID accounts generally require the standard minimum age. A limited age-buffer may allow account creation up to six (6) months before a user reaches sixteen (16), currently from fifteen (15) years and six (6) months, only if the user gives the required acknowledgement and passes the relevant review flow. Accounts below that buffer are not eligible and may be blocked, restricted, or held until the user becomes eligible.

(4) Age-buffer access is a safety exception, not a right. It may require Support review for ordinary member accounts and .SREC. Access review for staff-related access. Certain features may remain locked until the user reaches the normal age threshold.

(5) Public staff applications require the applicant to be at least eighteen (18) years old. Manual staff access outside the public application flow may be reviewed separately, but must never be granted below sixteen (16) and must be compatible with law, platform rules, operational risk, and .SREC. Access approval.

(6) Custom Battle Peacekeeper applications require the applicant to be at least sixteen (16) years old and require a verified or staff-reviewed War Thunder link. A linked Discord account is optional and is used only where Discord-side Peacekeeper roles or notifications need to be applied.

(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. .SREC. may require verification and may refuse repeated or suspicious correction requests.

(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) .SREC. usernames may be restricted to basic Latin characters, spaces, and limited separators. Usernames may be normalized for duplicate checks, impersonation prevention, readability, and security.

(3) 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 .SREC. system.

(4) 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.

(5) Staff-enabled .SREC. IDs must use authenticator-app 2FA where required. Discord login alone does not grant staff access.

(6) 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.

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

(8) 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.

(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.

(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 .SREC. 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. COMMS messages, replies, suggestions, and public contest entries must comply with these Terms.

(3) Public .SREC. COMMS 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. COMMS 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.

(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. COMMS content through the provided tools. Abuse of report tools may itself be sanctioned.

(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.

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

(5) Complaints involving staff conduct are restricted Internal Affairs matters and must not be exposed publicly or shared with unauthorized users.

(6) Staff applications are Human Resources matters and must contain truthful, applicant-owned information. A Discord account or War Thunder account is not required to submit a staff application. If staff access is later approved, verified linked platforms may be used to synchronize operational roles, Custom Battle access, or notifications where relevant. Peacekeeper applications may create a follow-up ticket for review and verification.

(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) Staff members are subject to the Staff Regulations in addition to these Terms.

(2) Staff authority is assigned through .SREC. ID permissions and internal role structure. Discord roles may be synchronized for visibility or operational access but do not grant authority by themselves.

(3) Staff members must use official systems for staff actions where available and must not use ordinary member-facing punish tools against other staff members. Staff conduct matters belong to Internal Affairs, CI, CE, System Admin, or other authorized oversight.

(4) Peacekeepers are trusted Custom Battle helpers, not general staff, unless they separately hold a staff role. Peacekeeper access requires age eligibility, verified or staff-reviewed War Thunder identity, clean conduct, and approval. Discord linking is optional and only affects whether Discord-side roles can be assigned.

(5) Staff and Peacekeeper privileges may be removed, restricted, reviewed, or suspended where needed for safety, trust, platform rules, inactivity, abuse, or operational concerns.

(1) .SREC. 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, Discord bans, linked-platform restrictions, appeal limits, application rejection, role removal, or permanent exclusion.

(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.

(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) .SREC. 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) .SREC. 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) .SREC. will not ask users to provide external platform passwords. Where an official or approved verification flow is available, .SREC. 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, .SREC. 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, event access, Custom Battle access, moderation context, or trust signals.

(1) .SREC. may host optional events, contests, public votes, suggestion boards, giveaways, reward-based activities, and Executive Committee 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 .SREC. 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) Suggestions, feedback, proposals, and feature ideas may be reviewed, discussed, adapted, implemented, declined, archived, or published by .SREC. without creating an obligation to implement the idea, provide compensation, or keep the suggestion confidential. Users must not submit private, confidential, or third-party personal information through public suggestions.

(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, automation, vote manipulation, false identities, coercion, or other attempts to influence results unfairly is prohibited.

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

(9) Executive Committee votes require a verified .SREC. ID and run in sequential representative phases: Supervision Representative, Staff Representative, and Member Representative. Eligibility and voting rights follow the Staff Regulations and the active EC vote system.

(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 .SREC. name, logo, branding, designs, website materials, documents, systems, original text, graphics, and other original .SREC. materials are reserved.

(2) Users may not falsely present themselves as officially representing .SREC. or use .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 .SREC., users grant .SREC. 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, suggestions, 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 .SREC. for the community media purposes described in § 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.

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

(2) .SREC. 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) Public .SREC. AI guidance and internal .SREC. Assistant draft suggestions are informational support tools only. They do not issue sanctions, decide appeals, replace staff review, create binding decisions, or automatically disclose data.

(4) Users must not attempt to bypass, overload, probe, scrape, exploit, reverse engineer, attack, or interfere with .SREC. systems, APIs, staff tools, rate limits, upload protections, authentication, authorization, bot systems, or security controls.

(5) 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) .SREC. services may change, be interrupted, be limited, be removed, be unavailable, or require maintenance. .SREC. does not guarantee uninterrupted access, permanent availability, or permanent preservation of every feature or user submission.

(2) .SREC. 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, desktop moderation tools, Virus-T, Web Virus, and related systems are provided only for authorized use. Users must not modify, redistribute, reverse engineer, abuse, or bypass access controls for .SREC. 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 .SREC. 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 .SREC. is voluntary and at the user's own risk, subject to mandatory rights that cannot be excluded under applicable law.

(2) .SREC. 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.

(3) .SREC. 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) .SREC. 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.

(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.