1. Information we collect
We may collect account details, contact information, chosen monikers, verified affiliations and organization membership, organization access-list changes, subscription and transaction records, connected public wallet addresses, watchlists, alert and news-filter preferences, public or restricted-audience community posts, post categories and private tags, edits and reports, support messages, event or 1:1 engagement requests, early-access preferences, and technical logs such as device, browser, IP address, timestamps, and security events.
Mission requests can include coordinates, polygons, time windows, objectives, research categories, visibility choices, analysis instructions, and uploaded material. Avoid including personal or confidential information that is not needed for feasibility review.
Projects can include a creator and organization, objective and research question, public or restricted visibility, expected outputs, work needs, cost estimate, funding goal, milestones, exact participation terms, access grants, chosen participation roles, statements about how a member may help, non-binding funding-interest amounts, status, and versioned terms-acceptance evidence. Do not submit payment credentials, classified or export-controlled technical data, trade secrets, precise security details, or sensitive personal information through a Project card.
Launch-intelligence records may include time-stamped raw snapshots retrieved from Launch Library 2 (LL2) and other identified sources, normalized launch, vehicle, payload, organization, schedule, and status records, source links, retrieval and verification times, freshness indicators, and correction history. AI-assisted research may collect prompts, selected launch context, generated responses, citations, feedback, and safety records.
2. How we use information
We use information to operate and secure accounts; verify people, affiliations, membership entitlements, and organization access; personalize launch tracking, filters, and alerts; ingest, normalize, cache, correct, and attribute launch data; create, review, display, secure, moderate, and administer Projects and participation interest; operate AI-assisted research and display supporting citations; administer events and engagement requests; review policy and feasibility; route, quote, process, and deliver missions; maintain collection and access records; provide support; communicate consented updates; improve workflows; prevent abuse; and comply with legal obligations.
OrbitalSN public pages are intended to use stored launch records, not make a new LL2 or other upstream-source call for each visitor request. Raw snapshots and related provenance may be retained to detect changes, explain corrections, reproduce a prior state, and audit the data pipeline.
3. Visibility and sharing
Public community activity may expose a profile identifier, post, edit history, declared affiliation, and moderation label. A public Project may expose its objective, research question, estimates, funding goal, milestones, participant count, aggregate non-binding funding interest, terms, and intended outputs. A public mission request may expose its title, target description, approximate or exact geography, category, summary, status, and licensed output. Organization-only and private records are intended for their permitted users and operational processors, but are still accessible to authorized OrbitalSN personnel and vendors who need the information to provide or protect the service.
Restricted Projects, restricted-audience posts, private tags, and organization access lists are not a promise of legal privilege, guaranteed confidentiality, end-to-end encryption, or a controlled technical-data environment. Project managers and organization administrators may add or remove permitted users and thereby change who can view content. Authorized OrbitalSN personnel and processors may access restricted content to operate, secure, moderate, support, and comply with law. Do not submit classified, export-controlled, trade-secret, highly sensitive personal, or other restricted material unless a separately approved protected workflow expressly permits it.
We may share necessary data with cloud, authentication, analytics, payment, email, AI, imagery, launch-data, ground-segment, geospatial, moderation, event, compliance, and professional-service providers under appropriate agreements. We may link to external source pages. Linked sources receive information under their own privacy practices when you visit them. We may also disclose information to comply with law, protect people and systems, or complete an approved corporate transaction.
Third-party photographs, logos, video, and other media are not imported for public display unless rights and a lawful processing basis have been confirmed. Records can still include a source link and non-infringing factual metadata about unavailable media.
4. Blockchains and wallets
Public blockchains are independent permanent ledgers. A wallet address, token transfer, and smart-contract interaction may be visible globally and cannot generally be deleted by OrbitalSN. Do not connect a wallet if you do not want its public activity associated with your account.
5. Retention and security
We retain records for as long as needed for the purposes above, contractual commitments, source correction and provenance, moderation and appeals, event administration, dispute handling, fraud prevention, accounting, and law. This may include time-stamped raw launch-source snapshots, correction history, Project and participation history, exact accepted participation terms, organization and Project access changes, community edits, and AI safety records. Retention periods should be documented before production.
We use layered technical and organizational safeguards, but no service, transmission, AI provider, wallet, access list, or storage system is risk-free. Restricted-audience features are access controls, not end-to-end encrypted confidential communications.
6. Your choices and rights
You can unsubscribe from marketing using the link in those messages. Depending on your location, you may have rights to access, correct, delete, restrict, object to, or export certain personal information and to appeal a decision. Legal exceptions may apply, including for security, transaction, and immutable blockchain records.
7. Children, regions, and changes
The service is not intended for children under 13 or the higher minimum age required locally. International processing and transfer terms must be finalized before regional launch. We will post updates here and provide additional notice when required.
8. Contact
Privacy questions and requests can be directed to [email protected]. Identity verification may be required before a request is completed.
Before production, identify the legal entity and address, data controller/processor roles, vendor list, analytics and cookie behavior, retention schedule, regional rights, cross-border mechanisms, incident process, and privacy contact required by applicable law.
