The essentials
You can read public product information without creating a profile. Account actions use Firebase Authentication and a protected host-specific website session. Profile information is stored privately in Cloudflare D1; code requests and administrative records use Firestore. Hosting providers also handle network information and may provide performance measurement.
Remember email and appearance choices stay in your browser. Signing out or clearing browser data does not delete server-side records. The current account settings edit supported profile fields; there is no automated account-deletion or privacy-export tool. This page explains those limits and the contact information currently available.
1. What this policy covers
This policy explains how the BeamMDT website handles information when you browse public pages, create or use a website account, save a profile, request an activation code, or enter an administrator workspace. It describes the services currently connected to those website flows. BeamMDT is an unofficial project for fictional BeamNG.drive gameplay. The website does not connect to government records, emergency services, real police databases, or a vehicle registration system. The public presentation may show dispatch screens and patrol scenarios, but those illustrations do not make the website a real public-safety service.
The policy covers the public site at beammdt.com, its account pages, and the related administrator hosts used by the project. The Firebase marketing mirror at beammdt.web.app displays public website content and sends account-related routes to the canonical service. A browser can therefore make requests to more than one provider during an ordinary visit. The address bar identifies the page you are using; a familiar logo alone does not establish that a page belongs to this project.
Website information is separate from information handled by a downloaded mod, an optional local bridge, your BeamNG installation, or an external AI or voice provider you choose to connect. Those products can have different permissions, storage locations, and network connections. This notice does not claim to describe every version of that software. Read the documentation supplied with your actual download and the website terms alongside this policy. A planned feature is not treated here as an existing collection system.
2. How to read the information here
The sections below follow the information through its practical lifecycle: what you enter, what your browser keeps, what the servers receive, who can access it, and what controls currently exist. Some entries describe a definite application behavior, such as saving an appearance preference locally. Others describe provider processing, such as the network information a hosting company handles to deliver a page. Those are different kinds of activity and should not be confused with each other.
An account identifier, an email address, a profile picture, or a request message can identify you even when a display name is fictional. A unit number can also become identifying if you reuse a number associated with you elsewhere. Information does not become anonymous merely because the project is intended for simulation. Choose what you submit with that distinction in mind. Public examples use fictional material; information that you personally type into an account form is still your submission.
This expanded explanation reflects the website as reviewed on October 10, 2026. It does not create a new setting, a new deletion button, or a new support channel. It also does not change the account-policy version already recorded by the setup service. Where a retention period or contact method is not established, the relevant section says so. That is a limitation of the current service, not an invitation to assume that information vanishes immediately. Use the contents links to reach the topic that matters to your decision.
3. The main categories of website information
The website handles several distinct categories rather than one combined profile. Authentication information identifies the Firebase account and establishes whether an email address is verified. Website profile information supplies the display name, unit number, optional avatar, and recorded setup agreement. Session information allows a particular browser and host to make protected requests for a limited period. Code-request and assignment information supports the separate process for requesting and receiving access. Technical information supports delivery, security, and service troubleshooting.
A public visitor can read product pages without submitting a website profile. Hosting providers still receive the requests necessary to send those pages, fonts, scripts, and images. A signed-in customer supplies more information when using account features. An administrator can access additional protected operational records through a separate gate. The fact that these categories use a common account identifier does not make every record visible to every user or publicly searchable.
The summary table identifies the principal storage boundary. It is not a promise that a record exists in only one physical copy: service backups, browser caches, provider logs, or copies you make yourself can exist separately. Nor does the table assign an unverified deletion date. The detailed sections explain the useful distinctions, including why clearing browser data does not erase a saved server profile and why leaving a page does not automatically cancel a code request.
| Category | Examples | Primary boundary |
|---|---|---|
| Authentication | Email, account identifier, verification status | Firebase Authentication and protected account service |
| Website profile | Display name, unit number, avatar, agreement record | Private account database |
| Browser preferences | Appearance and optional remembered email | Your browser's local storage |
| Requests and assignments | Reason, message, reference, assigned access | Protected Firestore records |
| Technical activity | Request metadata, security counters, session timing | Application and hosting infrastructure |
4. Reading the public website
Public pages include product descriptions, edition comparisons, release information, credits, help, and the launch countdown. Reading them does not require you to create a profile or provide a password. The browser asks the hosting service for each page and its supporting assets. The service must receive enough request information to send the response back, distinguish the requested resource, and apply its delivery and security rules. A visit is therefore not a zero-information exchange even when you leave every form untouched.
The page may check whether a website session is available so it can show the appropriate account state in the header. That check is different from creating a new account or giving public visitors access to protected records. If no valid session is available, account-dependent controls remain limited. An error message about sign-in does not imply that a public visitor has submitted a profile or that an account has been created behind the scenes.
Public screenshots, branding, font files, and product captures are website assets. Loading a capture does not upload your own game screen. Moving through edition choices or reading a trailer date does not pair the site with your running game. The countdown uses the published release instant and can format it in your browser's local timezone. That formatting is done in the browser; it is not a request for your home address or exact location. If a future public feature changes these boundaries, its actual collection behavior needs its own clear explanation.
5. Network and device request information
An ordinary web request can include an IP address, a requested path, timing information, browser headers, and information needed for secure transport. Some requests also include a referring page, depending on your browser and the site's referrer rules. IP addresses and similar metadata may relate to a person or household, but they are not reliable proof of an exact physical location or of who is using a shared device. The website does not treat an IP address as a verified personal identity.
Cloudflare serves the canonical website and executes its protected service requests. Firebase Hosting serves the marketing mirror. Their infrastructure can process delivery and security information beyond the fields that a BeamMDT form visibly asks for. Blocking an account form does not prevent the hosting provider from receiving the request that loads that form. Equally, the provider receiving a page request does not mean that the visitor's account password is placed into a public page log.
The application uses request-related information for safeguards such as limiting repeated account operations. The source contains protected rate counters, and the hosting services have their own operational systems. This policy does not promise that all requests are unlogged or that every log has an identical lifetime. Avoid putting passwords, full codes, or private records in page URLs: a URL can be copied, stored in browser history, or included in operational diagnostics more broadly than a protected form field.
6. Creating a Firebase-backed account
The connected customer sign-in flow uses an email address and password through Firebase Authentication. When you create an account, those credentials are sent to the authentication provider using its service connection. The website receives the account result needed to establish its own session. Authentication is separate from assigning an activation code: creating a Firebase account does not grant a mod download, a purchase, an administrator role, or an automatic license.
Account creation can be followed by website profile setup. The setup asks for a display name, a unit number, an optional picture, and acknowledgement of the account policies and fictional-simulation context. These details support the website's account presentation and protected feature gates. The service rejects submitted role changes or unsupported profile fields rather than using a customer form to grant administrator access. A profile field should contain the requested website information, not a real agency credential or another person's identifying record.
Use an email address that you control and can safely access for verification and recovery. A shared mailbox can expose account messages to anyone else with access to that mailbox. Choose a password you do not use elsewhere. The current website does not supply a separate vault for storing your other passwords, payment details, or identification documents. If you decide not to complete setup, do not assume that an authentication account already created with the provider has been deleted; account creation and profile completion are separate steps with separate records.
7. Password handling and sign-in credentials
In the current customer password flow, the browser submits your password to Firebase Authentication. BeamMDT's account-session endpoint accepts a short-lived authentication token rather than asking the application to store your plaintext password in its profile database. The profile fields are the display name, unit number, optional JPEG avatar, and agreement information. Code requests and administrator notes are also separate from password storage. Do not type a password into those free-text areas.
The page contains a password visibility control so you can check what you entered. Revealing the field changes what is visible on your screen; it does not convert the password into a public profile field. Anyone looking at the screen, a screen recording, or a remote-control session can still see a revealed password. The browser or a password manager may separately offer to remember credentials. That is a browser or password-manager choice, distinct from the site's Remember email option.
Temporary values can exist in the page while an authentication request is being prepared or completed. The sign-in flow clears sensitive form and token state when it resets or signs out, but this policy cannot control extensions, operating-system capture tools, browser crash recovery, or screenshots you create. Avoid using a shared or untrusted browser for an account you care about. If a page behaves unexpectedly, verify its address and stop before entering credentials into an unfamiliar form. A secure-looking card is not by itself evidence of a trusted destination.
8. Email verification and account status
Email verification establishes that the account holder can open a message sent to the account's email address and complete the provider's verification process. It does not verify a legal name, age, real employment, police status, ownership of a vehicle, or eligibility for every project feature. The website reads the provider's verification status and uses it as one requirement for protected customer flows. An unverified account can be shown instructions to verify before continuing.
Verification messages and their action links pass through your email provider as well as Firebase. Your email service can apply spam filtering, link checking, forwarding rules, and its own storage practices. An action link may contain a limited-purpose token. Treat that complete link as private: do not post it in a public chat, a bug screenshot, or a shared document. Opening the link on the intended website is different from sharing it with a person who asks to verify your account for you.
The website can provide resend and recheck controls where the connected flow supports them. A successful button click is not proof that a message reached your inbox; delivery can fail or be delayed. Check the recipient address, spam folders, and the result shown by the page. The provider account's verification status can change after the message is completed, and the website may require another check or renewed sign-in. This process does not subscribe you to a separate newsletter or publish the verified address on the public site.
9. Password reset and action links
The password-reset flow asks Firebase Authentication to send an account action message to the submitted email address where appropriate. A reset message enables the provider's recovery process; it does not give the project a new copy of the old password. The website's reset-action page accepts the provider's action code and a new password through the connected flow. Recovery depends on controlling the email account and satisfying the provider's checks, not on knowing a display name or unit number.
A page can use deliberately general wording after a reset request so the response does not become a convenient list of which email addresses have accounts. That wording should not be read as proof that a specific account exists or that an email was delivered. If you receive an unexpected reset email, avoid sharing the action link and check the account and your mailbox security. A reset request itself does not authorize another person to receive your profile, codes, or download access.
Email-action parameters belong to the recovery or verification operation and can be sensitive. The marketing mirror redirects account action routes to the canonical host while preserving the query needed for the intended operation. That transfer is not a public posting of the token, but browser history and copied URLs can still retain it. Clear private links from screenshots and support examples. The site does not currently offer a separate customer recovery promise based on real-world documents, an invented support phone number, or a guaranteed response deadline.
10. Authentication tokens in the browser
After authentication, the connected page can hold short-lived identity and refresh values in its JavaScript memory while it completes the account flow. The current client does not intentionally save those authentication values as a persistent local-storage login record. The account module uses in-memory authentication persistence. The dedicated sign-in flow also keeps its temporary values in page state. Reloading or leaving a page can clear that client state even while a valid server session remains available.
A token is a credential. It should not be pasted into a request message, copied into a public diagnostic report, or given to someone who claims to need it to inspect a layout problem. In-memory storage reduces one kind of persistence; it does not make tokens immune to a compromised browser, malicious extension, or code running with access to the page. The website's security controls and your device's security serve different roles.
The browser sends a token to the protected account service to establish a server session. The server also needs provider authentication material to validate protected work and, for certain customer database operations, to keep the provider's access rules authoritative. This means 'the browser keeps tokens in memory' is not a promise that no authentication material exists on the server. The important boundary is that these values are handled by the protected authentication/session service, rather than being placed in a public profile or saved as a convenient long-term browser preference.
11. The protected website session
Once the account service accepts authentication, it issues an opaque website-session cookie. The browser's cookie identifies a private server-side session record; it is not a readable copy of your password or the whole profile. The canonical deployment stores private session state in Cloudflare D1. The state includes the account identifier, an expiry time, recent-activity timing, role information needed for authorization, and protected authentication material used to verify requests. The raw browser-session value is represented by a hash in the database lookup.
The current session lifetime is thirty minutes. The server checks expiry and provider validation before authorizing protected requests. Session rotation replaces a prior session on the same host, and sign-out asks the server to remove the current record and clear its cookie. A browser tab remaining open does not entitle it to indefinite protected access. The interface may return to sign-in when an expiry or verification failure is detected.
Expiry is an authorization boundary, not a complete retention schedule for every kind of data. An expired session cannot be used as a valid login, but that fact does not prove when all infrastructure backups or diagnostic records are removed. The source deletes expired session records when they are encountered in protected requests; this notice does not invent an additional verified cleanup timetable. A saved profile and a pending code request are separate records. They are not erased merely because the session that created or viewed them has ended.
13. Display names and unit numbers
The website profile contains a display name and a unit number or callsign. These fields personalize account presentation and support the website's setup rules. A display name does not have to function as proof of a legal identity. Use a fictional or otherwise appropriate name that you are comfortable associating with the account. The current validation accepts a limited-length display name and rejects certain unsafe characters. It is not a real-name verification service.
The unit number is a short combination of letters, numbers, or hyphens, normalized to uppercase. The account service checks availability and enforces uniqueness in the private profile store so different accounts do not claim the same website callsign. An availability response reveals whether the submitted callsign is available; it does not supply another person's email address or full profile. Avoid repeatedly probing numbers to infer other users' identities.
Your account settings can update these profile fields once the relevant setup requirements are satisfied. A changed display name does not create a new provider identity or transfer assigned access to another account. A changed callsign is also separate from any number shown inside a downloaded game mod. The website does not promise automatic synchronization with a running game, a public roster, or an actual agency directory. A profile can be private to the website workflow even though the name you choose is recognizable to people who already know you.
14. Optional profile pictures
You can choose an optional profile picture during setup or through the existing account-settings flow. The current browser flow reads an image you deliberately select, prepares a square preview, and converts it to a small JPEG representation before submission. The preparation uses a canvas in your browser; selecting a file is not permission for the site to browse unrelated folders or upload your entire photo library. The protected service validates the submitted picture format and size.
The saved picture is still visual information. Cropping and resizing do not remove a face, a name badge, a house number, or other identifying content that remains visible. Use an image you are allowed to provide and that is suitable for the account context. A picture does not have to be a photograph of you. The default account artwork is available if you prefer not to supply a personal image. The site does not use this setup flow as a document-upload or identity-verification process.
Choosing the default picture in account settings prepares a request to remove the custom avatar when you save the change. The preview alone is not confirmation that a server update succeeded. Read the saved-state or error message before leaving. A successful replacement changes the active profile value; it does not guarantee that every previously cached image, screenshot, or service backup is immediately destroyed. Pictures you publish outside the website are controlled by those separate copies and services, not by this profile setting.
15. The recorded account-policy acknowledgement
Account setup requires acknowledgement of the website terms, privacy information, and fictional-simulation context. The profile service validates the required acknowledgements before it accepts setup. It records the applicable account-policy version and an agreement timestamp with the saved profile. The current backend account-policy identifier remains 2026-10-02. This page's October 10 explanatory expansion does not silently replace that identifier or rewrite the first agreement time.
The profile store preserves the original recorded agreement timestamp when a profile is updated or setup is repeated for the same account. A change to your picture or callsign is not a new acceptance event with an invented date. The visible acknowledgement boxes are part of the setup interaction, while the stored record is the profile's version and timestamp. This distinction matters when reviewing which account workflow was completed.
The agreement record is used to determine whether the account has completed the required website setup. It does not certify that you read every sentence, establish your legal name, or authorize arbitrary future data collection. Nor does acknowledging fictional gameplay mean that real information submitted in a message ceases to be personal. Read the current page before choosing what to provide. If the website introduces materially different processing, an explanatory document alone should not be mistaken for a newly implemented permission control or an updated historical consent record.
16. Where profiles are stored and displayed
The canonical website uses a private account database for its profiles. The record is associated with the provider's account identifier and includes the display name, unit number, optional avatar, policy version, and agreement time. The normal customer interface receives the limited profile information it needs for the current account, rather than exposing the complete database to every browser. The avatar is obtained through the protected account flow when it is needed for presentation.
The header, sign-in success card, setup flow, and account settings can show your account identity and profile state after authorization. Those screens are not a public profile directory. A person looking over your shoulder, using your unlocked browser, or viewing a screenshot can still see whatever the page displays. A protected server boundary and a private physical screen are separate considerations. Do not use public screen sharing while sensitive code or account details are visible.
Authorized administration and service maintenance can involve access to account records. That is a different permission boundary from a customer viewing their own settings. The current website does not provide a public toggle to make an entire profile anonymous to the service operator, because the service needs an account association to manage protected access. This policy also does not describe a public profile-search or real employment lookup feature. A future community feature would need a clear explanation of which profile fields become shared and how that sharing is chosen.
17. The account settings you can use today
The account settings page lets an eligible signed-in account edit its display name, unit number, and optional profile picture. The form displays the current account email and verification state for context. It does not turn a profile edit into an email-address change, a password reset, an account export, or a deletion request. The service rejects attempts to use this profile endpoint to change the account identifier, administrator role, or original agreement timestamp.
Changes are applied when the protected save request succeeds. Typing into a field or selecting an image can produce a local preview without saving the value to the server. If a session expires during editing, the form can stop and require another sign-in. If a callsign is already taken, the attempted update can be rejected. Check the result message instead of assuming that leaving a page completes a pending save.
These controls are useful but limited. There is no current self-service Delete account button or complete downloadable privacy export in this settings page. There is also no implemented switch that promises to disable all provider logs or remove an account from every backup. You can minimize the information in the editable profile fields and choose the default picture. For information outside those fields, consult the request and contact limitations described later in this policy rather than trying to place a deletion instruction into an unrelated code form.
18. The optional Remember email preference
The sign-in card offers a Remember email checkbox. When you choose it and supply a valid email address, the current script saves that address in the browser's local storage for the same website origin. On a later visit, it can refill the email field and reflect the remembered choice. The stored value is an email address, not a saved password or a server permission to grant access. A prefilled form still needs the authentication and session checks required by the service.
This preference is opt-in in the page flow. The script removes the remembered-email entry when the preference is not selected during its update. Browser storage controls can also remove it. Remembered data belongs to that browser profile and origin; it does not automatically follow you to another device, another browser, or every BeamMDT host. A shared browser can show the remembered address to another user who opens the sign-in page.
Use this option only when you are comfortable keeping the address on the device. Signing out ends the protected session but should not be assumed to erase every convenience preference. Check the checkbox and clear site storage if you want the browser to stop retaining the address. Private browsing and browser cleanup settings may clear local storage independently. If local storage is blocked, the sign-in flow can still work without this convenience, but the remembered address may not persist. The website does not intentionally use this local preference as a public account list.
The account chooser can show the account currently authenticated on this host and an email address already saved by the existing Remember email preference. A saved card helps you choose an address; it does not store a password, prove that you control the account, or authenticate you instantly. Selecting a saved email temporarily passes that choice through this tab's session storage to the sign-in page, which clears the temporary value after reading it. The chooser does not create a permanent library of profiles or passwords. Its remove control forgets the remembered address locally; removing an active account also signs out the current host. Choosing another account signs out the current host before returning to sign-in. Those actions do not promise to sign out accounts on every other hostname, browser, or device.
19. Appearance and local browser preferences
The appearance controls support light, dark, and system presentation. The selected mode is stored locally so the browser can apply the same appearance when you return. System mode can use your browser's reported color-scheme preference without asking for a personal identity. The scripts apply the preference early in page loading to reduce a visible theme change. This is a presentation setting, not a choice to expose or hide account records from the server.
Local preferences are origin-specific. The canonical site and a Firebase mirror can therefore remember different appearance choices in the same browser. A redirected account page may use the preference already saved for the canonical origin rather than the one from the mirror. Browser rules, extensions, storage blocking, or a cleared browser profile can change what is retained. The site treats storage errors as a reason to continue with a default presentation where possible.
Other local presentation state can exist where the current feature stores it, such as a remembered choice in a local demonstration. A browser preference should not be mistaken for a server transaction or a completed purchase. Clearing local storage can reset convenience settings, but it does not cancel an assigned activation code or erase a submitted request. Conversely, saving an appearance preference does not by itself create a Firebase account. To understand a particular feature, look at the actual control and whether it submits a protected request rather than assuming every click has the same privacy effect.
20. Clearing browser data and using shared devices
Your browser provides controls for cookies, local storage, cached files, browsing history, and sometimes saved form entries. These categories overlap in everyday language but have different effects. Removing the website's session cookie can stop that browser from presenting its previous session. Removing local storage can clear the remembered email and appearance choice. Clearing a cache can make the browser download fonts and images again. None of these actions is a direct command to erase the provider's account or the website's server records.
On a shared device, sign out before another person uses the same browser profile. Also consider whether the browser saved a password, whether a remembered email remains, and whether a sensitive page is still open in a restored tab. Closing a window is not a reliable substitute for checking those separate controls. The server session is time-limited, but an active session can remain usable during its valid period if another person controls the same browser.
Private or incognito browsing may reduce the local information retained after that browsing session ends. It does not conceal the network request from the service providing the page, and it does not make information submitted to a form disappear from server storage. Browser extensions and device administrators can have their own access. Choose a device and browser you trust, especially when viewing assigned access or administrative information. If a browser operation fails, avoid repeatedly sharing screenshots containing credentials while trying to troubleshoot what may simply be a blocked-storage or expired-session condition.
21. Requesting an activation code
The protected code-request flow allows a verified customer account to submit a request associated with its own account identifier and email address. The request includes a selected reason, an optional reference, a message, a pending status, and a server-supplied creation time. The current reasons distinguish new access, assignment, and replacement. This helps an administrator understand what you are asking for; it does not guarantee approval or constitute a purchase.
The request is stored in Firestore through the protected customer service. The current flow keeps one current request for the account rather than exposing an unrestricted general-purpose message archive. It limits the reference and message lengths and checks the account association before accepting a write. The request can be updated subject to the service's limits. A successful submission is different from an administrator reviewing it, assigning a code, or enabling a download.
Provide only the information needed to explain the access request. A short reference can help connect your request to an existing project interaction, but it should not contain a full payment-card number, password, identity document, or another person's private records. The message is visible to the authorized review workflow. A request-form label such as ticket does not turn it into a confidential medical, legal, or emergency-reporting channel. If you need to correct your current request, use the supported request page and check its result rather than submitting sensitive details repeatedly in different places.
22. Free-text messages and references
A free-text box can contain much more identifying information than the form actually needs. The site cannot make a message private from its intended reviewer simply because you added the word confidential. A code request may be read by an authorized administrator and handled within the project's access workflow. Before submitting, remove unrelated names, full access codes, credentials, real addresses, and personal records. Describe the request using the minimum details that let a reviewer understand it.
The reference field is a convenience for an existing interaction, not a request to upload an identity document or payment proof. If you refer to another person, choose a non-sensitive project reference and avoid sharing their private email or account details unless genuinely necessary for the legitimate request. A screenshot pasted into another service can expose more information than a short written explanation. The website's code-message form does not currently include a dedicated protected attachment-review system.
Free-text records can outlast the session used to submit them. They can also be included in administrative summaries or copied by a reviewer when resolving an issue. The current interface does not give you an automatic purge button for every copy of a message. Editing your current request changes the request state handled by the service; it is not a verified guarantee about prior backups or diagnostic traces. If you notice that you submitted a secret, treat the exposed credential itself as needing attention instead of relying on a later edit to undo every possible exposure.
23. Assigned codes and license-related records
Activation-code assignments are separate from the website profile. Protected Firestore records associate assigned access with an account identifier. A customer can query its own assignment records and obtain the related license information allowed by the service. The customer service checks the requesting identity and the assignment relationship instead of allowing arbitrary queries for other accounts. The fact that a collection has a name containing public does not mean every license record can be read by an unauthenticated visitor.
Your account page can show whether access is assigned and present the supported next action. An empty assignment list means the service has not returned an assignment for that account; it is not proof that another account with a similar display name has the same access. A display-name or callsign edit does not transfer an assignment. A server-side code record can contain access-management state and related operational details that are distinct from the personal profile fields you can edit yourself.
Treat any usable code, serial, download credential, or activation link as private. Showing one in a public screenshot can allow others to copy it even if the page itself requires sign-in. This policy does not promise that the website can recover or revoke every credential once it has been copied into an unrelated service. The protection boundary is the authorized website flow. Use the code-request process for a legitimate assignment or replacement request, and avoid including the full credential when a partial or non-sensitive reference will explain the issue.
24. Administrator access and role checks
The administrator workspace has a separate sign-in gate and server-side role checks. The current page uses a username-and-password proof for the administrator flow rather than making every ordinary customer account an administrator. Protected routes repeat authorization checks when data or files are requested. Hiding a button is not the only access control. A customer cannot grant itself administrator access by changing a display name, submitting a profile role field, or navigating to a familiar administrative URL.
Authorized administrators can review the operational records needed for code assignment, requests, recorded sales, recent website activity, and private beta administration. That access can include account-related information relevant to a request or assignment. It is a working administrative interface, not a public community feed. Screenshots from this workspace can contain other people's information even when no password is visible, so they should not be shared as routine public examples.
Administrator access also creates its own security context: authentication checks, session timing, protected requests, and provider processing can occur just as they do for a customer session. The site does not claim that administrators are invisible to hosting logs or that privileged access is an anonymous operation. If you use an authorized administrator account, keep the browser secure and verify the destination host. Do not share an administrator session, password, or token with a person who only needs to inspect public design or release information.
25. Private administrator notes
The administrator workspace includes a private draft-note feature stored through the protected Firestore service. The note can contain text deliberately entered by an authorized administrator and an update time set by the service. A separate protected administrator-profile record supports the workspace identity. These records are not the same as a customer's editable display name or the public credits page. The customer account interface does not provide general access to the administrator's draft.
A private note is a work area, not a safe place to accumulate unnecessary personal information. An administrator should keep notes relevant to the project task and avoid recording passwords, complete authentication links, real police information, or unrelated personal details. Naming a field private describes the access gate; it is not a promise that the text never reaches the database provider, service backups, or an authorized operator performing maintenance.
Changing a note updates the active draft handled by the service. The current site does not expose a customer control that can inspect or erase every administrator note mentioning that customer. This policy does not invent a separate retention schedule for the note store. If an operational concern involves an administrator's record, it needs to be considered through the actual project contact arrangements and the appropriate record boundary. Sending the same personal information again through a code request does not by itself resolve what is already in an administrative record.
26. Code logs, recorded sales, and operational summaries
The protected administrator service accesses code and log collections used for project operations. These can record changes or states related to access management and can support summaries shown in the workspace. The recorded-sales display derives amounts from available code records. Its values are administrative records, not a claim that the website has processed a bank payment, verified a payment receipt, or collected card details through a checkout.
A chart can summarize a period without becoming a new customer-data source. Selecting a range changes how the existing authorized data is presented. A summary may be limited by the records returned by the service, and a zero or incomplete total should not be used as proof that every relevant event is present. These displays are available behind the administrator gate; they are not published as a searchable list of customers.
The current public website does not have an open purchasing flow that asks you to enter payment-card information. Do not add card details to a code request in an attempt to create a purchase or establish a receipt. If payment-related features are introduced later, their actual provider, fields, and collection process will need a clear explanation. This policy does not make a promise that operational records are deleted when a chart range changes, when a code stops being active, or when a customer signs out. Record presentation and record retention are separate operations.
27. Recent website activity and active-user counts
The private session store includes recent-activity timing so the service can handle sessions and provide an administrative count of recent website accounts. The current count uses a recent window and deduplicates account identifiers rather than treating every tab as a different person. It excludes administrator sessions from the customer count. It is a measure of recent website sessions, not a live census of people playing BeamNG or using the mod.
An activity time can be updated when the protected service validates an existing session. A browser opening another tab or revisiting an account page may therefore affect session activity without any gameplay connection. The service can limit updates so every request does not require a new activity write. The count also depends on session validity and the query or store implementation. A dashboard number is not a verified attendance record or a reliable indicator of a particular person's physical presence.
Recent activity is associated with the account identifier within protected storage. It is not a public broadcast of your exact address, game location, or every action you take on your computer. Nevertheless, a timing record is account-related information and should not be described as completely anonymous. Expiry of the counting window changes whether a session contributes to the current number; it does not establish a universal deletion deadline for profiles, assignments, requests, or infrastructure records created during the same period.
28. Abuse prevention and request limits
The account service limits repeated operations such as establishing sessions, checking callsign availability, or saving profile information. Some limits use request IP information; others use an account identifier. The protected rate store represents its keys as hashes and keeps counters and timing needed to decide whether another request should be accepted. A hash is a technical representation for lookup, not proof that the underlying activity can never be related back to a request or account.
Limits help keep a small website service usable and reduce automated guessing, repeated writes, and other abusive request patterns. A limit response may tell you to wait before trying again. It does not mean that the website has verified you as malicious, and it is not a permanent account judgment. Shared networks can produce related request characteristics, so several people using the same connection may encounter a limit during a busy period.
Do not attempt to bypass a limit by cycling credentials, probing other account identifiers, or distributing a request across unrelated pages. If a legitimate action fails, wait as instructed and check the session and connection state. Security counters are separate from a public profile and from the request message you choose to submit. Their short request window is also distinct from a verified storage-purge schedule. The website uses these controls alongside provider security services, which can have their own request classification, network metadata, and operational records.
29. Private beta files and download access
The private beta library is restricted to authorized administrators in the current website flow. The file catalog describes available versions and artifacts, while the actual private objects are held outside public website assets in Cloudflare R2. Public release information is not itself a download permission. An unauthenticated visitor seeing a version number, a changelog, or a planned release date does not gain access to a private installer or ZIP.
When an authorized download is requested, the protected service can issue a limited-purpose ticket bound to the account and current session. The ticket has an expiry and is intended for a single successful use. The ticket store uses a hash for lookup and validates the binding when the download is redeemed. These checks support controlled file delivery. They are different from a permanent public share link or a code that can be posted to let anyone retrieve the same private object.
Downloading a file still creates normal network activity and can leave a copy in your browser's download history and on your device. A copied file can be shared outside the website after delivery, and this policy does not claim that the website controls every later copy. Keep access links and tickets out of screenshots and public messages. Download-related records can include the account association and ticket state needed to authorize delivery; their expiry should not be confused with deletion of the whole account, release catalog, or provider's operational logs.
30. The optional beta request form
The public demo and support pages link to an external Google Forms beta-request form. The current website presents that form as an optional access-request route. Opening the link takes you to the external form service rather than submitting every visible website field in the background. Review the destination address, the questions displayed there, and any account or privacy information supplied by that service before entering a response.
A response submitted to the form is separate from a protected website code request and separate from creating a Firebase account. Those flows may serve related project purposes, but they do not necessarily share the same record structure, access control, or deletion mechanism. An access request is also not a guaranteed support ticket, a purchase, a release reservation, or a promise that your message will receive a reply within a particular period.
The website does not ask you to upload credentials or identity documents through that external form as a way to resolve every account issue. Provide only the information the legitimate form needs and that you are comfortable sending through the external service. The form service can have its own sign-in state, network processing, retention, and response-owner controls. This notice does not assert a verified retention timetable for those external responses. If you do not want to use the external form, you can read public information without completing it; declining an optional form does not stop ordinary public browsing.
31. Firebase and Google services
BeamMDT currently uses Firebase Authentication for account identity, Firestore for protected code and administrative records, and Firebase Hosting for the public marketing mirror. These are separate services with different responsibilities. A visit to a mirrored public page does not, by itself, create a customer profile or submit a code request. A protected action can involve the identity provider and the canonical website service even when the public navigation began on a mirror.
Firebase's privacy and security information, last modified September 15, 2026, describes provider handling of authentication credentials, email addresses, IP addresses, and user-agent information for authentication and abuse prevention. It also describes Hosting request information and service-specific processing locations, security, and retention. Those descriptions belong to the provider; they are not a deletion schedule or a certification for BeamMDT.
The current BeamMDT password flow uses an email address and password. It does not ask you to supply a telephone number merely because Firebase supports telephone authentication elsewhere. Likewise, a service listed in Firebase's general documentation is not automatically enabled on this website. The current site should be assessed by the account and hosting features described here, rather than every product available from the provider.
Firebase account data and BeamMDT's separate profile and code records can refer to the same account identifier without being the same database entry. Correcting a display name through BeamMDT settings does not automatically change the provider's account email. A provider account operation also should not be assumed to erase every related request, assignment, or administrative record in another store.
If a problem concerns the BeamMDT application, start with the available information on support. Provider documentation can help explain an authentication or hosting feature, but it does not make the provider a substitute support desk for BeamMDT profiles, activation assignments, or private beta decisions. Do not send an account password to either channel in an ordinary message.
32. Cloudflare hosting and private storage
Cloudflare serves the canonical public website and the protected administrator and dashboard hosts. The account service uses private Cloudflare D1 storage for profiles, session records, rate-limit state, and download tickets. Private beta package files are held in Cloudflare R2. These roles explain why a request can be processed by Cloudflare even when the page content contains no externally embedded video, social widget, or advertisement.
Cloudflare's privacy policy explains its treatment of information associated with people interacting with customer websites, including information it processes to deliver and protect its services. It distinguishes Cloudflare's own activities from customer-controlled website content. Read that policy for the provider's practices; this BeamMDT page describes the application information and choices that the website currently implements.
Ordinary hosting requires processing the requested connection and response. Security and service operations can involve request metadata and technical events. The fact that account database access is private does not mean that the hosting provider receives no connection information. This policy therefore does not make a zero-logging claim, an anonymity guarantee, or a promise that every request-related copy exists only in one application table.
The server-side role checks govern access to protected BeamMDT routes, including code records and private packages. A public link, a package filename, or knowledge that a D1 table exists does not grant permission to read it. Authorization is evaluated separately from the general ability to open the public website. Storage administration and deployment access also remain separate from an ordinary customer account.
A visitor cannot select a storage region through the current account-settings interface. This page does not promise that all hosting, provider operations, or related processing remain in the visitor's country. If the location of processing is essential to your decision, review the relevant provider documentation and current support information before submitting information you are not comfortable placing in this hosted account service.
33. Website performance measurement
The deployed canonical website can include a Cloudflare performance beacon. A review of the live privacy-page response on October 10, 2026 found a script loaded from Cloudflare's static.cloudflareinsights.com service. That script is supplied through the hosting layer rather than the locally authored font or theme files. A local development preview or the Firebase mirror can therefore show a different set of network requests from a canonical production page.
Cloudflare's Web Analytics collection documentation describes browser navigation timing and page-performance metrics, with beacon reports sent to a Cloudflare reporting endpoint. Its setup documentation explains that certain hosting configurations can insert the script automatically. These are provider measurement functions, distinct from BeamMDT's protected account-session records and the administrator's recent-account count.
Performance measurement helps identify whether a page loads or responds poorly; an active-account count concerns eligible website sessions. Neither should be presented as a count of people currently driving in BeamNG, an exact count of unique human visitors, or proof that a particular customer read every paragraph. The displayed administrative metrics have the limitations explained in the relevant activity section above.
The current BeamMDT appearance control does not disable hosting measurement. Remember email also has no relationship to that beacon. There is no separate website analytics-consent or privacy-preferences dashboard in the present account-settings flow. Browser or network controls may block a provider script, but this page does not claim that doing so prevents every server-side hosting or security event.
Avoid putting private information into a URL to communicate it to support. Page paths and connection metadata can reach services that deliver or measure a page, independently of the protected message box. Use the intended account fields for an eligible account action, keep shared links free of credentials or sensitive parameters, and review provider documentation if you need details about its current reporting practices.
34. Fonts, site assets, and gameplay boundaries
The website's custom fonts, brand images, and locally published gameplay captures are served as website assets. Loading a font is a request for a file; it is not a request to publish your account profile. The current font files are hosted with the site rather than retrieved from a third-party font subscription whenever you open a page. Hosting services still process the file request in the ordinary way.
A gameplay capture displayed on a product page is published demonstration material. It does not give the website access to the contents of your game window, vehicle state, game saves, installed mods, microphone, or camera. The connected public pages do not upload your current BeamNG session simply because the product is a BeamNG modification. Website activity and gameplay activity are different categories.
Remote MDT is an optional full MDT interface on another laptop while the mod runs on the game computer. Its planned website interface and upcoming community features should be read according to their current status. A visual interface, sample roster, or planned feature is not evidence of a live connection to your simulation. This privacy description does not invent a gameplay location history, voice transcript archive, or community telemetry database for features that are not connected on the current website.
Optional AI, voice, or local bridge components supplied with a separate mod release may use other services when you choose to configure them. Their instructions, permissions, and provider policies must be evaluated for the specific version you use. Do not paste an AI-provider key into a website profile or activation request. The public website examples do not need that key to show their content.
Website AI chat and Groq
The optional homepage chat sends your question and a bounded selection of recent conversation messages to the BeamMDT server when you submit it. If the server has its Groq connection configured, it sends those messages together with published BeamMDT guide facts to Groq for an AI response. Simply viewing the page, editing an unsent message, or browsing a saved guide answer does not submit that text to Groq. The provider is not asked to access your account, activation assignments, private release catalog, or game.
The current chat keeps its conversation in the open page's memory. It does not save chat messages to browser storage or an account conversation archive. Clear chat removes the page's visible conversation and context; leaving or reloading the page starts a new conversation. These controls cannot recall a request already sent to the server or provider. Recent context is limited to eight messages, each under 1,200 characters and 6,000 characters combined. A response may be displayed in full while only a shorter bounded portion can be sent back as later context.
The application endpoint does not intentionally write message content into its database or application logs. It uses short-lived request-count information to limit abuse, and ordinary hosting and provider request metadata can still be processed. An administrator's Groq API key is kept on the server; visitors should never provide their own key, password, session proof, or full activation code in the chat. Use fictional examples and avoid submitting other people's personal records.
Groq describes its handling of customer inputs, outputs, usage metadata, and available data controls in Your Data in GroqCloud. Its customer-service processing is also described through its data processing addendum; its privacy notice explains the scope of its separate website and business-contact processing. This website does not promise that a particular Groq account data-control setting is enabled or that all provider and hosting metadata has zero retention.
If AI is unconfigured, unavailable, or rate limited, the chat displays that condition. A published-guide answer is labeled as a guide answer rather than a generated response. AI text can be inaccurate; it is a navigation aid, not a decision about your account or a command executed inside BeamNG. The website chat does not request microphone or camera access, upload attachments, or operate the mod.
External links can take you to a provider, form, documentation page, or another project. Once you open that destination, it receives its own ordinary connection information and applies its own practices. A link on BeamMDT does not mean the destination follows this policy. Check the address and the relevant privacy information before logging in, uploading an image, granting a permission, or submitting a message there.
35. Who can receive or access information
Information reaches the services required for the action you choose. Firebase receives authentication information for the connected account flow. The canonical account service receives the proof and profile information needed to establish and manage a website session. Cloudflare provides hosting and the private stores used by that service. Protected code requests and administrative records use the configured Firestore service. The external beta form is a separate destination.
Authorized project administrators can access the protected operational information their role permits, including code requests, assigned-code records, logs, and private notes. That access supports the current review and management features; it does not make the information public. A customer is limited to eligible information associated with its own account. Registering another ordinary account does not create administrator rights.
An operator with legitimate deployment or storage-administration access has a different technical role from a customer using the account page. Hosting and identity providers may also have access needed to operate their services under their applicable practices and terms. This page does not claim that data is inaccessible to everyone other than the person who typed it, or that application authorization replaces provider administration.
The current application does not provide a public directory of account emails, a customer advertising-audience export, or a social feed of submitted code-request messages. That describes implemented features rather than a broad legal promise about every conceivable future transaction or every provider's independent business. Any future feature that changes how information is presented or sent should be described before people rely on it.
Legal requirements, security investigations, or a properly authorized request may require a different assessment from routine account use. This policy does not specify an invented jurisdiction, agency relationship, or automatic disclosure process. It also does not authorize a visitor to demand someone else's information through a code request. Questions about a record should identify your own account and the issue without exposing another person's credentials or unnecessary personal details.
36. Retention, expiry, and removal are different
The current website has a defined operational lifetime for its protected session: 30 minutes. Expiry ends the session's ability to authorize requests. The service also handles explicit sign-out, session rotation, and expired records it encounters. Those operations concern website access. They do not mean that the Firebase account, profile, assigned codes, request history, or hosting events are deleted when the session timer ends.
Short-lived download tickets have their own validity and single-use checks. A ticket becoming unusable is not the same as removing the beta package from the private archive. A saved appearance preference or remembered email has a different lifecycle again: it remains in that browser's local storage until it is changed, removed by the relevant flow, or cleared through browser controls. It is not governed by the session cookie's timer.
The site does not currently publish one automatic deletion timetable for all profiles, Firestore requests, operational records, private notes, server logs, and provider copies. Do not assume that an inactive account is erased after a stated number of days, that a rejected request disappears immediately, or that editing a field removes every prior technical record. There is no account-settings button promising that result.
Provider retention, backup behavior, and application records must be considered separately. A provider's general documentation can describe its own handling after a properly initiated operation, but that does not establish that BeamMDT has initiated the operation for every related record. This policy does not offer a deadline for completing a manual removal request or a guarantee that backups and operational systems are erased simultaneously.
If you need information removed or corrected beyond the available profile controls, consult current support availability and the request guidance below. Identify the information and the intended change without sending the secret value itself. Until an appropriate request route and its handling are confirmed, clearing a browser, signing out, or abandoning an account should not be treated as a complete server-side deletion request.
37. Corrections, access questions, and privacy requests
You can make the profile changes actually offered by account settings. You can also change the local appearance choice, manage the Remember email option, sign out, and use your browser's site-data controls. These are useful controls with specific effects, explained above. They are not a general export, account-deletion, provider-retention, or consent-management system.
The current website does not have an automated Delete account control, downloadable privacy-data archive, or dedicated privacy-request form. The public support page describes which contact routes are available and which are still being finalized. It currently does not publish a support email, Discord server, or social contact account. The beta Google Form should not be treated as a promised privacy-request or support-ticket channel.
Applicable privacy rights can depend on the person, the information, and the governing law. This page does not limit rights that actually apply, and it does not represent that every listed right under every country's law applies to every visit. It also does not invent a local regulator, registered business address, or designated privacy officer. Where a legal right applies, its requirements need to be assessed for the actual request.
A useful correction or access question identifies the account you control, the category of information, and the problem. For example, asking about an outdated display name is different from asking whether a particular request message remains stored. Avoid submitting full activation codes, passwords, complete session links, or another person's records merely to explain what you want checked.
A provider may offer its own account, privacy, or support routes for matters within that provider's responsibility. Those routes do not automatically alter BeamMDT's separate profile or code data. Review the linked provider information for provider-specific questions, and use the project's published support information for the application. This page describes the current limits honestly rather than suggesting an unavailable self-service process already exists.
38. Verifying requests and communicating safely
Before changing or disclosing protected account information, an operator needs a reasonable basis to connect a request with the affected account. An email address mentioned in a message is not, on its own, proof that the sender controls it. The existing verified sign-in and protected account access help establish account context, but they are not a public invitation to send identity documents or secret credentials.
This website does not publish a general identity-document upload requirement for privacy requests. Do not send a driver's license, passport, real agency identification, financial statement, or similar document to a beta form or ordinary code-request box. If a future published support route asks for verification, confirm that the route is authentic and understand which information is actually needed before providing it.
A useful technical report can usually begin with the page address without private parameters, an approximate time, the visible nonsecret error, the browser type, and a description of what you expected. A screenshot can help explain layout or navigation, but first remove email addresses, revealed codes, private request messages, account-action links, and unnecessary identifying images. Cropping a screenshot is often safer than sharing the entire desktop.
A password-reset link, verification code, access code, or session value can enable an action even when it does not look like a traditional password. Treat those values as secrets. Do not place them into a support subject line, a public comment, a shared URL, or an image filename. A legitimate explanation of a failure does not require publishing the value that grants the access.
If you suspect that an account or browser has been exposed, use the available sign-out and provider password-recovery controls and review the current support information. The site does not currently offer a customer dashboard for remotely revoking every session on every host. This policy does not promise a particular incident-response deadline; it explains the controls you can use now and the information to avoid exposing while seeking help.
39. Children, fictional identities, and sensitive information
BeamMDT is an unofficial entertainment and simulation project. A fictional callsign, invented character name, and suitable generic avatar can serve the website profile without including real agency credentials or operational records. The fiction notice does not make a real email address or an identifiable profile image fictional; those remain information about the person who supplies them.
The current account form is not an age-verification system. This page does not claim that the website verifies every visitor's age, obtains parental permission through a connected workflow, or applies a newly invented minimum age. Any applicable requirements concerning children's information still need to be considered. A young person should involve a responsible adult when deciding whether to create an account, submit identifying information, or contact an external service.
Do not put a child's real full name, school, home address, daily movements, or identifiable picture into a demonstration profile, public screenshot, or code-request message. The site does not need that material to explain a mod-access request. The same principle applies to information about other people: choose details that support the action without revealing someone's personal circumstances unnecessarily.
The current website is not designed to receive medical information, official case files, financial credentials, government identification numbers, real dispatch records, or details of an emergency. Free-text fields and private administrative notes do not turn the project into a suitable storage location for those categories. Private access controls reduce ordinary exposure but do not establish a specialized confidential-records service.
If sensitive information was entered by mistake, avoid reproducing it in additional messages. Identify the affected field or request category and consult the available support information about correction or removal. The current settings controls can change supported profile fields, but this page does not promise that such a change automatically removes every server record or provider copy. In an actual emergency, use the appropriate real-world emergency service rather than this simulation project's website.
40. Policy updates and related information
This expanded website privacy information was updated on October 10, 2026. It explains the current application and its limits in greater detail. The date of this page is separate from the policy-version value stored during account setup. This editorial expansion does not itself overwrite an existing account's acceptance timestamp, create a new consent event, or claim that a person accepted new data uses by reading the page.
The connected setup service currently records its existing policy version, 2026-10-02. Keeping that value unchanged avoids silently representing an explanatory page edit as a new account acknowledgement. If a future implementation changes what must be acknowledged or introduces a materially different use of information, the account flow and public explanation should be reviewed together rather than treating this longer page as an automatic substitute.
Read the website terms for account-use conditions and the support page for the current project, installation, and contact information. Account settings shows the profile controls actually available to an eligible signed-in account. Linked provider documentation explains provider-specific practices; this page should not be read as changing their terms or granting controls their services do not provide.
A release announcement, new visual design, or animation does not by itself connect an upcoming gameplay feature to the website account database. Future account, payment, community, analytics, or remote-service features may need additional explanation before they are used. Check the current page when deciding to submit a new type of information instead of assuming that an older screenshot describes the latest flow.
The practical choices today are to browse public information without creating a profile, provide only the information needed for a chosen account action, use the existing profile and browser controls, keep access secrets private, and consult published support information for questions beyond those controls. This policy provides detail for making those choices; it does not invent an automated removal tool, an unpublished contact address, or a retention promise that the current website has not established.