Hangar Sync privacy policy

Information processed

When you choose Read RSI hangar, the extension reads My Hangar pages from robertsspaceindustries.com using the RSI session already present in your browser. Page contents are parsed in browser memory. The structured result contains ship model names, assigned custom ship names, pledge-item identifiers used to match repeat imports, and counts of pages and pledge entries read. This list can reveal pledged inventory and is treated as account-linked information.

The helper checks the URLs of matching RSI and Odyn tabs to validate where it reads and returns data. It does not request the browser history API or collect a history of unrelated sites.

The helper does not ask for your RSI password or export RSI password text, cookie values, session tokens, raw RSI HTML, purchase prices, insurance or payment records to Odyn. Browser-managed cookies may accompany requests to RSI itself. Non-ship items and unapplied upgrades are excluded from the returned ship list. No payment or transaction history is extracted for import.

The connected Odyn service uses account identifiers and authenticated sign-in sessions. Its security records include source IP addresses and approximate location, request times and paths, and sign-in and import actions. These records support account protection, abuse prevention and import troubleshooting. The helper does not monitor unrelated clicks, keystrokes or browsing activity.

Transmission and use

The structured ship list returns to the Odyn page in your browser. The website submits that list over HTTPS to its authenticated import service to create a review preview. Odyn receives the structured list before you confirm the final import. Confirming the preview updates the selected authorized hangar.

The list is used for model matching, repeat-import matching and hangar management. Imported records can support fleet planning, event manifests and exports you request. Imported ships start with Private sharing. Sharing or exporting changes who can see the records according to the options you select.

An import is a user-supplied snapshot. It does not independently verify RSI identity or ownership and does not represent live in-game inventory. Loaners are not generated automatically.

The extension has no advertising or analytics component. Odyn does not sell imported information, use it for personalized advertising, use it to determine creditworthiness or use it for lending. Data use and transfers are limited to the disclosed hangar features and necessary operational, security or legal purposes.

Odyn's use of information handled by this extension follows the Chrome Web Store User Data Policy, including its Limited Use requirements.

Access and service providers

Every signed-in personal account can manage its own hangar. Private ships and notes are visible to their owner and the site’s root administrator. Approved Odyn members with assigned fleet permissions can see ships their owners share with the organization; planners can also see Command-shared ships. Shared fleet views withhold private notes and import source identifiers. Losing organization eligibility removes shared fleet access while retaining the account’s personal hangar.

Odyn uses DigitalOcean for hosting and backups and Cloudflare for HTTPS proxying and security. These providers process traffic or stored data as needed to operate the service. RSI processes requests to its own website under its policies. Google distributes the extension through the Chrome Web Store under its policies; the helper does not send your ship list to Google as an import destination.

Human access to extension-derived data is limited to your explicit consent for the specific data, necessary security investigations, applicable legal obligations, or aggregated and anonymized internal operations. Owner-selected sharing and fleet planning must remain consistent with the choices disclosed in the application.

Storage and retention

The extension does not use browser storage to keep a persistent copy of your fleet. Scan results exist in memory during the read and while the Odyn page holds the result.

Odyn stores an import preview in its database. It becomes unusable after 15 minutes. Expired preview rows are removed during later import-preview activity; expiration does not mean immediate deletion from every database or backup.

Confirmed hangar records remain until an authorized removal is performed. Retiring a ship preserves its record and operation history rather than deleting it. Audit summaries, security records and backups can retain related information. A deletion request may require handling both active records and their backup copies.

Isolated reviewer sessions

The publisher provides a separate, credential-protected review service at Hangar Sync Review. It is isolated from production organization records and accounts. Its credentials do not grant access to the organization backend.

A reviewer can run the bundled reader against fictional sample pledge pages without an RSI account, or explicitly read their own RSI hangar. Sample results are labeled as demonstration data. Both paths use the same snapshot validation and model-matching routines. This mode does not certify ownership.

Review sessions use a separate temporary session key held in page memory. Production cookies and authorization headers are stripped before requests reach the review service. No review ship list is written to disk or included in organization backups. Each sign-in starts its own empty temporary hangar.

Review sessions become inaccessible after at most two hours and are discarded on logout, service shutdown or periodic expiry cleanup. Preview choices expire after 15 minutes. A snapshot file that a reviewer chooses to export remains on their device until they remove it. Gateway security logs can retain request metadata as described above; review session keys are excluded from those logs.

Your choices and contact

Reads are initiated by you. You can decline the final import, edit supported hangar fields, export your hangar, change sharing, or disable or uninstall the extension. Removing the extension does not delete records already imported into Odyn.

For access, correction or deletion of stored import data, contact an Odyn administrator through the Odyn Discord and identify your Odyn account. Requests require account verification and a review of related event history, security records and backups. Do not post passwords, authentication codes, cookies, tokens, account pages or fleet exports in a public channel.

Odyn operates this extension and its connected import service at odyn.abysswakestudios.com. This page will be updated when data handling changes. The Chrome Web Store privacy-policy link will point to the current published version.