Legal · Effective 2026-07-31

Privacy Policy

What we collect, how we use it, where it goes. The site is informational — we collect almost nothing beyond what you choose to send us through the contact form, and we sell or share nothing with third parties.

01

What we collect

Information you submit. When you fill out the contact form on the home page, the demo request page, or the investor inquiry page, we collect the fields you provide: name, email, company / organization, role / interest, and your message. Each submission is tagged with a source value that identifies which page generated it (home_demo_cta, demo_form, proposal_cta, investor_inquiry) so the inbound team can route it correctly.

Public dashboard data. The 2,000 debris objects rendered in the public tracker at /dashboard.html are synthetic seeded data generated internally, not personal data of any individual. The catalog covers LEO / MEO / GEO / HEO regimes and serves as a static visualization baseline.

02

How we use it

Inbound submissions are used to respond to demo proposals, SBIR partnership outreach, investor diligence packets, and government-program introductions (SpaceWERX Orbital Prime, NASA SBIR, Space Force / SDA pipeline intelligence, IQT introductions). We follow up by email after we have read your message; we do not subscribe you to marketing lists and we do not share your message with anyone outside the immediate operating cell.

03

Contact-form routing

Contact-form submissions are posted to the in-app endpoint at /api/leads, which is implemented in routes/leads.js and writes to the leads table in our database. We do not use third-party form handlers: no Typeform, no JotForm, no Google Forms, no HubSpot forms, no Mailchimp embedded forms. Nothing on this site routes inbound messages through a third-party service.

We do not sell, rent, lease, or otherwise share submitted lead information with third parties. We do not enrich leads with third-party data brokers (Clearbit, Apollo, ZoomInfo, etc.). The leads table is internal to OrbitReclaim and Polsia.

04

Cookies & local storage

We use one first-party browser-storage value: localStorage['polsia_vid']. On your first visit, the page assigns a random UUID v4 to that key. Every subsequent visit reads the same UUID and pings the Polsia analytics beacon at polsia.com/api/beacon/pixel. This is a passive visitor-count pixel — it does not track you across sites, and we have no way to correlate the UUID with any other personal identifier because the key never leaves your browser except as the URL parameter v= on this site.

  • No authentication or session cookies — the site has no login.
  • No advertising cookies — there are no ads on the site.
  • No third-party analytics cookies — the only analytics is the Polsia pixel described above.
  • No cross-site tracking, fingerprinting, or device-graph construction.

Clearing your browser's site data or switching browsers resets the UUID. We treat the UUID as a low-sensitivity visitor counter, not as personal data.

05

Third-party services

The site uses a small, honest list of third-party services:

  • Polsia analytics beacon — a single-pixel request to polsia.com/api/beacon/pixel with a visitor UUID and the page-specific __POLSIA_SLUG__ slug. No JavaScript, no cookies set by the beacon, no personal data in the request.
  • Google Fonts — the Space Grotesk and DM Sans font files are loaded from fonts.googleapis.com. No personal data is sent; the request carries only the font URL and your IP, which Google uses to serve the file.
  • Cloudflare CDN (cdnjs) — the Three.js bundle for the swarm-vis landing-page hero is loaded from cdnjs.cloudflare.com. Same posture: no personal data is sent, only the asset URL.

That is the complete list. We do not run third-party analytics beyond the inline beacon above. We do not run Google Analytics, Meta Pixel, Hotjar, Mixpanel, Segment, Plausible, Fathom, or any comparable third-party analytics product.

06

Data retention

Submitted leads are retained until you request deletion or the inquiry is closed and forgotten. Public-dashboard synthetic data has no retention horizon; the seed catalog is regenerated only when intentionally reset. Local-storage UUIDs persist until you clear your browser's site data.

07

Your rights

You can request access, correction, or deletion of any personal data we hold by emailing orbitreclaim@polsia.com. We respond within two business days. Deletion requests are honored in full — we do not retain backups of deleted lead records beyond the standard database backup window (typically 30 days).

08

Children's privacy

The site is not directed at children under 13. We do not knowingly collect personal data from anyone under 13. If you believe we have inadvertently collected information from a child under 13, email orbitreclaim@polsia.com and we will delete it promptly.

09

Changes to this policy

We may update this policy from time to time. The effective date at the top of this page reflects the most recent revision. Material changes will be highlighted briefly on the home page for at least 30 days after they take effect.