1. Controller
Thomas Gewinner
Bachstraße 23
55569 Monzingen
Email: info@nexus-outpost.de
2. Hosting and Server Log Files
Nexus Outpost is operated via Einzelunternehmen Tom Gewiese (SKRIME), Obernaglbach 2, 94259 Kirchberg im Wald, Germanland, operated. When the service is accessed, technically required connection data such as IP address, time, requested URL, referrer, browser/device information and HTTP status may be processed in server log files. This serves secure and stable operation as well as error and abuse detection. The configured standard deletion period is 14 days, unless longer storage is required to investigate specific security incidents.
3. User Account and Game Operation
For registration and operation of the account, we process in particular commander name, email address, password hash, verification status, login times, game progress, resources, buildings, research and expeditions. This processing is required to provide the requested game and account service.
4. Persistent Login
If you enable “Keep me signed in”, a technically required remember-me cookie is set. Only a cryptographically secured token is stored server-side. You can revoke saved logins in the account settings.
5. Profiles, Avatars and Social Features
If you voluntarily provide an avatar, profile description, website or contact details, we process this information to display your commander profile. Contact details are shown publicly only if you enable the corresponding profile option. Friendships, alliances, roles, donations and chat messages are stored so the respective game features can function.
6. Contact Form
If you contact us through the contact form, we process in particular your name, email address, selected category, subject and message content in order to handle and answer your request. The information is not used for advertising. To prevent spam and abuse, the form is protected by Google reCAPTCHA if you have enabled the external security service.
7. Email Delivery
We use SMTP/PHPMailer for email verification, email changes and password recovery. The data required for delivery is transmitted to the configured mail server.
8. Google reCAPTCHA
Google reCAPTCHA v2 may be used on security-sensitive forms to make automated access and abuse more difficult. The external reCAPTCHA code is loaded only after you enable “External security services”. This may establish a connection to Google servers and process technical usage/device data. Without activation, the reCAPTCHA-protected action is unavailable.
9. Cookies, Local Storage and Consent
Technically required cookies or storage are used for sessions, login, security functions and storing your privacy choices. Optional external services are activated only after your selection. You can change your choice at any time via “Cookie Settings” in the footer.
10. Legal Bases
Depending on the processing, the relevant legal bases include in particular Art. 6(1)(b) GDPR for providing the account and game, Art. 6(1)(f) GDPR for security and abuse prevention, and Art. 6(1)(a) GDPR for consent-based external services. Section 25 TDDDG additionally applies to access to information on terminal devices.
11. Retention Period
Account and game information is generally stored for as long as your account exists and the data is required for the features. Security and reset tokens have short technical expiration periods. When an account is deleted, associated game data is generally deleted through the database relationships unless legal retention obligations or legitimate security purposes require otherwise.
12. Your Rights
Within the applicable legal framework, you have rights including access, rectification, erasure, restriction of processing, data portability and objection, as well as the right to withdraw consent with effect for the future. You also have the right to lodge a complaint with a competent data protection supervisory authority.
13. Data Security
Passwords are not stored in plain text. Nexus Outpost uses password hashes, CSRF protection, secure session cookies and token-based verification or recovery links. The web space should be operated exclusively over HTTPS.
14. Changes
This Privacy Policy will be updated when features, service providers used, or legal requirements change.
Last updated: August 11, 2026