Privacy Policy

Effective Date: 17 August 2026

Last Updated: 16 September 2026

Version: 1.3

Data Controller: Flint Tilley, trading as Voidworks Industries

Address: Rozenstraat 2, 7102 CB Winterswijk, the Netherlands

Contact: Flint.tilley@voidworks-Industries.com

1. Introduction and Scope

Voidworks Industries operates the mobile game Holovia, its online game features, Holovia challenge-sharing pages, and the Voidworks website. This Privacy Policy explains what information is collected, how it is used, when it is shared, how long it may be kept, and the choices and rights available to users.

Voidworks Industries determines the purposes and means of processing for data used to operate Holovia and is the data controller for that processing. Some advertising, analytics, app-store, and platform providers may also act as independent controllers for data they process under their own policies.

Using Holovia does not by itself constitute consent to every type of data processing. Holovia requests an age category first, then asks for optional in-app privacy choices where applicable. Google User Messaging Platform (UMP) handles advertising consent, notification permission is requested by the operating system only after you enable notifications, and Apple App Tracking Transparency (ATT) is shown separately on iOS after the relevant 16+ choices. Other processing is carried out to provide requested features, protect the Service, complete purchases, or pursue the purposes and legal bases described below.

2. Important Summary

• Players select “Under 16” or “16 or older.” Under-16 mode keeps online gameplay features unavailable and does not create a Firebase account or start optional Firebase Analytics, Crashlytics, attribution, or push-notification services.
• On supported Android releases, under-16 players may choose to watch restricted contextual rewarded ads for a revive or a Daily Streak increment. Under-16 mode does not use banner ads or forced interstitial ads. See Advertising and attribution.
• In app versions that include Usage Stats, under-16 players can separately choose whether to send limited, aggregate usage totals to our own statistics service. This choice does not create an account, enable online play, enable Crashlytics, or control the separate contextual rewarded-ad route. See Basic usage statistics.
• In 16+ online mode, a pseudonymous Firebase account and related identifiers may be created to support online features.
• Player-chosen display names, scores, and some challenge or lobby information may be visible to other players.
• Multiplayer, spectating, challenge, leaderboard, replay, notification, analytics, and diagnostic data may be transmitted to cloud services.
• Core progression such as coins, owned items, settings, and entitlements is primarily stored locally, but related scores, statistics, and online-feature data may also be stored online.
• Holovia uses advertising and attribution services, including Unity LevelPlay, Unity Ads, Google AdMob, and Tenjin.
• Voidworks Industries does not directly receive or store full payment-card information.
• Voidworks Industries does not sell personal data for money.

3. Information You Provide

Player Name

Holovia asks you to choose a player display name. The game may add a suffix or generate a related unique player name so players can be distinguished. The name is stored locally and may be uploaded to Firebase for leaderboards, challenges, multiplayer, notifications, and other online features. It may be shown publicly or to opponents and spectators.

Do not use your real name, email address, phone number, home address, school, or other identifying or sensitive information as your player name.

Age Category and Advertising Choice

Holovia asks whether the user is “Under 16” or “16 or older” and stores the selection locally without asking for a date of birth. If basic usage statistics are enabled, the selected broad age category is also included in those submissions. Under-16 mode blocks multiplayer, challenges, spectating, leaderboards, online replays and score uploads. Basic usage statistics are a separate, optional connection described below. Existing players may see the age request again when the privacy-state version changes.

Optional Privacy Choices

Where applicable, Holovia separately asks whether you allow “Help Improve Holovia” data and whether you allow “Share Crash Reports.” These choices are stored locally and can be reopened in Settings. Refused optional events are not queued for later transmission.

Notification Preferences

If you enable notifications, Holovia processes your notification settings and may store related information such as language, platform, app version, daily-mission status, and streak timing. Holovia does not request notification permission or upload an FCM token at startup. A token is used only after notification permission and the relevant in-game choice allow notifications. When notifications are disabled, Holovia deletes the local and server-side FCM token where available.

Support Communications

If you contact Voidworks Industries, we receive the information you choose to provide, such as your email address, player information, message, and any attached diagnostic material. Do not send information that is not needed to resolve your request.

4. Identifiers and Technical Information

Holovia and its service providers may process:

• A locally generated player UUID
• An anonymous Firebase Authentication user ID
• Firebase Cloud Messaging registration tokens, only when notifications are enabled
• Tenjin installation identifiers
• Advertising identifiers, such as Android Advertising ID or Apple IDFA, when available and permitted
• Other platform or device identifiers, such as an app-set or vendor identifier
• IP address and an approximate country or region inferred from technical information
• Device model, operating system, platform, language, locale, and time zone
• App version, build information, package identifier, and SDK version
• Network, tracking-permission, and limited-ad-tracking status
• Apple Game Center account information made available by Apple, such as the authenticated Game Center user name

Holovia does not request precise GPS location for these features. Advertising and service providers may derive an approximate location from an IP address or device settings.

5. Gameplay, Analytics, and Diagnostic Information

Information processed in connection with gameplay may include:

• Game mode, games played, session and run duration
• Scores, high scores, coins collected, and challenge or multiplayer results
• In-game grid position, movement, actions, dashes, flow state, wall state, and death context
• Performance information such as target, average, minimum, and maximum frame rate, render scale, low-frame-rate time, and hitch count
• Pause and quit information
• App opens, installs, attribution source, sessions, and interactions
• Crash reports, stack traces, startup logs, device state, app state, and related diagnostics

Firebase Analytics is optional and is started only after you allow “Help Improve Holovia.” Holovia does not queue analytics events after you refuse or withdraw that choice. Firebase Crashlytics is started only after you allow “Share Crash Reports” in the 16+ privacy flow and is used to diagnose crashes, startup failures, and stability problems. It is not started in under-16 mode. Advertising consent, ATT, and notification permission are separate choices and do not automatically grant these optional analytics or crash-reporting choices.

5.1 Basic Usage Statistics

In app versions that include Usage Stats, Holovia can send limited first-party usage totals to Voidworks Industries to understand how the game is used and improve its gameplay, tutorials, navigation and technical performance. The totals cover modes, sessions, round starts and outcomes, broad duration, score and frame-rate ranges, tutorial events, gameplay actions, death categories and opened features. Activity totals measure active installations playing supported rounds, not verified individuals.

Each submission contains a protocol version, a UTC date, the selected broad age group (under 16 or 16 and older), a random submission identifier and fixed counters. New submissions receive new identifiers; an identifier is reused only when retrying the same submission to avoid counting it twice. These submissions contain no player name, account identifier, advertising identifier, date of birth, precise location or permanent installation identifier. They are added to daily totals and are not joined to player profiles, used to build individual play histories, or used for advertising, attribution or messages encouraging an individual player to return.

Google Cloud receives the submissions on our behalf and adds them to daily totals in Cloud Firestore. Network delivery processes technical information such as IP addresses and HTTP headers. Our statistics handler does not write those details or individual submissions into the statistics database. Project-level request logging for this service is excluded from ordinary log storage. This does not mean that no technical personal data is processed by the hosting infrastructure; Google may also process service data under the terms described in section 8.

For under-16 players, the separate Usage Stats screen offers No and Yes before these counters are collected. That choice does not enable advertising, detailed analytics Crashlytics, or online gameplay and is not verified parental consent. The counters are aggregate daily totals and are not a crash-reporting or player-profile system. For players aged 16 and older, the existing Help Improve Holovia choice controls both detailed analytics and basic usage statistics; there is no additional Usage Stats prompt.

You can switch future collection off in Settings → Privacy & Data: under-16 players use Usage Stats; players aged 16 and older use Privacy Choices → Help Improve Holovia. Switching it off clears unsent counters and stops future collection through this route. Previously received totals cannot be linked to a player to remove that player's contribution separately. This does not limit rights concerning other information that we can identify as relating to you. Parents can contact us using section 22.

6. Local Save Data and Cloud-Connected Data

Core save data is primarily stored locally on the device. This may include coins, currency, skins, locker items, settings, preferences, missions, streaks, purchase entitlements, and general progress.

Some related information is transmitted to online services only when an online feature is available and used. This includes player names, identifiers, scores, games played, last-online timestamps, challenge and multiplayer information, notification data, analytics events, diagnostics, and race replays. Basic usage statistics may also be transmitted when the applicable Usage Stats or Help Improve Holovia choice permits them, including in under-16 mode as described in section 5.1. Therefore, not all gameplay-related information is stored only on the device.

Uninstalling Holovia, clearing app data, or resetting a device may permanently remove local save data. Uninstalling the app does not automatically delete data already stored in Firebase, analytics systems, advertising systems, platform services, or app-store records.

7. Online Features and Visibility to Other Players

Leaderboards

Leaderboards may display your player name, unique player name, score, and rank. Associated records may include your anonymous Firebase user ID, games played, app version, platform, and timestamps.

Challenges and Race Replays

Creating or joining a challenge may upload the creator and participant identifiers, player names, scores, mode, status, timestamps, reward or entry values, and a compressed race replay. A replay can contain a detailed timeline of in-game movement, actions, world state, and visual information needed to reproduce the run.

Public challenges and their player names, scores, and summaries may be visible to other users. Challenge codes can be shared through web links.

Multiplayer and Spectating

Multiplayer and spectating use cloud services to exchange lobby identifiers, player identifiers and names, readiness, connection presence, last-seen timestamps, live position, score, actions, wall and world state, selected visual or skin data, game-over state, results, and disconnect or timeout reports. This information is shared with the relevant opponent, spectator, and backend systems as required to provide the feature.

8. Firebase and Google Cloud Services

Holovia uses the following Firebase services provided by Google when required by the selected mode and feature:

• Firebase Authentication: creates and maintains a pseudonymous anonymous account and user ID for 16+ online features. Holovia uses anonymous authentication only, does not ask players for login credentials, and does not create this account in Under-16 or offline mode.
• Cloud Firestore: stores user profiles, display names, notification settings and tokens, leaderboards, statistics, challenges, lobbies, operation requests, results, ranks, and related metadata. Basic usage totals and temporary duplicate-submission receipts are stored separately from player profiles.
• Firebase Realtime Database: synchronizes live multiplayer, spectating, presence, movement, action, world-state, disconnect, and version-status data.
• Cloud Storage for Firebase: stores compressed challenge race-replay files in paths associated with a Firebase user ID.
• Cloud Functions for Firebase and Cloud Run: perform backend processing for multiplayer, results, leaderboards, notifications, rate limits, fraud prevention, version checks, authenticated data access and deletion requests, scheduled cleanup, and receipt and aggregation of basic usage statistics.
• Firebase Cloud Messaging: provides remote push notifications and issues a device/app registration token.
• Google Analytics for Firebase: records app, gameplay, device, and performance events only after “Help Improve Holovia” is allowed.
• Firebase Crashlytics: collects crash and diagnostic information only after “Share Crash Reports” is allowed in the 16+ privacy flow; it is not started in under-16 mode.
• Firebase Hosting: hosts Holovia challenge-sharing and app-link pages.

For customer data stored in Firebase backend services, Voidworks Industries generally acts as controller and Google generally acts as processor. Google may also process service data under its own terms and privacy policy.

More information is available from Firebase Privacy and Security, Firebase Data Processing and Security Terms, the Google Cloud Privacy Notice, and the Google Privacy Policy.

9. Advertising and Attribution

Holovia displays rewarded, interstitial, and banner advertisements. The current advertising and attribution integration includes:

• Unity LevelPlay mediation, including ironSource advertising services
• Unity Ads
• Google AdMob
• Tenjin mobile attribution

These services may process advertising or vendor identifiers, IP address, approximate country, device and app information, ad interactions, impressions, clicks, install source, app opens, tracking status, and fraud-prevention signals. Mediation providers may make an ad request available to advertising demand partners in order to fill it.

In regions where consent is required, Google UMP displays and records the advertising consent choices. Holovia requests ads and initializes LevelPlay only after UMP allows ad requests. The UMP message covers the configured mediation partners, including LevelPlay/ ironSource, Unity Ads, and Google AdMob. If personalized advertising is declined, ads may still be shown where permitted, and limited information may still be processed to deliver contextual ads, limit repetition, provide rewards, maintain security, and prevent fraud.

On supported Android releases, under-16 mode can offer only voluntary contextual rewarded ads for a revive or a Daily Streak increment. It does not show under-16 players banner ads or forced interstitial ads. Before this restricted route starts, Holovia marks the session as child-directed, requests non-personalized treatment, opts out of device-ID use through the available provider controls, applies a general-audience content limit, and selects the dedicated Under16Contextual mediation segment. The configured child route accepts only Unity Ads rewarded demand. Holovia blocks the ad for the launch if the reported network or segment does not match that route.

This restricted Android route starts Unity LevelPlay, Unity Ads and the Google Mobile Ads SDK only after the age category and child-directed settings are applied. These SDKs and their hosting infrastructure may still process technical information needed to deliver, secure and measure the contextual ad, such as IP address, approximate country, device and app information, ad availability, impressions, completion and fraud-prevention signals. The under-16 route does not start Tenjin, does not request ATT, and does not use Google UMP to ask the child for personalized-ad consent. Child advertising is currently disabled in the iOS release configuration.

On iOS, Holovia shows Apple's App Tracking Transparency prompt only after the relevant 16+ privacy choices and before requesting tracking access where the system requires it. Under-16 and offline mode do not start ATT. Outside the restricted Android child-ad route, under-16 and offline mode do not start advertising SDKs. Denying tracking permission limits access to the IDFA but does not necessarily stop all contextual advertising or processing based on non-advertising identifiers that is otherwise permitted.

Tenjin is connected only when advertising measurement is permitted. It may then be used to measure installs, app opens, and advertising attribution. Depending on device and permission settings, Tenjin may process an installation ID, advertising or vendor ID, IP address, app and SDK version, operating system, device model, locale, country, and tracking status. Tenjin is not started and attribution events are not sent in Under-16 or offline mode or after advertising measurement permission is refused.

See the Unity Game Player and App User Privacy Policy, Unity Privacy Policy, Google Advertising Policies, and the Tenjin Privacy Policy.

10. Notifications

Holovia can schedule local notifications on the device and can use Firebase Cloud Messaging for remote notifications after you enable them. Remote notifications may concern expiring streaks, daily missions, leaderboard changes, challenges, multiplayer, or important app updates.

Remote notifications require a Firebase Cloud Messaging token. The token and related metadata, such as platform, app version, update time, notification settings, language, and relevant streak or mission status, may be stored in Firestore. You can disable notification permission in your device settings or turn notifications off in Holovia. Disabling notifications removes the local token and requests deletion of the server-side token where available.

11. Platform Services and In-App Purchases

Holovia uses Unity In-App Purchasing to communicate with the Google Play Store and Apple App Store. Purchase options may include the Remove Ads Package and Supporter Package. Product identifiers, prices, order status, purchase status, and entitlement information may be processed by Unity and the relevant app store. In offline or Under-16 mode, online purchases are unavailable and Holovia must not initialize purchase or cloud services that are not needed for offline play.

Payments are completed by Google Play or Apple. Voidworks Industries does not directly process or store full credit-card or bank-account details. Local entitlement records are used to apply purchased benefits, and store records may be checked to restore or reconcile entitlements after a reinstall or device change.

On iOS, Apple Game Center may be used for authentication, displaying Game Center features, submitting high scores, and restoring high scores when that platform feature is enabled and allowed. It is not used in Under-16 or offline mode. Apple may provide Holovia with a Game Center user name and score information. Apple's processing is governed by the Apple Privacy Policy.

12. Website and Shared Links

The main Voidworks website is delivered through GitHub Pages. GitHub may process standard web-request information such as IP address, browser or device information, requested URL, date and time, and security logs. Review the GitHub General Privacy Statement.

Holovia challenge links and app-link landing pages may be delivered through Firebase Hosting. Opening a shared link may reveal the challenge code in the URL and may produce ordinary hosting request logs. If a link opens the Holovia app, the app may then request the associated challenge data from Firebase.

If you contact Voidworks Industries by email, your email provider and our email provider process the message and related delivery information under their own terms.

13. How Information Is Used

Information is used to:

• Create and maintain a pseudonymous online player identity
• Provide leaderboards, challenges, multiplayer, spectating, replay, sharing, and version-check features
• Synchronize gameplay and determine challenge or multiplayer results
• Send requested or permitted local and remote notifications
• Provide purchases, restore entitlements, and respond to transaction problems
• Display, measure, limit, and personalize advertising where permitted through the applicable consent flow
• Attribute installs and measure marketing performance only when advertising measurement is permitted
• Measure detailed gameplay, performance, stability and feature usage after “Help Improve Holovia” is allowed
• Use the separate basic usage statistics described in section 5.1 to improve the game, subject to the applicable in-app choice; these totals are not used for advertising, attribution or individual profiles
• Diagnose crashes, errors, connection failures, and other technical issues only after “Share Crash Reports” is allowed
• Prevent cheating, abuse, fraud, spam, duplicate requests, and unauthorized access
• Apply rate limits, enforce game rules, and maintain service integrity
• Respond to support, privacy, safety, and legal requests
• Comply with applicable law and platform requirements

14. Legal Bases for Processing

Depending on the feature, location, and applicable law, processing is based on one or more of the following:

• Performance of a contract or steps requested by you: providing gameplay, online features, purchases, restoration, and support.
• Consent: advertising choices collected by Google UMP, “Help Improve Holovia,” “Share Crash Reports,” Apple tracking permission, push-notification permission, and other processing where consent is legally required.
• Legitimate interests: operating and improving Holovia, basic service measurement, maintaining security and stability, preventing abuse and fraud, and protecting users and the Service, where those interests are not overridden by user rights.
• Legal obligations: retaining or disclosing information where required by law, tax, accounting, consumer-protection, platform, or valid legal-process requirements.
• Protection of vital interests or public interest: only where applicable in an exceptional safety or legal situation.

You may withdraw consent for future processing where consent is the legal basis. Withdrawal does not affect processing that occurred before withdrawal. Some core online features cannot function without the processing necessary to provide them.

For basic usage statistics, truly anonymous totals are not personal data. Related technical personal data requires a legal basis: our interest is limited to understanding and improving the operation of Holovia, subject to applicable law and the rights and interests of players, particularly children. A child's Usage Stats selection does not itself establish a legal basis or replace parental consent where that consent is required.

15. Sharing and Disclosure

Information may be disclosed to:

• Google and Firebase for cloud hosting, authentication, databases, storage, analytics, crash reporting, messaging, functions, advertising, and app-store services
• Unity and supported LevelPlay advertising partners for mediation, advertising, measurement, fraud prevention, and Unity IAP
• Tenjin and configured marketing partners for mobile attribution and campaign measurement
• Apple for App Store purchases, Game Center, platform services, and device permissions
• GitHub for website hosting and security
• Other players when a leaderboard, public challenge, multiplayer, spectating, or sharing feature requires it
• Professional advisers, authorities, courts, or other parties where reasonably necessary to establish, exercise, or defend legal claims, protect users, investigate abuse, or comply with law
• A successor or prospective successor in connection with a merger, acquisition, financing, reorganization, or sale of all or part of the business, subject to appropriate safeguards

Voidworks Industries does not sell personal data for money. Some privacy laws use broader definitions of “sale,” “sharing,” or “targeted advertising” that can include disclosures for personalized advertising. You may select non-personalized advertising and use device or provider privacy controls to limit that processing.

16. Data Retention

Information is retained only for as long as reasonably necessary for the purposes described in this policy, including service operation, security, dispute resolution, legal compliance, and enforcement. Current operational retention includes:

• Local save data remains until it is overwritten, reset, cleared, or removed with the app.
• Basic usage statistics use a local queue of at most four sealed submissions. Batches older than the previous UTC day are discarded when the app next processes the queue. If the app stays closed, local data remains until that processing occurs, collection is switched off, or app data is removed. Local choices and the marker used for daily counting remain until changed, replaced or cleared.
• Server-side basic usage receipts contain an expiry time and are keyed by a hash of the random submission identifier and date. They expire three days after the start of the submission's UTC day. Basic usage totals expire 90 days after that day's start. Automatic deletion is asynchronous.
• Multiplayer operation requests are generally configured to expire after approximately 24 hours.
• Live multiplayer lobbies and sessions are generally configured to expire after approximately 30 minutes, subject to asynchronous cleanup.
• Multiplayer result records are generally configured to expire after approximately 7 days.
• Challenge lobby records are generally configured to expire after approximately 7 days, subject to asynchronous cleanup.
• Pending notification-queue records may be kept for up to approximately 30 days; handled queue records are generally scheduled to expire sooner, commonly after approximately 3 days.
• Challenge replay files may remain until they are no longer needed for the challenge, integrity checks, dispute handling, maintenance cleanup, or a verified deletion request.
• User profile, notification-token, leaderboard, rank, and other aggregated game-statistic records may remain while the online service operates or until deletion is requested and legally permitted. The separate basic usage totals follow the 90-day expiry above.
• Support messages may be retained while needed to resolve the request and maintain reasonable business, safety, or legal records.
• Analytics, crash, attribution, advertising, app-store, and platform information is retained according to configured provider settings and the providers' applicable retention rules.

Deletion and expiration jobs are asynchronous, so data may remain for a limited period after its expiration time. Security logs, fraud-prevention records, legal records, and backups may be kept longer where reasonably necessary or legally required.

17. International Data Transfers

Voidworks Industries and its providers may process information outside your country, including in the United States and other countries where Google, Unity, Tenjin, Apple, GitHub, or their subprocessors operate. Data-protection laws in those countries may differ.

Where required, transfers are supported by measures such as adequacy decisions, Standard Contractual Clauses, the EU-US Data Privacy Framework where applicable, contractual protections, and provider security measures. Firebase Authentication is operated from United States data centers, while other Firebase services may use global infrastructure or selected cloud regions.

18. Data Security

Reasonable technical and organizational measures are used to protect information. These include authenticated access, Firebase security rules, restricted backend permissions, rate limits, validation, encrypted network transport, and provider security controls. Firebase services generally encrypt supported customer data in transit and at rest according to the service's documentation.

No transmission or storage system is completely secure. Voidworks Industries cannot guarantee absolute security. Users should avoid placing identifying or sensitive information in public player names or shared challenge content.

19. Your Rights and Choices

Depending on your location, you may have rights to:

• Request access to information associated with you
• Request correction of inaccurate information
• Request deletion of information
• Request a portable copy of certain information
• Object to or restrict certain processing
• Withdraw consent for future processing
• Opt out of certain personalized or targeted advertising
• Complain to the competent data-protection authority in your country
• Receive equal service and pricing where applicable law prohibits discrimination for exercising privacy rights

If Holovia is still installed, open Settings → Privacy & Data. Privacy & Data Request creates an authenticated ZIP copy of online account data associated with the current Firebase profile and includes stored replay files where available. The ZIP is prepared in app-private storage and is shared only through the destination selected in the device share window. Private staging exports older than approximately seven days may be removed automatically by Holovia.

The in-game Delete Account & Data control can be used to request deletion of the current online account and associated cloud data. For correction requests, former players, or anyone unable to use the in-game controls, visit the Holovia Privacy Request page or email Flint.tilley@voidworks-Industries.com. Include enough information to locate the relevant records, such as the player display name, unique player name, player ID shown in the app, platform, and an explanation of the request. Do not send Firebase authentication tokens, notification tokens, advertising identifiers, or unnecessary identity documents. We may need to verify that the request concerns your data before acting on it.

Because Holovia uses anonymous identifiers, some advertising, analytics, or diagnostic records may not be reasonably linkable to a request without a relevant device or provider identifier. Voidworks Industries will respond as required by applicable law and may retain limited information where a legal exception applies.

Players aged 16 and older can reopen Privacy Choices in Settings → Privacy & Data to change optional analytics and crash reporting. Help Improve Holovia also controls their basic usage statistics. Under-16 players use Usage Stats in the same menu to change their separate basic-statistics choice. Changes apply to future processing. Where supported, advertising choices can be reopened through the UMP privacy controls. You can manage notification permission and advertising identifiers in device settings. On iOS, tracking permission can be changed in the system's Privacy & Security settings. Privacy controls may also be available inside an advertisement or through the relevant provider.

20. Children and Younger Users

Holovia asks for an age category of “Under 16” or “16 or older.” When a user selects “Under 16,” Holovia does not create a Firebase account or start optional Firebase Analytics, crash reporting, Tenjin, push-notification or ATT services. On supported Android releases, the restricted contextual rewarded-ad route described in section 9 may start advertising SDKs after child-directed settings are applied. This route is currently disabled for under-16 users on iOS. Multiplayer, challenges, spectating, leaderboards, online replays and online score submission remain unavailable. In versions with Usage Stats, a separate choice can enable the limited statistics connection described in section 5.1. Under-16 mode is therefore not a promise of no network processing when Usage Stats or the supported contextual rewarded-ad route is enabled.

Holovia does not ask for a date of birth, real name, postal address, or direct contact details during normal gameplay. A public display name and pseudonymous online identifiers are requested only from 16+ players who choose to use online features. Under-16 players are not asked for an online username. Players who use online features must not use a real name or other identifying information as their player name.

A user who is below the age at which they can lawfully make privacy choices in their country should use Holovia only with the involvement and authorization of a parent or legal guardian where required. Parents or guardians who believe a child has provided personal information or who want to review or delete a child's information should contact Flint.tilley@voidworks-Industries.com.

21. Changes to This Policy

This Privacy Policy may be updated when Holovia, its service providers, or legal requirements change. Material changes will be posted on this website with a revised “Last Updated” date. Where required, an additional notice or new consent choice will be provided in the app.

22. Contact Us

For questions, complaints, privacy requests, or concerns about a child user's data, contact:

Flint Tilley, trading as Voidworks Industries
Rozenstraat 2
7102 CB Winterswijk
The Netherlands
Email: Flint.tilley@voidworks-Industries.com