Privacy Policy

1. Who runs this site

The Service is operated by the [LoR] 21st Nova Corps unit leadership for use by members and applicants of the unit. For any privacy enquiries, contact 54xto on Discord.

2. What we collect

When you sign in or apply, we collect the following:

• From Discord (via OAuth), when you sign in: your Discord user ID, your Discord username/display name, and your membership of the unit’s Discord server. We request the scopes identify and guilds. A verified Discord account is required to sign in, enlist, and use the Service as a member.
• From Roblox (public APIs, or OAuth where available): your Roblox user ID, your current Roblox username, your public profile description (read once to confirm a one-time verification code you place there), and your membership in Roblox group 35826701 including which role you hold in that group.
• From your application: your CT identification (e.g. CT-#### “NAME”) and timezone.
• From your activity on the Service: events you host or attend, promotions you receive, awards issued to you, leave of absence records, and similar unit-administration entries created by yourself or your superiors.
• Technical data: session cookies, timestamps of logins, and standard server access logs.

3. How we use it

• To verify that you are a member of the Roblox group and the unit’s Discord server.
• To grant rank-gated access to roster, dossier, and command features.
• To maintain the Order of Battle, attendance records, and promotion history.
• To allow officers to review applications and manage the roster.
• Through our Discord bot, to set your server nickname, assign and remove roles based on your rank, unit, and medals, post event announcements, and record your event RSVPs.

We do not use your information for advertising, profiling beyond what is needed for unit administration, or any commercial purpose.

4. Where it is stored

Data is stored in a PostgreSQL database hosted on infrastructure controlled by the unit leadership. Cached lookups of Roblox group membership are kept briefly in a Redis cache (typically for up to five minutes) to reduce load on the Roblox API.

5. Who can see what

Access is controlled by an internal rank tier system:

• Public visitors see only public transmissions and these legal pages.
• Enlisted members see the full roster and their own dossier.
• Non-commissioned officers and above can view other troopers’ dossiers and log events.
• Commissioned officers and command staff can edit the roster, issue promotions, and approve applications.

We do not sell or rent your data. The Service calls the Roblox public API to look up group membership, and Discord’s API to verify your linked account and to manage your nickname and roles in the unit’s Discord server. Your in-game identification and Discord mention may be visible to other members in event announcements posted to that server. No other external services receive your data.

6. Retention

Active personnel records are retained while you remain a member of the Roblox group. Historical records (events you participated in, promotions received, citations issued) are kept indefinitely as part of the unit’s permanent archive. If you leave the group your dossier may be marked as discharged but historical entries that reference you will remain for continuity of the archive.

7. Your rights

You can request a copy of the data we hold about you, or request that your personal identifiers (Roblox username, timezone) be redacted from historical records, by contacting 54xto on Discord. Note that the Roblox user ID associated with historical actions may be retained for audit-trail integrity even after redaction.

8. Children

The Service follows Roblox’s own age requirements. We do not knowingly collect data from accounts that do not meet Roblox’s minimum age. If a parent or guardian believes their child has provided information to the Service, contact 54xto on Discord and the record will be removed.

9. Changes

This policy may be updated as the Service evolves. The effective date at the top of this page indicates when the current version took effect. Substantive changes will be announced in unit channels.