aRCadeRally
Terms of use of the platform
MVP VERSION • DRAFT
§01

General provisions

  1. These Regulations define the rules for using the aRCadeRally platform, which enables users to remotely participate in competitions using real RC vehicles controlled via the Internet.
  2. The aRCadeRally platform enables in particular:
    • registering and maintaining a user account,
    • topping up your virtual currency balance,
    • booking a driving session,
    • remote control of an RC vehicle during an active session,
    • reviewing session history and reporting complaints.
  3. Using the platform constitutes acceptance of these Terms and Conditions.
  4. The Terms and Conditions apply to the use of the platform by players, regardless of whether they use the web or desktop version of the platform.
§02

Definitions

  1. Platform — aRCadeRally system available online, used to book and participate in remote driving sessions with RC vehicles.
  2. Player / User — a natural person who has an account on the Platform.
  3. Session — a reserved time period during which the Player can use the assigned RC vehicle in the selected arena.
  4. Arena / Track / Board — the physical place where gameplay using RC vehicles takes place.
  5. Vehicle — a real RC vehicle powered by the aRCadeRally system.
  6. Coins — virtual currency used on the Platform to purchase and book sessions.
  7. Wallet — coin balance assigned to the Player's account.
  8. HOLD Reservation — temporary blocking of funds and session space while the reservation is finalized.
  9. Reservation CONFIRMED — confirmed reservation for which coins were charged.
  10. Track Administrator — operator responsible for handling a specific arena and session.
  11. Super-Admin / Platform Administrator — central administrator of the aRCadeRally platform.
§ 03

Technical requirements

  1. To use the Platform you must:
    • a device with Internet access,
    • an up-to-date web browser or compatible desktop application,
    • a stable internet connection enabling the reception of video streams and transmission of control commands.
  2. The platform may also be available as a desktop application for selected operating systems.
  3. The quality of gameplay depends on, among other things, the quality of the Player's internet connection, network latency and current infrastructure availability.
  4. aRCadeRally does not guarantee the complete absence of lag, momentary image disruptions or temporary technical problems, but takes steps to ensure the smoothest possible gameplay.
§04

Registration and user account

  1. Using the reservation and game functions requires the creation of a user account.
  2. During registration, the User provides true and current data required by the registration form.
  3. Email address verification is required before making your first reservation.
  4. The user is responsible for securing their login details and not disclosing them to third parties.
  5. It is prohibited to:
    • creating accounts using false data,
    • using other users' accounts,
    • taking actions aimed at circumventing the Platform's security measures.
  6. The Administrator may block a user's account in the event of violation of the Regulations, abuse, attempts to disrupt the operation of the system or suspicion of acting to the detriment of the Platform, other players or operational partners.
§ 05

Wallet and payments

  1. The Platform uses a coin-based settlement system.
  2. Under the current MVP assumptions, 1 PLN is equivalent to 10 coins.
  3. The minimum top-up amount is PLN 50, unless the Platform indicates otherwise.
  4. The Wallet is topped up via an external payment operator.
  5. Coins are used to book sessions and other services available on the Platform.
  6. The history of top-ups, reservations and refunds is visible in the user's Wallet.
  7. Any refund to the bank account does not take place automatically and may be made manually after the application has been approved or in other cases specified by the administrator.
§ 06

Booking a session

  1. The Player can only book an available session published on the Platform.
  2. The booking process includes in particular:
    • arena selection,
    • selecting the date and time,
    • selecting the type of journey, if available,
    • optional selection of a specific vehicle or random allocation,
    • confirmation of reservation.
  3. Once the booking process has started, funds may be temporarily placed on HOLD for a maximum of 5 minutes.
  4. After successful confirmation of the reservation, it receives the CONFIRMED status and the appropriate number of coins is debited from the Player Wallet.
  5. Failure to finalize the reservation during the HOLD period will result in the automatic expiry of the hold and the unblocking of funds.
  6. The platform may limit the availability of certain arenas or sessions depending on the user's region, connection quality or technical parameters of the game.
§07

Cancellation and no-show policy

  1. The player can cancel a confirmed reservation within the time specified for a given slot.
  2. In the current MVP model, default penalty-free cancellation is possible up to 2 hours before the start of the session, unless a different time is specified for the track.
  3. If cancelled within the permitted time, the Player will receive a full refund of the withdrawn coins.
  4. In case of cancellation after the permitted time, coins are non-refundable, except for situations covered in the complaint.
  5. If a Player fails to appear in a session or does not connect on time without a reason attributable to the Platform or the organizer, it is treated as a no-show and the coins are forfeited.
  6. In case of technical problems, the Player may submit a complaint in accordance with §11.
§08

Rules for participating in the session

  1. Game View can be activated before the session is scheduled to start, usually around 5 minutes before start.
  2. Before starting, the Player can access the video preview and connection test, but vehicle controls remain locked until the session officially starts.
  3. The session may be started and ended automatically or by the Track Administrator.
  4. During the session, the Player gains the ability to control the vehicle using the provided control methods.
  5. Once the session ends, control is locked and the session is assigned a terminated status.
  6. The platform can display system messages, countdowns, technical information, and session status.
§09

Rules for safe and fair play

  1. The Player undertakes to use the Platform in a manner consistent with its intended purpose.
  2. It is prohibited to:
    • intentionally destroying a vehicle or taking actions intended to damage equipment,
    • intentionally ramming obstacles, track elements or other vehicles if the given mode does not provide for it,
    • attempting to disrupt the session, stream or control,
    • using software, scripts, macros or devices that automate control in an unauthorized manner,
    • bypassing system restrictions and security measures.
  3. In the event of a violation of the rules, the Track Administrator or Super-Admin may:
    • lock the controls,
    • interrupt the session,
    • refuse to refund funds,
    • temporarily or permanently block the user account.
  4. If required for game or equipment safety, the Track Administrator may take control of the vehicle, initiate an emergency stop, or end the session.
§ 10

Technical problems and loss of connection

  1. aRCadeRally makes every effort to ensure the continuity of the Platform and sessions.
  2. If the connection is lost, the system may automatically attempt to reconnect during the session.
  3. The session is generally not automatically paused due to a user disconnection.
  4. Momentary image distortions, increased ping, drops in stream quality or a short-term loss of control may result from both the Platform infrastructure and the connection on the user's side.
  5. If the problem had a significant impact on the ability to use the session, the Player may file a complaint.
§ 11

Complaints

  1. The player has the right to submit a complaint regarding the session, in particular in the case of:
    • vehicle breakdown,
    • serious technical problems,
    • loss of connection or inability to control,
    • stream malfunctioning,
    • unjustified takeover of control or interruption of the session.
  2. Complaints must be submitted no later than 24 hours after the end of the session.
  3. The complaint should include at least:
    • session identification,
    • description of the problem,
    • if possible, the time of occurrence of the problem.
  4. Complaints are considered by the Track Administrator, and in the absence of a decision within a reasonable time, they may be forwarded to the Super-Admin.
  5. The complaint may be:
    • taken into account in its entirety,
    • partially taken into account,
    • rejected.
  6. If the complaint is accepted, the user may receive a full or partial refund of coins.
  7. The decision regarding the complaint is communicated to the user electronically or within the Platform.
  8. The user may appeal against the decision regarding the complaint in accordance with the instructions provided in the decision.
§ 12

Data, logs and monitoring

  1. In order to ensure the proper operation of the Platform, the security of the game and the handling of complaints, aRCadeRally may process data regarding user activity on the Platform.
  2. The Platform may keep logs including:
    • payment and reservation logs,
    • technical session logs,
    • events related to connection, disconnection, locks and administrator actions.
  3. Logs can be used for:
    • consideration of complaints,
    • counteracting abuses,
    • ensuring system security,
    • analysis of the quality of the Platform's operation.
  4. Detailed rules for the processing of personal data are specified in the Privacy Policy.
§ 13

Responsibility

  1. aRCadeRally is responsible for the operation of the Platform to the extent required by mandatory legal provisions.
  2. aRCadeRally is not responsible for:
    • problems resulting from insufficient quality of the Internet connection on the user's side,
    • incompatibility of the user's device with technical requirements,
    • consequences of user actions violating the Regulations,
    • temporary unavailability of services due to technical work, updates or force majeure.
  3. aRCadeRally reserves the right to temporarily limit the availability of selected functions, tracks, arenas or vehicles, in particular for technical, safety or service reasons.
§ 14

Changes to services and availability

  1. The platform may develop and change available gameplay modes, payment system, price lists, vehicle availability, control methods and account features.
  2. Not all arenas, vehicles and features may be available to all users at all times.
  3. Individual tracks and vehicles can have an online, offline, test or service status, which affects their visibility and booking options.
§ 15

Right of withdrawal and digital services

  1. Regarding Wallet top-ups, session bookings and other digital services, the relevant provisions of consumer law apply.
  2. If required by law, the user, before purchasing, consents to the commencement of the service provision before the expiry of the withdrawal period and acknowledges the consequences of such consent.
  3. Detailed rules regarding withdrawals, exceptions and returns should be indicated in the purchase form and sales policy.
§ 16

Final provisions

  1. The Regulations come into force on the date of their publication on the Platform.
  2. aRCadeRally may change the Regulations for important reasons, in particular in the event of legal, technical, organizational or business changes.
  3. Users will be informed about significant changes to the Regulations in an appropriate manner on the Platform or electronically.
  4. In matters not regulated by the Regulations, the provisions of the law applicable to the registered office of the Platform operator and mandatory provisions protecting consumers shall apply.
// Draft Notes - To be completed before publication Before the final publication of the Regulations, the following issues should be clarified:
  • Who is formally the operator and what are their full details?
  • Do you start with wallet/coins or product + code?
  • How to precisely describe the withdrawal from the contract and consent at checkout
  • Should a stricter ban on deliberately crashing cars and damaging the track be introduced?
Scroll to Top