PRIMARY RULES

PROVISIONS AND RESOLUTIONS

GENERAL PART: RULES OF Ranked Bridge

Informed Consent

ScreenShare (Inspection) is conducted only after the user has agreed to/filled the Consent Form (see Consent Form tab). Not being provided with the Consent Form will unban the Player regardless of when, where, by whom and how it was conducted, security and privacy, provision of these forms are ScreenSharer's and SS Management's responsibility.

Implied Consent

Although not provided with consent forms, accepting the inspection by allowing a connection for the inspection, running automated scanners, discussing the conduct with the inspector (ScreenSharer) is considered enough to validate the ScreenShare. Not being provided with the Consent Form for this occasion does not warrant a release from penalties. A persistent or by count of at least two times, history of accepting ScreenShares will also be considered implied consent.

Purpose, Introduction and Scope

The code establishes a regulatory and procedural framework for the practice of ScreenSharing within Ranked Bridge, to ensure fairness and probity in conduct. These provisions apply to all staff members, players, and associated parties involved in ScreenSharing activities to protect competitors of organized events. This Code is authentic, valid and active only within Ranked Bridge, for as long as the ScreenSharing sector has autonomy over the affair. Any act or addition to this document is valid only after changelog announcements.

Definitions & terminology

1. ScreenSharers are non-staff members of the team, segregated from staff duties for the sole purpose of identifying cheats on reported suspect's devices. Synonym term for ScreenSharers is: Inspectors

2. ScreenSharing is the entire procedure, which begins from the moment of a ScreenSharer receiving verbal (by text or voice), formal (by the freezing system) or personal (DMs, staff chats, higher-up requests) reports, except for when personal reports are done through public chats in the Ranked Bridge server, onward, reviewing evidence filed against Players, followed by Players getting Frozen. Any ScreenShare conducted on other than permitted basis is invalid.

3. Players are all members of the community, regardless of their roles, permissions, status in the server. This includes the Ownership, Administration, Moderation, Partnership and other groups of individuals who are involved in ELO-based games. Players can not be ScreenShared, inspected or otherwise treated as subject to any penalties or acts defined in the code until receiving the status of Suspects.

4. Suspects are Frozen Players who are undergoing ScreenShare. This status lasts until the end of ScreenShare.

5. Authorized Personnel are the ScreenShare Management, Sr.Mods, Admins, Owners, Developers and individual Suspects.

Usage of the code, Authority

1. This code is the only imperative document regulating interactions and scenarios involving the practice of ScreenSharing in Ranked Bridge. Any ticket, appeal, application, request must adhere to this code if not regulated otherwise in the Special Part of the document.

2. Only ScreenShare Managers have the authority to properly enact the Code. No other member of the team, be it the Ownership, shall infringe in regulations of this code.

3. Everything that is not explicitly disallowed by the Code is permitted.

Implementation and audit

1. ScreenSharers must follow a standardized protocol for initiating and conducting ScreenSharing sessions, including obtaining consent from players and ensuring transparency throughout the process.

2. All ScreenSharing activities must be documented, and records must be maintained for audit and review purposes for no longer than the ongoing season's duration.

Data privacy, security and user safety

1. Access to ScreenSharing data is restricted to authorized personnel only, visible to ScreenSharers, ScreenShare Managers, Admins and Ownership of Ranked Bridge; measures are set in place to prevent unauthorized access or disclosure and such disclosure is only allowed upon the request ocean of the Player.

2. Players have no permission to refuse the usage of Echo SS Tool.

3. Players maintain an unrestricted right to refuse Ocean SS Tool, given that they do not wish to temporarily pause their Anti-Virus to avoid the packed file's deletion.

4. Maintaining the rights mentioned in section "3", any SS Tool is banned, disallowed to be used on Players and any SSer is disallowed to SS Players with or without the usage of scanners if they (Scanner or the SSer) are not partnered with Ranked Bridge

5. Nobody has the right to ScreenShare Players in Ranked Bridge apart from the SS Teams of Echo, Echo Certificates, Storm, Ocean and the designated SS Team of the Ranked Bridge Screenshare Management.D

6. Players and Staff members can not ScreenShare other Players manually or with SS Tools. They may only open reports.

7. Players may employ cybersecurity and self-defense practices as advised by the Ranked Bridge Screenshare Management with combined efforts of Echo, Ocean and Storm SS Tools with all partner SS and Gaming Communities.

8. In situations where Players have not employed mechanisms mentioned in section "7", ScreenSharers ask for a secondary verification of the Player's consent during SS, consult with SS Managers and ScreenShare under the supervision of one SS Manager and/or one Admin/Owner of Ranked Bridge.

Appeals and audit

How appeals are handled is established by the ScreenShare Management only, based on this code, under Article 12-12¹.

Provisional principles

Under the general provisions, no regulation shall be made or enacted in the SS code if it violates the principles of promoting collective evaluation of evidence and appeals (nonarbitratus); deciding in favor of suspects during lack of evidence or controversial evidence (In statu pendentis); never permanently clearing suspects to aid infringement of this code (ex post facto) or not using force to SS Suspects regardless of refusal (ratihabitio);

Impossibile Attempts

There are two kinds of Impossible attempts in the Ranked Bridge SS System - Factual and Codified. No Player or Suspect may be banned for Factually Impossible Attempts, such as executing discontinued cheat samples that factually by its current build and in the given scenario, has no possibility of ever running on the system. No Player or Suspect may be banned for Impossible Codified Attempts, such as attempting impossible ways of bypassing regulations defined in this code. For example, using cheats to cheat in different servers and acts of this nature.

SPECIAL PART

Chapter I

Article 1 - Reporting Suspects

1. A ScreenShare report cannot be issued by players who have not warned and fought and/or witnessed the Suspect in an ongoing game, personally.

2. If the player is muted, other participants of the ongoing game that are spectators, viewers, bystanders (afk) or third-party watchers, shall not report on their behalf.

3. Suspects may be reported during the second and final half of the game by opening tickets against them, ScreenSharers must be notified when the game ends to proceed.

4. Suspects may notify the ScreenSharer through tickets that they are in an ongoing ranked match. Queues do not count. Then proceed by section 3 of this article.[02/05/2025]

5. Suspects may only be reported with full screenshots of the ongoing game, with all of the following clearly displayed:

   1. The entire chat open (with "T" key), where "Don't Log" warning includes a specific Player to report;

   2. Scoreboard with the Date clearly displayed.

Article 2 - Suspect Regulations

1. Suspects are not free from penalties for having Discord DMs or Notifications closed.

2. In violation of Limitations, section (3) (19) of Chapter V, Suspects/Reported Players reserve the right to refuse every SS Request made against them from the same individual repetitively throughout the day/next 12 hours.[02/06/2025]

3. Suspects are not allowed to choose ScreenSharers who can ScreenShare them in hosted Events. Doing so will be considered refusal.

4. Suspects may ask for a different ScreenSharer to ScreenShare them. However, if no ScreenSharer arrives in the next 10 minutes, and they still deny the initial ScreenSharer, it will count as refusal.

5. Suspects may ask for a different SS Manager to ScreenShare them. Other Managers will be notified immediately. However, if no SS Manager arrives in the following 3 minutes, it will count as refusal.

6. Suspects can refuse a ScreenShare from unauthorized ScreenSharers who are not a part of the team.

7. Not knowing the rules does not free the Suspect from their consequences.

Internal Regulations

1. ScreenSharers in Ranked Bridge follow the regulations and ethics of the Ranked Bridge Screenshare Management.

2. Breaching section 1 is bannable across all of the unity.

Article 3 - Scoring Application

1. The ScreenShare Management applies Scoring rules into this Article.

2. Voiding offenses over the Medium games is under the Scoring Management's autonomy and by this Article defined in Section 2 of "Procedural Errors";

3. ScreenSharers determining that the Suspect had broken Medium to Severe offenses over the past 7 days may Ban the Players. However, games must not be voided. Section 2 of this Article is enacted otherwise.

4. When banned for Cheating, Refusal, Inability, Bypass Attempt, ScreenSharers and Scorers have the possibility to provide exact games that can be Voided. Scorers reserve the right to wipe elo of players punished through ss and their teammates

5. Changes to this Article are possible if every single SS Manager is informed and agrees to the changes by totality, if at least one Scoring Manager has cooperated with them.

Chapter II

Preventive Adjustments

1. ScreenSharers hold the right to deny reports made against suspects untraditionally (through Discord DMs, Ongoing game tickets, public chat @-s and so on), however, if Players warn suspects in-game and then proceed to additionally warn them through every possible way, ScreenSharers lose the ability to deny requests.

Article 4 - Recommendations, Adjustments, Guarantees

1. If Players find flaws in the contexts of current regulations, they may notify ScreenShare Managers if it suggests that they can be freed from their punishment.

2. During scans, bans are issued for in instance detections.

3. Individual ScreenSharers can not open tickets against players. This section is regulated in the internal SS regulations document.

4. Individuals interfering with ScreenSharer duties do not hold the authority of a ScreenSharer, therefore Suspects are allowed to deny them without facing penalties.

Chapter III

Refer to Chapter IV - Penalties for Elaborations

Informative Section

Article 5 - Informativeness

1. Suspects who are aware they are getting ScreenShared and show their presence lose the ability to appeal under the excuse of unawareness, invalid report or any other privilege given by this Code.

2. Suspects who claim they were unable to view the report filed against them must show any evidence in appeals. Decisions are under SS Managers' discretion.

3. "Newbies" who newly joined Ranked Bridge will receive a one day penalty after their first light to medium offense to properly read the regulations. Their offenses will not stack up counting from this penalty. Players whose medium to severe offense bans were caused by force majeure scenarios may receive a single day penalty if they are capable of proving it was out of their control.

4. Event Penalty means being disallowed to participate in money-based events or tournaments, permanently.

Article 6 - Appeal Permissions

1. Suspects who miss warnings from players, but request to be ScreenShared overdue, do not lose the ability to verbally appeal but they will not be ScreenShared.

2. Suspects banned for Medium Offenses, in addition to misbehavior towards ScreenSharers, lose the ability to verbally appeal the whole span of a penalty.

3. It is impossible to appeal replay bans through ScreenSharing.

4. It is impossible to appeal any degree of offenses in which suspects recorded the sessions using the ScreenShare Appeals system.

5. Suspects lose the ability to appeal penalties if they do not appeal within the ongoing season.

Chapter IV

Penalties

Article 7 - Light Offenses

1. "Inability to SS" - This rule is divided into three types.

   (i) Extremely low-end PC or internet connection, or no Admin permissions, or issues with remote connection applications, when it is evident that none of these cases were intentionally caused, set-up or falsified by the Suspect - shall be penalized for no less than 2 days and no more than 4 days.

\n- The same Type (i) inability, which was intentionally caused or falsified by the Suspect - shall be penalized for no less than 10 days and no more than 21 days.

(ii) User appears to be on a Customized OS and the ScreenSharer acts under personal discretion of leniency, or it is evident the suspect had to leave from the beginning of the game whilst intentionally avoiding screenshares, or or any other form that makes it impossible to conduct a ScreenShare - shall be penalized for no less than 3 days and no more than 5 days.

• The same Type (i) and Type (ii) inability, which happened during international holidays, shall be penalized for no more than 1 day as a first instance offense, no more than 3 days as a second instance offense and no more than 7 days for every other instance, which will not lead to Permanent bans.

  (iii) When Suspects decide to agree on SS Tool scans and they are capable of running the scanners, inability is pardoned and the ScreenShare is considered to be concluded.

2. "2+ Mouse Plugged in" - this rule applies to cases where suspects have two mice connected, even if they have pre-installed mouse softwares, whether one of the mice is broken or regardless of any other reason.

3. "Stalling" - this rule applies to cases where Players go AFK whilst Frozen, or deliberately, or unintentionally fail to reply within the given interval. This rule also applies to scenarios where suspects re-queue matches to avoid being ScreenShared.

4. It is advised for [Players] to check DMs and Message Requests if [Players] were frozen, but they were not added to the ScreenShare Ticket, if a ScreenSharer has not opened a separate general ticket or higher-ups were unable to add the Suspect in a general ticket.

5. "=SS Misuse" - Players who jokingly warn suspects, regardless of their changed intentions, will be banned under this rule; same spreads on baiting newcomers and other players into breaking SS Rules. This includes sabotaging. This unites Baseless SS and Troll SS.

6. This rule also applies to suspects who fabricate evidence or tamper with falsified evidence, context-less evidence, after they have been banned to reduce or remove the punishment.

7. Revenge ScreenSharing is disallowed. The first ScreenShare will be taken and if resources allow, the second ScreenShare will be taken as well. If blatant revenge Screensharing is proven, permission to screenshare players will be revoked + 7 day ban.

8. Sabotaging occurs when Players wait for a specific team to report with an intention of slowing down the Scoring system, wasting time or bypassing the Limitations system of this Code.

9. SS Misuse is also considered when Players use the same screenshot of an expired SS Report to break Limitation rules.

Article 7¹ - Force Majeure

1. "Force Majeure" refers to an irresistible force or unforeseen event beyond the control of any person. No Player, Suspect shall be penalized if the cause of an offense is an unforeseen event.

2. Force Majeure events do not lead to stacked-up penalties, however, they are calculated separately and are not subject to Amnesty or Pardon of the ScreenShare Management.

3. If Inability and/or Trimmed OS offenses are judged as Force Majeure by the ScreenSharer/SS Manager(s), they are subject to Alternative Penalties of:

   1. 1-2day Ranked bans and voiding (or not voiding) of the game; and

   2. no rank-ban penalties but voiding of the game or an ELO sanction

4. Using the clause of Force Majeure in bad faith results in Bypass Attempt penalties and transfers the penalty stacking onto main penalties.

5. This classification of Force Majeure is in force from Chapter 3, Season 8 of Ranked Bridge.

Article 7² - ELO Restitution, Compensation

1. Every Player is eligible for ELO Restitution, which means recovery of any lost ELO per game to a Cheater if:

   1. They SS Reported the cheater within the 7-day period of the suspect's SS Penalty and the report did not get claimed or was claimed but took less than 25 minutes to finalize and/or where the suspect was only scanned with SS Tools;

   2. They SS Reported the cheater within the 7-day period of the suspect's SS Penalty, when during their report the suspect was released due technicality (force majeure, procedural errors, etc);

   3. Their SS Report of the suspect within the 7-day period was deemed invalid due to technicality;

   4. They reported the suspect but the ScreenSharer got bypassed, had to go or otherwise caused an unwanted result themselves;

   5. They queued against the cheater/suspect within the season and the ScreenShare Management believed that the cheater/suspect had cheated periodically, matching these queues;

   6. The ScreenSharer mishandled a report against the Player/Suspect, whether or not the Player/Suspect got SS Banned.

2. This Article is in power immediately.

Article 8 - Medium Offenses

1. "Disabled Services" - Ranked Bridge bans for disabled Sysmain, CDPUserSvc_{. . . }, PcaSvc, DPS, EventLog, Scheduler, SearchIndexer, BAM/DAM, Dusmsvc, Appinfo. Players may open tickets to verify these services are not disabled. If there is a pending ticket nobody replied to, they will not be banned if caught with disabled services. The use of optimizing softwares is at your own risk. If you feel like you are at risk of getting banned for this rule, open a ticket so that SSers attempt to fix them for you.

1.1 Important definition - Disabled services also includes:

1. Terminating BAM Inheritance

2. Disabled Activitiescache

3. Disabled JumpLists

4. Terminated Threads in services

1.2 Important definition - Interpreting section 1 of Article 8:

When Players open tickets to VERIFY the state of services, staff or SSers are not obliged to help them toggle it on. For the purposes of this code, having services on is a responsibility of the player and carelessly leaving them disabled without doing general research or putting effort into enabling them during or before the ticket is open is not subject to leniency.

2. "Closing MC/AnyDesk" - Suspects may not close their game after being warned not to log nor close AnyDesk mid session. This rule will be used even if the suspect's game crashes. Logging off alone is not bannable, unless the suspect simultaneously broke other rules.

3. "Refusing/Admitting" - Refusing and Admitting share the same ban length. Refusing is considered when suspects refuse to comply with the ScreenSharer before, as well as after accepting AnyDesk. Admitting is considered when suspects admit to the advantages asked by ScreenSharers.

IMPORTANT (REFUSING) - Users do not have the right to deny Echo SS Tool. However, they maintain the right to refuse the use of any other automated scanner. Refusal of SS Tools must not be used as a basis for revocation of assumption of innocence.

4. "Tampering" - this rule shares the same offense as "Stalling"; applies when suspects make it deliberately harder for ScreenSharers to search for anything. If suspects have specific confidential items, they must notify ScreenSharers prior to agreeing to share their desk. Images, Documents, Text files, Script files will not be considered confidential, ScreenSharers only check them if there is a reasonable suspicion.

5. "Cheating" - Cheating with hacked clients, cheat applications or unfair advantages, when:

1. The cheats used were also not self-destructed or do not have alerting self-destruction modules;

2. No Bypass methods or anti-forensic techniques were used;

3. The Player made an effort to hide the cheat but its form was not altered;

4. When no combination of offenses under Bypass Attempt are implemented.

Article 9 - Severe Offenses

1. "Bypass Attempt" - this rule only applies in guaranteed violations of Ch.3 regulations.

   Type (I) - Restarting Services, Clearing Journal, Clearing Registry Entries, Clearing Event Logs, Clearing or Modifying Prefetch, Using String Clearing applications, File Shredders, clearing shell:recent, NvAPPTimestamps tampering, lying to SSers as defined under Bypass Attempt

   Type (II) - Any interaction with PsExec, Scripting Applications (VsCode / NodeJS e.t.c), overwriting files on FAT32, replacing files on FAT32, Using FAT16/32 exFat Drives when the user has a history of mass bans and executions from the FAT drive is atypical from its common usage Apr 14, 2025, re-connecting Mass Storage Devices, Virtual Mounts;

   Type (III) - Scheduled: Powershell, Powershell_ISE, Scripting Applications, CMD or .bat files. Accessing regedit, Accessing scripting environments, Accessing ProcessHacker/SystemInformer/ProcMon, Cleaners, Optimizers near / close ScreenShares, running Process Hacker/SystemInformer/ProcMon, WMIC bypass methods, Unicode Characters on Cheats, Modified default Downloads path;

   Type (IV) - Switching PCs, Public Anti-Forensics, Modifying file data, Combined degrees of offenses;

1.1 Important definition *"Bypass Attempt" - users attempting to bypass by lying to SSers about their condition or knowingly selecting lesser punishment offenses to evade proper punishment will be re-banned under this rule*

1.4 Important definition "Bypass Attempt" Type IV - Under these offenses, Suspects will be banned for respective times without the possibility to verbally appeal, having to purchase an unban.

2. "Illegal Modifications" - this includes: Proxy Clients (ex. Lilith), Mouse Macros, External Macros, Clients that enable HitDelayFix, Freelook. Applications or Launchers banned by Ranked Bridge itself. Cloudflare / Cloudflare WARP is allowed.[02/22/2025]

   A) In "force majeure" scenarios, ScreenSharers can choose to not issue bans for the use of them but rather whitelist suspects for the next time.

   B) Any other form of Force Majeure, upon appealing, decided by SS Management, can be pardoned.

2.1 Important definition - Any current and future launcher used for optimizing game performance & its visuals (Lunar QT, Feather Client, etc) that does not come with a built-in advantage (hit delay fix, freelook, etc) is allowed.

Players using Lunar QT must not rename the QT launcher to confuse ScreenSharers.

2.2 Important definition - Any form of Ping manipulation falls under Ping Spoofing.

Ping Spoofing - *Intentionally or unintentionally, when Players had the capability to open SS Rules inquiry tickets, using applications or methods (ex. Hotspots) that manipulate the Ping following Ping Spoofing regulations**(since 04/24/2024). Ping Spoofing is bannable unless it solely serves to reduce or stabilize your ping (latency) without providing an unfair advantage (e.g. exitlag, VPN). General Server rules still apply.(since 03/02/2025)***

2.3 Important definition - *Any external or internal (within the game, via mods, launchers or related) applications modifying mouse input, sensitivity or acceleration, is allowed as long as they do not include CPS, HitDelay or other related banned settings disallowed by this Charter or Ranked Bridge itself.(since 10/16/2024)*

3. "Modified OS" - this rule applies to Customized Operating Systems (for example, Atlas OS) that are impossible to ScreenShare due to the majority services being off or the impossibility of re-enabling them. ScreenSharers must try everything to still ScreenShare the suspect before verdict.

3.1 Important definition - If the system is so modified / trimmed that it disables / limits more than 3 settings (defined in "Disabled Services"), the first offense ban will be for Inability to SS.

3.2 Important definition - Boot Camp Assistant (MacOS) is allowed.

3.3 Important definition - *Having used Hone or other partnered system optimizers, for the purposes of optimizing the device, when it is directly or indirectly trimming the system as penalized by this code is not subject to leniency or unbans. [02/04/2025]*

4. "Alting/Ban Evading" - banning alts is the responsibility of non-ScreenShare staff members, however, ScreenSharers still may ban alts of users who evade their previous punishments by creating alts.

Article 9¹ - Alternative Penalties

1. Suspects banned for Light offenses may alternatively be sanctioned without receiving Ranked bans.

2. Types of alternative sanctions are limited to:

   1. ELO reduction penalty;

   2. ELO transfer penalty;

   3. Warning of a severed penalty

3. Warning of a severed penalty is a conditional penalty, where the suspect is let go under the condition that he/she does not repeat the same offense. Otherwise, they will be penalized for up to triple the penalty length.

Article 10 - Unappealable Offenses

1. "Continuous Cheating and Bypassing" - breaking this rule will lead to a blacklist from the ScreenShare Management team, continuously cheating will not get suspects blacklisted, however, if they also possess, create, sell, distribute (for free) bypasses to players within Ranked Bridge, they will be held accountable.

2. "Bribing ScreenSharers" - ScreenShare Managers do not control the greed of their ScreenSharers, however, if suspects manage to bribe the ScreenSharer they will be permanently banned without the possibility to verbally appeal it; ScreenSharers will be demoted. Same rule applies to ScreenShare Managers.

3. "Organized Alting" - organizing a group of Players for the sole purpose of alting on one shared account under the motive of avoiding or complicating the procedure of ScreenSharing for Cheating, Alting, Ban Evading, e.t.c or for the purposes of confusing, misleading, manipulating staff and/or administration or Ownership, or for the purposes of bypassing ScreenShares by letting legitimate (cheat free) devices to be ScreenShared;

   The following rule spreads on any individual involved, regulated by the following hierarchy:

   The Instigator (here: Original Account Owner) - Permanent Ranked ban or a Server ban; Unappealable Verbally, Unappealable by Purchases; will be allowed to remain on the server as long as one causes no complications in appeal tickets.

   The Accomplice (here: Participants of the Plan) - Permanent Ranked ban or a Server ban; Unappealable Verbally and/or through Purchases.

   The Assistant (here: Those who deliberately confuse the staff or hide information from staff before exposure) - Permanent Ranked ban, Unappealable verbally; is allowed to purchase an unban (does not count as a ScreenShare Unban)

   The Ownership or Event Organizers hold full authority more imperative than this section of the ScreenShare Code, overruling, changing or ignoring this section, or making it more severe or lenient - as the funds of Events are at risk of such act's succession.

4. "Popularizing Bypasses" - suspects caught to be using "popular" bypasses and bypasses specifically directed against Ranked Bridge may be issued a permanent unappealable Ranked or Server ban.

   Ranked Ban: If they have not bypassed more than one individual ScreenSharer, have not gotten "too far" into the leaderboards (at least top 16) and were caught too late (after 1/3 of SS Requests or 2/3rd of the season)

   Server Ban: If they have bypassed more than one individual ScreenSharer or at least one ScreenShare Manager, gotten "too far" into the leaderboards (at least top 16) or were caught too late (after 1/3 of SS Requests or 2/3rd of the season)

   The suspect can be unbanned only if they buy an unban from the store.

Chapter V

Limitations

1. The time limit to report suspects after games is 8 minutes.

2. ScreenShare reports after the game are valid if they were issued under 8 minutes.

3. Cooldown on reporting suspects after expired tickets is 30 minutes. (since 04/24/2024)

4. Cooldown on reporting suspects after immediately denied tickets is not set.

5. "after game" countdown begins from the moment a game channel gets closed for every other reason than inactivity. Otherwise, the countdown starts after the next (1) minute a game ends.

6. If the ScreenSharer concludes that the report was based on personal impulse or bias after the Player loses a match, they lose the ability to issue reports generally for the next 24 hours. Here, SS Misuse regulations will be used. (since 04/24/2024)

7. Baselessly warning players not to log off for more than 3 instances will lead to a suspension from the ScreenShare tickets, up to a maximum of 1 (one) season's time span (until the ongoing season's end); The count carries over seasons and does not reset to 0 until the penalty is applied and expired.

8. The time limit of each ScreenShare is 1h30m.

9. The time limit for the special event ScreenShares is 2h.

10. The average time requirement of a ScreenShare is 25 minutes. (since 04/24/2024)

11. The average time requirement for the special event ScreenShares is 40 minutes. (since 04/24/2024)

12. Time limit for the ScreenSharer to go AFK before connecting is 10 minutes. Making SS Requests Void and invalid to be continued.

13. If ScreenSharers decide to switch due to them having to leave entirely, suspects are free to leave if no second ScreenSharer arrives in the next 15 minutes.

14. "after frozen" countdown begins from the moment a ScreenSharer talks.

15. "before ScreenShare" counts from the moment of the first Ranked match of the day of the suspect. Clearing files "before ScreenShare" is counted from the moment of the Suspect being warned not to log off.(since 06/11/2025) - CHANGE

16. Suspects are free to re-queue if no ScreenSharer responds to the ticket within the first 5 minutes of the ticket being opened.

17. Suspects will not face penalties if they log off after 7 minutes of the ticket being opened, or close MC after 10 minutes of the ticket being opened.

18. Stalling is considered 7 minutes of no response to the ticket. By this definition, suspects must show presence in the ticket to face no penalties. Typing in the ticket counts as showing presence. In this case the ban will be issued for 15 minutes of inactivity after the report ticket is open.

19. Players can only request 1 ScreenShare on the same Suspect per day. Expired requests or requests by mistake do not count. The Player Base can only request 4 ScreenShares on the same Player a day.

20. Suspects can not request to swap ScreenSharers who ScreenShare them if no other ScreenSharer is online. Doing so is considered refusal regardless, if no other ScreenSharer takes the report in 10 minutes from the initial refusal. (since 12/07/2024) - Clarification

Important Regulations & Procedural Errors

1. Players banned for incorrectly handled ScreenShares by ScreenSharers will be unbanned regardless of their offense stages or severity, or re-banned for a reasonably lesser than applicable penalty.

2. Players banned due misinformation provided by Staff or ScreenSharers & ScreenShare Managers in SS Inquiry tickets will be unbanned if their ban was issued on the same clarification. Whether or not the games should be voided, shall be decided by Scoring Management by or without following the rules to restore fairness for both the Suspect, Reporter and for the Community.

3. Echo SS Tool's Privacy Policy; Ocean SS Tool's Privacy Policy;

Chapter VI

Established by the Ranked Bridge Screenshare Management

Article 12 - Appeal Instances

1. Seasonal Ranked Bridge Appeals undergo 3 stages of appealable permissions-First Instance (Senior ScreenSharer), Second Instance (Collegial Composition of at least 3 Senior ScreenSharers excluding the initial handler of an appeal), Third Instance (SS Management).

2. Appeals can be transferred to IPSU Trial, Delegate's Trial, Division Trial and, finally, Headquarters if they are dissatisfied with the SS Management's decision in the Third Instance. First and Second Instances are handled within Ranked Bridge Itself, the rest are passed to the Ranked Bridge Screenshare Management.

3. Individual Sr. SSer, who had not SSed the Person, handles appeals in First Instance tickets. If the appeal is denied at first, minimum three Sr. SSers and the SSer (who ScreenShared the Suspect) handle appeals in the Second Instance.

4. If an appeal takes more than 24 hours to be handled, persons are eligible for ELO Compensation with an amount of 1 ELO per 6 hours wasted. Initial 24 hours count into this compensation.

Article 12¹ - First & Second Instance Appeals

1. Complaints as First Instance appeals are handled by an individual Senior ScreenSharer.

2. Nobody has the right to infringe with, interact with, overrule, affect, influence or otherwise disregard the decisions of the Senior ScreenSharer in this instance of appeals.

3. SS Management is limited with restrictions imposed under section 2 of this article. The Ownership or the SS Administration ensure no SS Manager influences or infringes with the appeals handled by Senior ScreenSharers.

4. Senior ScreenSharers face no penalties nor any form of sanctions for incorrectly handled appeals in the first instance.

5. In the First Instance, Senior ScreenSharers can handle cases related to Chapters I-IV, except for:

   1. Type III-IV Severe Offenses

   2. Unappealable Offenses

   3. ELO Restitution or Compensation

   4. Penalties imposed by the Ownership or non-ssers

6. Senior ScreenSharers are independent. Suspects/Players may issue appeals for the Second Instance to handle, where decision is finalized by majority votes of the Senior ScreenSharers.

Chapter VII

Legal

General Disclaimer

1. Within the server of Ranked Bridge (https://discord.gg/48yn5nvA) "Ranked Bridge" this Code is attributed to, data of Players is subject to the Terms of Service of "Echo" (Echo.ac) as an allowed Autonomous Scanner entailed and bound by the Terms.

2. Manual Inspections "ScreenShares" are subject to Data Protection Laws and we try to, as strictly and accordingly as possible, to not breach the rights of the Players. Every ScreenShare Document, Code, Rules document, SS Related Discord Ticket, form of consent comes with informative clauses explained in plain English; we the ScreenSharers by genuinity elaborate through communication, without rushing or being rushed, every complication, misunderstanding or trouble of comprehension by the Player ("Suspect").

Your Data

1. The title of this clause ("Your Data") is formulated in such a manner to attract attention.

2. Your Data during the process of Inspection is regulated by the following Laws and Definitions:

• EU Charter of Fundamental Rights (Article 8)

• GDPR

• Data Protection Act (U.K)

• U.S Data Privacy Laws

• European Convention on Cybercrime

3. For such, inspection is conducted by an experienced ScreenSharer, restricted to follow established protocols of conduct (Internal Regulations), with an assumption based on the general demographic of the server, that the Player ("Suspect") is of Legal age to consent, us otherwise retaining rights to restrict their access to the services of gameplay. Assumed age until told otherwise is 16.

4. On the basis of honesty, we retain the right to abandon the ScreenShare ("Inspection"), restrict the Player ("Suspect"), if and when it is revealed that the Player ("Suspect") is not of required age of consent regulated by applicable Laws.

5. For the purposes of applying the Laws in protection of Players, in Appeal tickets of ScreenShare the Management may inquire the Player's ("Suspect's") country of residency.

6. No method or approach to cheat analysis in this server violates the European Convention on Cybercrime.

Legitimacy

1. We do not collect nor require Personal Data. Inspection commences by the rules, under informed consent, with a legitimate purpose of detecting Cheats or otherwise sanctioned ("Banned") utilities (AutoClickers, Disallowed Modifications, Hacked Clients, Cheats, Cheat Injectors) and measures or practices generally known as MITRE Attacks or Digital Anti-Forensics to restore fair-play environment. Players ("Suspects") are given the option to admit to cheating or refuse the inspection as a whole before inspections.

2. Inspections are done via remote connection through Team Viewer or AnyDesk. Players have an imperative control over their devices, are allowed to move their mouse or refute any act by the Inspector ("ScreenSharer"). Penalties/Bans for such movements or tampering are issued under specific circumstances when:

3. The Inspector is about to detect a cheat file or a bypass but the Player prevents them from doing so.

4. The Inspector has a reasonable belief, based on general experience and insider information that the Player is using an anti-forensic technique, which is believable and assumed based on objectively unusual tracks of evidence.

5. The Player is purposefully mocking the Inspection to reach the imperative limitation time of the Inspection and be released from the Inspection.

6. The Player has cheated before and had gotten banned for it.

7. Other scenarios defined in the Special Part of this code.

3. Other measures of Player protection, honesty, genuinity and transparency are regulated by Unity Charters and Internal Regulations that include clauses for Ethics.

Guarantees

1. ScreenShare Administration guarantees that not a single clause is breached by the Inspectors nor ScreenShare Management, alone or with the help of ScreenShare Managers.

2. Every Player has the right to review the evidence collected against them, unless they are on a verge of a Blacklist or a second SS Permanent ban and the sufficiency of evidence is undoubtful as judged by the ScreenShare Management. Such evidence can still be requested and provided to them, if under the age of 18, under supervision of a parent.

3. Any undisclosed evidence can be given out to the Banned player after two months of the Penalty or when the Bypass, Cheat or technique they were banned for has been leaked to the public sooner and no longer presents grounds for secrecy.