Privacy & account information
Effective 1 November 2026.
This notice covers the public tools, Odyn accounts and the private organization workspace. The separate Hangar Sync policy covers the browser extension and ship import service.
Public tools and browser storage
You can browse reference data, build loadouts and run public battles without an account. Public battle requests use a browser session and security tokens to keep runs separate and limit abuse. Requests reach the hosting and security providers with your IP address and ordinary connection information.
Ship Builder saves its current build and power settings in this browser’s local storage. Use its export controls to keep a file. These local preferences are separate from organization records and can be removed through your browser’s site-data controls. A loadout sent for fitting or acquisition calculations reaches Odyn even when you do not save an organization record.
Accounts and organization records
Discord sign-in supplies your Discord identifier and profile information, together with the membership information required by the configured connection. Onboarding can include your claimed organization membership, RSI handle and in-game name. Administrators review permissions separately.
Organization records can include roster details, ranks, units, approval notes, fleet and asset assignments, operation attendance, intelligence reports and uploaded evidence. What you can view or edit depends on the permissions assigned to your account.
Administrator-issued passwords are stored as salted password hashes. Sign-in sessions, provider credentials and authenticator records are protected separately. Do not send passwords, authentication codes or access tokens in public support messages.
Hangars and sharing
A scan sends structured ship model names, custom names and pledge-item identifiers to Odyn for a preview before the final import is confirmed. The import screen asks for acknowledgement before that transmission.
Private ships are visible to their owner and the site’s root administrator. Command sharing also permits authorized operation planners; Organization sharing permits authorized shared-fleet viewers. These settings do not make a hangar public. Member hangar access remains disabled during the private preview.
Security and service providers
Security records include IP addresses, approximate region information, request times, sign-in outcomes and administrator actions. They support account protection, access review, abuse prevention and troubleshooting. The application does not send each member’s IP address to an external location lookup service.
DigitalOcean hosts the service and its server storage. Cloudflare handles proxied web traffic, HTTPS and security filtering. Discord processes its own sign-in requests. RSI processes visits and hangar requests to its website. Patreon receives information when you visit its external support page. Each provider also applies its own policies.
The application does not include a third-party advertising or analytics script. Reference sources supply game data; they do not receive your private organization database through the public reference tools.
Retention and deletion
Completed battle history, results and dependent replay records expire after 12 hours and can be removed sooner for capacity. Named organization battle plans are separate saved records. An exported plan, result or comparison file stays wherever you choose to keep it.
Accounts, organization records, audit history and persistent sign-in security records do not all have automatic expiry. They remain until an authorized administrator removes or changes them, or a retention procedure is applied. Disabling an account does not erase its historical attribution.
Backups are separate from live records. The backup service does not automatically purge old snapshots, so deleting a live record does not immediately remove every backup copy. An administrator must review retained backups when handling a deletion request.
Requests and support
For access, correction, export or deletion requests, contact an Odyn administrator through Discord ↗ and ask for a private support route. Identify the account or record involved without posting credentials or private fleet exports publicly.
An administrator may need to confirm your identity and review records linked to other members, security investigations or organization history before acting on the request. This page does not promise automatic deletion of every connected record or backup.
Issue-report downloads include only the details you choose. Fleet configuration is excluded unless you explicitly select it. Review the file before sharing it.