Privacy Policy
Last updated: October 8, 2026
Privacy Policy
Effective date: October 8, 2026
This Privacy Policy explains how personal data is handled when you visit aerorival.app, create an AeroRival account, play games, participate in the community, read or contribute to the Blog, or contact us. It also covers the services used to operate the website and its application programming interface.
Some features are available only to signed-in members, verified accounts or users with particular permissions. Descriptions of optional features apply when those features are available and you use them. This policy is separate from our Terms of Use and Cookie Policy. Acknowledging this policy is not consent to every processing activity or to optional cookies.
1. Who is responsible for your personal data?
AeroRival is operated by NODE HUB S.R.L., a Romanian company registered under Trade Register number J2026038669006, tax identification number (CUI) 54895290, with its registered office at 33 Nae Leonard Street, Apartment 2, Galați, Galați County, Romania.
NODE HUB S.R.L. is the controller of the personal data described in this policy. You can contact us about privacy, your personal data or your rights at contact@aerorival.app or through https://aerorival.app/en/contact.
We have not appointed a Data Protection Officer (DPO). Please use the contact details above for privacy enquiries and requests.
2. What information do we process?
The information we process depends on how you use AeroRival.
Account and profile information
- Your email address, username, account identifier, email-verification status and account timestamps.
- Your password in hashed form, password-reset and email-change verification records, and authentication-token records. We do not store your account password as readable text.
- The display name and avatar you choose to provide, and your available interface and profile-visibility settings.
- Account roles, permissions and relevant account-administration or security events.
Authentication and technical information
- IP addresses, request times, browser or device information, and technical information associated with accessing and operating the service.
- Authentication-session records, including token identifiers, expiry and revocation information, IP addresses and a hash of the browser's user-agent information.
- Diagnostic and security records, such as request failures, rate-limit events and administrative actions. These records may contain identifiers or limited request context.
Games and game rooms
- Room identifiers, names, visibility, settings, memberships, invitations, membership roles and relevant join, leave and activity timestamps.
- Presence and availability information used to show whether a player is connected, ready or participating in a match.
- Online game state, including aircraft placements, coordinates, moves, turns, results, scores, wins, match history and leaderboard statistics.
- Game-room chat messages and their author and timing information.
- Email addresses supplied for invitations, the inviter's identity, invitation status, expiry and response information.
Community information
- Social posts and comments, discussion titles and replies, their language, media and attachments, and the metadata needed to display and manage them.
- Reactions, follows, bookmarks, mentions, subscriptions, selected solutions and read or seen states, where the relevant feature is available.
- Visibility choices, muted or blocked accounts, reports, moderation decisions, warnings, restrictions and appeals.
- Content identifiers, creation and edit times, and relevant publication, removal or moderation history.
Blog information
- Articles, language versions, drafts, media, editorial revisions, review and publication records, and the identities of authorised contributors or reviewers.
- Author names, biographies, avatars or links chosen for publication.
- Temporary preview links and their validity information, where preview access is used.
Support and correspondence
- Information you provide by email, through a contact channel or in a Support ticket, including messages, attachments and contact details.
- Ticket identifiers, categories, status, assignment, relevant timestamps and the information needed to investigate a request or complaint.
- Staff notes and associated audit records, accessible to authorised staff rather than other members.
Notifications and legal records
- Service notifications, their delivery and read status, and information necessary to send account, invitation, community or Support messages.
- Records identifying the version and language of legal documents acknowledged by your account, when acknowledgment occurred, and associated IP and browser information.
- If optional-cookie consent is offered, records of your choices, the applicable configuration or policy version, language and time, and a pseudonymous browser identifier. This consent record is separate from other technical logs.
Files and information stored on your device
- Uploaded files and their metadata, which can include filenames, type, size, dimensions, descriptions and information contained inside the file.
- Browser storage used for settings, local game progress or statistics, recent-room information and Blog-editor draft recovery.
Do not include passwords, identity documents, financial information, sensitive personal data or unnecessary information about other people in public posts, chat or attachments. Files and images can themselves contain identifying information or metadata; do not assume that every upload has all metadata removed.
3. Where does the information come from?
We receive information directly from you when you register, change settings, play, contribute content, send messages or contact us. The application and its infrastructure also generate records when you use the service.
Other members may provide information about you by inviting you to a room using your email address, mentioning you, replying to your content or submitting a report. Moderators may record information needed to investigate those interactions. An invitation recipient does not need an existing account for us to process the address supplied by the inviter.
Invitations are used to deliver and manage the requested invitation, not to add the recipient to a marketing list. Please use this feature only for people you reasonably expect to welcome the invitation. If an invitation or a report concerns you and you want information about its source or processing, contact us.
4. Why do we use the information, and on what legal basis?
We process personal data for the following purposes:
- Providing the service you request: creating and managing your account, authenticating you, running online games and rooms, recording results, displaying rankings, publishing content according to its visibility, and handling your service-related requests. Where necessary to provide the service under our Terms of Use, the basis is performance of a contract or steps taken at your request before entering into a contract.
- Operating community features: displaying contributions and interactions, notifying members of relevant activity and making permitted content available in their chosen language. Our interests include maintaining a usable multilingual community and supporting the interactions requested by members. Depending on the processing involved, the basis is performance of the requested service or our legitimate interests, taking account of contributors' and readers' rights.
- Protecting accounts and the community: preventing abuse, enforcing access controls, investigating reports, moderating content, responding to complaints and protecting the integrity of games. The basis is our legitimate interests in a safe, fair and reliable service and, where applicable, compliance with legal obligations.
- Maintaining and recovering the service: diagnosing problems, managing infrastructure, keeping proportionate operational records and making backups. The basis is our legitimate interests in security, continuity and availability.
- Meeting applicable obligations and handling rights or legal claims: responding to lawful requests, keeping necessary evidence and establishing, exercising or defending legal claims. The basis is a relevant legal obligation or our legitimate interests in handling and defending claims.
- Using optional technologies that require consent: the basis is your consent. You can change or withdraw it through the available settings without affecting processing that occurred before withdrawal.
For processing based on legitimate interests, you can object on grounds relating to your particular situation. We assess such requests against the purpose of the processing and the applicable legal requirements.
First-party font delivery is part of providing and maintaining the website.
5. Which information is required?
An email address, account credentials and the account information required by the registration form are needed to create and secure an account. Email verification is required for features that are restricted to verified members. Without this information, we cannot provide those account features.
Display-name customisation, an avatar, public contributions, uploaded media and many preferences are optional. Particular activities, such as sending an invitation or requesting Support, require the information necessary for that activity.
You can browse public pages without an account. This still involves technical processing needed to deliver and protect the website, including requests for locally hosted fonts and other site assets.
6. Who can see your information?
Your email address, account password and authentication tokens are not intended to be displayed to other members as profile information. Authorised staff and relevant service providers may process account information for the purposes explained in this policy.
Other users can see the identity you use in the relevant feature, such as your username, display name or avatar, together with information made available by that feature.
Community visibility
Public Blog articles, public discussions and publicly visible Social content or profiles may be accessible without signing in and may appear in search engines, feeds or sitemaps. Content restricted to members, followers or another permitted audience is served according to that feature's access rules. Privacy settings for one feature do not automatically make your identity or activity private in every other feature.
Games and chat
Authorised room participants can see the relevant membership, presence, game information and room chat. A game's hidden aircraft placements are not shown to an opponent while the rules require them to remain hidden. Game results, player identities and statistics may appear in account-accessible rankings or match history. Global rankings can include scores earned in private rooms; a private room does not make those scores private.
The game's "public room" designation concerns discovery and joining within the member service. It should not be confused with an unrestricted public webpage.
Support and moderation
Support conversations are available to the requesting user and authorised staff. A Support reply described as public means visible in that ticket to the requester, not published to the internet. Reports, staff notes and restrictions are accessible to authorised personnel as necessary; relevant information may be disclosed to affected parties when needed to handle a case.
Recipients of content can copy it, take screenshots or quote it. Search engines and other third parties may retain independently obtained copies. Changing visibility or removing content on AeroRival cannot automatically delete all such copies.
7. Automatic translations
When this feature is available, a signed-in reader with a verified email address can request an automatic translation of a Social post or comment, or a discussion or reply they are authorised to view. We do not automatically translate the entire feed.
The application sends the necessary text and language information to a LibreTranslate instance operated by us on the same server as AeroRival. When the source language is unknown, text may also be processed to detect its language. The request does not intentionally include the author's account credentials or a separate profile identity, but the text itself may contain personal data.
Our current translation server is hosted by Hetzner in Germany. This configuration does not send community translation requests to a public third-party translation API. The feature uses existing language models for translation; it does not train models on your community content.
We store the translated result, its source-content reference and fingerprint, languages, processing status and relevant timestamps so that authorised readers can reuse the result. Inactive translations become eligible for daily deletion after 90 days from their last access, or from creation if never accessed. Regularly accessed translations can remain longer. Edits invalidate the previous translation and access remains subject to the original content's availability and permissions.
Translations are labelled as automatic and can be inaccurate, including changes of meaning. The original remains available and is the reference for editing, moderation, reporting and search. This feature does not translate game-room chat or Support conversations. Blog language versions use a separate editorial workflow.
We protect the translation service's identified content logger against recording source text and translation output. This does not mean that all application or infrastructure logs contain no personal information. Backups, caches and operational records have separate retention rules.
8. Hosting, providers and other recipients
We use infrastructure and services necessary to operate AeroRival:
- Hosting and infrastructure: Hetzner hosts the application, database and self-managed translation service on our VPS in Germany and provides server backups and snapshots.
- Email delivery: We use Zoho Mail for service emails and correspondence. Our account uses Zoho's United States data region. Further information about Zoho Mail's data protection practices is available at https://www.zoho.com/mail/gdpr.html. Account, verification, reset, invitation and other service emails involve processing recipient addresses and the content required for delivery. Correspondence sent to our contact email may also be stored in our Zoho mailbox. Delivered messages may remain in the recipient's mailbox.
- Uploaded-file storage: we use Hetzner Object Storage in Helsinki, Finland, for uploaded files. These can include avatars, community media, Blog media and Support attachments. Public files may be served directly to browsers; access to restricted attachments follows the applicable application rules.
- Font delivery: we host the Inter font with the website and deliver it from the same website origin. Loading this font does not require your browser to contact Google Fonts. Requests for the font are handled by our website hosting infrastructure in the same way as other site assets.
Authorised administrators, moderators and support personnel access information according to their responsibilities. Providers acting on our behalf process information for the services they supply, subject to the applicable contractual and data-protection arrangements. External services may also act as separate controllers for their own processing.
We may disclose necessary information to professional advisers, competent authorities or other parties where required by law or needed to handle a dispute or protect rights. We do not sell personal data. Our use of service providers is not a sale of data.
Links to other websites, including links in member content, lead to services with their own policies. Opening them may disclose information directly to those services.
9. International processing
Our application and self-managed translation service are hosted in Germany, and our configured Hetzner Object Storage is located in Helsinki, Finland, within the European Economic Area. Server snapshots are kept in the same hosting location as the VPS. Our Zoho email account uses the United States data region, so email processing involves a recipient outside the EEA. These locations do not by themselves establish where every subprocessor processes data.
Where a transfer to a recipient outside the EEA occurs, it must have an applicable legal basis and transfer mechanism, such as a relevant adequacy decision or appropriate contractual safeguards. You can contact us for information about safeguards applicable to your data. This section does not mean that the location of every infrastructure copy is identical to the VPS location.
10. How long do we keep information?
We use retention periods or criteria appropriate to the purpose of each record. We consider whether your account or content is active, the feature's operation, the time needed to investigate issues, applicable legal obligations, security needs and any relevant limitation period or dispute.
- Account and profile information is generally kept while your account exists. Deletion is described in section 11.
- Game and community records are kept while needed to provide the feature, display permitted history or content, maintain fair rankings, or handle moderation and disputes. Removing a post from view is not always the same as immediately erasing every associated record.
- Blog publications and editorial history may remain while the publication and its revision history serve an editorial purpose. Removing an author's account does not automatically erase published articles or all author information appearing in them.
- Support information is kept while a request is being handled and afterwards for the period reasonably needed to resolve follow-up issues, document handling and address disputes.
- Notifications and technical or audit records are retained according to their purpose, whether they remain actionable or unread, and the need to investigate incidents. The system journal has a configured 90-day retention limit with a storage limit that can remove older archives sooner; this is not a universal 90-day rule for all logs.
- Automatic translations follow the 90-day inactivity rule described in section 7.
- Temporary authentication, verification and invitation records expire or are revoked according to their purpose. Expiry of a token does not necessarily mean immediate deletion of every associated audit record.
- Legal-document and consent evidence is kept only for as long as needed to demonstrate the relevant acknowledgment or choice, operate the preference or address a dispute, subject to the application's deletion behaviour.
- Browser-local data may remain until cleared through a feature's controls or your browser settings. Logging out or deleting your account does not necessarily clear local game information or editor drafts.
Backups are handled separately from the live application. Our local database-backup selection keeps snapshots covering the latest 14 distinct available days, 8 distinct available weeks and 12 distinct available months. Categories can overlap. This is a selection rule based on available backups, not a guarantee that every copy older than 12 calendar months is deleted.
Hetzner automatic server backups cover the latest seven days. Manual server snapshots and recovery copies on the operator's own computer are also maintained. Our configured retention policy for manual recovery copies is a rolling year; this is separate from the local database-backup selection rule. Access to the copies on the operator's computer is restricted to the operator. The infrastructure is recent and does not yet have a full year of backup history.
Backups can contain information removed from the live application. They are intended for recovery, not ordinary use of deleted account data. Erasure may therefore take longer in historical copies than in the live service. If data is restored, applicable erasure or restriction requests must be reapplied.
Where information is no longer needed, it should be deleted or irreversibly anonymised. Truly anonymous statistics that no longer identify a person may be retained separately.
11. Removing content and deleting your account
You can change available profile settings and use content-removal controls where the feature permits them. For erasure or other privacy requests not covered by those controls, contact us.
Account deletion is available through the account settings and requires confirmation of your current password. It removes the active account and revokes its authentication credentials, with related records handled according to their relationships and applicable retention rules.
Deletion does not guarantee immediate erasure of every reference in historical logs, backups, independently retained copies, quotations in someone else's content or editorial publications. Some removal actions hide content or change its status rather than physically deleting all associated records.
If you want personal information removed from an article, quotation, report or other retained material, identify it in your request so we can assess it separately. Where retention is necessary and lawful, we will explain the relevant reason rather than treating account deletion as unlimited authorisation to retain personal data.
12. Cookies and browser storage
We use cookies and similar browser technologies for authentication, preferences and the features you request.
A secure authentication-refresh cookie helps maintain and renew your session. In the documented configuration, choosing "Remember me" allows a persistent cookie with a rolling 30-day expiry after a successful renewal. Without that option, the browser cookie is a session cookie, while the server-side refresh record has its own expiry. Access tokens are kept in application memory rather than persistent browser storage.
Local storage can hold game preferences, saved local game progress and statistics, recent-room information, or a Blog-editor recovery draft. Session storage can hold an interface preference. These records can persist independently of your server account and can be accessible to others using the same browser profile. Clear them before sharing a device if they contain information you do not want others to see.
Where optional-cookie consent is offered, a separate preference record remembers your choices. Optional analytics, advertising or embedded-media technologies, if introduced, will be described separately and offered on the applicable legal basis, including prior consent where required. Accepting the Terms or acknowledging this policy does not enable optional-cookie categories.
Blocking or clearing essential storage can prevent sign-in or affect saved game and editor functionality. The Cookie Policy provides complementary information. Requests to external services, where used, can involve personal-data processing even when a service does not set a cookie; the Inter font is hosted locally as described in section 8.
13. Automated processing
Software validates moves, calculates scores and rankings, updates presence, detects languages, generates translations and applies technical restrictions such as rate limits. These operations are used to provide and protect the service.
We do not use the translation function to make moderation decisions or determine your legal rights. The original content remains the moderation reference. You can contact us or use an available appeal process to ask for review of a restriction.
AeroRival does not use solely automated decisions that produce legal effects or similarly significantly affect you within the meaning of Article 22 GDPR.
14. Your rights
Depending on the processing and applicable conditions, you can request access to your personal data, correction, erasure, restriction, or portability of data processed by automated means on consent or contract. You can object to processing based on legitimate interests and withdraw consent where processing relies on consent. These rights are not absolute.
Send requests to contact@aerorival.app. We may ask for proportionate information to confirm your identity or clarify the request. We will respond without undue delay and within one month. Where the law permits an extension because of the complexity or number of requests, we will notify you within that first month and explain the reason.
You can complain to the Romanian National Supervisory Authority for Personal Data Processing (ANSPDCP), https://www.dataprotection.ro/, or another competent supervisory authority. You do not need to contact us first.
15. Security
We use measures such as HTTPS, hashed passwords and refresh tokens, access controls, role-based permissions, request limits, backups and restricted administrative access to help protect information. Private support conversations and room chat are not end-to-end encrypted; authorised operators can access relevant information for service and safety purposes.
No system or transmission is completely secure. Use a strong, unique password, protect your email account and do not share authentication credentials or invitation and preview links. Report suspected misuse or security problems through our contact channel. If a personal-data breach occurs, we will assess and make any notifications required by applicable law.
16. Children and younger users
We recommend that minors use AeroRival with the knowledge and permission of a parent or legal guardian, and that parents help them understand privacy settings, public contributions and interactions with other users.
This recommendation does not replace parental authorisation where it is required by applicable law, including for processing based on a child's consent. It does not override legal rules concerning a minor's capacity to enter into a contract.
The registration system does not currently establish a user's age by collecting a date of birth, and we do not claim to operate a verified parental-consent process. If you are a parent or guardian with concerns about a child's account or personal information, contact us so we can investigate and take appropriate action.
17. Changes to this policy
We may update this policy when the service, providers, processing purposes or legal requirements change. The current policy is available on the website with its effective date. We will provide an appropriate notice of material changes and request a new acknowledgment or consent where necessary.
A new acknowledgment is not a replacement for consent where consent is legally required. Earlier versions may be retained to document the information provided at the relevant time.
For questions about this policy or your personal data, contact contact@aerorival.app.