Scope
This policy explains how AURA - CMDR Companion, VEIL - AURA CMDR Overlay, Xeno_X - StarGuide, Stellar Data Relay (SDR), and the website at aura-command.net access, use, store, and disclose information. These are independent companion projects and are not affiliated with or endorsed by Frontier Developments.
VEIL desktop data
VEIL reads locally generated Elite Dangerous journal, status, and navigation-route files to present navigation, ship-state, surface-context, critical-status, and data-health panels. VEIL processes this telemetry locally, does not request Frontier account credentials, and does not require Aura to be installed. Its Copy Diagnostics feature is designed to omit Commander identity, journal contents, and personal file paths.
Xeno_X desktop data
Xeno_X uses a bundled catalog of sourced Thargoid, Guardian, and Titan sites and may read supported local context to help search, project, and target a selected destination. It does not require a public Commander profile.
Stellar Data Relay
SDR reads supported local Elite Dangerous journal events, removes configured private Commander, group, crew, squadron, and carrier identity fields, and validates intended public community data locally. Dry run is the default. SDR transmits supported public telemetry to EDDN only when you explicitly enable live mode; its visible counters and payload preview are designed to make that state clear.
Information the desktop app accesses
When you choose to use the related features, Aura may access:
- Elite Dangerous journal files stored on your Windows PC, including Commander name, game events, systems visited, ship state, missions, routes, discoveries, inventory, and related gameplay telemetry.
- Preferences, Commander notes, mission or project information, and operational memory you create in Aura.
- Frontier account and Commander data returned through an optional Frontier authorization flow. Aura does not request or store your Frontier password.
- Technical information needed to operate the app, such as app version, provider status, and local error or runtime logs.
How desktop information is used and stored
Aura uses this information to provide live context, Commander status, route and exploration intelligence, mission support, recommendations, and personalized local memory. Journal processing and Commander memory are designed to run locally. Persistent Aura data is stored in the current Windows user's local application-data area. Session-only Frontier access tokens are held in app memory by default and are not written to disk by Aura.
Aura does not sell personal information and does not operate an advertising profile or cloud-hosted Commander profile.
Optional external services
Aura connects to an external service only when needed for a related feature or when you choose to follow an external link:
- Frontier Developments: optional account authorization and Companion API features. Frontier receives the authorization request and information required to service it under Frontier's own privacy terms.
- Spansh and other game-data providers: system identifiers, system names, locations, or route queries may be sent to obtain public galaxy, station, or route information. Aura is designed not to send your local journal history or Commander notes with those lookups.
- Patreon: the optional "Support Aura on Patreon" link opens Patreon in your browser. All Aura features remain free. Patreon processes visits and any support transaction under its own policies.
- Microsoft Store: Microsoft processes Store installation, licensing, updates, and related diagnostics under Microsoft's privacy terms.
Network providers may receive standard connection information such as your IP address, request time, and user agent when your device contacts them.
Website and launch-list information
The Aura website does not use advertising cookies or behavioral analytics. If you join the launch list, we process your email address, consent time, and subscription status to send confirmation and release communications. The site uses Cloudflare for hosting, security, and abuse prevention and Resend for email delivery; those providers may process standard network, security, and delivery metadata.
Retention, access, and deletion
Desktop data remains on your device until you remove it, clear the applicable feature data, or uninstall Aura and delete its local application-data folder. You can disconnect optional providers by ending the session or revoking authorization with the provider. Launch-list records are retained while subscribed or as reasonably needed to honor an unsubscribe request and legal obligations.
To request access to or deletion of launch-list or support records controlled by Aura, email [email protected]. We may need to verify that the request relates to you. Aura cannot delete data controlled independently by Microsoft, Frontier, Patreon, Cloudflare, Resend, or another provider; requests for that data should be directed to the relevant provider.
Security and children
We use reasonable technical and organizational safeguards appropriate to the information processed. No storage or transmission method is completely secure. Aura is not directed to children and is intended for users who meet the age requirements for Elite Dangerous and the services they choose to connect.
Changes and contact
We may update this policy as Aura changes. The effective date above identifies the latest revision. Material changes will be posted at this URL. Questions can be sent to [email protected].