This English version is provided for your convenience. Only the German version is legally binding.
We are pleased that you are interested in OMSI Mod Hub. Protecting personal data is important to us. You can generally visit our website without actively providing personal data. However, when you use specific features of OMSI Mod Hub, we may need to process personal data required to provide those features. We obtain consent where consent is required for the relevant processing. The website currently uses only technically necessary cookies; no cookie banner for analytics or advertising purposes is used.
We handle personal data in accordance with applicable data protection laws. This Privacy Policy explains what data we process, why we process it, how long we retain it, and what rights you have.
We have implemented technical and organisational measures intended to protect personal data. Nevertheless, complete protection of data transmitted over the internet cannot be guaranteed.
This Privacy Policy is intended to describe our data processing in accordance with the General Data Protection Regulation (GDPR) and other applicable data protection laws. Where other laws apply, this policy should be interpreted in accordance with the relevant legal requirements.
For readability, gender-specific language is not used consistently throughout this policy. All terms apply equally to all genders.
This Privacy Policy uses terms from data protection law. The following definitions are intended to make the policy easier to understand.
Personal data means any information relating to an identified or identifiable natural person.
A data subject is an identified or identifiable natural person whose personal data is processed.
Processing means any operation performed on personal data, such as collection, recording, organisation, storage, alteration, retrieval, use, disclosure, restriction or erasure.
Restriction of processing means marking stored personal data with the aim of limiting its future processing.
Profiling means automated processing of personal data used to evaluate certain personal aspects of a natural person, such as preferences, interests, behaviour or location.
Pseudonymisation means processing personal data so that it can no longer be attributed to a specific person without additional information, provided that such additional information is kept separately and protected.
The controller is the natural or legal person or other body that determines the purposes and means of processing personal data.
A processor is a natural or legal person or other body that processes personal data on behalf of the controller.
A recipient is a natural or legal person, public authority, agency or other body to which personal data is disclosed.
A third party is a person or body other than the data subject, controller, processor or persons authorised to process personal data under the direct authority of the controller or processor.
Consent means a freely given, specific, informed and unambiguous indication of the data subject’s wishes by which they agree to the processing of their personal data.
The controller within the meaning of the GDPR and other applicable data protection laws is:
omsi-modhub — Tobias Schmidt
c/o Online-Impressum 11973
Europaring 90
53757 Sankt Augustin
Germany
Telephone: 04743/9501413
Email: kontakt@omsi-modhub.de
Website: www.omsi-modhub.de
Whenever the website is accessed, the server may automatically collect general technical data and information in server log files. This may include browser type and version, operating system, referrer URL, pages accessed, date and time of access, IP address, internet service provider and other data needed to protect against attacks on our information technology systems.
These data are generally not used by us to draw conclusions about individual visitors. They are processed to deliver the website, maintain its stability and security, and investigate security incidents.
The purpose of processing is to prevent threats and ensure IT security. The legal basis is Article 6(1)(f) GDPR. Our legitimate interest is protecting our information technology systems. Access logs are deleted no later than 14 days after collection, unless they exceptionally need to be retained longer to investigate a specific security incident or comply with a legal obligation.
If you contact us by email or through a contact option provided on the website, we process the information you provide to handle your request and, where necessary, to contact you again.
We process and store personal data for as long as necessary to achieve the purpose of processing, or for as long as required by applicable laws or regulations.
When the purpose no longer applies, a statutory retention period expires, or the legal basis for processing ceases to exist, personal data is routinely restricted or erased in accordance with applicable legal requirements.
You have the right to ask us to confirm whether personal data concerning you is being processed.
You have the right to obtain information about the personal data we store about you and to receive a copy of that data. This includes, where applicable, information about processing purposes, data categories, recipients, retention periods, your rights to rectification or erasure, your right to lodge a complaint, the source of data not collected directly from you, and information about automated decision-making.
You may also ask whether personal data has been transferred to a third country or international organisation and, where applicable, request information about the safeguards used.
You have the right to request the correction of inaccurate personal data and the completion of incomplete data.
You have the right to request the erasure of personal data where the conditions laid down in Article 17 GDPR are met, for example where the data is no longer necessary for the purposes for which it was collected, consent is withdrawn and no other legal basis applies, processing is unlawful, or erasure is required by law.
You may request restriction of processing where the conditions set out in Article 18 GDPR are met, for example while the accuracy of data is being checked or where you object to processing and the balancing of interests is still pending.
Where the legal requirements are met, you have the right to receive personal data you have provided to us in a structured, commonly used and machine-readable format and to transmit it to another controller.
You have the right to object, on grounds relating to your particular situation, to processing based on Article 6(1)(e) or (f) GDPR. We will stop processing unless we demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or the processing is needed for the establishment, exercise or defence of legal claims.
You have the right not to be subject to a decision based solely on automated processing, including profiling, where it produces legal effects concerning you or similarly significantly affects you, subject to the exceptions set out in Article 22 GDPR.
Where processing is based on consent, you may withdraw your consent at any time. Withdrawal does not affect the lawfulness of processing carried out before withdrawal.
To exercise these rights, please contact us using the contact details in Section 2.
Depending on how you use OMSI Mod Hub, we may process account data, profile data, content published by creators, session and security data, report and moderation data, watchlist and notification data, and communication data.
Recipients may include technical service providers used to operate and secure the website, as well as public authorities where disclosure is legally required.
Article 6(1)(a) GDPR applies where processing is based on consent. Article 6(1)(b) GDPR applies where processing is necessary to perform a contract with you or to take steps at your request before entering into a contract. Article 6(1)(c) GDPR applies where processing is necessary to comply with a legal obligation. Article 6(1)(d) GDPR may apply where processing is necessary to protect vital interests. Article 6(1)(e) GDPR applies where processing is necessary for a task carried out in the public interest or in the exercise of official authority. Article 6(1)(f) GDPR applies where processing is necessary for legitimate interests, provided those interests are not overridden by your interests or fundamental rights and freedoms.
Where we process personal data on the basis of Article 6(1)(f) GDPR, our legitimate interests include operating OMSI Mod Hub securely and reliably, preventing misuse, handling reports and ensuring compliance with the platform rules.
OMSI Mod Hub does not send newsletters or direct marketing emails. Emails are sent in response to relevant events, including account verification, password resets, account changes, account-deletion confirmations and moderation decisions. When a creator publishes a new version of a published project, users who have bookmarked it and enabled notifications may also receive a version-update email.
Personal data is retained for the applicable statutory retention period or, where no statutory period applies, for as long as necessary for the relevant purpose. Once the purpose has ceased and any applicable statutory retention periods have expired, the data is deleted unless another lawful basis requires further retention.
The following retention periods apply to OMSI Mod Hub:
These are the intended standard retention periods. If data must be retained longer in a specific case to comply with legal obligations or investigate a specific security incident, it will be retained only to the extent and for the period necessary.
Some personal data may be required by law or by a contractual arrangement. Certain data may also be necessary to enter into or perform a contract. If required data is not provided, we may be unable to provide the relevant service or enter into the relevant agreement. Where appropriate, we will explain whether providing the data is required and the consequences of not providing it.
We do not normally use automated decision-making or profiling that produces legal effects concerning users or similarly significantly affects them. If this changes, we will provide information as required by applicable law.
Where personal data is transferred to a country outside the European Economic Area, such transfers will be made in accordance with applicable data protection law. Depending on the circumstances, the transfer may rely on an adequacy decision or appropriate safeguards, such as standard contractual clauses. You may contact us to request further information about the safeguards applicable to a transfer.
You have the right to lodge a complaint with a data protection supervisory authority, in particular in the EU Member State of your habitual residence, place of work or the place of the alleged infringement, if you believe that the processing of your personal data infringes the GDPR.
You may register on OMSI Mod Hub and use the forms provided for the platform’s functions. The data processed depends on the fields in each form and the features described in this Privacy Policy. Data is processed to create and manage your account, provide requested features and protect against misuse.
In connection with registration and use of the website, we may also process IP addresses, dates and times, and other technical security data. This helps protect our information technology systems and prevent misuse. Where required by law, data may be disclosed to competent authorities.
Users can delete their own accounts. The data affected by deletion is described in Section 17 and is subject to the retention periods in Section 10. Further retention may be necessary where required by law or where data is needed for the establishment, exercise or defence of legal claims.
You may request access to your personal data and the correction of inaccurate data. Data will be erased upon request where no statutory obligation or other lawful reason prevents immediate erasure.
Hetzner Online GmbH provides hosting services and data-centre infrastructure. In connection with the hosting services used for OMSI Mod Hub, technical and usage data may be processed as necessary to provide and secure the infrastructure.
The service provider and potential recipient of relevant data is:
Hetzner Online GmbH
Industriestr. 25
91710 Gunzenhausen
Germany
The processing may be based on Article 6(1)(b) GDPR where necessary to perform the relevant service contract and Article 6(1)(f) GDPR where necessary to provide secure, reliable and efficient hosting.
We additionally use a Hetzner Storage Box for backups (location: Falkenstein, Germany). It stores copies of daily full database backups and uploaded images. Database backups may include account data, email addresses, password hashes, session data including IP addresses, reports, appeals, moderation and administration logs, rate-limit hashes, watchlists and emails awaiting delivery, including recipient addresses, codes and links. Transfers to the Storage Box are encrypted via SSH. Access is restricted to our own server using an SSH key; snapshots cannot be deleted from the server. The stored backup files are not additionally encrypted. The legal basis is Article 6(1)(f) GDPR; our legitimate interest is data security and the ability to restore the service. Retention periods are described in Section 10.
The retention criteria depend on the service relationship and any applicable statutory, contractual or technical retention requirements. Further information is available at https://www.hetzner.com.
When you create and use an OMSI Mod Hub account, we process the following data:
During registration, the email address is verified using a six-digit confirmation code. The code is valid for 15 minutes. Users must be at least 16 years old to create an account.
Two-factor authentication (2FA): Two-factor authentication is optional for regular accounts and mandatory for administrator accounts. When enabled, signing in requires a six-digit code generated by an authenticator app in addition to the password. Alternatively, one of ten single-use backup codes may be used. We store the authenticator app secret and backup codes in encrypted form, a flag indicating whether setup has been confirmed, a counter of incorrect codes, and an account flag indicating that two-factor authentication is enabled. After ten consecutive incorrect attempts, second-factor sign-in is blocked for 15 minutes. The authenticator app generates codes on the user’s device; no data is transmitted to the app provider for this purpose. The setup QR code is generated by our own server without an external service. Enabling two-factor authentication signs out all other logged-in devices. The legal basis is Article 6(1)(f) GDPR; our legitimate interest is protecting user accounts against unauthorised access and, for administrator accounts, protecting the platform.
Watchlist and version notifications: Signed-in users can bookmark projects in a private watchlist. Only the user can see their watchlist; creators and other visitors cannot see who bookmarked a project or how many users did so. The “Email me about new versions” preference is enabled by default, and a notice is displayed next to the bookmark button. Users can disable it at any time under Settings → Account → Email notifications or via the unsubscribe link in each version-update email. Unsubscribing does not remove bookmarks. The legal basis for providing these user-requested features is Article 6(1)(b) GDPR.
Users can delete their own accounts. Account deletion also removes the creator profile, projects, images and sessions, subject to the backup periods described in Section 10 and any applicable legal retention obligations.
Creators can publish a publicly visible profile containing a display name, description and website, as well as projects containing text, images, contributor information, versions and download links. This content is publicly accessible to website visitors and may be viewed, copied or redistributed by third parties.
Creators can link other published projects as requirements. The referenced project page may then show a “Required by” section linking to those public projects.
Uploaded images are re-encoded before they are made available. Image metadata, especially GPS or location data, is removed.
We use an SMTP mailbox provided by checkdomain GmbH, Lübeck, Germany to send emails. In connection with email delivery, the recipient’s email address, display name or username, and the content of the message may be processed or transmitted to the email service provider.
We do not send newsletters or marketing emails. Emails are triggered only by specific actions and may include:
Both two-factor authentication change notifications contain a link to account settings and recommend changing the password if the account holder did not make the change.
Version-update notifications: When a creator publishes a new version of a published project, verified account holders who bookmarked that project and have notifications enabled may receive an email. The creator does not receive notifications about their own project. The email includes the recipient’s name, project title, version number, an excerpt of up to 600 characters from the creator-written changelog, and a link to the project. At most one notification per project is sent within six hours. Each email includes an unsubscribe link containing the account ID and a signature. Visiting the unsubscribe page does not unsubscribe the user; they must click “Unsubscribe”. We also support one-click unsubscribe via List-Unsubscribe, which causes the recipient’s email provider to send a request to our server. Unsubscribing does not delete the watchlist. Emails do not include tracking pixels or click tracking. Messages are temporarily stored in an email queue; see Section 10 for retention periods.
OMSI Mod Hub currently uses only technically necessary cookies or browser-side storage values for login, registration and language settings. No cookies are used for analytics or advertising.
| Cookie | Purpose | Duration |
|---|---|---|
better-auth.session_token or, over HTTPS, __Secure-better-auth.session_token | Maintains the login session | 30 days; the duration is extended through use |
omh-pending-registration | Temporarily stores the email address and username between the two registration steps | 24 hours; deleted after confirmation |
NEXT_LOCALE | Stores the selected language | Until the browser is closed |
better-auth.two_factor or, over HTTPS, __Secure-better-auth.two_factor | Signed reference to the pending sign-in process between password entry and two-factor code verification; set only for accounts with two-factor authentication enabled | Up to 10 minutes; deleted after successful code verification |
For each login, the IP address and browser identifier (User-Agent) may be stored to manage sessions and help secure the account. Users can view these entries under “Logged-in devices” and log out individual devices or sessions. Entries are deleted upon logout or no later than 30 days.
To prevent automated requests and misuse, we apply rate limits using IP addresses, email addresses, usernames or account IDs, depending on the function. Our own rate limits use these keys:
Attempts are also limited per pending two-factor sign-in process. The key for this limit is a hash of the cookie value, rather than an IP-derived identifier.
Appeal submissions are limited to ten attempts per hour per hashed IP address. Our rate-limit data is deleted after 24 hours. Hashes are pseudonymised, not anonymous: IP addresses and potentially email addresses or usernames may be recoverable by systematic guessing. The authentication system may additionally process IP addresses in plain text for security purposes. The legal basis is Article 6(1)(f) GDPR; our legitimate interest is preventing abuse and protecting the service.
The six-hour limit of one version-update email per project uses only the project ID as its key, not an identifier derived from an individual user.
Visitors can report projects even without an account. A report includes a reason and may include optional free text. If a report is submitted by a logged-in user, it may be associated with that user’s account. Moderators may add internal notes to reports.
For suspended accounts, the reason for the suspension and its expiry date may be stored. We also log which account performed a moderation or administrative action; these log entries contain the relevant account IDs. The retention periods for reports and log entries are set out in Section 10.
Admins can mark individual download links as broken or block them. We store the link status and a reason visible to the creator in the project editor. The reason is removed when an admin re-enables the link; for links marked as broken, it is also removed when the creator enters a new URL. Otherwise, the reason is retained for as long as the link exists. Changes are logged with the admin account ID, previous and new status, and reason for twelve months. Project category changes are also logged with the admin account ID for twelve months.
We also log enabling and disabling two-factor authentication and generating new backup codes, each with the relevant account ID. When a creator deletes a project, we log the account ID, project address (slug), project title and last project status. If an administrator disables two-factor authentication in an emergency through the server command line, the event is logged without an administrator account ID. These account-security and project-deletion logs are retained for twelve months.
When an external download link is clicked, we count the click only. The click count is recorded without storing the IP address and without linking the click to an identifiable person. After clicking, users are redirected to the relevant external provider’s website. The provider’s own privacy policy applies to its processing of personal data on that website.
Fonts are served from our own server. As currently implemented, we do not use analytics tools or directly embed external content, such as third-party videos or comparable third-party content, into the website.
To protect against automated bulk requests, spam registrations, abusive login attempts and unwanted project reports, we use the open-source software Cap (https://trycap.dev/de). Cap is hosted entirely on our own server as part of the OMSI Mod Hub application. No external CAPTCHA provider is involved in the verification, and no data is transmitted to the software provider for this purpose.
Cap is used for registration (including correction of the email address), login, the “Forgot password” function and project reports. When a protected form is submitted, the browser requests a computational challenge from our server without transmitting the form contents. The challenge is solved locally using JavaScript and WebAssembly. The solution is sent to our server; following successful verification, a single-use token valid for five minutes is issued. The token is checked and consumed when the form is submitted. The protected form cannot be submitted without a valid token.
Our Cap implementation does not use image puzzles, behavioural analysis or browser fingerprinting. The optional automated-browser detection feature is disabled. Cap does not set cookies or store data in Local Storage or Session Storage. The browser's CPU core count and language preference are read locally to distribute the computation and display the widget text, respectively, but are not transmitted to the server. All scripts and computational modules are served from our own domain.
For verification, random challenge values or signatures and SHA-256 hashes of one-time tokens are processed. These verification values are not linked to an individual by themselves; Cap does not store form contents. To enforce a limit of up to 30 requests per minute, we also process a SHA-256 hash of the IP address without a secret key, a request counter and a timestamp. The IP hash is pseudonymised, not anonymous. Standard technical server access logs may additionally contain the IP address, time, requested URL and browser identifier.
The legal basis for processing personal data is Article 6(1)(f) GDPR. Our legitimate interest is to protect the website and user accounts against automated abuse and to ensure IT security.
Redeemed challenges expire within ten minutes and are removed by the next daily cleanup (04:15), no later than approximately 24 hours. Used one-time tokens are deleted immediately. Unused tokens expire after five minutes and are removed during the next cleanup, no later than approximately 24 hours. IP-based request counters are deleted after 24 hours, and server access logs no later than 14 days. Data may remain temporarily in backups as described in Section 10.
Without JavaScript, the four Cap-protected forms cannot be submitted. Other pages and forms are unaffected.
Creators may appeal a decision to hide or reject their project. Account suspensions and dismissed project reports are excluded from this process. Appeals are decided by a human reviewer, not solely by an automated system.
The email notifying the creator that a project has been hidden or rejected includes a secret link valid for six months. The creator can use this link once, without logging in, to submit a reasoned appeal. For the original moderation decision, we store the decision type (hidden or rejected), affected project, moderation reason, decision timestamp and appeal deadline. Only a SHA-256 hash of the secret link is stored; the link itself is sent in the email. When an appeal is submitted, we store the creator's explanation and submission timestamp. After review, we store the outcome (upheld or rejected), the reason, the deciding admin's account ID and the decision timestamp.
The moderation log records the submission of an appeal without an account ID and the appeal decision with the deciding admin's account ID. To prevent abuse, appeal submissions are limited to ten attempts per hour per IP address hashed with SHA-256 (see Section 22).
If no appeal is submitted, the associated data is deleted during the next daily cleanup after the six-month appeal period expires. Resolved appeals are deleted six months after the appeal decision; pending appeals remain stored until a decision is made. When the project or account is deleted, related appeal data is deleted immediately from the active system. Moderation log entries are generally retained for twelve months; backup retention periods are described in Section 10. The legal basis is Article 6(1)(f) GDPR, reflecting our legitimate interest in fair, traceable review of moderation decisions and preventing misuse.