Privacy & data
ASRP uses the website to publish community information and live leadership. Operational credentials, private Discord metadata, and unrelated member information stay out of the browser.
Public website
Departments, Civilian Operations, Training, Media, Join, About, Map, Community, Standards, Privacy, and the public Nexus guide are normal public pages. Discord, Nexus, CAD/MDT, Instagram, TikTok, and YouTube are separate external systems when you follow their links.
The current public source does not include an advertising pixel, marketing-cookie framework, or third-party analytics SDK. Hosting and web-server systems may still maintain ordinary request and security logs needed to operate the site.
Opening Discord, Nexus, CAD/MDT, or an official social profile uses that service's own account, privacy, authentication, permission, and data practices. This public site does not replace those services' controls.
Public browsing does not create a separate ASRP website password. Nexus authentication is handled in Nexus, with Discord serving as the authoritative identity provider for that platform.
Live Discord leadership
The community Leadership page and department command sections are designed to read designated Discord roles through the server-side leadership API when production synchronization is configured. The browser never receives the Discord bot credential.
The production design uses a low-privilege website sync bot for leadership lookup. Its token belongs in a server environment secret and is not embedded in HTML or JavaScript.
The server keeps only the role membership and public display information needed to resolve configured leadership positions.
The public response contains position/status plus the public display name and avatar needed for the directory. It does not publish configured guild IDs, role IDs, email, Discord permission data, or unrelated account metadata.
A position is shown as Vacant only after the configured role is confirmed and a complete synchronized member snapshot contains no human holder. Failed or unresolved synchronization is shown as unavailable instead.
Browser fallback
The community leadership component and individual department-command components can retain their own last successful public snapshot in browser local storage for approximately one hour. This keeps a brief Discord/API interruption from immediately replacing useful public information with an empty directory.
The saved snapshot does not log you into ASRP, Discord, Nexus, CAD, or any department and cannot grant permissions.
If live synchronization fails and a saved snapshot is used, the interface identifies it as last-known data rather than representing it as a fresh live result.
Clearing local site data removes the saved public leadership snapshots. The next successful visit requests current public information again.
Common questions
The leadership JSON does not expose a dedicated user-ID field. A Discord-hosted avatar URL can contain identifiers required by Discord to serve that public avatar asset.
No. Permission values, email, guild IDs, configured role IDs, and unrelated member metadata are not part of the public leadership response.
The normal correction is to update the authorized Discord role assignment or website role mapping through ASRP leadership. The website should not be maintained as a second manual list of office holders.
Use the official ASRP Main support workflow. Do not post sensitive personal or account information into public channels.
Need help?
Privacy, access, account, or leadership-directory questions should use the current support workflow so they reach authorized community personnel.
