Privacy Policy
Last updated: July 26, 2026
This Privacy Policy explains how Velarium Industries ("Velarium", "we", "us", or "our") collects, uses, and protects information when you use our website, member portal, and associated services (the "Service"). By using the Service, you consent to the practices described in this policy.
1. Information We Collect
When you authenticate and link accounts through the member portal, we collect only the information necessary to identify you and operate the Service:
- Discord account data: your Discord user ID, username, and avatar reference, obtained through Discord OAuth (the "identify", "guilds", and "guilds.join" scopes). If you grant it, we also store your Discord access and refresh tokens, encrypted at rest, so that we can add you to Discord servers you consent to join.
- Discord server membership: records of the Discord servers you are added to through the Service, and the list of servers your account belongs to (read through the "guilds" scope) to show which you can still join.
- Roblox account data: your Roblox user ID and username for your linked main account and, if provided, one alternate account, obtained through Roblox OAuth (the "openid" and "profile" scopes). We also display your public Roblox avatar image, which is served by Roblox.
- Google account data (optional): if you choose to link a Google account, your verified email address and Google account identifier, obtained through Google OAuth (the "openid" and "email" scopes). This is used to add you to Google Groups.
- Group membership: records of the Google Groups you are added to through the Service.
- Session data: a session identifier stored in a cookie to keep you logged in.
- Device and integrity data (Auspex): described in Section 2 below.
We do not collect your password for any third-party platform, payment information, or your precise location through the portal. A Google email is collected only if you choose to link one; it is optional.
2. Auspex: Device and Integrity Information
Auspex is our account-integrity system. It records characteristics of the device and browser you use to reach the member portal. It compares those characteristics between member identities to work out when two accounts belong to the same person. We use it to detect duplicate and alternate accounts, ban evasion, and cheating, and for nothing else.
Auspex does not operate inside our Roblox experiences. It collects nothing from your Roblox client, reads nothing from your Roblox profile, and does not use your play activity. The only Roblox information it holds is the Roblox user ID you yourself linked to your member account, which we use to apply moderation decisions. This is a deliberate limit set by Roblox's Creator Third-Party App Policy, which permits creators to identify players by user ID alone.
What Auspex collects from your browser:
- A device identifier: a random value we generate and store on your device in local storage, IndexedDB, and a first-party cookie. It contains no personal information and is only meaningful to us. Clearing all three removes it; we will generate a new one on your next visit.
- Browser and operating system details: user agent, browser build and version list, platform, architecture, and language settings.
- Display and hardware characteristics: screen resolution, available screen area, colour depth, pixel ratio, orientation, reported CPU core count, approximate device memory class, touch-point count, and the number of attached audio and video devices (counts only and never labels, and never their content).
- Rendering characteristics: a hash of how your device renders a reference image on a canvas, your graphics vendor and renderer strings, WebGL and WebGL2 capability values, and a hash of how your device processes a reference audio waveform. These are stored as one-way hashes, not as images or audio.
- Software environment: which fonts are installed, which media codecs and CSS features your browser supports, which speech-synthesis voices are present, the results of a set of standard mathematical operations, your time zone and UTC offset, and your available storage quota.
- Request characteristics: which headers your browser sends, in what order, whether it sends a referer, and your Accept-Language setting. This is stored as a one-way hash and describes your browser software, not you.
- Integrity flags: automated indicators such as browser-automation signatures, mismatches between the details your browser reports about itself, and anti-fingerprinting measures in use.
What Auspex does not do: Auspex does not record your IP address, your network, or your location, and does not attempt to determine where you are. It does not read your Roblox friends list, the groups you belong to, your Roblox account creation date, or any other part of your Roblox profile. It does not fingerprint the device you play on. It is not used for advertising, profiling for marketing, or tracking you across other websites. It does not read the contents of your files, screen, microphone, or camera. It does not use cache-based or other covert storage techniques designed to survive you clearing your browser data. We do not sell or share this data with third parties, other than the hosting provider that stores it on our behalf.
Activity timing: Auspex records when your portal visits start and end. If two accounts are frequently signed in to the portal at the same moment, Auspex treats that as evidence they are different people and lowers its confidence that they are linked. This is how shared computers and households are protected from being matched wrongly. If two accounts are each active regularly but never at the same time, that counts as weak supporting evidence that they may be the same person. Timing can never link two accounts on its own, and your Roblox play sessions are never used for this.
Account timing: Auspex compares the date your Discord account was created (which is derivable from your Discord user ID and requires no additional collection), the date you joined Velarium, and the dates of any moderation action, to identify accounts created in close succession or immediately after a ban. As with activity timing, this can never link two accounts on its own: timing evidence can raise confidence in a match already supported by device evidence, but can never create one by itself.
How it is used: Auspex compares these characteristics between member identities and produces a confidence score. Characteristics that turn out to be common across many members carry proportionally less weight, so widely shared traits cannot on their own connect unrelated people. Scores above a high threshold may result in a ban applied to one identity being extended automatically to identities matched to it, and may prevent a new member account from being created on a device tied to an active ban. All matches are visible to authorised staff for manual review, and a match can be dismissed by staff.
Basis: Auspex operates on every member account for as long as the account exists, and collection begins when you first reach the portal while signed in. It is a condition of holding a member account, not an optional feature, and there is no separate opt-in or opt-out. We describe it here and in the Terms of Service, which you accept when you create a member account, so that you can decide before you sign up. If you do not wish this data to be collected, do not create or keep a member account; you may still take part in our Discord community and Roblox experiences under those platforms' own terms.
Retention: Auspex observation records are deleted automatically after 12 months. Device records with no remaining links are deleted with them. Deleting your account deletes your Auspex records.
Your rights: you can request a copy of the Auspex records held about you, ask for a match to be reviewed, or object to a decision, using the contact route in Section 12.
3. How We Use Information
- To authenticate you and maintain your logged-in session;
- To link and display your connected Roblox, Discord, and Google accounts, including avatars;
- To add you to, and remove you from, Google Groups when authorized;
- To add you to Discord servers you consent to join, either from the portal or on acceptance of an application;
- To determine management permissions from your rank in the relevant Roblox group;
- To operate, maintain, and improve the Service and community features;
- To enforce our Terms of Service and prevent fraud or abuse, including detecting duplicate or unauthorized account links and rate-limiting Discord account changes;
- To operate Auspex, our account-integrity system, in order to detect alternate accounts, ban evasion, and cheating, and to apply moderation decisions consistently across the accounts of one person (see Section 2);
- To comply with legal obligations.
4. Legal Basis
Where applicable law (such as the GDPR) requires it, we process your information on the basis of your consent, which you provide by authorizing the OAuth connections, and our legitimate interest in operating a secure community service. For Auspex specifically, the device identifier is stored and read as a strictly necessary part of operating the member account you asked us to create, and we rely on our legitimate interest in preventing fraud, ban evasion, and cheating for the analysis of the resulting information. You may withdraw consent at any time by requesting account deletion (see Section 8).
Where Auspex produces an automated outcome, a cascaded ban or a blocked signup, you have the right to contest it and to have it reviewed by a person. Every automated outcome is recorded with the evidence behind it and is reversible by staff.
5. Third-Party Services
We use the following third parties to provide the Service. Their handling of data is governed by their own privacy policies:
- Discord: authentication, community, avatar images, and server membership management.
- Roblox: authentication, gameplay, group ranks, and avatar images.
- Google: optional email linking and Google Groups management.
- Railway: application hosting, database hosting for account and session records, and file storage for content uploaded through the portal.
6. Cookies and Device Storage
We use a strictly necessary session cookie to keep you authenticated. Disabling it will prevent you from logging into the portal.
While you are signed in we also store an Auspex device identifier on your device, in a first-party cookie, local storage, and IndexedDB (see Section 2). It is written by us, readable only by us, and used only for account integrity. Neither cookie tracks you across other websites, and neither is used for advertising.
7. Data Retention and Security
We retain your account and link records for as long as your account remains active. Auspex observation and portal activity-timing records are deleted automatically 12 months after they are recorded, and device records that are no longer linked to any identity are deleted with them. The values Auspex compares between accounts are stored as keyed one-way hashes, so the underlying characteristics cannot be reconstructed from them. The full device snapshot is additionally encrypted at rest with AES-256-GCM under a key held outside the database, and is readable only by authorised staff through the portal. Discord access and refresh tokens are encrypted at rest in the same way. The account details we need in order to operate the Service, meaning your Discord, Roblox, and Google identifiers and usernames, are stored in readable form. Data is transmitted over encrypted connections and stored with our hosting providers using industry-standard safeguards. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.
8. Your Rights
Depending on your jurisdiction, you may have the right to access, correct, or delete the personal information we hold about you, and to withdraw consent. To exercise these rights, including deletion of your account and linked data, contact us through the community Discord server. We will respond within a reasonable timeframe.
This includes the Auspex records held about you: the devices recorded against your identity, the links Auspex has drawn to other identities, and the evidence behind each. You may request a copy, contest a link, or ask for an automated outcome to be reviewed by a person.
9. Children's Privacy
The Service is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child under 13 has provided us with personal information, please contact us so we can delete it. Where required, children should only use the Service with parental or guardian consent.
10. International Users
Your information may be processed and stored in countries other than your own. By using the Service, you consent to the transfer of your information to facilities and service providers that may be located in jurisdictions with different data-protection laws than yours.
11. Changes to This Policy
We may update this Privacy Policy from time to time. Material changes will be indicated by updating the "Last updated" date above. Your continued use of the Service after changes take effect constitutes acceptance of the revised policy.
12. Contact
Questions about this Privacy Policy or your data may be directed to us through the community Discord server.