Terms of Use.

Website use, account access, beta releases, and the limits of a fictional simulation project.

Updated October 10, 2026Website and account informationRead the Privacy Policy

The essentials

BeamMDT is a fan-made BeamNG.drive simulation project. Creating an account does not grant mod access. Activation codes and private downloads require separate authorization. Public purchasing and general mod downloads are not open yet.

This page explains the current website. Final paid-mod license, purchase, and refund conditions must be published before purchasing opens.

1. Scope of these Terms

These Terms describe use of the BeamMDT website, its account pages, and the protected website features that are currently available. They explain the distinction between browsing product information, creating an account, requesting access, and receiving permission to use a particular feature or download. Read them alongside the Privacy Policy, the legal notice, and the information attached to a specific release. Those pages address different subjects; a product feature list is not a substitute for release instructions.

BeamMDT is a fan-made simulation project. The public website presents planned editions, screenshots, release history, help, and an upcoming release schedule. Some account and administrator features already operate, while general public purchasing and mod downloads are not open. Availability therefore depends on the feature, the host you are visiting, and the permissions attached to your account. A page being visible does not establish that every action described on it is available to you.

This expanded website text provides more detail about the current service. It does not establish a new paid-mod license, checkout agreement, refund program, or service-level guarantee. Those conditions require their own published terms before purchasing opens. An editorial update date on this page is also distinct from the policy version recorded when an account profile was created or completed.

Back to contents

2. Fictional simulation and real-world boundaries

BeamMDT is intended for entertainment and gameplay in BeamNG.drive. People, agencies, vehicles, calls, incidents, records, and dispatch situations shown in the project are fictional game content. Interfaces that resemble a mobile data terminal, dispatch console, radio system, government form, or desktop workspace are simulation interfaces. Their appearance does not give them authority to access government systems, make official records, identify real people, or issue directions to emergency responders.

Do not rely on the project for an actual emergency, real dispatch, public-safety decision, legal assessment, medical decision, or professional qualification. A simulated response, record, warning, or vehicle status is not confirmation of a real event. Contact the appropriate real-world service through its established channels when you need actual help. Neither a BeamMDT account nor an activation code is a government credential.

When sharing screenshots or gameplay, keep the fictional context clear. Avoid presenting invented incidents or roleplay identities as official information about a real person or organization. Do not enter sensitive real-world case files, identification numbers, confidential workplace records, or private emergency information into a simulation merely because its screen resembles a familiar operational tool. Use fictional examples that you have permission to share.

Back to contents

3. What is available now

The public site supports browsing, reading the release catalog, comparing planned editions, reviewing setup information, viewing countdowns, and following the published beta-request link. Account sign-in, email verification, profile setup, and account-specific code views are separate features with their own requirements. Protected administrator tools and private beta downloads are available only to authorized accounts. This does not mean a visitor has access to the same features that an administrator can see.

A disabled control, coming-soon label, planned video, or future release date describes a feature that is not currently available through that control. Do not interpret a screenshot of an interface as a live browser application or a promise that every illustrated behavior ships in every edition. Where the page distinguishes a website example from an in-game feature, preserve that distinction when explaining or sharing it.

Features may also be temporarily unavailable while a provider, network, browser, or service is unable to complete a request. A successful page load only confirms that the page was served. It does not prove that authentication, code assignment, a download ticket, or a connected game feature succeeded. Read the result shown by the action you actually performed and check the applicable release information.

Back to contents

4. Release dates, trailers, and countdowns

The current schedule lists the official trailer for October 24, 2026 at 7 PM Eastern Daylight Time, the gameplay trailer for November 5, 2026 at 5 PM Eastern Standard Time, and the planned release for November 15, 2026 at 5 PM Eastern Standard Time. The countdown page shows the current release target. Eastern changes from daylight time to standard time between the October and November events, so their UTC offsets differ.

For the release, 5 PM EST corresponds to 22:00 UTC on November 15. A viewer in another time zone may see a different calendar date. A countdown is an informational display derived from the published target; reaching zero does not itself open a checkout, create a download entitlement, assign an activation code, or guarantee immediate access. Use the published availability and release notices to confirm what has actually opened.

Archived version dates describe previous releases and are not instructions to replace them with the next launch date. Plans, trailers, compatibility information, and feature descriptions can be refined during development. If current pages appear inconsistent, compare their update dates and the release-specific notes, and use the current official website surfaces for subsequent decisions.

Back to contents

5. Accounts and sign-in

Creating a BeamMDT account is separate from receiving mod access. The current account flow uses email and password authentication through Firebase Authentication, followed by a protected website session. Use an email address you control and follow the verification instructions when requested. Administrator sign-in is a separate gate; typing an administrator-style username into an ordinary customer form does not create administrator authority.

Keep your password private and use the password-reset flow when you need to regain access. Do not share a password, verification link, reset link, session cookie, or authentication token in screenshots, public posts, support examples, or messages to other users. A page asking you to complete profile setup is not asking you to disclose your password to another person. The website has dedicated forms for account authentication.

Authentication controls depend on the service capabilities actually enabled. Do not assume that a reference design, screenshot, or familiar icon means passkeys, email codes, or an additional authentication factor is available. The account page should show the methods currently supported. If a sign-in request fails or your session expires, use the provided retry or sign-in controls instead of treating an old screen as proof that you remain authenticated.

Back to contents

6. Email verification and account recovery

Email verification confirms access to the email address associated with an account. It does not verify a real-world job, agency affiliation, roleplay rank, purchase, or entitlement. The verification view distinguishes an email that has been requested from an email that has not yet been sent. Check your inbox and spam folder, and follow the current link. Requesting another message can make an older action link unsuitable for completing the current flow.

Password-reset and verification links are sensitive account actions. Open them only when you recognize the request and the intended account. An expired, invalid, already-used, or mismatched link may require you to return to sign-in and start again. Completing a reset does not assign a code or grant administrator access. A generic reset confirmation also does not disclose whether another person has an account.

Changing the email used during an unfinished verification flow requires following the available account controls; it is not permission to alter another account. A browser restored after a reload may need fresh sign-in before it can request or recheck verification. Keep access to your email provider secure as well, because access to that mailbox can affect account recovery. Do not send recovery links to people offering unofficial account assistance.

Back to contents

7. Profiles, callsigns, and avatars

The account setup flow collects a display name or callsign, a unit identifier, an avatar choice or upload, and the required agreement record. These details help identify your fictional account within the project. Use an identity that you are allowed to use and that does not misrepresent a real person, government body, staff member, or organization. A callsign or unit number is a profile label, not evidence of a real credential or verified employment.

The form applies its own length, character, and image limits. Those technical checks make data suitable for the interface; they do not establish that the content is lawful, accurate, or appropriate. Use an avatar you created or have permission to use. Avoid images containing private documents, visible access codes, another person’s sensitive information, or content you would not want associated with the account.

A completed profile may be required before a protected customer feature can open. Finishing setup does not create a purchase, approve a beta request, or override an administrator decision. When changing profile details, verify the saved result. If a callsign is unavailable or an upload is rejected, choose an acceptable alternative through the form rather than trying to bypass the validation rules.

Back to contents

8. Sessions and shared-device use

Protected website pages use a session that lasts 30 minutes. The server enforces the protected session; a remembered email address or a visible account card does not extend its authorization. The public, administrator, and dashboard hosts use separate host-scoped session cookies. Signing out on one host should not be assumed to clear every independent browser profile or every session on another device.

Use Sign out when you finish, especially on a shared computer. Close sensitive tabs and remove any private files you intentionally downloaded or exported when the device should not retain them. Signing out does not erase a browser’s history, a saved screenshot, an operating system clipboard, an exported file, or a download that already completed. The remember-email option saves the email locally for convenience and should be left off on a shared device.

If a protected request returns an authentication error, sign in again through the normal flow. Do not rely on stale data still visible on a screen after authorization has ended. Browser privacy settings that block essential cookies or storage can affect sign-in. Keep the browser and device under your control, and avoid granting an unfamiliar extension access to account pages or sensitive downloads.

Back to contents

9. Activation codes and separate access decisions

Activation codes are assigned separately from account creation. A verified email, saved profile, beta-request submission, countdown, or signed-in greeting does not mean a code has been issued. The account page shows the codes actually associated with the authenticated account and distinguishes pending assignment from an assigned code. An administrator must confirm access where the current process requires that approval.

Treat an activation code as private account information. Revealing it on your own screen does not authorize redistribution or posting it in a public example. An edition label, masked value, assignment record, or request status should be read in the context of the actual code record. Empty or malformed records are not a usable code. If a page reports an error while loading codes, do not interpret the error as proof that your entitlement has disappeared or been granted.

A request for a new or replacement code enters a separate review process. Submitting it does not guarantee approval, a response deadline, a particular edition, or automatic replacement. Provide only the information the request form needs and avoid including passwords or verification links. The activation-code pages explain the current account-facing controls and status.

Back to contents

10. Administrator authority and protected tools

Administrator pages are intended for accounts that already have the required authority. Their existence, a visible sign-in form, a navigation link, or possession of an ordinary customer account does not grant that authority. Protected server checks decide whether a request can read or change restricted data. Do not attempt to impersonate a staff member, reuse another person’s session, or change a request to retrieve another account’s private records.

Authorized administrators can work with code assignments, requests, catalog access, and the records exposed by their permitted tools. Use those tools only for the project purpose for which access was granted. Keep customer information, code values, administrative notes, private release links, and exported records out of public screenshots. A dashboard revenue chart reflects recorded data available to that interface; it is not a bank balance, payment processor statement, or independent financial audit.

Read the action and target before submitting a change. A temporary draft or interface preview may differ from the saved record. Check the server response and the refreshed result after a mutation. If access is withdrawn or expires, stop using the restricted tools and return through the sign-in process. These website explanations do not expand an administrator’s existing permissions.

Back to contents

11. Beta requests and early access

The beta-request button opens an external Google Forms request form. Submitting the form expresses interest in early access. It does not guarantee selection, immediate delivery, a specific edition, continued participation, a reply deadline, or permission to redistribute a private build. The form is an access-request channel; the website does not describe it as a general support ticket system or a verified privacy-request process.

Private betas can contain unfinished behavior, changing interfaces, missing features, known defects, and compatibility differences. Use the instructions and release notes for the exact build you receive. Preserve your existing settings and files through the supplied installation or backup steps. Do not infer that a newer-looking screenshot describes every earlier archive, or that a public version-history entry makes its private artifact publicly downloadable.

Keep access details private and identify the exact version when reporting a problem. A useful report describes the steps, expected result, actual result, and relevant environment without revealing account credentials or personal records. Acceptance into a beta does not by itself establish a paid license or promise that every experimental feature will appear in the final release. Look for separately published participation conditions accompanying any private access.

Back to contents

12. Protected downloads and release archives

Private release downloads require the appropriate authenticated authorization. The current protected download process can issue a short-lived, single-use ticket associated with the requesting account and session. A ticket is not a permanent public URL and should not be shared or embedded in another site. An expired or consumed ticket may require a new authorized request. A download that fails partway through is not proof that a complete, usable package was saved.

Release archives preserve version-specific artifacts and notes. Select the intended version and artifact type, and follow its supplied instructions. A package name, historical date, Latest label, or file-size display does not change the permissions needed to access the artifact. Do not rename an old package and present it as the current build. Where hashes or verification information are supplied, compare the downloaded artifact using the documented workflow.

Treat files obtained through a restricted library according to the conditions supplied with that release. These website Terms do not grant a blanket redistribution license for private builds, installers, optional bridges, logos, or other bundled components. Retaining an archive entry on the website also does not guarantee that every historical build is suitable for a current game version or operating system.

Back to contents

13. Installation, backups, and compatibility

BeamMDT is a native BeamNG.drive modification. Its in-game desktop appearance does not make the public marketing site a replacement for the game or an independently installed operational dispatch system. Obtain and maintain your own legitimate copy of BeamNG.drive; it is not included in a planned BeamMDT edition price. Setup guidance currently targets BeamNG.drive on Windows, and a complete tested game-version range and minimum hardware specification have not been published.

Follow the instructions for the exact ZIP, Windows setup utility, or optional bridge you obtain. The private Windows installer is currently unsigned. Some releases use direct ZIP installation while others offer a separate setup utility. Keep one intended active copy where the release instructions require it, and preserve unrelated mods and existing settings. Check the selected profile folder before installing, updating, or removing a package.

Backups are useful only when they contain the files you need and can be restored. Review any installer report and verification result rather than assuming a completed wizard proves every game feature works. A successful website download, archive integrity check, or setup utility launch does not establish in-game compatibility or performance. Consult setup and support and the release-specific notes before changing a working installation.

Back to contents

14. Planned editions and feature descriptions

The edition comparison describes the planned Lite, Plus, Pro, and Ultra offerings. Current displayed prices and feature lists are release planning information. They are not a completed order, entitlement record, or final sales contract. A visitor choosing an edition in a website finder does not purchase that edition, reserve stock, create a charge, or automatically assign a code.

Read feature availability in context. Website illustrations, guided tours, screenshots, optional integrations, in-game interfaces, and future release descriptions are different kinds of information. Some examples are static and make no AI or voice requests. A visual resemblance to a third-party desktop or dispatch tool does not establish access to that third party’s software, database, account, or services.

If a feature depends on a particular edition, version, external account, provider, or optional component, those dependencies matter. Remote MDT is an optional way to use the full MDT on another laptop while BeamNG.drive and the mod continue running on the game computer. It does not run the whole mod on the second device. Do not assume that an edition includes every demonstration or that a planned comparison describes an already-installed private beta. Final compatibility, licensing, purchase, and support information must be available before purchasing opens. Recheck the current published comparison at that point instead of relying on an old screenshot or informal summary.

Back to contents

15. Purchases, refunds, and future commercial terms

Public purchasing is not open through the current website. There is no current public checkout that these Terms turn into a purchase service. The website does not presently collect a payment-card number through a BeamMDT checkout. A planned price or countdown should not be interpreted as permission to send money to an unofficial contact or an assurance that an off-site payment will create access.

Final paid-mod license conditions, purchase terms, refund rules, and compatibility information have not yet been published. This page does not invent those conditions or waive rights that may apply to a future transaction. A completed commercial flow will need to identify the offered product and the applicable terms clearly. Review those published conditions before you buy when purchasing becomes available.

The purchase and refund availability page explains the current status. Do not assume there is a particular refund period, cancellation mechanism, replacement guarantee, or delivery deadline merely because another digital product uses one. Third-party game purchases and optional provider subscriptions are separate arrangements governed by their own sellers. A BeamMDT account, code request, or private beta selection is not a receipt for those external purchases.

Back to contents

16. Optional AI, voice, and other providers

AI and voice connections are optional external services. A release that supports them may require your own provider account, credentials, software component, or subscription. Provider charges and usage limits are separate from the planned BeamMDT edition price. Built-in replies are available without connecting those services where the release describes that option. The website examples themselves do not make AI or voice requests.

Before enabling an integration, read the instructions supplied with the particular release and the provider’s current terms and privacy information. Consider what audio, text, prompts, or other data the integration sends and where credentials are stored. Do not paste provider keys into a public bug report or a website account field that does not request them. A key intended for an optional local bridge should be handled through that bridge’s documented configuration.

Provider availability, output, pricing, and account approval are outside the website’s direct control. A generated response is simulation content and should not be treated as a reliable real-world instruction. These website Terms do not replace an external provider’s agreement or promise that an optional integration will continue to work indefinitely. Disabling or avoiding an optional service remains distinct from deleting an account with that provider.

The homepage guide can generate AI answers through Groq when the server connection is configured. Your submitted question and bounded recent conversation are processed for that response as explained in the AI chat privacy details. Generated text can be wrong or incomplete; check the published guide and release instructions before using it. The chat cannot assign codes, approve beta access, recover an account, make a purchase, or execute a command in your game. A scenario draft remains a fictional draft, and a saved guide answer is labeled separately from an AI response. Provider availability and request limits can interrupt the chat.

Back to contents

17. Responsible use of the website

Use the public and account features for their intended project purposes. Do not attempt to obtain another person’s private account data, activation code, session, download ticket, or administrator records. Do not submit credentials that belong to someone else, present yourself as authorized staff when you are not, or intentionally alter requests to bypass a permission check. A publicly accessible sign-in page is not authorization to probe protected customer or administrator data.

Avoid flooding forms, automated repeated authentication attempts, disruptive requests, and content intended to interfere with the service. Rate limits and validation can reject a request even when the page loads normally. Do not treat a blocked attempt as an invitation to rotate identities or evade the control. Ordinary browser tools may help you understand your own request, but they do not establish permission to exploit another account or service.

Use accurate, relevant information where a form asks for it, and keep private or unrelated information out of free-text fields. Do not upload content you lack permission to use. If you encounter a malfunction or suspect unauthorized access, preserve a concise description with sensitive details removed and use a currently published project contact channel when one becomes available.

Back to contents

18. Content, screenshots, and intellectual property

Project screenshots, artwork, logos, interface designs, release notes, and bundled components may involve different creators and rights holders. Publication on the website does not establish that every asset has the same reuse license. Refer to credits and any release-specific notices when identifying contributors or checking the origin of material. Attribution is useful, but it is not automatically permission for every kind of redistribution or commercial use.

Product names and logos belong to their respective owners. BeamMDT is not affiliated with BeamNG GmbH or the manufacturers, agencies, companies, or brands depicted. Their presence identifies inspirations or game content and does not imply endorsement, partnership, official status, or verified licensing. A lore-friendly version is planned with each edition; that plan should not be described as an already-available replacement in every release.

When sharing your own gameplay or a public page, keep the context and version accurate and redact private details. Do not include a hidden code, customer record, administrative note, session value, or private download URL in an otherwise public screenshot. These website explanations do not grant a license for third-party trademarks, copyrighted material, or a private package beyond whatever permission its rights holder actually provides.

Back to contents

20. Privacy and data handling

The Privacy Policy describes the information involved in browsing, authentication, profiles, codes, requests, protected downloads, local preferences, and administration. It also explains the use of Firebase and Cloudflare, the distinction between a 30-minute session and persistent account records, and limits in currently published contact and retention information. Read that page before providing information beyond ordinary public browsing.

Only submit information that is appropriate for a fictional game project and necessary for the action. Public product questions and website demonstrations are different from private account records. A profile, code request, support example, or administrator note can persist after a browser session ends. Signing out is an access-control step; it is not an account-deletion command, a provider-data deletion request, or an eraser for files already exported.

Use device and browser controls for local convenience preferences, and the available account interface for supported profile changes. Do not assume the project has a self-service deletion, complete data export, or a verified privacy-request inbox unless a working route is actually published. This page does not create a new data-sharing consent by describing a feature or retroactively change the agreement record stored during an earlier setup flow.

Back to contents

21. Service interruptions and information limits

Website behavior depends on the browser, network, hosting service, identity provider, and protected backend. A timeout, stale view, interrupted request, or provider outage can prevent an action from completing. Refresh carefully and check whether an action already succeeded before submitting it again, particularly when an authorized administrator changes a record. A loading indicator is not a final success result.

Public descriptions are intended to explain the project clearly, but they cannot establish every device’s performance, every third-party integration’s behavior, or every historical release’s compatibility. A website screenshot is a representation of a particular view, not a guarantee of a professional system or a complete native application acceptance test. Use current release notes and direct testing of your installed build for version-specific decisions.

No uptime percentage, round-the-clock staffing commitment, response deadline, or formal support service level is currently published for the website. These limits explain the present offering; they are not a broad exclusion of responsibility for every situation or a statement that applicable legal rights disappear. If a feature is important to you, verify its actual availability and published conditions before depending on it.

Back to contents

22. Changes, maintenance, and older versions

The website and project can change during development. A current page may update a release target, correct a description, improve an interface, or explain a workflow more fully. An archive preserves historical releases and should be read as historical information. Current labels and links do not necessarily make earlier packages appropriate for a new environment. Keep the version number with any saved release notes or issue report.

Some changes require generated pages and multiple hosts to be refreshed. If you see inconsistent text, reload the page and compare the canonical website with the current release information. A locally cached page, saved screenshot, local development page, or marketing mirror can differ temporarily from the active protected service. The public marketing mirror does not provide an independent customer or administrator backend.

Check this page’s editorial update date when returning after a long absence. A future material change to account conditions or commercial terms should be described through the relevant published flow; this expanded explanation does not assert that every existing account has accepted a new contract. When a release supplies more specific operating instructions, follow those instructions for that release while maintaining the privacy and access boundaries described here.

Back to contents

23. Getting help and reporting a problem

Start with the FAQ, setup and support, the relevant release notes, and the visible account status. A useful report includes the page or exact version, the steps you took, the expected result, and the actual result. Include a browser or game version when it helps explain compatibility. Remove passwords, tokens, full activation codes, customer records, and private links before sharing a screenshot or console excerpt.

The developer is identified on the project’s credits pages. A support email, Discord server, and social accounts have not yet been published, and the beta form is not a promised support ticket channel. This page therefore does not invent a staffed help desk, claim a guaranteed response time, or direct sensitive account information to a made-up address. Use only verified contact routes that the project actually publishes.

For a problem with an external account, subscription, purchase, or mailbox, use that provider’s own support and recovery process. BeamMDT sign-in cannot resolve an unrelated provider’s billing or identity issue. If the project later publishes a dedicated support or privacy channel, check its scope and instructions before sending information. Keep private evidence available for an appropriate channel without exposing it publicly.

Back to contents

24. How to read these pages together

Use the website Terms for the current website scope and access expectations. Use the Privacy Policy for data handling, the legal notice for simulation and affiliation context, the purchases and refunds page for current commercial availability, and release instructions for the exact package. A brief summary card or footer is a navigation aid and cannot explain every detail of a protected feature.

These pages should not be read as an invented legal entity, a jurisdiction-specific contract, an arbitration requirement, a published age threshold, or a new paid-mod license. The project has not supplied those decisions through this website text. Where applicable law provides rights or obligations, an explanatory website page does not determine their existence merely by naming or omitting them.

If a statement seems to promise more than the current interface, published product status, or release-specific conditions support, verify the concrete feature before acting on that interpretation. The website should explain what exists and what remains planned. Your account status, actual assignment records, authorized download result, and the instructions provided with a release are more useful evidence than an assumption drawn from a countdown or a familiar-looking design.

Back to contents

Editorial expansion published October 10, 2026. Account setup agreement records retain their existing version; this page update does not rewrite those records.