← BACK TO STELLAROCK

STELLAROCK INDUSTRIES · OCTOBER 26, 2026

Privacy notice

Stellarock Industries is an independent, unofficial Star Citizen fan site. This notice explains the data used for Discord accounts, recruitment, member profiles, fleets and internal operations.

Discord accounts and sessions

Discord sign-in requests the identify scope. We receive your Discord User ID, username, display name (when provided), and avatar (when provided). Your Discord User ID is the permanent link to your Stellarock account; changing your names or avatar does not create a new account. A first sign-in creates a Pending Approval account without an Org rank or protected member access. Formal recruitment takes place through the RSI organization page. Authorized leadership reviews the existing website account and can approve it as an Org Member with a selected rank. Discord sign-in does not request or store your email address for approval, and we do not ask for your Discord password.

We store your website username, optional RSI handle, account status, rank, permissions, and sign-in dates. A secure, HTTP-only session cookie identifies your sign-in for up to 12 hours; a session also expires after about two hours without activity or when revoked at sign-out. If you select “Keep me signed in”, a separate secure, HTTP-only cookie can restore your sign-in on that device for up to 30 days. We store a hash of its random credential, rotate it when restoring a session, and check account and membership eligibility. It does not store your Discord password or access token. Signing out revokes remembered access on that device. Leave this option unchecked on shared devices. A temporary cookie protects the Discord sign-in redirect and expires after ten minutes.

Recruitment, fleets and activity

Formal applications are submitted on the RSI organization page rather than through a current website recruitment form. Historical website applications and reviews remain stored for authorized review, including submitted identity, availability, interests, introductions, reviewer messages and status history. Website account approval and rank/access changes are recorded separately.

Member fleet records include registered ships, ownership, crew preference and private notes. Public Fleet pages show aggregate composition; private fleet details are available according to member access rules. Account actions, member status, rank, permissions, bans and internal operations changes are recorded in audit history.

Website notifications record a remaining feature event, its recipient and when that recipient reads it. Obsolete commerce notifications are excluded from the active notification center and unread counts. Marking a notification read does not change the related record or audit history.

Stellarock Operations coordinates current Mining Service Requests and Order status between Discord and the website. The older marketplace and website request portal remain retired. Discord handles its own platform information under its privacy policy.

RSI hangar imports

Active Org members may upload a local JSON or CSV hangar export, or use the optional Stellarock bookmark, to preview and synchronize their pledged ships. The bookmark reads active pledge identifiers and current ship names on RSI in your browser. It does not read login cookies, passwords, prices, billing information or buybacks. Choosing Review on Stellarock transfers the minimal scan in a URL fragment, which is removed from the address bar on arrival and held in page memory. It is sent to our server only when you generate a preview; no fleet changes are applied until you confirm. Bookmark scans never remove missing ships. We do not request RSI usernames, passwords, session cookies, tokens or 2FA, and do not log into RSI. The complete raw upload is processed in memory and discarded after processing. We keep only the file fingerprint, format, counts, timestamps, minimal pledge and vehicle-slot identities, canonical ship links, review decisions and sync/audit history. We do not store purchase prices, melt values, insurance, giftability, billing details or private hangar images. Private pledge identifiers and import summaries are restricted to the member who owns that fleet. Public Fleet totals show ship classes and counts. Missing pledges are archived only through a reviewed complete-export sync; their history remains.

Older email records

The current Discord sign-in and member promotion flow does not need an email address. Historical accounts, member profiles, approval records, inventory activity, and any older bans may still contain an email address from the previous system. The legacy site sign-in can also provide an email address, which is used for that existing account and older access or ban records. We retain those fields while their links to existing accounts and history are reviewed; we do not use them to create a new Discord account or approve a new Org Member.

Manual order tracking

Members with Manage Order Tracker permission can record a buyer name, optional Discord or RSI handle, requested materials, quantities, rates, notes, payment totals and member contributions in the manual Order Tracker. These records are restricted to approved accounts with Manage Order Tracker permission. The order creator and authorized Order Tracker managers can edit them. Manual Contributors can be recorded as separate reusable tracking identities with an optional RSI/Discord name and private notes; they do not receive accounts, login or membership. Discord-only contributors may also be identified by immutable Discord User ID. Authorized staff can later link a Manual Contributor to a Stellarock website profile, retaining the identity links and recorded history. Display names alone are not used as permanent Discord identity keys. Item-level customer payment and contributor payout records include amounts, dates, status, acting account and correction history. Customer Rates used as contributor gross earnings, the transaction fee and any order-specific Org Bank deduction are snapshotted. Linked members can view their own payout/payment history and confirm receipt on their protected profile. Payout status notifications are delivered to the linked recipient; unlinked manual contributors do not receive website accounts or website payout notifications. Internal operational notes, customer-facing notes and member status notes remain separate. Authorized Order Tracker users can generate member-facing text and PNG status summaries from saved order data and choose to copy, download or share them. Status images are rendered from saved Order data. Authorized staff may deliver customer-facing status, invoice and receipt links or summaries through Stellarock Operations in Discord. Delivery records retain the Discord destinations and message IDs needed for coordination and retries. Saved visibility settings control whether the shared summaries include customer payment totals and member payout amounts. Completed orders and change history are retained with the accounts involved.

Invoices and receipts store customer-facing billing snapshots and retained revisions. Authorized order managers can create unpredictable share links, revoke or replace them, and optionally set expiry dates. Anyone holding an active link can view that customer document or download its PDF without signing in; it does not grant access to the internal Order Tracker. Share tokens are stored as hashes. Customer documents exclude contributor identities, member rates, net payouts, transfer fees, internal notes and audit data. Document branding images and configured RSI/Discord links are public-facing artwork/settings. Documents are marked noindex and omitted from the sitemap.

Stellarock Operations and Discord requests

Discord Mining Service Requests record the requester’s immutable Discord User ID, display-name snapshot, requested materials, quantities and request notes. A customer can use the Discord request flow without a website profile or Org membership. Authorized Discord staff controls use current Guild roles; those roles alone do not grant website Admin access. When an official Order is created, the website Order Tracker is authoritative and Discord displays coordinated request and Order status. Request, Order, channel, thread and message identifiers, staff actions and delivery/cleanup retry state are retained to coordinate that work.

Discord-only customers are excluded from the private Order Tracker. Customer-facing invoice, receipt and status delivery excludes internal contributor payouts, private operational notes and audit information according to the existing document and visibility controls. Active document share links can be opened by anyone holding the link, as described above. Discord messages and channel membership are also subject to Discord’s own platform controls.

Retired customer systems

The marketplace, checkout and customer-request portal are disabled. Historical customer accounts, inventory, orders, requests, contributions, payouts and their audit history remain stored for authorized archival review. Existing non-member accounts are classified as applicants, community users or legacy accounts using their recorded links. Ambiguous memberships are marked Needs review. This classification does not grant Org membership or create a new Discord identity.

Who can see it

Visitors can see recruitment pages, aggregate fleet information, permitted public profiles and the published Chain of Command. Members can choose whether their Discord username and RSI handle appear on their profile and the public roster. Approved Org Members can access their own profile, fleet and payouts. Admin and operational tools require the relevant effective permission. New Discord sign-ins create pending accounts with no Org rank or protected access until leadership approves them. Authorized staff can review recruitment, accounts, permissions and bans according to their roles. Formal applications now take place on RSI. Historical website applications remain stored for authorized review. Our hosting provider stores the site records and uploaded photos needed to operate the website. We do not sell account information or use it for advertising.

Retention and your choices

We keep account, inventory, activity, ban, request, and order records as needed for site operations, access decisions, history, and resolving disputes. Demotion or suspension preserves the account and its past requests, orders, contributions, and activity. We do not have an automatic self-service account deletion button.

To ask for access, correction, or deletion of your data, privately contact a site administrator through the Stellarock Discord server or the RSI organization page. Include your Discord identity and the specific record so we can verify and process your request. If you cannot access the server, use the org page to reach leadership. We will assess requests under applicable law and technical or record-keeping needs; we cannot delete copies controlled by Discord or RSI on your behalf. You may revoke the site’s Discord authorization from your Discord account settings, but that does not itself erase site records.

Updates

We will revise this notice if the features or data practices change. Check the date above for the latest published version. For site conduct and in-game request details, read the site terms.